Red Hat Bugzilla – Bug 132490
i810 video driver flat out reboots the entire sytem
Last modified: 2007-11-30 17:10:49 EST
I've been trying to configure a multiheaded setup for my new
workstation which has an onboard AGP i810 video controller and a PCI
Voodoo3 video controller. When I configured it in Multihead mode, when
X starts, the entire machine reboots. I tried configuring it for
singlehead using only the i810, and when X starts, the entire machine
reboots. I tried configuring it for singlehead using on the tdfx, and
when X starts, all is well.
The /var/log/Xorg.0.log file gives no information of any help. Running
Xorg -probeonly does not yield any error that would shed light on the
problem. I don't know what other debugging steps I can try.
I've tried upgrading to the latest Rawhide version of the server
(188.8.131.523-6) and the problem remains.
Please help! I need multiheaded for my work!
Now the i810 doesn't crash the entire system -- it just blanks the
screen with a white square as my mouse cursor, locks up the keyboard,
crashes X, and won't give me control of my video anymore.
However, once I physically remove the tdfx hardware, all is well with
the i810. It works just great.
Is it a memory conflict of some sort?
If 3Dfx video hardware is used in a multihead system, it must
be configured to be the "Primary" VGA device. You need to go into
your BIOS CMOS settings and set the onboard video to be non-primary.
This is either a complex long standing bug in the tdfx driver, or
it is a 3Dfx BIOS bug. Nobody has ever debugged the issue that
deep to draw any conclusions however.
Let us know if setting the 3Dfx to be the primary VGA device
In the examination of the problem above, the 3dfx acts as the primary
graphics adaptor. There is a BIOS setting for selecting PCI vs. AGP as
the primary, but it seems to have no affect. Console always appears on
the 3dfx card and /etc/X11/xorg.conf treats the tdfx device as the
primary device. The i810 device has BusID but tdfx device does not.
Since this bugzilla report was filed, there have been several major
updates to the X Window System, which may resolve this issue. Users
who have experienced this problem are encouraged to upgrade to the
latest version of Fedora Core, which can be obtained from:
If this issue turns out to still be reproduceable in the latest
version of Fedora Core, please file a bug report in the X.Org
bugzilla located at http://bugs.freedesktop.org in the "xorg"
Once you've filed your bug report to X.Org, if you paste the new
bug URL here, Red Hat will continue to track the issue in the
centralized X.Org bug tracker, and will review any bug fixes that
become available for consideration in future updates.
Setting status to "CURRENTRELEASE".