How to debug Xorg problems
From FedoraProject
(→General bug reports) |
m (→KMS problems (most Intel and AMD/Radeon hardware)) |
||
| Line 22: | Line 22: | ||
Additionally, please add nomodeset to the kernel command line and try to reproduce the problem, and include the following information : | Additionally, please add nomodeset to the kernel command line and try to reproduce the problem, and include the following information : | ||
* if you were able to reproduce the problem or not | * if you were able to reproduce the problem or not | ||
| − | * X server log file(s) {{filename|/var/log/Xorg.*.log}} | + | * X server log file(s) {{filename|/var/log/Xorg.*.log}} (these are different in KMS and non-KMS mode, we may need both) |
to your bug report as well. | to your bug report as well. | ||
Revision as of 21:00, 25 June 2009
Foreword
If you are experiencing a problem with Xorg, please see the Fedora 11 common bugs document before filing a bug. Some easy configuration tweaks that fix a wide range of issues are listed there. If the problem you are seeing is not listed there or none of the workarounds seem to help, please consider filing a bug to help us make Fedora run better on your hardware. Be prepared to include some information (logs) about your system as well.
Contents |
General bug reports
The following would be useful to attach to your bug report (full log file, no archive, uncompressed, with MIME type set as text/plain):
- all of the X server log file(s)
/var/log/Xorg.*.log - if you use a xorg.conf, please include it in the bug report, otherwise, please specify in the bug report that it does not.
-
/var/log/Xorg.0.logfrom a trial run where you move/etc/X11/xorg.confaside and let Xorg autodetect your hardware (if you have such a file).
Rendering problems (fonts, garbaged text...)
All of the above, with a screenshot showing the problem if at all possible.
KMS problems (most Intel and AMD/Radeon hardware)
Please add drm.debug=1 to the kernel command line, reboot and attach /var/log/messages to your bug report.
Additionally, please add nomodeset to the kernel command line and try to reproduce the problem, and include the following information :
- if you were able to reproduce the problem or not
- X server log file(s)
/var/log/Xorg.*.log(these are different in KMS and non-KMS mode, we may need both)
to your bug report as well.
You can follow the instructions listed on the Xorg/KMS page to edit the kernel command line.
OpenGL / Mesa problems
- the output of glxinfo
- a screenshot of the problem
- whether other OpenGL applications are able to run without problems
Creating a xorg.conf
If you need to make manual changes to X configuration, you will need to create a xorg.conf file.
Stack traces
See the documentation on the upstream wiki.