Why would you want to play Q3 anyway? ;-)
Rune and Tux Racer, actually! :-P, the driver provided by X is WELL below par (in fact unusable) for openGL games. HOWEVER, I now want it back, at least it damn well worked! :'(
No, the problem is that when they fry the system, you can't debug it. The cause is that they are needlessly restricted.
I get Mark's point, though. It would be a much better idea if NVIDIA left it open for the XFree86/kernel hackers to work on, cos they seem to have a better idea of what they're doing.
Sorry to selfishly steer towards my problem. I still have a seriously fscked X configuration (i.e. it don't work), with no NVdriver module anywhere. So... this module- part of X or part of the kernel? Does the kernel load this module, which is provided by X, or vice versa? I think I'm getting confuZed here.
Am I gonna have to install a kernel from source whether I like it or not now, to get the module back? OR X? How could I find the headers for my existing kernel, if they're not where they're meant to be, so I can rebuild the NVIDIA kernel patch from source?
TIA Ricardo
On Fri, 15 Feb 2002, Ricardo Campos wrote:
No, the problem is that when they fry the system, you can't debug it. The cause is that they are needlessly restricted.
I get Mark's point, though. It would be a much better idea if NVIDIA left it open for the XFree86/kernel hackers to work on, cos they seem to have a better idea of what they're doing.
I think the driver is closed source though as lots of their technology is in there so they don't want other gfx card manufacturers to steal it from them.
Sorry to selfishly steer towards my problem. I still have a seriously fscked X configuration (i.e. it don't work), with no NVdriver module anywhere. So... this module- part of X or part of the kernel? Does the kernel load this module, which is provided by X, or vice versa? I think I'm getting confuZed here.
Am I gonna have to install a kernel from source whether I like it or not now, to get the module back? OR X? How could I find the headers for my existing kernel, if they're not where they're meant to be, so I can rebuild the NVIDIA kernel patch from source?
Well you can fix it by editing the XF86Config-4 file, look in the file for a line that says, driver "nvidia" change it to read "nv" and try restarting X this should now work using the default X driver (no hardware acceleration). Then you can grab kernel 2.4.17 and build it and install it etc. etc. Then you can get hold of the nvidia drivers and install them, when you see that you have got a NVdriver module loaded into your kernel change the "nv" line back to "nvidia" and it should all work nice and lovely.
HTH Adam
On Fri, 15 Feb 2002, Ricardo Campos wrote:
Am I gonna have to install a kernel from source whether I like it or not now, to get the module back? OR X? How could I find the headers for my existing kernel, if they're not where they're meant to be, so I can rebuild the NVIDIA kernel patch from source?
Erm, thinking about it my last reply didn't make it to clear.
NVdriver is a proprietary driver released by NVidia, you can get it at www.nvidia.com it is not part of the kernel or X-windows, when you build it, it will live in your kernel modules directory and will get loaded when you start X-windows. X-windows only has a non-accelerated driver for the NVidia cards, if you want to use this temporarily then you can change things as discussed in my last mail.
In my experience you should grab the latest kernel source from www.kernel.org and put it in /usr/src unpack it and create a symlink to a directory called linux if it doesn't already exist. Then put the NVidia drivers into /usr/src also. Now build your kernel when you have installed it and rebooted the machine you should login as root again and go to the NVidia directorys and run make and it should sort everything out for you.
This is how i have done things to get my Nvidia cards working in Linux, YMMV
Adam
-
Adam Bower -
Ricardo Campos