Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 228646 - Default resolution doesn't work. Boot goes to a blank screen after install.
Default resolution doesn't work. Boot goes to a blank screen after install.
Product: Fedora
Classification: Fedora
Component: pyxf86config (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Adam Jackson
Depends On:
  Show dependency treegraph
Reported: 2007-02-14 00:30 EST by Greg Martyn
Modified: 2008-08-02 19:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-05-26 15:09:10 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Greg Martyn 2007-02-14 00:30:29 EST
Description of problem:
After install, I get a "Refresh rate out of range" error from my monitor. If I
do the Ctrl+Alt+Backspace several times, I can get to a console and run
system-config-display to fix the problem, but a newbie wouldn't know to do that.

Version-Release number of selected component (if applicable):
Whatever ships on the DVD

How reproducible:

Steps to Reproduce:
1. Install Fedora Core
2. Remove installation media
3. Boot for the 1st time. Screen shows the usual text messages but then goes
blank with the rate out of range message on my monitor.
Actual results:
xorg.conf is missing the Modes line which system-config-display puts in. A
non-working mode must've been automatically chosen.

Expected results:
User should verify that higher resolutions work before they are used.

Additional info:
Comment 1 Adam Jackson 2007-02-19 13:43:43 EST
Please attach the /var/log/Xorg.0.log from the misbehaving configuration.
Comment 2 Adam Jackson 2007-05-26 15:09:10 EDT
Mass closure: This bug has been in NEEDINFO for over six weeks with no
additional information provided, and is therefore being closed.  If this bug is
still an issue for you, please supply the requested information, and reopen the bug.

Note You need to log in before you can comment on or make changes to this bug.