Arch Linux

cuteclown

Guest

Failed to start Load Kernel Modules

At boot, I a message that looks like an error:

[FAILED] Failed to start Load Kernel Modules.

However, the system succesfully boots after that, and everything seems to work as expected. I still want to get rid of the error. I have found others with similar issues, but usually the system won't boot at all. I have this problem consistently across different systems (in virtualbox, on a BIOS system, and on a UEFI system).

The modules look like they belong to virtualbox. I do have the virtualbox package installed, but removing it does not solve the problem.

In the output of

journalctl -xb

I found the following lines:

-- Subject: Unit systemd-tmpfiles-setup.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-tmpfiles-setup.service has begun starting up.
Sep 04 21:20:58 T410 systemd-modules-load[427]: Failed to find module 'vboxdrv'
Sep 04 21:20:58 T410 systemd-modules-load[427]: Failed to find module 'vboxpci'
Sep 04 21:20:58 T410 systemd-modules-load[427]: Failed to find module 'vboxnetadp'
Sep 04 21:20:58 T410 systemd-modules-load[427]: Failed to find module 'vboxnetflt'
Sep 04 21:20:58 T410 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Sep 04 21:20:58 T410 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Sep 04 21:20:58 T410 systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-modules-load.service has failed.
-- 
-- The result is RESULT.
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0: autoconfig for ALC887-VD: line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:li>
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:    speaker_outs=0 (0x0/0x0/0x0/0x0/0x0)
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:    hp_outs=1 (0x1b/0x0/0x0/0x0/0x0)
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:    mono: mono_out=0x0
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:    dig-out=0x11/0x0
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:    inputs:
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:      Front Mic=0x19
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:      Rear Mic=0x18
Sep 04 21:20:58 T410 kernel: snd_hda_codec_realtek hdaudioC1D0:      Line=0x1a
Sep 04 21:20:58 T410 kernel: kvm: disabled by bios
Sep 04 21:20:58 T410 kernel: MCE: In-kernel MCE decoding enabled.
Sep 04 21:20:58 T410 kernel: input: HD-Audio Generic Front Mic as /devices/pci0000:00/0000:00:08.1/0000:27:00.3/sound/card1/input14
Sep 04 21:20:58 T410 kernel: input: HD-Audio Generic Rear Mic as /devices/pci0000:00/0000:00:08.1/0000:27:00.3/sound/card1/input15
Sep 04 21:20:58 T410 kernel: input: HD-Audio Generic Line as /devices/pci0000:00/0000:00:08.1/0000:27:00.3/sound/card1/input16
Sep 04 21:20:58 T410 kernel: input: HD-Audio Generic Line Out as /devices/pci0000:00/0000:00:08.1/0000:27:00.3/sound/card1/input17
Sep 04 21:20:58 T410 kernel: input: HD-Audio Generic Front Headphone as /devices/pci0000:00/0000:00:08.1/0000:27:00.3/sound/card1/in>
Sep 04 21:20:58 T410 kernel: EDAC amd64: Node 0: DRAM ECC disabled.
Sep 04 21:20:58 T410 kernel: EDAC amd64: ECC disabled in the BIOS or no ECC capability, module will not load.
                              Either enable ECC checking or force module loading by setting 'ecc_enable_override'.
                              (Note that use of the override may cause unknown side effects.)
Sep 04 21:20:58 T410 systemd[1]: Starting Load Kernel Modules...
-- Subject: Unit systemd-modules-load.service has begun start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-modules-load.service has begun starting up.
Sep 04 21:20:58 T410 systemd-udevd[340]: Process '/usr/bin/alsactl restore 0' failed with exit code 99.
Sep 04 21:20:58 T410 systemd-modules-load[433]: Failed to find module 'vboxdrv'
Sep 04 21:20:58 T410 systemd-modules-load[433]: Failed to find module 'vboxpci'
Sep 04 21:20:58 T410 systemd-modules-load[433]: Failed to find module 'vboxnetadp'
Sep 04 21:20:58 T410 systemd-modules-load[433]: Failed to find module 'vboxnetflt'
Sep 04 21:20:58 T410 systemd[1]: Started Create Volatile Files and Directories.
-- Subject: Unit systemd-tmpfiles-setup.service has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-tmpfiles-setup.service has finished starting up.
-- 
-- The start-up result is RESULT.
Sep 04 21:20:58 T410 systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Sep 04 21:20:58 T410 systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Sep 04 21:20:58 T410 systemd[1]: Failed to start Load Kernel Modules.
-- Subject: Unit systemd-modules-load.service has failed
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit systemd-modules-load.service has failed.
-- 
-- The result is RESULT.

Any help or clues to what's going on would be appreciated

loqs

Member

Registered: 2014-03-06

Posts: 19,113

Re: Failed to start Load Kernel Modules

Try working through Systemd#Investigating_systemd_errors
The above should help you determine which package if any provided the config that is trying to load those modules.
If it is a DKMS package did it build successfully for the loaded kernel?  If not does the kernel version match the version the package was built for?

cuteclown

Guest

Re: Failed to start Load Kernel Modules

Thanks for pointing me to the right place on the wiki! I know that it is excellent, but I often fail to find the right page.

The error was indeed caused by a version mismatch. I was running version 4.18.8, but /usr/lib/modules contained modules for 4.18.9. I solved this by re-installing the kernel with

sudo pacman -S linux

And now "uname -a" says I'm running 4.18.9

cuteclown

Guest

Re: Failed to start Load Kernel Modules

Hm, this worked for me on my desktop, but when I run my arch installation in virtualbox, I still have an error for the same modules. The kernel version do match this time, so I'm not sure what to try next. The four modules (vboxdrv, vboxpci, vboxnetadp, and vboxnetflt) are listen in /lib/modules-load.d/virtualbox-host-dkms.conf.

If it is a DKMS package did it build successfully for the loaded kernel?

I'm not sure what this means, and how I can check this...

Last edited by cuteclown (2018-10-05 14:39:37)

loqs

Member

Registered: 2014-03-06

Posts: 19,113

Re: Failed to start Load Kernel Modules

Dynamic_Kernel_Module_Support

Raynman

Member

Registered: 2011-10-22

Posts: 1,539

Re: Failed to start Load Kernel Modules

When you run Arch as a guest OS in VirtualBox, you should not be loading the host modules.

cuteclown

Guest

Re: Failed to start Load Kernel Modules

When you run Arch as a guest OS in VirtualBox, you should not be loading the host modules.

I want to be able to use the guest OS as a host OS as well, and I think that it is appropriate to install the virtualbox package on the guest OS in this case.

Last edited by cuteclown (2018-10-06 16:50:36)

loqs

Member

Registered: 2014-03-06

Posts: 19,113

Re: Failed to start Load Kernel Modules

You want to nest virtualization meaning arch would be a guest of some other OS that is running on bare metal but it would be the host for some other guest?
Or do you mean you want to use the same system on bare metal as a host and as a guest of some other OS?

cuteclown

Guest

Re: Failed to start Load Kernel Modules

You want to nest virtualization meaning arch would be a guest of some other OS that is running on bare metal but it would be the host for some other guest?
Or do you mean you want to use the same system on bare metal as a host and as a guest of some other OS?

I have an install script which I can use to install and configure Arch. This script installs a lot of applications that I use, including virtualbox. I use this script on my laptop, desktop, and in a virtualbox image (mainly to test it). So I have an Arch Linux instance which is the guest OS, but potentially also a host OS (even though I don't really use it as such).

Anyway, I was wrong in my second last post: Installing the linux package does not solve the problem. Installing the linux headers solved my problem:

sudo pacman -Syu linux-headers

This is indeed pointed out in the wiki entry on DKMS. Thanks for the help everyone (and especially loqs)

Last edited by cuteclown (2018-10-08 19:59:09)