Ubuntu 17.10 full disk encryption + Nvidia drivers not booting

Bug #1721988 reported by Maraschin on 2017-10-07
46
This bug affects 9 people
Affects Status Importance Assigned to Milestone
plymouth (Ubuntu)
Undecided
Unassigned

Bug Description

I've installed ubuntu 17.10 with full disk encryption and then installed the nvidia drivers (v 384). when I boot the computer I will get the graphics interface to enter the encryption key but the system will stop to work, like it has hang. Basically I'm not able to enter the password!

I've to restart in safe mode to be able to enter the password for the encryption, after that I can just resume the boot and all works.

There seems to be some issues with the initial boot screen and nvidia drivers... I'm not able to press any combination of Control+Alt+Fx key to get any extra info about what is going on (not able to get any text mode).

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: nvidia-384 384.90-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3
Uname: Linux 4.13.0-12-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.7-0ubuntu2
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 7 20:07:29 2017
InstallationDate: Installed on 2017-09-25 (11 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170919)
SourcePackage: nvidia-graphics-drivers-384
UpgradeStatus: No upgrade log present (probably fresh install)

Maraschin (carlo-maraschin) wrote :
Maraschin (carlo-maraschin) wrote :

I've just updated it to nvidia-387 and it still the same problem.
By the way, I've installed ubuntu-gnome-desktop before I did install nvidia drivers.

Another thing: when I start the computer I'm not able to see grub options to decide how to boot, I only can see it after I press control + alt + delete and reboot the computer, than it shows up.

Running on a Dell Precision T5600
Intel® Xeon(R) CPU E5-2665 0 @ 2.40GHz × 16
64GB RAM, GeForce GTX 680/PCIe/SSE2

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nvidia-graphics-drivers-384 (Ubuntu):
status: New → Confirmed
Jelmer Draaijer (jelmert) wrote :

This problem exist at least since 16.10 and i'm experience it in 17.04 also.

The solution can be found in the comments of the accepted answer here: https://askubuntu.com/questions/809477/keyboard-not-working-with-full-disk-encryption-after-installing-nvidia-drivers-o

Qoute: "It seems to be related to the fact that the nvidia drivers need access to something on the encrypted disk."

Work around:
open /etc/default/grub
and change
GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”
in the to
GRUB_CMDLINE_LINUX_DEFAULT=””
and
sudo update-grub

Sean Tasker (0xseantasker) wrote :

I am also affected by this and have also been booting into recovery then resuming.

This issue appears to be related (found it first) but had expired -
 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1387107

I am running:

Kubuntu 16.04.1 LTS
Kernel: 4.10.0-42-generic
nvidia-384 (384.90)

John Vines (jvines-s) wrote :

I'm also experiencing this issue on 16.04 LTS with Nvidia-390, kernel 4.13.0-26-generic

rick beldin (rick-beldin) wrote :

Verified with Kubuntu 17.10 on a Zbook15 G3

I found a workaround in another bug report of ensuring that "noquiet nosplash" are passed on the kernel cmdline at grub. This works but disables all of the pretty splash screens (perhaps not such a bad thing). There appear to be other variations of this workaround that may be device specific.

There is still something squirrely suggesting a timing or ordering issue. If I stop in grub and just view the current grub entry and boot with ctrl-x, sometimes the screen will go completely black, with no inputs. On a hunch it was waiting for the encryption password, I entered it and waited. Graphics came up somewhat normally although all the graphics terminals except the graphics one were completely black.

Reference:

https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/1359689

rick beldin (rick-beldin) wrote :

A slightly better workaround is this from the other bug:

If this works for you and you want to make it persistent, edit the /etc/default/grub file (with sudo):

1. remove the "splash" from GRUB_CMDLINE_LINUX_DEFAULT
2. uncomment the line GRUB_GFXMODE and set it to "auto", GRUB_GFXMODE=auto
3. save the file and run the command "update-grub"

The text console resolution is set properly and you are prompted in text mode with minimal debugging information.

Mathias Bynke (mabynke) wrote :

I was previously affected by this (albeit with the 340 version) and had to do the workaround. After making a fresh install of the just released Ubuntu 18.04, it seems to no problem. Even with the same encrypted setup as before on the same machine as before, I am now prompted for the passphrase in the splash, and the boot completes as it should. So I would say that either this happens randomly, or it has been fixed in 18.04.

Justin Nichols (jnichols21) wrote :

I concur, this is fixed in Ubuntu 18.04, with one exception. The time it takes to see the prompt to enter the encryption passphrase it considerably longer than when using the open source nouveau driver -- a good 20 seconds compared to just a couple seconds using nouveau.

NVIDIA Driver: nvidia-driver-390
CPU: Intel Core i7-4870HQ @ 8x 3.7GHz
GPU: GeForce GTX 980M
Kernel: x86_64 Linux 4.15.0-20-generic

Toliet WC (goingwc) wrote :

The splash works fine with fulldisk encryption if I do not install any Nvidia drivers, however if I install the latest stable Nvidia driver then this problem will also occurs to me. Changing the GRUB is one way but I find it pretty sad that we are not able to something that ruins the first impression of a OS.

OS: Kubuntu 17.10.1
CPU: AMD Ryzen 1700X
GPU: ASUS 1050 TI
Nvidia Driver: 384

Dariusz Gadomski (dgadomski) wrote :

Hi,
Could anyone that has it working on 18.04 add plymouth:debug to their kernel cmdline, reboot and share the /var/log/plymouth-debug.log?

I'm looking into this, but also experience the issue on 18.04. I'm curious where the difference comes from.

Thanks!

Toliet WC (goingwc) wrote :

Hi Dariusz!
I will see to it in the coming weeks when I upgrade to 18.04. Can you tell me how I can add plymouth:debug to my kernel cmdline and will it destroy my system?

I am dualbooting and do not want to reformat my PC...

Dariusz Gadomski (dgadomski) wrote :

Thanks @goingwc, I have managed to reproduce it here so I can use my own plymouth log. Turns out I couldn't get even 18.04 working correctly, because I had integrated GPU enabled in my motherboard settings (i7-6700K with HD 530) despite nvidia being set to "primary GPU". I had to disable the integrated one completely.

After doing some experiments I noticed that this is not related to nvidia, but to modesetting - I was able to reproduce this issue without nvidia drivers installed, just by adding nomodeset to kernel cmdline on pre-bionic releases (tested on Xenial and Artful).

Toliet WC (goingwc) wrote :

Hi @dgadomski
Yeah, in a new installed version of Kubuntu 17.10 there is NO problem if the full-disk encryption is not ENABLED, however it also works if you do not install the Nvidia drivers for Kubuntu. This problem occurs when you decide to install Nvidia drivers for Kubuntu (as in my case) and have to set add nosplash for it to show the prompt to write your password before booting the OS.

If the user decide to set splash (GUI, to prompt password) then a black window will appear or you can not write the password or any character into the password prompt.

How can I as a user help Kubuntu to solve this problem?

no longer affects: nvidia-graphics-drivers-384 (Ubuntu)
Toliet WC (goingwc) wrote :

This is now working splendid on Kubuntu 18.04 LTS, kernel parameter splash works fine with fulldisk encryption and GRUB.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in plymouth (Ubuntu):
status: New → Confirmed
Aaron Von Gauss (avongauss) wrote :

With Ubuntu 18.04 LTS or Ubuntu 18.10 and full disk encryption enabled, after I install the nVidia drivers I also receive the blank screen though I can type the passphrase in and it will continue to boot successfully. What seems odd based on some past comments is adding the "nomodeset" parameter for me presents the splash screen as expected even with the nVidia drivers installed. I've tested this with both the 390 and 415 drivers.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers