DebuggingHardwareDetection

Differences between revisions 22 and 23
⇤ ← Revision 22 as of 2008-09-18 04:36:45 →
Size: 1040
Editor: c-24-21-234-111
Comment:
← 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 2: Line 2:

## 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
Line 5: Line 24:

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)