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