DebuggingHardwareDetection
Differences between revisions 17 and 19 (spanning 2 versions)
|
Size: 1177
Comment: just added Hardy
|
Size: 1034
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(Debugging/Header)]] | |
| Line 8: | Line 9: |
| 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, for Gutsy it is linux-source-2.6.22 and for Hardy its linux-source-2.6.24 | 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. |
| Line 21: | Line 22: |
| ------ '''Also see:''' * DebuggingProcedures |
|
| Line 27: | Line 23: |
| CategoryBugSquad | CategoryBugSquad CategoryDebugging |
ContentsBRTableOfContents |
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
DebuggingHardwareDetection (last edited 2012-10-21 04:10:21 by penalvch)