LinuxQuestions.org - Problems with nVidia drivers starting ut2004

- Linux - Software (https://www.linuxquestions.org/questions/linux-software-2/)

- - Problems with nVidia drivers starting ut2004 (https://www.linuxquestions.org/questions/linux-software-2/problems-with-nvidia-drivers-starting-ut2004-180987/)

Problems with nVidia drivers starting ut2004 [solved]

when I try to start it from the console it says:

Code:

zac@moe-server zac $ ut2004

open /dev/[sound/]dsp: No such file or directory

NV: could not open control device /dev/nvidiactl (Permission denied)

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.

The sound related errors are correct because i don't have any sounds on this machine right now, but I am using the nvidia driver and I didn't see any problems like mine the FAQ like the error message said. I emerged the nvidia kernel and glx drivers and updated the XF86Config which seems to be working fine. I see the nvidia logo when KDE starts and everything appears to be well and good except for this error.

I'm running a gentoo system with a Geforce 4 MX440

Code:

Section "Device"

        Identifier  "Card0"

        Driver      "nvidia"

        VendorName  "nVidia Corporation"

        BoardName  "NV17 [GeForce4 MX 440]"

        BusID      "PCI:0:12:0"

EndSection

Any ideas?

Straight from the docs:

Quote:

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*

Håkan

thanks hw-tph somehow I missed that when I went over the README. I followed the instructions and it worked :)

i got also a problem with nvidia opengl

i can use the normal nv driver
but not nvidia

i did:
emerge nvidia-kernel nvidia-glx

when i do:
modprobe nvidia

it says:
FATAL: Error inserting nvidia (/lib/modules/2.6.6/video/nvidia.ko): Invalid module format

i added "nvidia" also to /etc/modules.autoload.d/kernel-2.6
at booting it says:

* Using /etc/modules.autoload.d/kernel-2.6 as config:
* Loading module nvidia...
* Failed to load nvidia [!!]

* Autoloaded 0 module(s)

anyone got a clue?

because the compiler that you use to compile kernel is different ( version ) with the one you use to compile nvidia module