DebuggingHardwareDetection

Differences between revisions 16 and 18 (spanning 2 versions)
⇤ ← Revision 16 as of 2007-11-25 02:26:56 →
Size: 1143
Editor: ibc-74-218-61-45
Comment:
← Revision 18 as of 2008-05-31 00:05:35 → ⇥
Size: 1038
Editor: c-24-21-206-172
Comment: update kernel package information
Deletions are marked like this. Additions are marked like this.
Line 8: Line 8:
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 When reporting a problem with hardware detection, you should report the bug against the kernel. Beginning with the Hardy release, all kernel bugs should be reported against the '''linux''' kernel source package.

Debugging procedure

Reporting a bug

When reporting a problem with hardware detection, you should report the bug against the kernel. Beginning with the Hardy release, all kernel bugs should be reported against the linux kernel source package.

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:

CategoryBugSquad

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