Folks,
I'm having an issue with loading kernel modules after a kernel
update. Specifically I'm having an issue with loading virtual box
kernel modules. After an update I sign the modules according to the
information listed here
https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/kernel-module-driver-configuration/Working_with_Kernel_Modules/
After signing the modules and verifying them via
modinfo <module> | grep "^sig"
I reboot the system. After booting the system I run lsmod to check if
the modules have been loaded and they have not. I go check the modules
again and I find they are no longer signed.
I resign the modules and rather than rebooting I run insmod to install
them and this works.
Now I also have vmware installed on the system and I follow the exact
same procedure to sign the vmware kernel modules and reboot the system
and when I do an lsmod after rebooting the vmware modules are loaded.
I even tried rebuilding both the virtual box and vmware modules from
source, resigned all the modules and rebooted and again only the vmware
modules are loaded. The virtual box modules no longer show they are signed.
Can anybody tell me why the virtual box modules are no longer signed
after rebooting?
Any help is appreciated.
Paolo
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure
