PDA

View Full Version : GF4MX PCI & GF3Ti500 AGP not playing nice


mdw
11-26-02, 05:45 AM
these two cards don't seem to want to play together. I think something is happening at bootup that is keeping the GF4MX from getting initilized because I always get this warning from the nvidia driver about that card

(WW) NVIDIA: No matching Device section for instance (BusID PCI:0:12:0) found

lspci confirms that is where the card is, and I get this same problem when I have the PCI as the main video card in the bios. Just for reference here's is the relevent part of my XF86Config, do they just not want to do this, am I going to have to throw in one of my less liked pci video cards just to make things work?

---------------------------------------

Section "Monitor"
Identifier "Proview VM500E"
HorizSync 30.0 - 60.0
VertRefresh 50-150
EndSection

Section "Monitor"
Identifier "Gateway EV500"
HorizSync 30.0 - 69.0
VertRefresh 50-110
EndSection

Section "Device"
Identifier "GeForce3Ti 500"
Driver "nvidia"
BusId "PCI:01:00:0"
# VideoRam 65356
Option "DPMS"
Option "CursorShadow" "true"
Option "CursorShadowAlpha" "80"
EndSection

Section "Device"
Identifier "GeForce4MX PCI"
Driver "nvidia"
# VideoRam 65356
BusId "PCI:00:0c:0"
Option "CursorShadow" "true"
Option "CursorShadowAlpha" "80"
EndSection
Section "Screen"
Identifier "Magview"
Device "GeForce3Ti 500"
Monitor "Proview VM500E"
DefaultDepth 16
<snip, just modes here>
EndSection

Section "Screen"
Identifier "Gateway"
Device "GeForce4MX PCI"
Monitor "Gateway EV500"
DefaultDepth 16
<snip, just modes here>
EndSection

Section "ServerLayout"
Identifier "Simple Layout"
Screen "Magview"
Screen "Gateway" RightOf "Magview"
Option "Xinerama" "on"
InputDevice "Mouse1" "CorePointer"
InputDevice "Keyboard1" "CoreKeyboard"
EndSection

r0gu3
11-26-02, 08:04 AM
Don't use lspci, use XFree86 -scanpci...
if it doesn't output to your screen it will output to your log file...

It seems like the card may be actually at :0:12...

You may wanna check your logs (debug) for any postin errors from the kernel module...

- r0gu3

mdw
11-27-02, 01:09 AM
heh, you were right. i had to put 0:12:0 instead of 0:c:0. Personally that doesn't make sense, using base-10 instead of base 16, but hey, it fixed it, so all is well.