Red Hat Bugzilla – Bug 203570
Starting X brings up a blank screen
Last modified: 2007-11-30 17:11:41 EST
Description of problem: I installed the nightly rawhide tree on Aug. 21. X
worked fine with anaconda. After rebooting, firstboot came up just fine as
well, so X was working there. After firstboot, gdm failed to start. Machine
has a Matrox G400 and is connected via a KVM, although this setup has worked
before on previous releases.
I dropped to runlevel 3 and ran "/usr/X11R6/bin/X". I could see the monitor
status light blink like it normally does when starting X. Then the screen
turned blank. No graphics, no pointer, nothing. I went back to the virtual
console that I ran "X" from but did not see any error messages. Nothing in the
X logs looks suspicious to me.
However, the xorg.conf file looks suspiciously small to me, and it lacks any
resolution modes or module information. Maybe firstboot just mangled the config
file? I'm attaching the X log and the xorg.conf file.
Version-Release number of selected component (if applicable):
How reproducible: every time on my test machine
Created attachment 134639 [details]
xorg config file
Created attachment 134640 [details]
Created attachment 134641 [details]
updated X log
Another data point: When I specify the "vesa" driver, X will start. So maybe
the problem is specific to the mga driver.
Do you happen to have an X log from starting the machine with an older version
of X? Say, FC5.
I don't have an old log handy. I can reinstall the box with FC5 if necessary.
Just let me know.
(In reply to comment #6)
> I don't have an old log handy. I can reinstall the box with FC5 if necessary.
> Just let me know.
That would be helpful.
Most likely the same than bug 197033 (X doesn't work anymore with Matrox G400).
I'm affected, too. My work-around is to downgrade to the driver
from FC5 (xorg-x11-drv-mga-18.104.22.168-1.2).
> I'm affected, too.
I have an MGA G200 and have it up an running. I did have out of range errors
with the xorg.conf file that worked fine for FC5 version. See bug 207804
X -configure followed by changing the vertical refresh rate from *190* Hz to 70
Hz does not cause out of range errors for games now.
Created attachment 137839 [details]
[mschwendt] X log with xorg-x11-drv-mga-22.214.171.124-1.2
Created attachment 137840 [details]
[mschwendt] X log with xorg-x11-drv-mga-1.4.1-5.fc6
Created attachment 137893 [details]
Log on recently installed system.
This is with no xorg.conf file at all. I am using xorg-x11-drv-mga-1.4.1-5.fc6
*** Bug 197033 has been marked as a duplicate of this bug. ***
As suggested by Alexei Podtelezhnikov, I've tried reducing the
800x600, true-colour : works
1024x768, true-colour : works
1152x768, true-colour : works
1280x960, true-colour : -FAILS-
1280x1024, true-colour: -FAILS- (*)
(*) is the resolution I've used for a very long time and which works
flawlessly with FC5 and older!
s/true-colour/Thousands of Colors/
is what system-config-display says about the colour resolution,
and it's right (I mixed that up with a different machine, seems
s-c-d uses the "Millions of Colors" there).
Historically, I learned about videoram in bug 25920. I hope there is an option
for the new driver to disable some advanced feature that eats up to much
videoram. We do want old 16Mb hardware to work.
Created attachment 138374 [details]
Today's (20061012) rawhide. Stock xorg.conf. Panel says display is using
Hsync of 82.4kHz, Vref of 103Hz which is out of range, and out of the detected
# Xorg configuration created by pyxf86config
Identifier "Default Layout"
Screen 0 "Screen0" 0 0
InputDevice "Keyboard0" "CoreKeyboard"
Option "XkbModel" "pc105"
Option "XkbLayout" "us"
Viewport 0 0
I rebuilt xorg-x11-drv-mga with version 1.4.2 and it works for me.
With xorg-x11-drv-mga 1.4.2 => it works for me.
Where is this version at? I checked development and updates-testing. Neither is
up to 1.4.2.
> Where is this version at?
At x.org :
rpm (with no warranty) : http://feliciano.matias.free.fr/xorg-x11-drv-mga/
$ rpm -q xorg-x11-drv-mga
works for me, too.
And 1.4.2 is from Sep 18th, it seems.
Thanks for the link to the driver sources. Especially thanks for the binary rpm
rpm itself is acting up for me, so I'll test later, after getting it to install.
Created attachment 138483 [details]
Log when checking effects of resolution changes.
The screens are not working as desired. They do not cause the display to go out
of range as was the case previously
Created attachment 138484 [details]
Log after running system-config-display --reconfig
100 percent better response with this compilation for the driver. This means it
is possible to fix.
As a note, I changed to the mga only instead of dual head.
Works for me too!
Perhaps bug #207804 is related to this one.
*** Bug 207804 has been marked as a duplicate of this bug. ***
As noted, the problem is corrected by the better version of the driver. As
above, I closed as duplicate of this bug. Thanks!
Possible dupe of this bug I filed upstream against the mga driver:
Would be good to get this fixed for FC6
The reference to out of range for Horizontal matches the problem that I was
experiencing. The vertical max range was also out of bounds. MGA G200 also in
Supposing that the xorg-x11-drv-mga-1.4.2-1.fc6 will be included when FC6 is
finalized, this bug seems to be resolved though the status is still new.
xorg-x11-drv-mga-1.4.2-1.fc6 from rawhide works when I change resolutions to
lower settings. Changing to lower settings did cause out of range with the
Thanks for the fix.
Brent, could you confirm that xorg-x11-drv-mga-1.4.2-1.fc6 does indeed fix the
issue and close this bug if so. Thanks, Kristian
Same problem with ATI 9600 M10. Solved problem by downloading ati-prop driver
and installing it. The x11 config was blank as described . Ran aticonfig
--initial and it made a new x11 config file.
NEEDINFO as per comment #33. Did 1.4.2 work any better? Does F7 exhibit the
Reporter, could you please reply to the previous question? If you won't reply in
two weeks, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
No information requested was provided, so I close this bug as INSUFFICIENT_DATA.
Reporter, if you could, please, reopen with additional information.