this post was submitted on 05 Aug 2025
451 points (99.6% liked)
Greentext
6917 readers
1488 users here now
This is a place to share greentexts and witness the confounding life of Anon. If you're new to the Greentext community, think of it as a sort of zoo with Anon as the main attraction.
Be warned:
- Anon is often crazy.
- Anon is often depressed.
- Anon frequently shares thoughts that are immature, offensive, or incomprehensible.
If you find yourself getting angry (or god forbid, agreeing) with something Anon has said, you might be doing it wrong.
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
That secure boot password was probably from akmods preparing its key so that it can sign the kernel module of the driver. This key needs to be loaded into the UEFI to use the driver with secure boot enabled. It shouldn't affect the bit locker key in theory, but you never know...
No bitlocker on that one but it still complained.
Set bios to disable secure boot (warning check if you have bitlocker active before you do that) and install Linux w/o secure boot.
Otherwise, with secureboot: akmod will generate a new key for you and prepare it to be loaded into you UEFI. That key is password protected, which was the password you were asked for. Depending on your distro it might even get loaded automatically on reboot (just follow the menu and enter the password when asked) or you might need to initiate the load with mokutil and a reboot.
Afterwards, akmods will make sure your graphics driver is signed with the corresponding key that is now known and trusted by the UEFI and you can boot with secure boot enabled while still using self compiled kernel modules.
Problem is that kernel modules are seen as part of the kernel and everything must be signed with a key your UEFI trusts when using secure boot. And initially it’s Microsoft’s key, which you will not have access to when using custom kernels/kernel modules/… so you just create your own.