Thats just it though.. I *did* compile the kernel driver against my current kernel. That is what the .RUN file is for from Nvidia.. so people can still compile the nvidia module against any kernel. I know the kernel module is getting installed and compiled against my running kernel, because after a recompile, X won't even start until I run the make install from the sources that come out of the .RUN file. The question is, why is 3Ddiag checking for modules in my old kernel modules directory instead of the new 2.4.20 modules directory? -Jim-
* Jim Norton (jrn@oregonhanggliding.com) [030416 12:11]: ->Hello all: -> ->I recently upgraded to a stock non SuSE 2.4.20 kernel and things appear ->to work fine. However, I can't enable 3D on my Nvidia card even though ->I followed SuSE's instructions on installing the new Nvidia drivers - I ->installed by RPMS as well as did the .run file as described by SuSE. -> ->3Ddiag is complaining about modules ( nvidia.o ) not being found in ->the stock SuSE 2.4.19 directories. Why the heck would it look there?
Um..it's not linked to your new kernel. You should get the tar.gz files not the rpm's and install it that way so that it gets linked to your running kernel and it's src.
-- Ben Rosenberg ---===---===---===--- mailto:ben@whack.org Tell me what you believe.. I'll tell you what you should see.
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com