DebuggingHardwareDetection
Differences between revisions 6 and 23 (spanning 17 versions)
|
Size: 1254
Comment: new template form
|
Size: 1690
Comment: Added ## comments how this article is obsolete
|
| 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)>> ## 20121020 https://launchpad.net/~penalvch This article is obsolete. Now that we are in the apport era, when one files an bug against the linux package via ubuntu-bug linux, a requirement as per https://wiki.ubuntu.com/Bugs/Responses#Missing_Apport_Information all of the information, the information requested in this article is filed: ## BootDmesg.txt ## CurrentDmesg.txt ## Lspci.txt ## Lsusb.txt ## As well as other helpful attachments: ## AlsaInfo.txt ## CRDA.txt ## Dependencies.txt ## IwConfig.txt ## ProcCpuinfo.txt ## ProcInterrupts.txt ## ProcModules.txt ## PulseList.txt ## UdevDb.txt ## UdevLog.txt ## WifiSyslog.txt ||<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 27: |
| When reporting a problem with hardware detection, include in file attach the following information: | 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 29: |
| * 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 `lspci -vvn > lspci-vvn.log` command * The output from the `lspci -vv > lscpi-vv.log` command * The output from the `dmesg > dmesg.log` command * The output of `cat /proc/version > proc_version.log` command |
Also, all reports should contain the following information. Please be sure to '''attach''' these files to the bug report. |
| Line 14: | Line 31: |
| = Debugging procedure = | * uname -a > uname-a.log * cat /proc/version_signature > proc_version_signature.log * sudo lspci -vvnn > lspci-vvnn.log (those are 2 v's not a w) * dmesg > dmesg.log |
| Line 16: | Line 36: |
| If the system is not correctly detecting a USB device, also '''attach''' the output of: | |
| Line 17: | Line 38: |
| = 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 39: | Line 41: |
| 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 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 (those are 2 v's not a w)
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)