-
|
When secure boot is enabled, modules must be signed - otherwise the kernel will refuse to load them. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
For your convenience, the build system provides as Prerequisites
How to create and enroll a signing certificate is outside the scope of this document. Simple usagemake signThis assumes that the certificate/signing key are listed in Advanced usageYou can manually pass the signing key and certificate to the build process via the If the key (and/or certificate) require super-user proviliges to be read, run the build process through read -s -p "Passphrase for your signing key: " KBUILD_SIGN_PIN
export KBUILD_SIGN_PIN
sudo --preserve-env=KBUILD_SIGN_PIN \
make sign KBUILD_SIGN_CERT=/var/lib/shim-signed/mok/MOK.der KBUILD_SIGN_KEY=/var/lib/shim-signed/mok/MOK.priv |
Beta Was this translation helpful? Give feedback.
-
|
Hey man, could you help me install the module for a secure boot enabled fedora 42 KDE edition. I've read the manual, but i cannot figure it out. please. i was using your module no problems when i had secure boot disable, but recently i had to enable it for my dual boot, so i have to sign the module. I tried the fedora repo (sudo dnf install v4l2loopback) but OBS does not like that one for some reason. much appreciated |
Beta Was this translation helpful? Give feedback.
For your convenience, the build system provides as
signtarget.Prerequisites
How to create and enroll a signing certificate is outside the scope of this document.
For Debian systems (and probably others), check out the documentation:
Simple usage
This assumes that the certificate/signing key are listed in
/etc/dkms/framework.confasmok_certificateresp.mok_signing_key.It also assumes that these files are readable by the current user and do not require a password to unlock.
Advanced usage
You can manually pass the si…