DebuggingHardwareDetection

Differences between revisions 17 and 23 (spanning 6 versions)
⇤ ← Revision 17 as of 2008-03-19 15:42:40 →
Size: 1177
Editor: 59
Comment: just added Hardy
← Revision 23 as of 2012-10-21 00:37:15 → ⇥
Size: 1690
Editor: penalvch
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>>||
Line 5: Line 25:
Line 8: Line 27:
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 14: Line 33:
 * sudo lspci -vvnn > lspci-vvnn.log  * sudo lspci -vvnn > lspci-vvnn.log (those are 2 v's not a w)
Line 21: Line 40:
------
'''Also see:'''

 * DebuggingProcedures
Line 27: Line 41:
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 (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

CategoryBugSquad CategoryDebugging

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