Red Hat Bugzilla – Bug 124413
Installer detects (and subsequently configures X accordingly) the onboard GD5465 instead of the Voodoo3, which the monitor is connected to.
Last modified: 2007-11-30 17:10:43 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; it-IT; rv:1.6)
Description of problem:
I have an HP Kayak XA with its native on board GD 5465 AGP graphic
adapter and an additional Voodoo3 card. The monitor (a Mitsubish
Diamond Scan 17HX) is connected to the 3dfx card while the onboard
monitor connector is being left unconnected.
When i start the FC2 installation via CDs, anaconda detects ONLY the
CirrusLogic adapter and configures X for the first boot with this card.
The fact, per se, doesn't cause any problem to the whole installation
process but, when the system reboots, X fails to come up.
You have to edit the xorg.conf file, manually modify it to match the
real configuration (i.e. add a "tdfx" device section and connect it to
the configured monitor) and reboot the system in order to have the
"first boot" phase go on.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install FC2 on an HP Kayak with a Voodoo3 graphic card.
Actual Results: Anaconda detects the Cirrus Logic video Adapter.
Expected Results: Anaconda should have detected the Voodoo3 card
I have Dell Dimension v400c and have exactly the same problem wiht my
native ATI Mach64 (3D Rage Pro AGP) and the additional 3dfx Voodoo3.
This should be better in current code.