| View previous topic :: View next topic |
| Author |
Message |
bammbamm808
Guru
Joined: 08 Dec 2002
Posts: 548
Location: Hawaii
|
 Posted: Fri Apr 11, 2003 3:55 am Post subject: Quirk w/new nvidia's |
 |
|
I have been using a script in ~/.kde/Autostart that runs nvclock, but Since installing the 4349 nvidia's nvclock gives users the following:
=======================
--- NvClock v0.5.0 ---
=======================
You don't have permissions to access the registers of your Nvidia card.
Try to run nvclock as root to get access to /dev/mem or install the Nvidia 3d drivers to use /dev/nv* instead.
Remember only root can access /dev/mem, most users can access /dev/nv*.
I have tried getting the script loading during the default runlevel via rc-update, which it does, but when I log in my user, or maybe startx, the setting revert to default.
Google got me one Russian posting on the message, which was really no help at all. How do I install the nvidia driver as instructed above or otherwise solve this?
_________________
MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 2070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
| Back to top |
|
 |
nerdbert
l33t
Joined: 09 Feb 2003
Posts: 981
Location: Berlin
|
| Posted: Mon Apr 14, 2003 1:03 pm Post subject: |
|
|
if I got this right you need to have access to /dev/mem as a normal user...
my suggestion is:
| Code: |
su
groupadd nvidia
groups <username> # displays the groups username already belongs to
usermod -G group,group,...,nvidia <username> #be carefull, not mentioning a group will [b]delete[/b] your group affiliation
groups <username> # just to control that you belong to nvidia now
chgrp nvidia /dev/mem
chmod g+w /dev/mem
|
if you want anybody else to have access to /dev/mem youll just have to add him to the group nvidia
_________________
I'm really wondering what Lovechild is doing nowadays... |
|
| Back to top |
|
|
bammbamm808
Guru
Joined: 08 Dec 2002
Posts: 548
Location: Hawaii
|
| Posted: Tue Apr 15, 2003 3:29 am Post subject: |
|
|
Actually, the new nvclock works fine with the new nvidia driver
_________________
MSI MAG B550 Tomahawk
Ryzen 3900x
32Gb Samsung B-die (16GB dual rank x2) DDR4 @ 3200MHz, cl14
Geforce RTX 2070S 8GB
Samsung m.2 NVME pcie-3.0
Etc.... |
|
| Back to top |
|
|
rbonthond
Apprentice
Joined: 24 Jun 2002
Posts: 190
|
| Posted: Tue Apr 15, 2003 6:47 am Post subject: |
|
|
from /usr/share/doc/nvidia-glx-1.0.4349/README.gz
| Code: |
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*
|
i just changed in /etc/security/console.perms the line
| Code: |
<xconsole> 0600 <dri> 0600 root
|
to
| Code: |
<xconsole> 0666 <dri> 0666 root
|
|
|
| Back to top |
|
|
|
Other Things Gentoo
