You are not logged in.
I installed Virtualbox and now want to remove it.
pacman -Qi virtualbox only listed virtualbox but, I seen virtualbox-host-modules-arch was also installed so I removed them:
# pacman -Rs virtualbox virtualbox-host-modules-arch
But, upon boot I get an error that says to enter this:
[cavsfan@ArchLinux ~]$ 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 Thu 2019-01-31 18:14:09 EST; 9min ago
Docs: man:systemd-modules-load.service(8)
man:modules-load.d(5)
Main PID: 516 (code=exited, status=1/FAILURE)
Jan 31 18:14:09 ArchLinux systemd[1]: Starting Load Kernel Modules...
Jan 31 18:14:09 ArchLinux systemd-modules-load[516]: Failed to find module 'vboxdrv'
Jan 31 18:14:09 ArchLinux systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE
Jan 31 18:14:09 ArchLinux systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
Jan 31 18:14:09 ArchLinux systemd[1]: Failed to start Load Kernel Modules.
I've been searching for the solution for quite a while and cannot find anything.
How do I get rid of this error?
Last edited by Cavsfan (2019-02-08 21:09:59)
Offline
It seems that you set vboxdrv to autoload by adding it to one of the module lists. Find the entry and remove it. It could be a kernel command line parameter in your boot loader or a module file in e.g. /etc/modules-load.d
The systemd service checks a number of places so it should be in one of the following (extract from the service file):
17 ConditionDirectoryNotEmpty=|/lib/modules-load.d
18 ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d
19 ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d
20 ConditionDirectoryNotEmpty=|/etc/modules-load.d
21 ConditionDirectoryNotEmpty=|/run/modules-load.d
22 ConditionKernelCommandLine=|modules-load
23 ConditionKernelCommandLine=|rd.modules-load
My Arch Linux Stuff • Forum Etiquette • Community Ethos - Arch is not for everyone
Offline
It seems that you set vboxdrv to autoload by adding it to one of the module lists. Find the entry and remove it. It could be a kernel command line parameter in your boot loader or a module file in e.g. /etc/modules-load.d
The systemd service checks a number of places so it should be in one of the following (extract from the service file):
17 ConditionDirectoryNotEmpty=|/lib/modules-load.d 18 ConditionDirectoryNotEmpty=|/usr/lib/modules-load.d 19 ConditionDirectoryNotEmpty=|/usr/local/lib/modules-load.d 20 ConditionDirectoryNotEmpty=|/etc/modules-load.d 21 ConditionDirectoryNotEmpty=|/run/modules-load.d 22 ConditionKernelCommandLine=|modules-load 23 ConditionKernelCommandLine=|rd.modules-load
I have a file in /etc/modules-load.d - /etc/modules-load.d/virtualbox.conf
It has one line:
vboxdrv
Nothing in the other locations.
So, should I just delete that virtualbox.conf file and rebuild the kernel?
Using mkinitcpio? Is there parameters I supply. I've seen it many times when a new kernel is installed but, do not remember exactly what it used.
I see this in /var/log/pacman.log:
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux.img
...
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux.img
==> Image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
-> -k /boot/vmlinuz-linux -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-fallback.img -S autodetect
...
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-fallback.img
==> Image generation successful
Since the kernel is the latest:
[cavsfan@ArchLinux ~]$ uname -r
4.20.6-arch1-1-ARCH
Would it be this to rebuild the kernel?
cd /var/cache/pacman/pkg/
# pacman -U linux-4.20.6.arch1-1-x86_64.pkg.tar.xz linux-headers-4.20.6.arch1-1-x86_64.pkg.tar.xz
I got that from how to downgrade packages but, I figured it should work to re-install the existing kernel.
Thanks for your help!
Offline
Offline
Just delete the virtualbox.conf file. That's it.
That did the trick. I thought it would be more complicated but, that worked great.
Thank you!
Offline
Please remember to mark your thread [SOLVED] (edit the title of your first post).
Offline