Red Hat Bugzilla – Bug 11995
#9 Revolution IV doesn't work with X.
Last modified: 2008-05-01 11:37:56 EDT
Graphical install doesn't start X. Says it's falling back to VGA16, but
that fails also. Machine is dual PII with AGP #9 Revolution IV.
could you confirm the following vendor id #s for your card?
(probably are 105d:5348)
(ie you can use lspci and lspci -n to find the ids...)
The Revolution series of cards has been having a lot of trouble in various cases
since Red Hat 6.1 from my roommate's experience (who's since gotten rid of the
card). In 6.1, X doesn't work at all. In 6.2, X works but not in the
installer; thus if the XF86_I128 is the same server it may just need to be
recompiled in a proper environment.
I really need those PCI ids to get this fixed.
OK, I think I may have it fixed.
It's still not fixed in beta2. I don't know if it should have been.
Yes, the PCI ids are 105d:5348
This defect is considered MUST-FIX for Winston Beta-5
Does this defect still exist with (on) Winston beta-4?
Yes, I still get the same failure using Beta 4.
This defect is considered MUST-FIX for Winston Release-Candidate #1
... we've fixed a lot of video-card problems in beta-5. Can you check to see if
the problem still exists in Pinstripe (beta-5)?
It's still failing for me. However, it doesn't look like it's getting as far as
trying to start X (and the text install crashes the same way). This machine has
a zip drive in it, is that bug still in beta 5?
What does the failure look like now? "Unknown card" or something else? You say
text mode fails too? Can we get some more info?
Ok, doing either type of install I get:
Make it through the "Loading Buslogic Drivers" and then
gets install exited abnormally -- recieved signal 11.
Alt-F3 screen ends with
* looking for video cards requiring agpgart module
* found video card controller unknown
* probing buses
* finished bus probing
* found suggestion of BusLogic
* found BusLogic device
* found suggestion of uhci
* found devices JustProbe is 0
* going to insmod BusLogic.o (path is NULL)
* trying to mount device hdc
* loopfd is 6
* found url image cdrom://hdc/mnt/source
* getting ready to spawn shell now
It doesn't look like it's getting as far as trying to start the X server. This
machine does have zip drive in it, so that's why I thought that may be problem
(assuming that bug is still in this beta).
What happens if you boot the system *without* the Zip drive in it?
I realize that removing the zip is the obvious thing, but this machine isn't
one that I can just tear apart on a whim. That's why I was trying to see if the
zip bug is supposed to be squashed in the this beta -- if it's not, then that's
obviously the problem and I don't need to tear this beast apart.
Disabling the zip drive in the BIOS doesn't change the behaviour.
This is all fixed in RC1.
I'd like to clarify that the installer is what will now work (it correctly uses
the VGA server). X itself will not, however, work with the #9 Revolution IV.
If I chose to test it using the installer, I get a blank screen and I'm hung.
If I skip the X configuration I can do the install fine, but I get the same hang
if I go through Xconfigurator.
Does Xconfigurator produce a working X display post-install?
Xconfigurator results in the same black screen as the installer when you get to
the 'Test X configuration' option.
This defect has been re-classified as SHOULD-FIX for Winston Gold-release
This was a last minute fix that was fixed in an "RC" release.
Verfied that the problem is resolved, and GUI installation
works, as well as running X.