Troubleshooting
Differences between revisions 43 and 45 (spanning 2 versions)
1285
Comment:
|
1561
|
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 20: | Line 21: |
== 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.
X/Troubleshooting (last edited 2017-11-18 18:25:00 by penalvch)