Hacker News Reader

Comment by huntie | Hacker News Reader

I was hoping this would have a big picture of Linus giving Nvidia the finger.

An issue I had that isn't on the list is installing Nvidia drivers on an encrypted install of Ubuntu 16.04. After installing the drivers it would no longer boot, so I could only encrypt my home folder.

View on HN

> An issue I had that isn't on the list is installing Nvidia drivers on an encrypted install of Ubuntu 16.04. After installing the drivers it would no longer boot, so I could only encrypt my home folder.

This makes no sense, do you understand the actual cause enough to explain it?

I have no idea, its been a year or two since I fiddled with it. I think it just never made it to the login screen? I didn't need to have encrypted root so I didn't look into it too much.

I had the same problem, it has something to do with Plymouth, if you use the classic console boot it works

Oh, so you can still boot, they just don't support (or have broken support for) DRM_IOCTL_MODE_CREATE_DUMB.

But what does that have to do with encrypted root? Just plymouth not being available for the LUKS passphrase entry?

I'd expect you to be able to get around that fairly trivially by disabling plymouth, LUKS works without it in any initrd I've encountered.

That effectively is breaking the boot process. Of course, you may be able to tinker with it in order to make things work again, but you have to do that.

It's not a breakage specific to whole-fs encryption, which is what didn't make sense.

Reply on news.ycombinator.com