Hi,

Am Mo 21 Mär 2016 23:29:01 CET
schrieb Andreas Beckmann <a...@debian.org>:

> So let's try what should happen within clinfo manually:
> 
> (as root)
> # modprobe -r nvidia-uvm
> 
> (as user)
> $ modprobe -v nvidia-uvm
 
I had to add /sbin to the path, the results are similar to what you are
expecting:

$ PATH=$PATH:/sbin modprobe -v nvidia-uvm
install modprobe nvidia ; modprobe -i nvidia-current-uvm $CMDLINE_OPTS 
insmod /lib/modules/4.4.0-1-amd64/updates/dkms/nvidia-current.ko 
modprobe: ERROR: could not insert 'nvidia_current_uvm': Operation not
permitted 
modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do()
Error running install command for nvidia_uvm modprobe: ERROR: could not
insert 'nvidia_uvm': Operation not permitted

> But the libnvidia-opencl.so.1 library does not call modprobe directly,
> it uses the nvidia-modprobe setuid root wrapper instead:
> 
> (as user)
> $ nvidia-modprobe -u
> $ dmesg | tail
> $ ls -la /usr/bin/nvidia-modprobe
> 
> Does that work?
> If it doesn't, do you use anything for extra hardening of the system?
> (selinux, apparmor, ...?)

It doesn't work:

$ nvidia-modprobe -u
modprobe: ERROR: could not insert 'nvidia_current_uvm': Operation not
permitted 
modprobe: ERROR: ../libkmod/libkmod-module.c:977 command_do()
Error running install command for nvidia_uvm modprobe: ERROR: could not
insert 'nvidia_uvm': Operation not permitted

$ dmesg|tail
[   30.210734] systemd[1]: proc-sys-fs-binfmt_misc.automount: Got
automount request for /proc/sys/fs/binfmt_misc, triggered by 724
(update-binfmts) 
[   30.225790] systemd[1]: Mounting Arbitrary Executable File Formats
File System... 
[   30.310574] systemd[1]: Started Journal Service. 
[   30.788185] systemd-journald[717]: Received request to flush runtime
journal from PID 1 
[   33.445899] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready 
[   36.568635] tg3 0000:3f:00.0 eth0: Link is up at 1000 Mbps, full
duplex 
[   36.568658] tg3 0000:3f:00.0 eth0: Flow control is on for TX and on
for RX 
[   36.568686] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  134.948174] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD data
byte 7 
[  257.279351] snd_hda_codec_hdmi hdaudioC0D0: HDMI: invalid ELD
data byte 7

$ ls -la /usr/bin/nvidia-modprobe
-rwsr-xr-x 1 root root 31224 Feb 17 00:47 /usr/bin/nvidia-modprobe

apparmor is installed, but I have not changed the configuration.
Maybe they have tightened the rules in a recent update? Should I remove
it?

Cheers
Michael

Reply via email to