Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Reply
 
Thread Tools
Old 12-21-02, 06:05 AM   #1
mrtom
Registered User
 
Join Date: Dec 2002
Posts: 2
Default 4191 GLUT + modules.conf problems

I have two separate problems with the new drivers.

Most annoyingly, the nvidia module does not load automatically on boot. This has always worked fine before, and works when I revert back to the older drivers. When 4191 is installed I have the following in my modules.conf

alias char-major-195 nvidia

This is the same as how the old drivers use it except obviously the driver name is NVdriver. I don't even know how to start looking for problems here. Does anyone have a link on how modules.conf actually works? I mean what makes the system know it should load the module 'nvidia'? I know I can just add an insmod somewhere in my boot, but I'd like to know how to do it properly

My other problem is with GLUT. After installing 4191 some apps, like celestia and billards-gl failed with a 'GLXBadRenderRequest'. The apps are linked to libGLU.so.1 which on my system is from a package named xlibmesa3. The same package and apps work fine with the older drivers though.

So I'm having to use 3123 at the moment, which seems a little slower (the new 2D work seems to go quite well on mine).
mrtom is offline   Reply With Quote
Old 12-21-02, 02:38 PM   #2
rnf
Registered User
 
Join Date: Dec 2002
Posts: 11
Default

Quote:
alias char-major-195 nvidia

This is the same as how the old drivers use it except obviously the driver name is NVdriver. I don't even know how to start looking for problems here. Does anyone have a link on how modules.conf actually works? I mean what makes the system know it should load the module 'nvidia'? I know I can just add an insmod somewhere in my boot, but I'd like to know how to do it properly
When the user-space app opens /dev/nvidia[0-n] and no kernel driver has registered with the major number 195 yet (the major number of character devices used by the app to communicate with the kernel driver), a kernel daemon looks in module.conf to find which file to load.

I do not know why it doesn't work for you (would need more details), but you can try to load the module at boot time by adding the line:
nvidia
to the file "/etc/modules". You might need to also add the line:
agpgart
before nvidia if you compiled the agpgart driver as a module.
rnf is offline   Reply With Quote
Old 12-21-02, 03:32 PM   #3
mrtom
Registered User
 
Join Date: Dec 2002
Posts: 2
Default

ah! excellent.

My agpgart is built as a module although I was trying to use the built in nvagp. I'll try again and see if I can solve it now.

Thanks!
mrtom is offline   Reply With Quote
Reply


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Hengeveld: Big Data Meets HPC to Solve Hard Problems and Improve Lives News Archived News Items 0 09-10-12 09:10 AM
problems with drivers after 295.40 (OpenSuSE 12.1, GeFroce 7900 GS, Phenom II X4) alawa NVIDIA Linux 0 06-09-12 06:37 PM
Nvidia Problems in Slackware 8.1 xtreme NVIDIA Linux 3 10-01-02 12:03 PM
DirectX 8 problems with GeForce4 Derwin NVIDIA GeForce 7, 8, And 9 Series 19 08-20-02 01:23 AM

All times are GMT -5. The time now is 06:18 AM.


Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.