Description of problem:
I boot on init 3 mode and when i launch startx command, Xorg and my keyboard
freeze (black screen).
I have no problem in my Xorg.0.log and I have ATI X800 Xl graphic card
I have never had problems with FC4 (with fglrx or vesa driver).
Steps to Reproduce:
1. boot on init 3 mode
2. launch startx command
Motherboard = ASUS A8N-SLI DELUXE
Created attachment 126771 [details]
Created attachment 126772 [details]
Xorg configuration file
unam -a :
Linux xblade 2.6.15-1.2054_FC5 #1 SMP Tue Mar 14 15:48:20 EST 2006 x86_64 x86_64
If I launch startx in vga mode :
[pti-seb@xblade yum.repos.d]$ startx -- -depth 16
xauth: creating new authority file /home/pti-seb/.serverauth.2871
X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.9-22.18.bz155725.ELsmp x86_64Red Hat, Inc.
Current Operating System: Linux xblade 2.6.15-1.1833_FC4 #1 Wed Mar 1 23:41:25
EST 2006 x86_64
Build Date: 15 March 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Sun Mar 26 18:11:20 2006
(==) Using config file: "/etc/X11/xorg.conf"
Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
(EE) VGA(0): Given depth (16) is not supported by this driver.
(EE) Screen(s) found, but none have a usable configuration.
Fatal server error:
no screens found
XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 0 requests (0 known processed) with 0 events remaining.
[pti-seb@xblade yum.repos.d]$ exit
If I use radeon driver, Xorg start correctly, but driver rejects any resolutions
higher than 640x480. But this is an another bug (cf.
However, the vesa mode does'nt work with my graphic card and I think is not normal.
When attaching config files, log files and other text files to bugzilla,
always be sure to attach them as MIME type "text/plain" to ensure that they
are viewable directly in the web browser when clicking on them. This
reduces the time required to view the attachments, which speeds up the
process of diagnosis and resolution.
The "vesa" driver should not be used for this chip, as the "radeon" driver
contains support for this hardware.
The log file attached in comment #1 is from using the "vesa" driver, and
shows an X server that has started up correctly. There are no indications
of a crash or other failure present in the log.
The "vga" driver is not expected to work in any useful manner on any
hardware. It only supports strict Standard VGA resolution, which is
limited to 640x480 16 colours (not 16000 colours), or 320x200 256 colours,
which is more or less useless on a modern desktop. We provide the "vga"
driver only for diagnostic purposes and completeness, however it is not
You have indicated that you have tried using the fglrx driver on this
system in the initial report. There are known problems that are caused
by the installation of 3rd party proprietary drivers, which can cause
malfunctions to occur afterward even if you are no longer using the
proprietary driver and are using the open source drivers supplied with
To ensure that your system is running in a supported configuration,
please completely uninstall all proprietary drivers from your system,
and reinstall all of the xorg and mesa packages as supplied by Fedora Core 5,
and fully update to the latest official FC5 updates. Configure your
system to use the "radeon" driver, which is the officially supported
driver for this hardware.
This bug was filed against the "vesa" driver, however there is insufficient
information present to diagnose. If you would like the "vesa" driver
problem that you encountered to be investigated as well, please file
a bug report in X.Org bugzilla at: http://bugs.freedesktop.org in the
"xorg" component, and attach your X server log and config from using the
"vesa" driver with no proprietary drivers installed, and X.Org developers
We will track the "radeon" driver problem you've mentioned in the other
report you've referenced.
Thanks in advance.