Hi!

The latest sources and rpm's for the NVIDIA chips can be found at 
http://www.nvidia.com/Products/Drivers.nsf/Linux.html

Also read Appendix F of the 
http://www.nvidia.com/Products/OpenLinuxDwn.nsf/09769readmefaq found there.
It deals with AGP configuration, and may be helpful to you!

Cheers,
Robert

----- Original Message ----- 
From: "Steven Taetzsch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, March 27, 2001 6:05 PM
Subject: [expert] NVidia OpenGL and modules. Help Please


> I'm trying to get OpenGl to work with my GeForce2 Mx based video
> card in an Asus A7V KT133 motherboard based system.
> 
> I've done a 'rpm --rebuild' on the Nvidia src rpm that comes on the
> 7.2 CD's. Installed the rebuilt rpm along with the Nvidia_GLX
> rpm. Edited my XF86Config-4 file and changed the Driver "nv" line to
> Driver "nvidia". Added Load "glx" also.
> 
> When I try to run tuxracer it complains about agpgart. So I looked in
> my messages file and below is some of the log. Now comes some stuff
> where I'm really not sure what I am doing.
> 
> # rmmod agpgart     says it's not loaded
> # modprobe agpgart agp_try_unsupported=1         returns ok
> # modprobe NVdriver    returns ok. BTW, I did this while running X.
> 
> Then if I run tuxracer, the system crashes. Invalid sync frequency and
> I have to hit the reset key.
> 
> Please Help!!!!
> 
> Thanks,
> Steve
> 
> A snippet of /var/log/messages:
> 
> Mar 27 22:34:20 localhost modprobe: modprobe: Can't locate module char-major-4
> Mar 27 22:34:22 localhost last message repeated 23 times
> Mar 27 22:34:22 localhost kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
> Mar 27 22:34:22 localhost kernel: agpgart: Maximum main memory to use for agp 
>memory: 203M
> Mar 27 22:34:22 localhost kernel: agpgart: Unsupported Via chipset, you might want 
>to try agp_try_unsupported=1.
> Mar 27 22:34:22 localhost insmod: /lib/modules/2.2.17-21mdk/misc/agpgart.o: 
>init_module: Device or resource busy
> Mar 27 22:34:22 localhost insmod: Hint: insmod errors can be caused by incorrect 
>module parameters, including invalid IO or IRQ parameters
> Mar 27 22:34:22 localhost insmod: /lib/modules/2.2.17-21mdk/misc/agpgart.o: insmod 
>char-major-195 failed
> Mar 27 22:34:22 localhost modprobe: modprobe: Can't locate module char-major-4
> Mar 27 22:34:25 localhost last message repeated 43 times
> Mar 27 22:35:03 localhost PAM_unix[722]: (system-auth) session opened for user root 
>by (uid=0)
> Mar 27 22:35:03 localhost modprobe: modprobe: Can't locate module binfmt-0000
> Mar 27 22:35:03 localhost modprobe: modprobe: Can't locate module binfmt-0000
> Mar 27 22:35:04 localhost kernel: Linux agpgart interface v0.99 (c) Jeff Hartmann
> Mar 27 22:35:04 localhost kernel: agpgart: Maximum main memory to use for agp 
>memory: 203M
> Mar 27 22:35:04 localhost kernel: agpgart: Unsupported Via chipset, you might want 
>to try agp_try_unsupported=1.
> Mar 27 22:35:04 localhost insmod: /lib/modules/2.2.17-21mdk/misc/agpgart.o: 
>init_module: Device or resource busy
> Mar 27 22:35:04 localhost insmod: Hint: insmod errors can be caused by incorrect 
>module parameters, including invalid IO or IRQ parameters
> Mar 27 22:35:04 localhost insmod: /lib/modules/2.2.17-21mdk/misc/agpgart.o: insmod 
>char-major-195 failed
> 
> 


Reply via email to