Red Hat Bugzilla – Bug 12018
GUI installer blacks out screen
Last modified: 2007-04-18 12:27:12 EDT
I am installing on a P90 with an ATI card currently loaded with RH6.0. X
is currently configured and working.
I created a boot diskette from boot.img and booted it. At the prompt, I
selected GUI install by pressing enter. The last thing I saw before the
screen blacked out is:
Probing for mouse type...
Followed by a bunch of stuff that went by too fast for me to see before the
screen blacked out. The (4x) CD-ROM spins for awhile then eventually
stops. The screen stays black for the limit of my patience.
I also experienced this problem on a Compaq DeskPro PII with an ATI RagePro with
8MB video ram and a Compaq V75 monitor.
I did get the system to install running in text mode.
for tracking purposes, could you supply the pci IDs for your cards ...?
(ie for the sample S3 machine below, the pci IDs are 5333:8a01:
[root@foobar /root]# lspci
00:0c.0 VGA compatible controller: S3 Inc. ViRGE/DX or /GX (rev 01)
[root@foobar /root]# lspci -n
00:0c.0 Class 0300: 5333:8a01 (rev 01)
I currently have Red Hat 6.0 installed and it doesn't appear to have that
command installed. I can't even install from text due to bug 12041 so I am
basically dead in the water.
lspci is from the pciutils package, which I don't remember being installed by
default in 6.2, but it should be easy enough to grab the package and install
I finally managed to install beta1 and was able to get lspci to work. "lspci"
00:00.0 Host bridge: Acer Laboratories Inc. [ALi] M1451 (rev bd)
00:02.0 Non-VGA unclassified device: Acer Laboratories Inc. [ALi] M1449 (rev b2)
00:05.0 VGA compatible controller: ATI Technologies Inc 210888GX [Mach64 GX]
00:06.0 IDE interface: CMD Technology Inc PCI0640 (rev 02)
lspci -n gives:
00:00.0 Class 0600: 10b9:1451 (rev bd)
00:02.0 Class 0000: 10b9:1449 (rev b2)
00:05.0 Class 0300: 1002:4758
00:06.0 Class 0101: 1095:0640 (rev 02)
thank you for your extra effort getting those PCI IDs ...! :)
Fixed in beta 3
*** Bug 12041 has been marked as a duplicate of this bug. ***
verified fix ... (synchronous reads in loop device issue)