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? I'm not running modules from that directory. Ideas?
* 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.
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
On Wed, 2003-04-16 at 21:23, Jim Norton wrote:
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?
This is perhaps a silly question, but what does "uname -a" say?
jrn@falcon:~> uname -a Linux falcon 2.4.20 #6 Sun Apr 13 01:04:11 PDT 2003 i686 unknown jrn@falcon:~>
On Wed, 2003-04-16 at 21:23, Jim Norton wrote:
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?
This is perhaps a silly question, but what does "uname -a" say?
-- 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
On Thu, 2003-04-17 at 05:16, Jim Norton wrote:
jrn@falcon:~> uname -a Linux falcon 2.4.20 #6 Sun Apr 13 01:04:11 PDT 2003 i686 unknown jrn@falcon:~>
OK, my hunch was wrong. Can you do "modprobe nvidia" ? Here's what I did to enable 3d. I let SuSE's tools set up X without 3d. Then I changed the Driver from "nv" to "nvidia" and added Load "glx" to the modules section and that was it. Restart X, so the new driver takes effect.
modprobe nvidia returns nothing... But I did lsmod and modinfo nvidia and got the following: falcon:/home/jrn # lsmod Module Size Used by Tainted: P snd-pcm-oss 50020 1 (autoclean) snd-mixer-oss 15992 0 (autoclean) [snd-pcm-oss] nvidia 1545696 10 (autoclean) snd-seq-midi 5248 0 (unused) snd-seq-midi-event 3304 0 [snd-seq-midi] snd-seq 43760 0 [snd-seq-midi snd-seq-midi-event] snd-ens1371 13932 1 snd-pcm 74368 0 [snd-pcm-oss snd-ens1371] snd-page-alloc 5868 0 [snd-pcm] snd-timer 17576 0 [snd-seq snd-pcm] snd-rawmidi 16064 0 [snd-seq-midi snd-ens1371] snd-seq-device 4928 0 [snd-seq-midi snd-seq snd-rawmidi] snd-ac97-codec 40224 0 [snd-ens1371] snd 39396 0 [snd-pcm-oss snd-mixer-oss snd-seq-midi snd-seq-midi-event snd-seq snd-ens1371 snd-pcm snd-timer snd-rawmidi snd-seq-device snd-ac97-codec] falcon:/home/jrn # modprobe nvidia falcon:/home/jrn # modinfo nvidia filename: /lib/modules/2.4.20/kernel/drivers/video/nvidia.o description: <none> author: <none> license: "NVIDIA" parm: silence_nvidia_output int parm: NVreg_VideoMemoryTypeOverride int parm: NVreg_EnableVia4x int parm: NVreg_EnableALiAGP int parm: NVreg_ReqAGPRate int parm: NVreg_UpdateKernelAGP int parm: NVreg_EnableAGPSBA int parm: NVreg_EnableAGPFW int parm: NVreg_SoftEDIDs int parm: NVreg_Mobile int parm: NVreg_ResmanDebugLevel int parm: NVreg_FlatPanelMode int Thanks... Jim
On Thu, 2003-04-17 at 05:16, Jim Norton wrote:
jrn@falcon:~> uname -a Linux falcon 2.4.20 #6 Sun Apr 13 01:04:11 PDT 2003 i686 unknown jrn@falcon:~>
OK, my hunch was wrong.
Can you do "modprobe nvidia" ?
Here's what I did to enable 3d. I let SuSE's tools set up X without 3d. Then I changed the Driver from "nv" to "nvidia" and added Load "glx" to the modules section and that was it. Restart X, so the new driver takes effect.
participants (3)
-
Anders Johansson -
Ben Rosenberg -
jrn＠oregonhanggliding.com