Le Mon, 9 Jun 2014 13:29:05 +0200, Laurent Bigonville <[email protected]> a écrit :
> Le Thu, 22 May 2014 11:43:32 +0200, > Andreas Beckmann <[email protected]> a écrit : > > > Control: tag -1 help > > > > On 2014-05-05 00:07, [email protected] wrote: > > > After quickly scanning the packages in the archive, it seems that > > > an udev rules file is using old ConsoleKit tags or executables > > > (udev-acl or ACL_MANAGE). > > > > The ConsoleKit support was contributed by some user a few years ago > > - unfortunately I have no clue how this works nor can I update it > > to the current way. A patch (supporting both logind and non-logind > > usage) would be highly welcome. > > I'm actually not using the NVIDIA proprietary driver at all so it's > not really easy for me to test. > > In the already existing udev rules, I'm seeing the following: > > 70-uaccess.rules:SUBSYSTEM=="drm", KERNEL=="card*", TAG+="uaccess" > > I'm wondering that just adding a similar rule like is not doing the > trick: > > SUBSYSTEM=="drm", KERNEL=="nvidia*", TAG+="uaccess" > > Could you please paste the output of the two following commands with > and without this rule (you maybe need to reboot between the 2) > > udevadm info /dev/nvidiactl > > udevadm info /dev/nvidia* OK, so I've reinstalled the proprietary drivers on my laptop, and now I realize that actually the devices are not even created by udev. I /think/ that this can actually be an issue to set the permission on the devices when using systemd/logind. On this machine using systemd 208 devices have the following mode: crw-rw-rw-. 1 root root 195, 0 jun 9 17:15 /dev/nvidia0 crw-rw-rw-. 1 root root 195, 255 jun 9 17:15 /dev/nvidiactl Looking on google, I found a quite old patch that was adding sysfs support to the kernel module, isn't it an option to revive it? Cheers, Laurent Bigonville -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
