I’ve seen this warning in the Ubuntu docs. Can someone explain exactly why a GPU driver would cause issues with disk encryption and UEFI boot?
I’ve seen this warning in the Ubuntu docs. Can someone explain exactly why a GPU driver would cause issues with disk encryption and UEFI boot?
[1] https://askubuntu.com/questions/1023036/how-to-install-nvidi...
Of course the low-quality binary blobs Nvidia ships can always contain some annoying bugs, so maybe this was fixed already and the author is just cautious or maybe I will run into those problems eventually.
I don't think it's a problem with the current iterations of Nvidia/Linux, though.
As for what can cause the problem, I have several ideas:
- Secure boot and code verification breaking driver loading
- The Nvidia driver, loaded during early startup, freaking out about config files not existing
- Some kind of handover problem between the fallback VGA driver and the proprietary blob that wouldn't exist if the boot files would be available from the bootloader directly
- Nvidia is known to track boot state in their GPU firmware (one way they used to prevent virtualizing consumer GPUs) so it could be related to a second attempt to initialize the GPU
Unencrypted boot leaves me vulnerable to a malicious actor taking my laptop, modifing grub and/or linux kernel to send and/or store my password to unlock the boot volume and then handing my laptop back and me typing in my un-lock password
Possible, but I view that threat as low
The issue I have seen is that a LOT of BIOS (at least on desktop machines) seem to just let you reset the secure boot enforcement status via the BIOS reset jumper... which defeats the point although it does raise the physical access requirement to a longer duration.