-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module not starting at boot time on a system with secureboot enabled #210
Comments
Fixed the problem. Because I have secureboot enabled, I had to create two keys called Then I just needed to run the Step-by-step:Ensure you have openssl and mokutil installed, then run:
Insert a passphrase two times, and then reboot to enroll that key. If you run
Then go to the |
Hi,
|
It seems DKMS updated, this should do it: Step-by-step:Step 1Ensure you have openssl and mokutil installed, then run:
OBS: By default DKMS searches for a key pair called mok.key and mok.pub at Step 2
Insert a passphrase two times, and then reboot to enroll that key. Step 3If you run
After that you can run the OBS: you don't need to change anything in the |
About Ubuntu not loading, I'm not sure what happened there. I think you can go into your BIOS and clear all the keys saved and then try again. Let me know if you are still having problems. |
Thanks a lot! Ubuntu still doesn't load, I can only enter recovery mode to access the root shell prompt, so I did this:
still ubuntu HMI doesn't load (I only get a blinking "_") |
This doesn't seem to be related to enrolling the key, but I'm not sure what happened. If you can enter recovery mode, I think this means you can get to grub. Have you done anything else before trying to enroll the key the first time? Like a System Update or something? Have you tried booting on an older kernel to see if it works? Usually there is the option to boot on previous kernel versions on grub. |
I'm using Fedora 36 (kernel 5.18.5-200.fc36.x86_64) and have compiled the driver. It works fine, but even after running
deploy.sh
the kernel module does not seems to start at boot time, so I have to runinsmod 88x2bu.ko
every time I boot my system.Edit: I was able to start the module by running
insmod 88x2bu.ko
because I had signed that file, but I didn't knew that dkms wasn't installing that same file that I had signed, it was compiling a new module and wasn't signing itThe text was updated successfully, but these errors were encountered: