> The XF86Config-4 and /var/log/XFree86.0.log are attached.  Both look
> good to me, yet no X appears.
Not to me, since it finds more than one primary device so it doesn't know
which one to associate the driver with. Either try setting the BusID (see
man XF86Config for the format of the BusID statement; in PCI speak your
Voodoo3 has ID 1:0:0 (see below)) or if you happen to have an onboard
video chipset, disable it in the BIOS. So, first try adding BusID
"PCI:1:0:0" to the Device section of your XF86Config-4 file...

[snip : calling a speckle of shit in the underpants a dunk heap;
        in this case, that might be true though >:-> ]

XFree86 Version 4.2.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
        If the server is older than 6-12 months, or if your card is
        newer than the above date, look for a newer version before
        reporting problems.  (See http://www.XFree86.Org/)
Build Operating System: Linux 2.4.18-23mdkenterprise i686 [ELF]
Module Loader present
[snip]
(II) Bus -1 prefetchable memory range:
        [0] -1  0x00000000 - 0xffffffff (0x0) MX[B]
(!!) More than one primary device found
     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(--) PCI: (0:10:0) BrookTree unknown chipset (0x036e) rev 2, Mem @ 0xdb022000/12
(--) PCI: (0:11:0) Creative Labs unknown chipset (0x0002) rev 8, I/O @ 0xac00/5
(--) PCI: (1:0:0) 3dfx Interactive Voodoo3 rev 1, Mem @ 0xd4000000/25, 0xd8000000/25, 
I/O @ 0x9000/8
             \
              ---------------> and this is the one you need

(II) Addressable bus resource ranges are
        [0] -1  0x00000000 - 0xffffffff (0x0) MX[B]
        [1] -1  0x00000000 - 0x0000ffff (0x10000) IX[B]
(II) OS-reported resource ranges:

[snip]
(II) Loading extension XFree86-DRI
(II) LoadModule: "tdfx"
(II) Loading /usr/X11R6/lib/modules/drivers/tdfx_drv.o
(II) Module tdfx: vendor="The XFree86 Project"
        compiled for 4.2.1, module version = 1.0.0
        Module class: XFree86 Video Driver
        ABI class: XFree86 Video Driver, version 0.5
[snip]
(II) TDFX: Driver for 3dfx Banshee/Voodoo3 chipsets: 3dfx Banshee,
        3dfx Voodoo3, 3dfx Voodoo5
(II) Primary Device is:
     ^^^^^^^
(WW) TDFX: No matching Device section for instance (BusID PCI:1:0:0) found
 ^^ stands for Warning (see legend at the beginning of the file)
That's why the BusID is needed...

(EE) No devices detected.
At least not unambiguously as required per the man page!
Do you actually read the log completely before you judge it "looking
good"? Since when it actually looks good, also your screen should look
good, which it obviously doesn't and so in fact the log does NOT look
good... (A.k.a. NEVER ignore Warnings (even not compiler warnings))

Hope this helps,

Guy


Reply via email to