Red Hat Bugzilla – Bug 439053
X fails to start when installing
Last modified: 2009-07-14 13:28:03 EDT
Description of problem:
Fedora 9 Beta - installation from DVD.
Display goes blank and the LED on the display blinks repeatedly indicating that
Xorg is trying to feed the display invalid resolution.
Version-Release number of selected component (if applicable):
Fedora 9 Beta
Steps to Reproduce:
1. Boot from install DVD - choose all defaults
2. Anaconda attempts to start graphical installer
1. Display goes blank
2. Endless unsuccessful tries to start Xorg - no fall back to text mode install
or low resolution mode even in 2008 :)
1. Successful graphical installation
Nvidia 8800GT card, Apple Cinema Display 20"
I have got the similar problems, could you download on USB drive from the
console (Ctrl+Alt+F2) whole content of /tmp?
Created attachment 299359 [details]
Contents of /tmp
I think what is happening is that Anaconda is forcing the nv driver to use a
800x600 mode which my monitor rejects as invalid.
IMHO the solution would be - newer xorg-nv driver does a good job of auto
detecting the right resolution and should be allowed to do so first. In case
that fails then a forced "known-good for that monitor" resolution be attempted.
Ubuntu does this and I get a much better resolution inside of the graphical
installer on the same hardware.
Created attachment 299533 [details]
anaconda.log from the attachment 299359 [details]
Created attachment 299534 [details]
syslog from the attachment 299359 [details]
Created attachment 299535 [details]
XConfig.test from the attachment 299359 [details]
Created attachment 299536 [details]
X.log from the attachment 299359 [details]
I am suspecting this bug should be against anaconda or whatever that is generating the XConfig.test and
not xorg-nv which is simply doing what it is told to do?
Sampe problem with F9 Preview. Also it happened on a Mac Mini w/Intel GMA950
in addition to my desktop with nVidia card. So this seems to be not related to
Why on earth is automagic mode setting not working and why is anaconda forcing
800x600 resolution? This will impact all monitors which do not support 800x600
or the modeline that Anaconda is using.
Changing version to '9' as part of upcoming Fedora 9 GA.
More information and reason for this action is here:
I am not sure of the relevance of this information to your reported case, but
I'll cite it as a possible diagnostic or workaround aid since it may have some
similar root causes. I'll file this as its own bug report additionally since my
8800GT/NV problem wasn't detected in the installer, but on an installed system.
I installed Fedora 9 with no video related problems on a system with
8800GT-512MB card, and an old 15" LCD monitor whose maximum capability is
1024x768 and analog VGA input.
Once the system was installed and updated fully online I relocated it to my desk
with a 24" DELL 2405FPW LCD connected via a DVI-to-VGA adapter which is
connected to the uppermost DVI/VGA port (near the card bracket screw) position.
I have been unable to get X started with the nv driver at any resolution I've
tried, including various lower resolutions like 1024x768. I just get a black
screen when I "init 5".
e.g. these did not help even when I did a cycle of init 3 / init 5 to restart X.
When I did this:
to switch /etc/X11/xorg.conf to the vesa driver instead of the nv driver, I am
able to "init 5" and use the default gdm + gnome + graphical environment.
I am now posting in 1600x1200xMillions of colors with the Vesa driver selected
on the same 8800GT and with the same DVI -> DVI to VGA -> DELL 2405FPW connected
as fails to work with the nv driver.
Exact same problem with recently released RHEL 5.2 x86_64 .
This message is a reminder that Fedora 9 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 9. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '9'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 9's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 9 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 9 changed to end-of-life (EOL) status on 2009-07-10. Fedora 9 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.