DebuggingHardwareDetection

Differences between revisions 16 and 24 (spanning 8 versions)
Revision 16 as of 2007-11-25 02:26:56
Size: 1143
Editor: ibc-74-218-61-45
Comment:
Revision 24 as of 2012-10-21 04:10:21
Size: 1201
Editor: penalvch
Comment: 1) lsusb -> lsusb -v. 2) RM'd request for lspci -vvnn, dmesg, and cat proc/version_signature as redudant. See ## wiki comments.
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| <<Include(Debugging/Header)>>

## 20121021 https://launchpad.net/~penalvch Now that we are in the apport era, when one files a bug using it against the linux package via ubuntu-bug linux, a requirement as per https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information , the following attachments (that requesting is redundant) are automatically attached to the bug report:
## BootDmesg.txt -> dmesg, gives very similar info as uname -a, and gives exactly same as cat
## CurrentDmesg.txt -> dmesg
## Lspci.txt -> lspci ---vvnn

||<tablestyle="float:right; font-size: 0.9em; width:30%; background:#F1F1ED; background-image: url('https://librarian.launchpad.net/1812570/bugsquad.png'); background-repeat: no-repeat; background-position: 98% 0.5ex; margin: 0 0 1em 1em; padding: 0.5em;"><<TableOfContents>>||
Line 5: Line 12:
== Reporting a bug ==
Line 6: Line 14:
= Reporting a bug =

When reporting a problem with hardware detection, you should report the bug against the appropriate linux-source-2.6.xx package. For example, the correct package in Malone for Dapper is linux-source-2.6.15, for Edgy is linux-source-2.6.17, for Feisty it is linux-source-2.6.20, and for Gutsy it is linux-source-2.6.22

Also, all reports should contain the following information. Please be sure to '''attach''' these files to the bug report.

 * uname -a > uname-a.log
 * cat /proc/version_signature > proc_version_signature.log
 * sudo lspci -vvnn > lspci-vvnn.log
 * dmesg > dmesg.log

If the system is not correctly detecting a USB device, also '''attach''' the output of:

 * lsusb > lsusb.log

------
'''Also see:'''

 * DebuggingProcedures
 * When reporting a problem with hardware detection, you should report the bug against the [[https://launchpad.net/ubuntu/+source/linux|linux]] kernel package.
 * If the system is not correctly detecting a USB device, also '''attach''' the output of:
  * lsusb -v > lsusb-v.log
Line 27: Line 19:
CategoryBugSquad CategoryBugSquad CategoryDebugging

Debugging Central

This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages.

Debugging procedure

Reporting a bug

  • When reporting a problem with hardware detection, you should report the bug against the linux kernel package.

  • If the system is not correctly detecting a USB device, also attach the output of:

    • lsusb -v > lsusb-v.log


CategoryBugSquad CategoryDebugging

DebuggingHardwareDetection (last edited 2012-10-21 04:10:21 by penalvch)