You are not logged in.
First, it's not easy to tell what's gone wrong from the journal:
~$ systemctl status systemd-modules-load.service
● systemd-modules-load.service - Load Kernel Modules
Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static; vendor preset: disabled)
Active: failed (Result: exit-code) since Mon 2016-12-12 09:43:36 SGT; 59min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Process: 1330 ExecStart=/usr/lib/systemd/systemd-modules-load (code=exited, status=1/FAILURE)
Main PID: 1330 (code=exited, status=1/FAILURE)
CPU: 2ms
Dec 12 09:43:36 teefour systemd[1]: Starting Load Kernel Modules...
Dec 12 09:43:36 teefour systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Dec 12 09:43:36 teefour systemd[1]: Failed to start Load Kernel Modules.
Dec 12 09:43:36 teefour systemd[1]: systemd-modules-load.service: Unit entered failed state.
Dec 12 09:43:36 teefour systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.I could swear this used to work. Why did it break?
~$ sudo /usr/lib/systemd/systemd-modules-load
Failed to find module 'vboxdrv'
Failed to find module 'vboxpci'
Failed to find module 'vboxnetadp'
Failed to find module 'vboxnetflt'
~$ uname -a
Linux teefour 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/LinuxVirtualbox tells me to run:
sudo /sbin/vboxconfig
But I don't have such a binary on my system and I'm not sure where it's packaged.
Last edited by hendry (2016-12-13 03:47:08)
Offline
Is your system fully up-to-date? Please post the output of
pacman -Qs virtualboxEDIT: please also post the output of
uname -a; pacman -Q linuxSakura:-
Mobo: MSI MAG X570S TORPEDO MAX // Processor: AMD Ryzen 9 5950X @4.9GHz // GFX: AMD Radeon RX 5700 XT // RAM: 32GB (4x 8GB) Corsair DDR4 (@ 3000MHz) // Storage: 1x 3TB HDD, 6x 1TB SSD, 2x 120GB SSD, 1x 275GB M2 SSD
Making lemonade from lemons since 2015.
Offline
~$ pacman -Qs virtualbox
local/virtualbox 5.1.10-1
Powerful x86 virtualization for enterprise as well as home use
local/virtualbox-host-dkms 5.1.10-1
VirtualBox Host kernel modules sources
~$ uname -a; pacman -Q linux
Linux teefour 4.8.13-1-ARCH #1 SMP PREEMPT Fri Dec 9 07:24:34 CET 2016 x86_64 GNU/Linux
linux 4.8.13-1Offline
So... the dkms hook should have run after you upgraded the kernel. But what I want to know is, why don't you use the binary modules which are built against the stock kernel? You only need the dkms version if you are using a non-repo kernel!
Managing AUR repos The Right Way -- aurpublish (now a standalone tool)
Offline
Same happened to me. After pacman -Syu and restarting the system, systemd was showing a message that it failed to load the Virtualbox module on system startup. And indeed, Virtualbox did not work anymore. So I just triggered rebuilding of the dkms modules manually by
pacman -S linuxEt voilà, Virtualbox is working again.
Offline
I've moved to `local/virtualbox-host-modules-arch` & rebooted. Virtualbox now works again. Peace and harmony has been restored. Thanks guys,
Offline