Hi, VirtualBox does not longer work after upgrade from F41 to F42 (and Secure Boot enabled). I have installed it from rpmfusion repository. In F41, at each kernel upgrade I had to sign again the modules (vboxdrv, vboxnetadp and vboxnetflt) using a private key enabled in EFI by means of mokutil tool,…

Yes, I have used dnf system-upgrade to upgrade Fedora from 41 to 42 release. After executing depmod -ae and rebuilding VirtualBox module (akmods --rebuild), now the vboxdrv module is loaded wihtout error. Thank you. CONCLUSION if using self-signed modules, the solution is to add proper flags to…

After upgrade to F42, I cannot load VirtualBox drivers signed modules in the kernel (SecureBoot)

Ask Fedora

leigh123linux (Leigh Scott) April 19, 2025, 4:28pm 14

The decompression issue was fixed a while back in kmodtool, does dkms also compress the modules?

Cant boot kernel 6.14.x on Fedora 41 machine with zfs disks

Topic		Replies	Views
Problem using signed kernel module Ask Fedora f29	1	1434	May 10, 2019
Virtualbox not working Ask Fedora f38 , virtualization , virtualbox	30	7344	September 10, 2023
Trouble signing kernel modules for Virtualbox Ask Fedora f34	2	7062	September 15, 2021
Virtualbox vboxdrv kernel module not loaded Ask Fedora f34 , kernel	12	21585	March 15, 2022
VMware kernel module updater; fedora 36 Ask Fedora f36 , vmware	2	3926	April 27, 2022

After upgrade to F42, I cannot load VirtualBox drivers signed modules in the kernel (SecureBoot)

Related topics