Hi,
On 07-10-15 19:02, Andreas Beckmann wrote:
On 2015-10-07 18:43, Manuel Bilderbeek wrote:
Please send the output of these 2 commands:
find /dev/dri* /dev/nvidia* -ls
$ find /dev/dri* /dev/nvidia* -ls
10721 0 drwxr-xr-x 2 root root 60 okt 7 14:13 /dev/dri
10722 0 crw-rw---- 1 root video okt 7 14:13
/dev/dri/card0
15614 0 crw-rw-rw- 1 root root okt 7 14:13
/dev/nvidia0
16557 0 crw-rw-rw- 1 root root okt 7 14:13
/dev/nvidiactl
These permissions (666 on the nvidia devices) are wrong ... and make
things work :-(
So let's check whether this is actually the case.
Go to a console (Ctrl-Alt-F1)
- stop gdm
invoke-rc.d gdm 3 stop
- and reload the module manually
modprobe -r nvidia
This gave some errors....
rmmod: ERROR: Module nvidia_uvm is not currently loaded
modprobe: FATAL: Error running remove command for nvidia_current
modprobe nvidia
ls -la /dev/nvidia*
- the nvidia devices should have 660 permissions now
They don't... still 666.
- starting gdm should fail with the known error
invoke-rc.d gdm3 start
That is indeed the case.
The way the module gets loaded upon boot is somehow wrong since it is
ignoring the module options, so it works after reboot.
What is the difference between 'upon boot' and 'after reboot'?
See also attached screenshot for my session.
--
Grtjs, Manuel
PS: MSX FOR EVER! (Questions? http://faq.msxnet.org/ )
PPS: Visit my homepage at http://manuel.msxnet.org/
