D
D
Denis Kotov2017-06-07 09:39:18
linux
Denis Kotov, 2017-06-07 09:39:18

Why won't Nvidia drivers start?

Pandora ~ # systemctl | grep nvidia
● nvidia-persistenced.service loaded failed failed NVIDIA Persistence Daemon
Pandora ~ # systemctl status nvidia-persistenced.service
● nvidia-persistenced.service - NVIDIA Persistence Daemon
Loaded: loaded (/lib/systemd/system/nvidia-persistenced.service ; static; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2017-06-07 13:40:49 +08; 3min 11s ago
Process: 1057 ExecStart=/usr/bin/nvidia-persistenced --user nvidia-persistenced --no-persistence-mode --verbose (code=exited, status=203/EXEC)
Jun 07 13:40:45 Pandora systemd[1]: Starting NVIDIA Persistence Daemon...
Jun 07 13:40:49 Pandora systemd[1]: nvidia-persistenced.service: Control process exited, code=exited status=203
Jun 07 13:40:49 Pandora systemd[1]: Failed to start NVIDIA Persistence Daemon.
Jun 07 13:40:49 Pandora systemd[1]: nvidia-persistenced.service: Unit entered failed state.
Jun 07 13:40:49 Pandora systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Pandora ~ # journalctl |grep nvidia
Jun 07 13:40:41 Pandora kernel: nvidia: module license 'NVIDIA' taints kernel.
Jun 07 13:40:41 Pandora kernel: nvidia-nvlink: Nvlink Core is being initialized, major device number 244
Jun 07 13:40:41 Pandora kernel: nvidia 0000:01:00.0: enabling device (0006 -> 0007)
Jun 07 13:40:41 Pandora systemd-udevd[523]: Process '/sbin/modprobe nvidia-modeset' failed with exit code 1.
Jun 07 13:40:41 Pandora systemd-udevd[523]: Process '/sbin /modprobe nvidia-drm' failed with exit code 1.
Jun 07 13:40:41 Pandora systemd-udevd[523]: Process '/sbin/modprobe nvidia-uvm' failed with exit code 1.
Jun 07 13:40:41 Pandora systemd-udevd[815]: failed to execute '/usr/bin/nvidia-smi' '/usr/bin/nvidia-smi': No such file or directory
Jun 07 13:40:41 Pandora systemd-udevd[523 ]: Process '/usr/bin/nvidia-smi' failed with exit code 2.
Jun 07 13:40:41 Pandora kernel: nvidia-modeset: Loading NVIDIA Kernel Mode Setting Driver for UNIX platforms 381.22 Thu May 4 00:21: 48 PDT 2017
Jun 07 13:40:41 Pandora kernel: [drm] [nvidia-drm] [GPU ID 0x00000100] Loading driver
Jun 07 13:40:45 Pandora systemd[1057]: nvidia-persistenced.service: Failed at step EXEC spawning / usr/bin/nvidia-persistenced: No such file or directory
Jun 07 13:40:49 Pandora systemd[1]: nvidia-persistenced.service: Control process exited, code=exited status=203
Jun 07 13:40:49 Pandora systemd[1]: nvidia-persistenced.service: Unit entered failed state.
Jun 07 13:40:49 Pandora systemd[1]: nvidia-persistenced.service: Failed with result 'exit-code'.
Jun 07 13:40:51 Pandora bumblebeed[1125]: rmmod: ERROR: Module nvidia_uvm is not currently loaded
Jun 07 13:40:51 Pandora bumblebeed[1125]: rmmod: ERROR: Module nvidia is in use by: nvidia_modeset
Jun 07 13:40:51 Pandora bumblebeed[1125]: modprobe: FATAL: Error running remove command for nvidia
Jun 07 13:40:54 Pandora bumblebeed[1125]: [ 27.146194] [ERROR]Unloading nvidia driver timed out.
Pandora ~ #
And it does not depend on the version of the drivers and tried 375 and 381, the result is the same.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
N
Nazar Mokrinsky, 2017-06-07
@kotov666

Such an idiotic error occurs after updating the Nvidia driver. Somehow it turns out that it demolishes the nvidia-persistenced user during the removal of the old package and does not create it back when installing the new one.
I have no idea how this happens, it is solved by reinstalling the driver. That is, if you have it nvidia-381, then you do it apt-get install --reinstall nvidia-381and it should work.
But as far as I remember, the driver generally worked for me even when the daemon nvidia-persistencedcrashed with an error. With X11, your driver is used from the moment you boot and until you turn off the computer, and this daemon is responsible for deinitialization and re-initialization, that is, in fact, it is not used on desktops.

V
Vyacheslav, 2017-06-07
@Firik67

There is a suspicion that you need to disable SecureBoot in the BIOS

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question