[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Note that I'm not suggesting that it be altered mechanically, but rather than a warning be written that it may not be what is wanted (note also that this issue is not about nouveau drivers but NVidia-provided drivers). If I'd seen a warning like that on doing `ubuntu-drivers autoinstall`, this issue would probably not have been filed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Yes and no... Occasionally someone will have an Nvidia-only desktop (or similar old laptop). Or they may have a very new laptop that the Linux kernel doesn't support properly yet. In such a case, using 'nomodeset' can be a life saver. Especially given the spotty stability and hardware support of the nouveau (modesetting) driver. Sometimes you just have to turn it off. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
As an after thought. This could be mitigated by having the nvidia drivers' postinst check for nomodeset in /etc/defaults/grub and warn if it is present. It is already running grub-update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Yes, sorry. Removing nomodeset allowed boot to desktop and a functional and stable system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon. ``` This is a fresh install of 18.04.2 (less than
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Great. Though I can't tell what fixed the problem. Do you mean the steps in comment #5? Regardless, if a problem was fixed without requiring any change to the binary packages then the appropriate status is 'Invalid' now. That just means it's not a bug in the assigned package. ** Changed in: nvidia-graphics-drivers-390 (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Invalid Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Thank you so very much. That has fixed the problem. In the next couple of weeks when I can find some time, I'll look into the other issue that you've been managing and try it with a mainline kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Laptops are almost always wired with only the Intel GPU connected to the LCD. If there is an Nvidia GPU then it is not connected to the screen; it only shares rendered frames with the Intel GPU via system memory. This allows the Nvidia GPU to be completely turned off without losing the screen or needing to change drivers. And the Intel driver absolutely requires modesetting to work (hence no 'nomodeset'), because that is the only mode of operation supported by the Intel driver (unless you want 1024x768 and software rendering). Yes, I think Escape is edge triggered only. It's not a modifier key like Shift is. But also yes I only use UEFI so maybe legacy BIOS modes still support Shift. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced:
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
re:nomodeset: That's odd unless the drivers on the live usb media are old; nomodeset is definitely needed to not lock up from the live usb on this machine. re:grubmenu: I'm not using UEFI, so AFAIU, shift should be the key (though I tried both). Is it edge triggered? If not, I've had the key held down from the moment the boot process is started at the boot medium option screen of my BIOS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
Your Intel GPU, which usually is the only GPU wired directly to the laptop screen, requires modesetting to be enabled. I recall old versions of the Nvidia driver did not like that, but current versions do. I think "current" includes Ubuntu 18.04. As for the grub menu, yes it might have become harder to trigger in recent years but I am pretty sure Escape still works. You just have to be very fast... -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
I will give that a go. The nomodeset option was set during istall, presumably because the live usb install media doesn't boot without it. I vaguely recall altering that option at the grub menu, but it was a long day yesterday, so I am not sure (as an aside, why does the grub menu not come up with shift or esc any more - I needed to alter the grub files to make it possible to see the menu at all, which is pretty unfriendly). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file
[Kernel-packages] [Bug 1830000] Re: NVIDIA driver (390) does not allow progress to login screen
** Package changed: gdm3 (Ubuntu) => nvidia-graphics-drivers-390 (Ubuntu) ** Tags added: nvidia -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/183 Title: NVIDIA driver (390) does not allow progress to login screen Status in nvidia-graphics-drivers-390 package in Ubuntu: Incomplete Bug description: Installing the nvidia-driver-390 package and disabling (or not) the nouveau drivers results in a system that superficially appears to busy hang before reaching the login screen, leaving only the fsck "/dev/sda1: clean,..." message on the screen. The machine is alive, and logging in remotely gives a hint at what is happening. The output of top shows that init and systemd are struggling with something: ``` top - 17:24:00 up 1 min, 1 user, load average: 2.76, 1.00, 0.36 Tasks: 188 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.0 us, 15.2 sy, 0.0 ni, 67.6 id, 0.0 wa, 0.0 hi, 0.1 si, 0.0 st KiB Mem : 16238012 total, 15513832 free, 242248 used, 481932 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15716900 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1 root 20 0 225600 9312 6672 S 60.4 0.1 0:51.63 /sbin/init nosplash 797 root 20 0 71656 7180 5296 S 26.8 0.0 0:14.92 /lib/systemd/systemd-logind 1133 root 20 0 46368 3584 1976 R 13.9 0.0 0:12.01 /lib/systemd/systemd-udevd 795 root 20 0 1773200 30772 12548 S 13.2 0.2 0:11.71 /usr/lib/snapd/snapd 784 message+ 20 0 51464 6036 3988 S 12.9 0.0 0:11.15 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --s+ 308 root 19 -1 249904 120460 114260 S 10.7 0.7 0:10.60 /lib/systemd/systemd-journald 1132 root 20 0 46368 3584 1976 S 10.0 0.0 0:08.71 /lib/systemd/systemd-udevd 1134 root 20 0 46368 3260 1656 S 10.0 0.0 0:08.61 /lib/systemd/systemd-udevd 333 root 20 0 46368 4684 3084 S 5.0 0.0 0:04.25 /lib/systemd/systemd-udevd ``` Eventually, Xorg does manage to get a word in, but falls over, to try again repeatedly. ``` top - 16:52:36 up 2 min, 1 user, load average: 1.69, 1.04, 0.43 Tasks: 187 total, 2 running, 106 sleeping, 0 stopped, 0 zombie %Cpu(s): 9.5 us, 3.7 sy, 0.0 ni, 85.6 id, 0.0 wa, 0.0 hi, 1.2 si, 0.0 st KiB Mem : 16238012 total, 15457080 free, 278152 used, 502780 buff/cache KiB Swap: 16001020 total, 16001020 free,0 used. 15680684 avail Mem PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 1821 root 20 0 312908 61228 20584 R 65.2 0.4 0:01.97 /usr/lib/xorg/Xorg vt1 -displayfd 3 -auth /run/user/121/gdm/Xauthority -b+ 806 root 20 0 71656 7200 5320 S 18.5 0.0 0:24.83 /lib/systemd/systemd-logind ``` A further hint comes from syslog which is spammed with systemd trying to start nvidia-persistenced, which is then killed. This happens hundreds of times while the machine is up. This except shows one instance. ``` May 22 16:34:52 cube systemd[1]: Starting NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Verbose syslog connection opened May 22 16:34:52 cube nvidia-persistenced: Now running with user ID 123 and group ID 127 May 22 16:34:52 cube systemd[1]: Started NVIDIA Persistence Daemon. May 22 16:34:52 cube nvidia-persistenced: Started (31927) May 22 16:34:52 cube nvidia-persistenced: device :01:00.0 - registered May 22 16:34:52 cube nvidia-persistenced: Local RPC service initialized May 22 16:34:52 cube nvidia-persistenced: Received signal 15 May 22 16:34:52 cube systemd[1]: Stopping NVIDIA Persistence Daemon... May 22 16:34:52 cube nvidia-persistenced: Socket closed. May 22 16:34:52 cube nvidia-persistenced: PID file unlocked. May 22 16:34:52 cube nvidia-persistenced: PID file closed. May 22 16:34:52 cube nvidia-persistenced: The daemon no longer has permission to remove its runtime data directory /var/run/nvidia-persistenced May 22 16:34:52 cube nvidia-persistenced: Shutdown (31927) May 22 16:34:52 cube systemd[1]: Stopped NVIDIA Persistence Daemon. ``` This is a fresh install of 18.04.2
