this post was submitted on 28 Oct 2025
502 points (98.5% liked)
Linux Memes
996 readers
1 users here now
A community for posting memes relating to linux!
Also check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Sounds representative, it didn't even try to stop you!
Everyone else is saying secure boot should be correct. I was unable to load my nvidia driver until disabling secure boot, but I luckily had integrated graphics. What I think happened is you switched to to nvidia drivers that required proper secure boot before it would load. The drivers that are loaded before that don't require secure boot to be setup so that's why you had an output.
This is just an nvidia thing unfortunately.
lol, yes. Thank you I disabled secureboot and it boots ok now. Thanks for the feedback it does help understanding a bit about how this all works. If that wasn't obvious enough I'm a big noob with Linux.
Anyway, can I leave secureboot disabled and be fine? or is this MOK business something I should solve right now?
Thanks again
My understanding is secure boot is kinda worthless so it's not that important to sort out. It let's the bios trust the OS but that is a fairly limited attack vector. I don't know enough about it though, so feel free to enroll the MOK keys bc it's not that hard tbh, just annoying
Ok thank you! I'd do it but I don't fully understand the implications. Can I for instance re-generate a MOK key from whatever distro I install next and use that?
I believe so. You just enroll the new keys and then you're good
oh alright. I'll try it. I must have missed a step in the tutorial the first time, or mistyped something... Cheers,