DebuggingHardwareDetection

Differences between revisions 14 and 21 (spanning 7 versions)
Revision 14 as of 2007-09-17 09:48:48
Size: 1453
Editor: 82-69-40-219
Comment: live CD
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]]|| <<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>>||

= Debugging procedure =
Line 5: Line 9:
When reporting a problem with hardware detection, please paste this text below into a terminal and press Enter. Make sure that it is all on a single line. Unless you are running from the live CD, you will be asked for your password. 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 7: Line 11:
 uname -a > uname-a.log; sudo lspci -vvnn > lspci-vvnn.log; sudo lspci -vv > lspci-vv.log; dmesg > dmesg.log; cat /proc/version > proc_version.log; cat /proc/version_signature > proc_version_signature.log Also, all reports should contain the following information. Please be sure to '''attach''' these files to the bug report.
Line 9: Line 13:
This will place the files ''uname-a.log'', ''lspci-vvnn.log'', ''lspci-vv.log'', ''dmesg.log'', ''proc_version.log'' and ''proc_version_signature.log'' in your home directory, please add them to your bug report.  * uname -a > uname-a.log
 * cat /proc/version_signature > proc_version_signature.log
 * sudo lspci -vvnn > lspci-vvnn.log
 * dmesg > dmesg.log
Line 11: Line 18:
= Debugging procedure = If the system is not correctly detecting a USB device, also '''attach''' the output of:
Line 13: Line 20:
= Known bugs =

Description of known issues, how to recognise them and stock responses/actions.

'''Open'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

'''Closed'''
||<rowbgcolor="#eeeeee"> '''Bug#''' || '''Description''' || '''Action''' ||
|| TBD. || TBD. || TBD. ||

= Non-bugs =

TBD.

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

 * DebuggingProcedures
 * lsusb > lsusb.log
Line 35: 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)