Troubleshooting
|
Size: 1651
Comment:
|
Size: 3088
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 2: | Line 2: |
| #start | |
| Line 5: | Line 4: |
| === Common Problems === * [[X/Bugs]] - Analysis of collection of similar bugs * [[X/Bugs/Transitions]] - Explanation for "installing xserver-xorg-core would break existing software" * [[X/i8xxUnsupported]] - Explanation of why i845, i855, i865, etc. chips aren't supported * [[X/HybridGraphics]] - How to make the most of your system with hybrid graphics * [[X/CommonErrors]] * [[X/ErrorMessages]] * [[Bugs/AtiDriver]] |
|
| Line 13: | Line 20: |
| * [[X/Troubleshooting/FglrxInteferesWithRadeonDriver|Switching between -fglrx and -ati drivers]] * [[X/Troubleshooting/NvidiaDriverSwitching|Switching between -nvidia and -nouveau drivers]] |
|
| Line 21: | Line 26: |
| Line 24: | Line 28: |
| == Troubleshooting Kernel Modesetting Issues == The {{{drm.debug=0x04}}} kernel option can be used to get additional debugging data included in your {{{dmesg}}} output. |
=== Troubleshooting Techniques === * [[X/Backtracing|X Backtracing]] - How to collect a backtrace for an X crash * [[X/Bisecting]] - Using bisection techniques to solve regressions or backport fixes * [[X/Testing/Touch]] - Touchscreen and multi-touch testing * [[X/Quirks|X Quirks]] - Fixes for some common hardware-specific issues * [[X/FixingCrashes|X Crash Fixing]] - How to fix X crashes * [[X/InterpretingIntelGpuDump]] - Ringbuffers, batchbuffers, and the meaning of `intel_gpu_dump` output * [[X/DebuggingWithValgrind]] * [[X/NonGraphicalBoot]] - Running X manually, without gdm * [[X/Debugging/WirelessWithoutX|Wireless Without X]] - How to get a wireless network connection without X. * [[X/Debugging/WiredWithoutRouter|Direct Wired Without WAP]] - How to connect two laptops with direct ethernet cord. * [[https://help.ubuntu.com/community/BootOptions|BootOptions]] * [[http://wiki.cchtml.com/index.php/Ubuntu_Feisty_Installation_Guide|fglrx installation on Ubuntu]] * DebuggingUsplash * [[X/Dev/DeviceTreeHWDetection]] * [[X/Troubleshooting/FglrxInteferesWithRadeonDriver|Switching between -fglrx and -ati drivers]] * [[X/Troubleshooting/NvidiaDriverSwitching|Switching between -nvidia and -nouveau drivers]] * The {{{drm.debug=0x04}}} kernel option can be used to get additional debugging data included in your {{{dmesg}}} output. |
Common Problems
X/Bugs - Analysis of collection of similar bugs
X/Bugs/Transitions - Explanation for "installing xserver-xorg-core would break existing software"
X/i8xxUnsupported - Explanation of why i845, i855, i865, etc. chips aren't supported
X/HybridGraphics - How to make the most of your system with hybrid graphics
Troubleshooting Techniques
X Backtracing - How to collect a backtrace for an X crash
X/Bisecting - Using bisection techniques to solve regressions or backport fixes
X/Testing/Touch - Touchscreen and multi-touch testing
X Quirks - Fixes for some common hardware-specific issues
X Crash Fixing - How to fix X crashes
X/InterpretingIntelGpuDump - Ringbuffers, batchbuffers, and the meaning of intel_gpu_dump output
X/NonGraphicalBoot - Running X manually, without gdm
Wireless Without X - How to get a wireless network connection without X.
Direct Wired Without WAP - How to connect two laptops with direct ethernet cord.
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)