You are not logged in.
Hello everyone!
After upgrading my Arch i have trouble starting VirtualBox. I get this message "The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall the kernel module by executing: /sbin/rcvboxdrv setup". After executing the command I get:
Loading modules: modprobe: FATAL: Module vboxnetadp not found in directory /lib/modules/4.4.3-1-ARCH
modprobe: FATAL: Module vboxnetflt not found in directory /lib/modules/4.4.3-1-ARCH
modprobe: FATAL: Module vboxpci not found in directory /lib/modules/4.4.3-1-ARCH
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.4.3-1-ARCH
I tried running 'depmod 4.4.3-1-ARCH' but that didn't work.
Any suggestions how can i solve this?
Last edited by Tetrix (2016-03-11 17:12:09)
Offline
Please search before posting.
https://bbs.archlinux.org/viewtopic.php?id=209966
Closing, for deletion. Restored after it became apparent that there wasn't the same problem. Some posts will seem slightly odd due to them original being an a different topic, and merged back into this one.
Last edited by WorMzy (2016-03-11 15:50:51)
Sakura:-
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
I have the same problem. I have virtualbox-host-dkms and virtualbox-guest-dkms installed and also linux-headers are installed but the problem is still here.
Offline
I have the same problem. I have virtualbox-host-dkms and virtualbox-guest-dkms installed and also linux-headers are installed but the problem is still here.
Different problem then (and your other thread probably shouldn't have been dustbinned). From the info in the other thread, I'm guessing you've updated your kenrel but neglected to reboot.
Last edited by Scimmia (2016-03-11 13:17:23)
Offline
Tetrix wrote:I have the same problem. I have virtualbox-host-dkms and virtualbox-guest-dkms installed and also linux-headers are installed but the problem is still here.
Different problem then (and your other thread probably shouldn't have been dustbinned). From the info in the other thread, I'm guessing you've updated your kenrel but neglected to reboot.
I actually did 3 or 4 reboots today, so that's not the problem
Offline
What is the output of `uname -r` and `pacman -Q linux linux-headers`?
Offline
What is the output of `uname -r` and `pacman -Q linux linux-headers`?
The output of 'uname -r' is:
4.4.3-1-ARCH
The output of 'pacman -Q linux linux-headers' is:
linux 4.4.3-1
linux-headers 4.4.5-1
Offline
The output of 'pacman -Q linux linux-headers' is:
linux 4.4.3-1
linux-headers 4.4.5-1
Bingo. You did a partial update (pacman -Sy). This is unsupported. Update your entire system and the problem will go away.
Offline
Tetrix wrote:The output of 'pacman -Q linux linux-headers' is:
linux 4.4.3-1
linux-headers 4.4.5-1Bingo. You did a partial update (pacman -Sy). This is unsupported. Update your entire system and the problem will go away.
I am usually doing pacman -Syyu. I did it again and it says:
error: failed to commit transaction (conflicting files)
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.alias exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.alias.bin exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.builtin.bin exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.dep exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.dep.bin exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.devname exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.softdep exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.symbols exists in filesystem
linux: /usr/lib/modules/4.4.5-1-ARCH/modules.symbols.bin exists in filesystem
Sorry for my lack of understanding, I am new to Arch
Offline
It seems I was too hasty in dustbinning your thread. I'll restore it and split these posts off into it so as not to derail this thread.
As for your conflict errors, please see this link: https://wiki.archlinux.org/index.php/Pa … 9.22_error
Last edited by WorMzy (2016-03-11 15:52:58)
Sakura:-
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
Those files are generally owned by the "linux" package. Since you did a partial update and the corrrect "linux" package wasn't installed, the files didn't exist when the modules were installed and depmod created them. Now you've got a bunch of orphaned files in the way.
Short version: deleted them.
Offline
Those files are generally owned by the "linux" package. Since you did a partial update and the corrrect "linux" package wasn't installed, the files didn't exist when the modules were installed and depmod created them. Now you've got a bunch of orphaned files in the way.
Short version: deleted them.
I successfully upgraded and now the output of 'uname -r' is:
4.4.5-1-ARCH
and the output of '-Q linux linux-headers' is:
linux 4.4.5-1
linux-headers 4.4.5-1
They are all same version but the problem is still here
Offline
What exactly did you delete? Just the files listed? or the entire dir?
Offline
What exactly did you delete? Just the files listed? or the entire dir?
I renamed the files just like the ArchWiki suggested "rename the file which 'exists in filesystem' and re-issue the update command".
Offline
Hmm, so the modules should be there. As you didn't have the correct kernel at the time, though, something could easily have gone wrong with the module generation. Reinstall the linux-headers package to regenerate them.
Offline
Hmm, so the modules should be there. As you didn't have the correct kernel at the time, though, something could easily have gone wrong with the module generation. Reinstall the linux-headers package to regenerate them.
I reinstalled them but the problem is still here. I also deleted the renamed files.
Last edited by Tetrix (2016-03-11 17:10:06)
Offline
What is the exact error when you modprobe them?
Offline
What is the exact error when you modprobe them?
I run '/sbin/rcvboxdrv setup' again and now the VirtualBox is working again. Thank you very much for the help, I owe you a beer
Offline
I don't think that was a good solution, but if it worked, ok. For anyone coming across this thread looking for help, don't do that.
Edit: oh, it's just a script that runs modprobe. I guess it's harmless.
Last edited by Scimmia (2016-03-11 17:15:49)
Offline
I successfully upgraded and now the output of 'uname -r' is:
4.4.5-1-ARCH
and the output of '-Q linux linux-headers' is:
linux 4.4.5-1
linux-headers 4.4.5-1They are all same version but the problem is still here
What the following command reports?
#/sbin/rcvboxdrv setup
If it complains about missing modules, have you tried to run
#dkms autoinstall
What is the result?
-----
Ooops, wrote my answer way too slow!
Last edited by hb860 (2016-03-11 17:28:45)
Offline
Was the same issue.
have installed:
linux-lts-4.1.19-1
linux-lts-headers-4.1.19-1
linux-4.4.5-1
linux-headers-4.4.5-1
all work doing under non-lts version
today updates break vbox modules to start
trying reinstalling virtualbox-host-dkms, but it build modules only for lts-version
after reinstalling linux-headers, hook was executed and succesfully build modules versions for non-lts version.
now all work fine.
Offline