Description of problem: With Fedora 14 Final TC1.1, I get a blank screen when entering stage 2 on the DVD. To make things weird, the KDE LiveCD works just fine. The blank screen persists when changing to another tty, but the system doesn't freeze. With sshd and networking enabled I can login remotely just fine. Version-Release number of selected component (if applicable): Fedora 14 Final TC1.1 i386 DVD How reproducible: Always Steps to Reproduce: 1. boot install dvd 2. wait for stage2 to start 3. experience blank screen Actual results: blank screen Expected results: graphical stage2 Additional info: Graphics card is an ATI HD 5850. When I add the nomodeset option my monitor says the input is out of range and goes to sleep - not sure if that's better or not. Might be better but then hit bug 624523, except it doesn't show red pixels...but still the wrong resolution. Not sure though.
Created attachment 453950 [details] anaconda.log from when the screen is blank
Created attachment 453952 [details] lsmod output from when the screen is blank
Created attachment 453953 [details] program.log from when the screen is blank
Created attachment 453954 [details] syslog from when the screen is blank
Created attachment 453955 [details] X.log from when the screen is blank
Adding F14Blocker as the following test case fails: https://fedoraproject.org/wiki/QA:Testcase_Anaconda_User_Interface_Graphical
[ 134.776] (--) RADEON(0): Chipset: "ATI Radeon HD 5800 Series" (ChipID = 0x6899) does it work with VESA? -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
from program.log : 20:22:37,911 ERR program: Window manager error: Unable to open X display :1 20:22:37,911 ERR program: Error running /usr/bin/metacity: SIGCHLD caught when trying to start the X server. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers
(In reply to comment #7) > > does it work with VESA? yes - sorry, forgot to mention that. Except that my eyes might segfault eventually when looking at the screen for too long ;)
Program log indicates that this is hitting the same regeneration race as bug #643580. Man I'm glad I fixed that one. Between that and comment #9 saying vesa works, I'm calling this not a blocker. X log indicates that we're not picking up the EDID extension block and therefore possibly screwing up mode selection, but also maybe not. Still if vesa works before the -noreset change it'll work after too.
ajax says this is a dupe of 643580. -- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers *** This bug has been marked as a duplicate of bug 643580 ***