4 ms·
n=1, but I've run fully-encrypted and /boot-encrypted Linux installs with the proprietary Nvidia-drivers without any issues. Of course the low-quality binary b
by jeroenhd 5y ago
n=1, but I've run fully-encrypted and /boot-encrypted Linux installs with the proprietary Nvidia-drivers without any issues.
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
- ltbarcly3 5y agoI've used both for years without any issues, so I'm also confused on this one.