Red Hat Bugzilla – Bug 243822
Install process sets max graphical resolution
Last modified: 2008-08-02 19:40:34 EDT
Description of problem:
Anaconda sets maximum graphical resolution by default. As this is the max
capability of the CARD, it can often exceed the max resolution of the MONITOR
attached to it.
Version-Release number of selected component (if applicable):
Has occurred on every FC6 and F7 installation I have attempted on 3 different
Steps to Reproduce:
1. Install Fedora in graphical mode.
2. Hope your monitor matches or exceeds your graphics card, or else you get a
nice black screen at some point during the install process.
3. Restart in rescue mode and find the conf file with the relevant data, and
manually adjust the max resolution.
- P2/400 with 8mb nVidia card (system purchased in 1998), default resolution
comes up as 1600x1200, 32bit color, 75Hz. Unbelievably, the monitor I purchased
with the system in 1998 happens to be able to display that resolution, so I was
able to verify exactly.
- P4/2.8gHz with 512mb nVidia card, default resolution comes up as 2500x1900 or
something, 32 bit color, 125Hz -- far exceeding any monitor I have.
Anyone heard of 1024x768? Works great for most install processes, and then you
can adjust settings to what you desire after the process is complete.
You can get around this by forcing Anaconda to use a specific resolution, but
once it gets to the GNOME, etc. desktop, it reverts to max resolution again.
You need to restart in rescue mode and locate the proper X11.conf file (I don't
remember filename offhand) and manually edit the section to force a lower max
That's not even close to accurate. Anaconda starts up at 800x600, and that's
the default setting for X if it can't determine what your monitor supports.
Please attach the X log from the misbehaving configuration, so we can see what's
actually going wrong.
Reporter, could you please reply to the previous question? If you won't reply in
one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.