On Mon, Jun 18, 2018 at 5:58 PM Ed Greshko <ed.greshko(a)greshko.com> wrote:
On 06/18/18 19:19, Sudhir Khanger wrote:
> I get *Failed to start Load Kernel Modules* during the boot.
> Everytime Kernel is updated VirtualBox modules fail I have to reboot
into the new
> Kernel, run the following commands and then it starts working.
> $ sudo akmods --force
> $ sudo dracut -v -f
> $ sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg
> Then everything starts working again and the boot error goes away. You
> the background of the issue in the link below.
You are using the VirtualBox packages from rpmfusion, yes?
I don't, but I seem to recall they operate differently than the packages
Oracle. The Oracle packages don't rely on akmod and don't put the
modules in the
initramfs. The vbox modules are checked for existence when
vboxdrv.service is run
and if they don't exist for the running kernel they are built at that time.
Assuming akmods is being used to build the modules when the kernel is
should be some sort of log file in /var/cache/akmods just like there is
Have you checked?
Also, have you considered asking about this on the rpmfusion user's list
since it is
Conjecture is just a conclusion based on incomplete information. It isn't
users mailing list -- users(a)lists.fedoraproject.org
To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Okay update time. Irrespective of where I install VirtualBox from if a new
kernel is installed then I have to manually create a new initramfs
otherwise systemd-modules-load.service fails at the boot.
sudo dracut -v -f