Red Hat Bugzilla – Bug 174074
Firstboot setup display problem
Last modified: 2007-11-30 17:11:17 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.Install Fedora Core 5 test 1
2.Boot for 1st time since install
3.Guided setup is impossible because only a quater of screen is visible
4.Second boot also brought this automated config up...
A quater of the screen is blown up so that I can't continue (ctrl+alt+backspace
to exit) because most of the screen and options are not visible. See url
http://helsinki.LA/IMG_4733.JPG (also attached to this report).
To be able to setup initial system configuration.
I have a matrox millenium 2megabyte PCI videocard. Asus A7N8X-X motherboard with
AMD duron 1,8Ghz processor. 512megabytes RAM. Display is Sony G520 CRT.
Created attachment 121443 [details]
Picture of screen resolution problem.
This seems to work ok with my other videocard, is it just time to retire my
Matrox Millenium board at this time?
What are the results if you run /usr/sbin/ddcprobe as root?
It seems that the firstboot is ok if you just press ctrl+alt+f1 to go to text
mode and then switch back to X with ctrl+alt+f8 (after this everything is
visible as should be).
I don't know what happened with the command you suggested [/usr/sbin/ddcprobe],
my monitor went out of scan range. My monitor also goes out of scan range
temporarily when the fedora X installing system first boots (I don't think this
happens with the FC4 release version).
Can you please attach /tmp/XConfig.test and /tmp/X.log to this bug report?
These two files should be written out by firstboot and I don't think they get
cleaned up so they should still be around.
Created attachment 122612 [details]
Maby this is what you asked for
Unfortunately I was unable to find the files in /tmp so I attached the only file
that seemed even close in /var/log/
Try a text mode installation, and then do a system update to the latest
packages with yum. Once you're fully updated, run:
Then examine /etc/X11/xorg.conf and if it is not configured to use the
"mga" driver, change it to that, and try to start X. Update the report
with the results you obtain, and attach the X server log file from
/var/log, and the config file as individual uncompressed file attachments,
and we'll continue diagnosing the problem.
Thanks in advance.
I didn't see any of these problems with FC5test2. Would you sitll like to have
this information about test1?
(In reply to comment #9)
> I didn't see any of these problems with FC5test2. Would you sitll like to have
> this information about test1?
Ah, cool. Naw, if it's not happening in FC5test2, then that's a good
indication the problem got fixed along the way. I'll close this as
fixed in "RAWHIDE" for now, but if the problem recurs, please reopen
it and we'll look at it again.
Thanks for the update.