DebuggingHardwareDetection

Differences between revisions 9 and 21 (spanning 12 versions)
⇤ ← Revision 9 as of 2007-08-01 22:51:59 →
Size: 1349
Editor: c-24-21-231-115
Comment: sudo lspci is slightly more informative
← Revision 21 as of 2008-08-06 17:01:16 → ⇥
Size: 1014
Editor: localhost
Comment:
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]]||

= Reporting a bug =

When reporting a problem with hardware detection, include in file attach the following information:

 * The make and model of the device (as much as you know)
 * The output from the `uname -a > uname-a.log` command
 * The output from the `sudo lspci -vvn > lspci-vvn.log` command
 * The output from the `sudo lspci -vv > lspci-vv.log` command
 * The output from the `dmesg > dmesg.log` command
 * The output of `cat /proc/version > proc_version.log` command
 * The output of `cat /proc/version_signature > proc_version_signature.log` command		 <<Include(Debugging/Header)>>
||<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 18: Line 7:
= Known bugs = = Reporting a bug =
Line 20: Line 9:
Description of known issues, how to recognise them and stock responses/actions. 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 22: Line 11:
'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||		 Also, all reports should contain the following information. Please be sure to '''attach''' these files to the bug report.
Line 26: Line 13:
'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||		  * uname -a > uname-a.log
 * cat /proc/version_signature > proc_version_signature.log
 * sudo lspci -vvnn > lspci-vvnn.log
 * dmesg > dmesg.log
Line 30: Line 18:
= Non-bugs = If the system is not correctly detecting a USB device, also '''attach''' the output of:
Line 32: Line 20:
TBD.

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

 * DebuggingProcedures		  * lsusb > lsusb.log
Line 40: Line 23:
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 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

CategoryBugSquad CategoryDebugging

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