On Tue, Apr 12, 2005 at 10:32:59PM +0100, John M Collins wrote: > I'll do that - trouble is round where I am they dish out Nvidia cards > like confetti, I've got them in the machine I use most and another 2 and > you have to do all that gyrating with running the script to FTP down and > build the secret module before you can run X. This is a big disincentive > when it comes to installing new kernels. > > I wish some kind soul would speak nicely to Nvidia and get them to see > reason on the point but I suspect I'm not the first person to wish that. > (Or is there a sneaky way of patching the modules so they'll work in > another kernel without tainting it?).
Well on my ssytem I can do something as simple as this in a script at boot (before starting X) and it should nicely take care of it: modprobe nvidia || m-a -t prepare nvidia && m-a -t build nvidia && m-a -t install nvidia && modprobe nvidia Most likely I will have a working loaded nvidia driver at that point and X will start successfully. m-a is module-assistant which is used on debian to build a module mathcing the running kernel (assuming it has access to either the source of the running kernel or the headers of the running kernel) using the sources from in this case nvidia-kernel-source package. I don't know if anything other than debian has anything like this, but it makes dealing with nvidia's binary drivers fairly tolerable. Len Sorensen - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
