Not sure does this affect to fedora, but on openSUSE driver keys have changed and can’t sign kernel modules, well you can but drivers won’t be loaded… Development side it was stated out of the development scope
Signing the drivers (and importing the key into bios) is done by following the steps in the file /usr/share/doc/akmods/README.secureboot.
This is the guide when using drivers installed from the rpmfusion repo.
The signing key does not change once it has been created unless forced deliberately by removal and recreation or in the case of a reinstall.
Any time the key is changed in the OS the new key must be imported again into bios before secure boot is able to accept kernel modules. If the key in the OS does not match the key known to bios the signed modules will not be allowed to load.
Note that openSUSE will create its own key and it will not match the key from fedora. This means that modules created and signed in openSUSE will not load until the key for openSUSE is imported into bios. Similarly, modules created in fedora will not load until the key for fedora are imported into bios.
When dual booting the import of the local signing key must be done from within each discrete OS.
1 Like