A normal frame-buffer-based installation fails with my ATI 3D Rage Pro AGP
Mach64 video card. Text install works fine of course. Installing normally
with the graphical install causes a blank screen after the installation
tries to start the X server. No attempts to switch virtual consoles
succeed. I got stuck on the previously-reported CD-ROM problem with
lowres, so I didn't get far enough to find out what was going to happen. I
didn't go back and retry since I actually prefer text-based installation
anyway. I know frame buffer works with this video card since I use frame
buffer support with other software (specifically, the Linuxcare bootable
business card rescue CD).
We (Red Hat) should really try to fix this before next release.
What happens when you try the 'nofb' option?
*** This bug has been marked as a duplicate of 26635 ***
I know this bug has been marked as a duplicate of 26635, but I don't seem to
have access to bug 26635 for some reason.
In response to bfox's question, I get the same behavior with a normal boot,
lowres, and nofb -- when the X server starts, I get a blank screen. I was
trying to read messages that were issued prior to the X server starting, so I
was hitting CTRL-s and then CTRL-q CTRL-s quickly to let it scroll just a little
at a time. Interestingly, after I get the blank screen, hitting CTRL-s still
turns the scroll lock light on. This may give a clue as to what state the
display is in. As I said before, attempts to switch virtual consoles fail.
Once in lowres, I got some message flashing by with the word GUI in it that I
didn't have time to read, and then the install went back to a text-based install
but with a higher resolution than just booting with "text". Unfortunately I
haven't been able to reproduce this.