PDA

View Full Version : MSI GeForce 4 Ti 4800SE & Mandrake 9.0


Mandingo
04-24-03, 11:09 AM
Is there support for this card?

Reading the README you can see the following lines:

o GeForce4 Ti 4800 0x0280
o GeForce4 Ti 4200 with AGP8X 0x0281
o GeForce4 Ti 4800 SE 0x0282

Thats my card.. If I list my pci devices I can see it:

$ lspci |grep VGA
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0282 (rev a1)

Well, the last drivers where installed without problems, but my surprise is that when I execute xf86cfg to see what cards are available the highest device number is "NVidia 0x0258". Where are the rest?

o Quadro4 750 XGL 0x0259
o Quadro4 700 XGL 0x025B
o GeForce4 Ti 4800 0x0280
o GeForce4 Ti 4200 with AGP8X 0x0281
o GeForce4 Ti 4800 SE 0x0282
o GeForce4 4200 Go 0x0286
o Quadro4 980 XGL 0x0288
o Quadro4 780 XGL 0x0289
o Quadro4 700 GoGL 0x028C
o NV30 0x0300
o NV30 0x0301
o NV30 0x0302
o NV30GL 0x0308
o NV30GL 0x0309


My current section device in XF86Config is:


Section "Device"
Identifier "Card0"
Driver "nv"
VendorName "nVidia Corporation"
BoardName "NV28 [GeForce4 Ti 4800 SE]"
ChipSet "0x0250"
Card "NVidia 0x0250"
BusID "PCI:1:0:0"
EndSection


I'm using a semi-compatible card, cause if I put my card ID it's not recogniced.

Moreover. I get the next message when I launch my Xwindows:


cat /var/log/XFree86.0.log |grep EE
(EE) [GLX]: Failed to add GLX extension (NVIDIA XFree86 driver not found)

So I can't execute programs that use OpenGL :|

bwkaz
04-24-03, 12:07 PM
Couple of things. First, the XFree86-provided driver named "nv" does not support any 3D whatsoever. You have to change the Driver line to read Driver "nvidia" instead.

Second, the nVidia driver gets very, very confused by ChipSet, Card, and even some BoardName lines in your config file. Get rid of them -- it should all be autodetected. But you do need to be using Driver "nvidia".

Mandingo
04-24-03, 02:31 PM
No way, when I use the driver nvidia the system hangs up! and if I don't configure myself the card it's undetected

Anymore, if you read the documentation they say that you must use "nv" instead of "nvidia"

bwkaz
04-24-03, 03:52 PM
What "documentation" are you talking about?

From the nVidia README, section 3:

If you already have an XF86Config file working with a different driver
(such as the 'nv' or 'vesa' driver), then all you need to do is find
the relevant Device section and replace the line:

Driver "nv"
(or Driver "vesa")

with

Driver "nvidia" You should NOT be using "nv" if you have the nVidia drivers installed. That's why you can't load the GLX extension -- it REQUIRES you be using Driver "nvidia".

As for the lockups... what chipset is your motherboard? How long have you let it sit?

And perhaps I wasn't clear -- when I said "autodetected", I didn't mean any GUI tools will tell you what you're using. I meant that the driver would be able to tell the difference between different cards, and adjust itself just fine. Your GUI tools very likely won't know; but then, they shouldn't care, either. You know what you have, after all, right?

Mandingo
04-24-03, 04:20 PM
Sorry, It's "nvidia" not "nv"... anyway my system is still unable to detect my card.

My motherboard is an ASUS A7V8X/LAN-EAYZ with a VIA KT400 chipset

More detailed information about my graphics card:


# lspci -v
01:00.0 VGA compatible controller: nVidia Corporation: Unknown device 0282 (rev a1) (prog-if 00 [VGA])
Subsystem: Micro-star International Co Ltd: Unknown device 9000
Flags: bus master, 66Mhz, medium devsel, latency 64, IRQ 11
Memory at ee000000 (32-bit, non-prefetchable) [size=16M]
Memory at f0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at effe0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0

bwkaz
04-24-03, 04:30 PM
How about you define "unable to detect your card"...

Have you read the KT400 workaround (http://www.nvnews.net/vbulletin/showthread.php?s=&threadid=9927&highlight=kt400+workaround) thread? Have you tried 4363? Have you tried both of them (4363 with the KT400 workaround)?

Mandingo
04-24-03, 05:38 PM
Thanks that thread solve my problem :thumbsup: