You are not logged in.
Pages: 1
Well, I get that famous error about the permissions being too restrictive on /dev/nvidiactl. I read a few posts on this forum about people getting the same issue. I did the following:
groupadd video
gpasswd -a me video
ls -l /dev/nvidiactl
crw-rw---- 1 root video 195, 255 1969-12-31 19:00 /dev/nvidiactl
I rebooted and I still get the error. I'm not sure were to go from here.
Offline
You might I've got an nVIdia card as well and the permissions on mine are as follows:
crw-rw-rw- 1 root video 195, 255 2005-04-01 17:33 /dev/nvidiactl
if you are using UDEV I bet you also need to add these perms. to your **.rules and/or **.perms files
-The more engineering courses I take, the more I lose my heart for engineering. I just want to F*@%ing build stuff!
Offline
hmmm...not sure if I am using udev and not sure exactly what udev does. You gave me a start though. I'll check it out when I go home.
P.S. I have a few more issues and it seems the Arch community is very helpfull so I will be posting them. You guys and your distro rock.
<EDIT>If I understand the document I just read correctly, hotplug needs udev to work. I am using hotplug and that is another one of my issues which I'll deal with later. So I must be using udev.</EDIT>
Offline
Okay fyi, I had to change permissions on both /dev/nvidia0 and /dev/nvidiactl:
# chmod 666 /dev/nvidia0
# chmod 666 /dev/nvidiactl
That did the trick.
Offline
hmmm...not sure if I am using udev and not sure exactly what udev does. You gave me a start though. I'll check it out when I go home.
P.S. I have a few more issues and it seems the Arch community is very helpfull so I will be posting them. You guys and your distro rock.
<EDIT>If I understand the document I just read correctly, hotplug needs udev to work. I am using hotplug and that is another one of my issues which I'll deal with later. So I must be using udev.</EDIT>
Udev is the successor of devfsd. Udev is software which creates dynamicly devicefiles in /dev. Udev needs hotplug, but this is a one way dependency (hotplug does not need udev).
Out / Gone
Mirgrating all my machines off ArchLinux . No longer part of the ArchLinux community / users .
Done. Goodbye.
Offline
Well, I see devfsd running at boot so I guess I'm not using udev. Strange thing though, after reboot the permissions are set back on /dev/nvidiactl to 660. Strange.
Offline
To use udev, add devfs=nomount to the append field in /etc/lilo.conf (or similar for grub). Of course you also need to have udev installed. I think that's all, but search the old news on www.archlinux.org, there was instruction how to do it and also how to change permissions.
Then I'd say you need to add this:
KERNEL="nvidia*", GROUP="video", MODE="0666"to /etc/udev/rules.d/00.rules
Offline
This has been pissing me off for some time now.
If /dev/nvidia* is in group video, and gives rw permission to that group, and I am in that group...then what gripes does it have about insufficient permissions???
*mumble*
The suggestion box only accepts patches.
Offline
I left the default permissions 660 and am a member of group video. The only thing that doesn't work is the xscreensaver with GL screensavers. This happened after xscreensaver upgrade, http://bugs.archlinux.org/index.php?do=details&id=2503
as someone said there, it has suid and it probably changes to another user, like nobody, who is not in group video.
Sure it works with 666 but that should not be necessary. IMHO this issue still needs better solution than this. I don't know if unsetting the uid bit of xscreensaver would be good, because then it would do everything under my account.
Offline
It works for me.
stat /dev/nvidia*
File: `/dev/nvidia0'
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: bh/11d Inode: 92693 Links: 1 Device type: c3,0
Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 91/ video)
Access: 2005-04-11 18:14:50.385174720 -0500
Modify: 2005-04-11 18:14:50.385174720 -0500
Change: 2005-04-11 18:14:50.385174720 -0500
File: `/dev/nvidiactl'
Size: 0 Blocks: 0 IO Block: 4096 character special file
Device: bh/11d Inode: 92682 Links: 1 Device type: c3,ff
Access: (0660/crw-rw----) Uid: ( 0/ root) Gid: ( 91/ video)
Access: 2005-04-11 18:14:50.380175480 -0500
Modify: 2005-04-11 18:14:50.380175480 -0500
Change: 2005-04-11 18:14:50.380175480 -0500·¬»· i am shadowhand, powered by webfaction
Offline
I read up on setuid and xscreensaver. It is setuid root becausee of it's screen locking mechanism that needs to read shadow password info, so some very small parts of code need to run as root. After these parts of code have been run, it changes to an unpriviledged user such as nobody, rather than the user that started the process.
According to their website, if PAM is set up correctly on the system in question, the program actually doesn't need to run as root, so it should be OK to take away the setuid bit, and it will run as the user that started it.
Noting that PAM is set up correctly under Arch, I took away the setuid bit and everything seems to work fine, including screen locking. YMMV
The suggestion box only accepts patches.
Offline
Pages: 1