DebuggingHardwareDetection
Size: 456
Comment: [Update] The info attach in file separrate (Pliss my english is bad, You revise
|
Size: 1254
Comment: new template form
|
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]]|| = Reporting a bug = |
|
Line 9: | Line 13: |
= Debugging procedure = = 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 ---- CategoryBugSquad |
ContentsBRTableOfContents |
Reporting a bug
When reporting a problem with hardware detection, include in file attach the following information:
- 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
Debugging procedure
Known bugs
Description of known issues, how to recognise them and stock responses/actions.
Open
Bug# |
Description |
Action |
TBD. |
TBD. |
TBD. |
Closed
Bug# |
Description |
Action |
TBD. |
TBD. |
TBD. |
Non-bugs
TBD.
Also see:
DebuggingHardwareDetection (last edited 2012-10-21 04:10:21 by penalvch)