sad 3D proformance with nvidia

[questionasker]

ive got a celeron 2.0G processor, and a PNY Geforece 5200 128MB AGP card.

i installed the nvidia-glx drivers through synaptic, changed the driver in my xorg.config file to "nvidia" as opposed to "nv", and try to run glxgears.

when i did at first, i got about 175 FPS...
after installing the drivers, i get this rror:

code:

glxgears
Error: Could not open /dev/nvidiactl because the permissions
are too resticitive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.
Segmentation fault



now what? i know i must have to change some configureation somewhere, but i can find anything on wht to change...


btw- what is the command to completely kill xorg, so i can run the nvidia official drivers?

[paj12]

btw- what is the command to completely kill xorg

init 3



Did you run the config program? I think you have to run

nvidia-glx-config enable

when you get the driver through apt.

By the way, 175 FPS with glxgears is not good. You should be getting in the thousands!

[questionasker]

yes, but i cant run the command while xorg is still running.

and i know, 175 FPS sucks, that why im asking for help.


edit: ok, i ran that command, and it finished successfully. but when i restart X, i get the same error as before...

[bsm2001]

directly from the readme

Q: OpenGL applications exit with the following error message:

Error: Could not open /dev/nvidiactl because the permissions
are too restrictive. Please see the FREQUENTLY ASKED QUESTIONS
section of /usr/share/doc/NVIDIA_GLX-1.0/README for steps
to correct.

A: It is likely that a security module for the PAM system may be
changing the permissions on the NVIDIA device files. In most cases
this security system works, but it can get confused. To correct this
problem it is recommended that you disable this security feature.
Different Linux distributions have different files to control this;
please consult with your distributor for the correct method of
disabling this security feature. As an example, if your system has
the file
/etc/security/console.perms
then you should edit the file and remove the line that starts with
"<dri>" (we have also received reports that additional references to
<dri> in console.perms must be removed, but this has not been verified
by NVIDIA). If instead your system has the file
/etc/logindevperms
then you should edit the file and remove the line that lists
/dev/nvidiactl. The above steps will prevent the PAM security system
from modifying the permissions on the NVIDIA device files. Next,
you will need to reset the permissions on the device files back
to their original permissions and owner. You can do that with the
following commands:
chmod 0666 /dev/nvidia* chown root /dev/nvidia*

[bwkaz]

Or just check the permissions on the /dev/nvidia* devices, to make sure that the user you run as has read and write permission. (If you don't use PAM, then this is especially applicable. )

If you use udev, for instance, the default permissions on everything are 0600, owned by root. If those permissions get applied to the nvidia* devices, then nobody other than root will be able to use the devices -- in the short term, you'll have to change the permissions, and in the long term, you'll have to figure out why they're getting set the way they're getting set.

Do you use udev? If so, which version? (Different versions put the permission config settings in different files.) If not, you should be able to just change the permissions so you can access the device files. (Alternately, if the devices are owned by group video and group-writable, you can add yourself to the video group, then log out and back in.)

[questionasker]

yes, changing the permissions did the trcik.

now i dont get an error message, and get right at 1800 FPS with glxgears.
thanks guys, now im off to try a lil Quake3Arena...

[bwkaz]

Might want to make sure it works after a reboot too...

[rocketpcguy]

it won't work after a reboot

[deathadder]

I had the same problem on my Debian box. The only way that I could get it to work, after reboots etc. Was to add my user to the video group.

[questionasker]

no, it doesnt work after a reboot. i have to re-issue the command.

waht do i do to make it permanent??

[DSwain]

Edit the user so that the user is part of the video group, or change the rules for udev so that the group isn't video and something else which your user is part of. I'm going to do it myself now. Also, you may have to add the group video for it to work.