From Fedora Project Wiki
(add necessary log collecting information for xorg-x11-drv-{intel,ati} with KMS) |
(add create xorg.conf link) |
||
| Line 15: | Line 15: | ||
* X server log file(s) {{filename|/var/log/Xorg.*.log}} | * X server log file(s) {{filename|/var/log/Xorg.*.log}} | ||
to your bug report as well. | to your bug report as well. | ||
== Creating a xorg.conf == | |||
If you need to make manual changes to X configuration for any reason, you will first need to [[How_to_create_xorg.conf|create a xorg.conf]] file. | |||
== Stack traces == | == Stack traces == | ||
See the [http://wiki.x.org/wiki/Development/Documentation/ServerDebugging documentation] on the upstream wiki. | See the [http://wiki.x.org/wiki/Development/Documentation/ServerDebugging documentation] on the upstream wiki. | ||
Revision as of 21:56, 22 June 2009
General bug reports
If you are experiencing a problem with Xorg, the following would be useful to attach to your bug report (individually, uncompressed, with MIME type set as text/plain):
/etc/X11/xorg.conf(or, if this file does not exist, specify in the bug report that it does not)- X server log file(s)
/var/log/Xorg.*.log /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).
KMS problems (most Intel and AMD/Radeon hardware)
Please add drm.debug=1 to the kernel command line (in /etc/grub.conf), 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
to your bug report as well.
Creating a xorg.conf
If you need to make manual changes to X configuration for any reason, you will first need to create a xorg.conf file.
Stack traces
See the documentation on the upstream wiki.