You are not logged in.
Solution: After installing virtualbox one should reboot their system.
After getting the "The vboxdrv kernel module is not loaded." error I run the suggested command, but it did not exist, there was no such file in the suggested location.
After running around with my head cut off I managed to find some dkms inconsistencies that I'm not too knowledged about to understand fully. I would guess the issue might lie in not having actual locations for "5.18.11-arch1-1" kernel, but then shouldn't /sbin/vboxconfig exist to help with that? (I'm making a lot of assumptions here.)
~]$ ls /usr/lib/modules/
5.15.55-1-lts 5.18.12-arch1-1Here are the
virtualbox errors:
~]$ virtualbox
WARNING: The vboxdrv kernel module is not loaded. Either there is no module
available for the current kernel (5.18.11-arch1-1) or it failed to
load. Please recompile the kernel module and install it by
sudo /sbin/vboxconfig
You will not be able to start VMs until this problem is fixed.
^C
~]$
~]$ sudo /sbin/vboxconfig
sudo: /sbin/vboxconfig: command not found
~]$
~]$ ls /sbin | grep vbox*
rcvboxdrv
vboxballoonctrl
vboxheadless
vboximg-mount
vboxmanage
vboxreload
vboxsdl
vboxwebsrvdkms errors:
~]$ dkms status
vboxhost/6.1.34_OSE, 5.18.11-arch1-1, x86_64: built
vboxhost/6.1.34_OSE, 5.18.12-arch1-1, x86_64: installed
~]$ sudo dkms autoinstall
Error! The directory /usr/lib/modules/5.18.11-arch1-1 doesn't exist.
You cannot install a module onto a non-existant kernel.
~]$ pacman -Q | grep headers
linux-api-headers 5.17.5-2
linux-headers 5.18.12.arch1-1
linux-lts-headers 5.15.55-1Thanks for any help!
Last edited by Mater (2022-07-19 00:53:49)
Offline
Have you rebooted since upgrading the kernel? Was your /boot partition mounted when you upgraded the kernel?
Last edited by skunktrader (2022-07-19 00:08:57)
Offline
Have you rebooted since upgrading the kernel? Was your /boot partition mounted when you upgraded the kernel?
bruh
thx love
Last edited by Mater (2022-07-19 00:43:18)
Offline