DebuggingHardwareDetection
Differences between revisions 12 and 24 (spanning 12 versions)
|
Size: 1366
Comment: ridiculous use of pipes
|
← Revision 24 as of 2012-10-21 04:10:21 ⇥
Size: 1201
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)>> |
| Line 3: | Line 3: |
| = Reporting a bug = | ## 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 |
| Line 5: | Line 8: |
| When reporting a problem with hardware detection, please paste this text below into a terminal and run, you will be asked for your sudo password. 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 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. |
||<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 13: | Line 12: |
| = Known bugs = | == Reporting a bug == |
| Line 15: | Line 14: |
| 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 |
* 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 35: | Line 19: |
| CategoryBugSquad | CategoryBugSquad CategoryDebugging |
This page is part of the debugging series — pages with debugging details for a variety of Ubuntu packages. |
Contents |
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
DebuggingHardwareDetection (last edited 2012-10-21 04:10:21 by penalvch)