Troubleshooting

Differences between revisions 43 and 46 (spanning 3 versions)
⇤ ← Revision 43 as of 2009-12-17 17:46:19 →
Size: 1285
Editor: ip24-255-18-229
Comment:
← Revision 46 as of 2012-04-13 21:32:36 → ⇥
Size: 1619
Editor: static-50-53-79-63
Comment:
Deletions are marked like this. Additions are marked like this.
Line 11: Line 11:
 * [[X/Troubleshooting/FglrxInteferesWithRadeonDriver|fglrx interferes with radeon driver]]  * [[X/Troubleshooting/FglrxInteferesWithRadeonDriver|Switching between -fglrx and -ati drivers]]
 * [[X/Troubleshooting/NvidiaDriverSwitching|Switching between -nvidia and -nouveau drivers]]
Line 16: Line 17:
 * [[X/Troubleshooting/NvidiaDriverMissingKernelDriver]]
Line 20: Line 22:
== Troubleshooting Kernel Modesetting Issues ==

The {{{drm.debug=0x04}}} kernel option can be used to get additional debugging data included in your {{{dmesg}}} output.

For hard bugs the analysis phase is the most important, and most challenging part of bug work. Depending on how the bug is behaving, there are multiple directions to investigate the issue. Here's some different approaches:

Troubleshooting Kernel Modesetting Issues

The drm.debug=0x04 kernel option can be used to get additional debugging data included in your dmesg output.

CategoryDebugging

X/Troubleshooting (last edited 2017-11-18 18:25:00 by penalvch)