Virtualbox, artix-modules, kernel and headers, seem like a dog chasing its tail all the time. I'd say more than 50% of the time recently with upgrades applied vb doesn't work. I hate having to use the stupid thing but I am constantly testing new distros and installers, in case I find something as good as artix, obarun, void.
What if vb was built from arch-source and placed on the galaxy repository so only when the kernel and modules upgrade would be uploaded would a new version be applied. This way they would all constantly be a match. Or if somehow a dummy pkg or link can prevent a premature update, maybe?
I'm sorry I haven't managed to learn pkging yet so I can assist, and I have learned to manage holding things back or reverting something when it is incompatible but it is all this required rebooting to get the damn non-free thing to work that is annoying. It also will look bad for new users who haven't learned the trick.
Just a friendly suggestion for when there might be some free time to think about it.
Simple solution, use dkms.
We basically only have packaged modules for the iso releases.
There is no fixed maintainer for modules, and we usually skip uneven kernel releases.
DKMS didn't do anything for 6.0.0-1 a few weeks ago. I only use DKMS and had to downgrade VB back to 5.2.22-3 for a few weeks until everything sorted itself out (eventually)
See thread here (https://forum.artixlinux.org/index.php/topic,803.0.html)
If you use dkms from arch, I think, you also have to use the arch kernel/headers and follow it, instead of artix.
Basically it is like running arch with nothing to do with artix as far as VB is concerned. If you do so everything synchs. If kernel in arch changes to 4.21, headers too, then dkms modules, but artix is still on 4.20 for a few weeks (for a good reason because when those kernels go massively out for use all kinds of crap pops up) and you are using the artix kernel you break virtualbox.
Oh well, ,maybe I'll have to keep publishing a chart with the current combination of kernel, vb, and modules that work together.
Today is:
local/linux 4.20.2.artix1-1
local/linux-headers 4.20.2.artix1-1
local/virtualbox 6.0.0-3
local/virtualbox-guest-modules-artix 6.0.0-5
local/virtualbox-host-modules-artix 6.0.0-5
If you upgrade any of those now you will break virtualbox
Ok I'm flipping the DKMS modules to modules-artix to see how it goes.
Remind me not to do that again:
RTR3InitEx failed with rc=-1912 (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing
'/sbin/vboxconfig'
may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.
where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.
Back to the same error.
This is the combo I have working again:
virtualbox 6.0.0-3
virtualbox-guest-iso 6.0.0-1
virtualbox-host-dkms 6.0.0-3
linux 4.20.artix1-1
linux-headers 4.20.artix1-1
The guest additions are flaky and bomb out sometimes when doing clipboard operations but I can at least do everything else.
Did you reboot after you substituted the modules?
Always just to make sure the modules load cleanly.
I had to totally go back to 5.22. 6 is just too much of a regression right now. Guest additions constantly crashing. When they don't, bidirectional clipboard access no longer works (other things like shared local folders seem ok), video tearing and flashing....
6.0.2 is out, try this.
I use 6.0.2 and no problems:
virtualbox-ext-oracle 6.0.2-1
virtualbox-guest-dkms 6.0.2-1
virtualbox-guest-iso 6.0.2-1
virtualbox-host-dkms 6.0.2-1
linux-zen 4.20.3.zen2-1
I was on 6.0.2
This still holds true (last valid combination) for those using artix modules, if the kernel is upgraded to 4.20.4 vb will be broken.
Just an update
this broke on me today, my stupid fault though, so if you going to ignore kernel updates make sure you ignore linux-header updates as well ::)
New working combination with artix modules:
local/linux 4.20.4.artix1-1
local/linux-headers 4.20.4.artix1-1
local/virtualbox 6.0.2-1
local/virtualbox-guest-modules-artix 6.0.2-4
local/virtualbox-host-modules-artix 6.0.2-4
All current upgrades work:
local/linux 4.20.4.artix1-1
local/linux-headers 4.20.4.artix1-1
local/virtualbox 6.0.4-1
local/virtualbox-guest-modules-artix 6.0.2-4
local/virtualbox-host-modules-artix 6.0.2-4
Not for me. Just tried upgrading again this morning and back to the same error.
EDIT: Didn't see my kernel was updated. On 4.20.6-artix1-1-ARTIX
EDIT2:
The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing
'/sbin/vboxconfig'
may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.
where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.
linux 4.20.6.artix1-1
linux-headers 4.20.6.artix1-1
virtualbox 6.0.4-1
virtualbox-guest-iso 6.0.4-1
virtualbox-host-modules-artix 6.0.4-3
These are the only packages I have available to me because I missed the 6.0.2-4 packages and only have 6.0.2-1 left over from the previous attempts and don't see your combination available :-/
EDIT3: Yes I tried dkms as well.
linux 4.20.6.artix1-1
linux-headers 4.20.6.artix1-1
local/virtualbox 6.0.4-1
local/virtualbox-guest-modules-artix 6.0.4-3
local/virtualbox-host-modules-artix 6.0.4-3
This combination works fine in my system, I wonder what else can make the difference.
Dunno. I'm pretty vanilla. Artix + VirtualBox + Firefox + Google Chrome + Spotify + pamac (for the update notifications "ONLY". I do all the updates manually with pacman) + Nvidia DKMS. that's the only things I've added.
delete
5.2.22 for life I guess....... ::)
Nope, vbox works, just use dkms.
For dkms to work, you need to have base-devel group and the kernel headers installed.
I seriously don't get the trouble with dkms.
I have been using DKMS since I came over to Artix. The 6 branch of Virtualbox has not worked no matter what combination I use. Fungalnet had the good fortune of downloading the 2-4 packages which I didn't so no Virtualbox 6 for me as I only had older and newer versions and not the combination that worked for him. But now, it appears that he found that the new QT5 update borks it so I'm holding off again.
The previous error about qt5 was my mistake, the upgrade was done with qt5-base being held back, hence the incompatibility.
I tried to delete the comment but couldn't so I replaced it with "delete" for an admin to do it.
I tried with DKMS and it works as well.
local/virtualbox 6.0.4-1
local/virtualbox-host-dkms 6.0.4-1
local/linux 4.20.6.artix1-1 (base)
local/linux-headers 4.20.6.artix1-1
Ok I'll give it a whirl tomorrow. Thanks Fungalnet.
I don't know if it makes a difference in any dependencies but I use gremlins repositories.
Name : virtualbox
Version : 6.0.4-1
Depends On : glibc openssl curl gcc-libs libpng python sdl libvpx libxml2 procps-ng
shared-mime-info zlib libxcursor libxinerama libx11 libxext libxmu libxt opus
qt5-base qt5-x11extras VIRTUALBOX-HOST-MODULES
None of the above seem to come from gremlins now, but I'm not sure if their dependencies do. Just mentioning it in case we can locate the incompatibility difference.
That I'm not using. I only run from the stable repos so maybe the issues have been fixed but they're still in Gremlins?
Here goes nothing again:
Packages (3) virtualbox-6.0.4-1 virtualbox-guest-iso-6.0.4-1 virtualbox-host-dkms-6.0.4-1
Total Installed Size: 270.85 MiB
:: Proceed with installation? [Y/n] Y
(3/3) checking keys in keyring [##################################] 100%
(3/3) checking package integrity [##################################] 100%
(3/3) loading package files [##################################] 100%
(3/3) checking for file conflicts [##################################] 100%
(3/3) checking available disk space [##################################] 100%
:: Processing package changes...
(1/3) installing virtualbox-host-dkms [##################################] 100%
Optional dependencies for virtualbox-host-dkms
linux-headers: build modules against Arch kernel [installed]
linux-lts-headers: build modules against LTS kernel
linux-zen-headers: build modules against ZEN kernel
(2/3) installing virtualbox [##################################] 100%
Optional dependencies for virtualbox
vde2: Virtual Distributed Ethernet support
virtualbox-guest-iso: Guest Additions CD image [pending]
virtualbox-ext-vnc: VNC server support
virtualbox-sdk: Developer kit
(3/3) installing virtualbox-guest-iso [##################################] 100%
===> virtualbox-guest-iso post install message:
===>
===> Redistribution of VBoxGuestAdditions.iso from the binary packages
===> on www.virtualbox.org with Arch Linux has been granted by
===> InnoTek Systemberatung GmbH.
===>
===> By using this package you accept
===> the VirtualBox Personal Use and Evaluation License (PUEL)
===> which can be found here: http://virtualbox.org/wiki/VirtualBox_PUEL
===>
===> If you do not accept this license, you must remove the package immediately.
===>
:: Running post-transaction hooks...
(1/6) Install DKMS modules
==> dkms install vboxhost/6.0.4_OSE -k 4.20.6-artix1-1-ARTIX
(2/6) Updating icon theme caches...
(3/6) Updating system users and groups
(4/6) Reloading device manager configuration...
(5/6) Updating the desktop file MIME type cache...
(6/6) Updating the MIME type database...
Removed or moved all old config directories just in case as well.
And after the reboot:
[Wed Feb 6 10:19:15 2019] vboxdrv: loading out-of-tree module taints kernel.
[Wed Feb 6 10:19:15 2019] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel
[Wed Feb 6 10:19:15 2019] vboxdrv: Found 8 processor cores
[Wed Feb 6 10:19:15 2019] vboxdrv: TSC mode is Invariant, tentative frequency 2903997793 Hz
[Wed Feb 6 10:19:15 2019] vboxdrv: Successfully loaded version 5.2.22 (interface 0x00290001)
[Wed Feb 6 10:19:15 2019] VBoxNetFlt: Successfully started.
[Wed Feb 6 10:19:15 2019] VBoxNetAdp: Successfully started.
[Wed Feb 6 10:19:15 2019] VBoxPciLinuxInit
[Wed Feb 6 10:19:15 2019] vboxpci: IOMMU not found (not registered)
RTR3InitEx failed with rc=-1912 (rc=-1912)
The VirtualBox kernel modules do not match this version of VirtualBox. The installation of VirtualBox was apparently not successful. Executing
'/sbin/vboxconfig'
may correct this. Make sure that you do not mix the OSE version and the PUEL version of VirtualBox.
where: supR3HardenedMainInitRuntime what: 4 VERR_VM_DRIVER_VERSION_MISMATCH (-1912) - The installed support driver doesn't match the version of the user.
Back in the same hole.
Think I'm getting further:
cat /sys/modules/vboxdrv/version
5.2.22 r126257 (0x00290001)
It doesn't look like the modules were updated unless I'm just looking in the totally wrong place.
This is what the stack looks like now:
linux 4.20.6.artix1-1
linux-headers 4.20.6.artix1-1
dkms 2.5-4
virtualbox 6.0.4-1
virtualbox-guest-iso 6.0.4-1
virtualbox-host-dkms 6.0.4-1
dkms status
nvidia, 415.27, 4.20.6-artix1-1-ARTIX, x86_64: installed
vboxhost, 6.0.4_OSE, 4.20.6-artix1-1-ARTIX, x86_64: installed
Ok now the problem is completely beyond me. I totally purged anything to do with virtualbox and the kernel modules and verified by checking the whole file system for anything named vboxdrv,vboxpci,vboxnetadp & vboxnetflt and made sure there was nothing and rebooted. Reinstalled the virtualbox packages and rebooted again. When the machine was booting back up, I watched rc start loading kernel modules and saw both success and failures for the virtualbox modules. When it was finally back up I checked /sys/modules/vboxdrv and somehow the 5.2.22 r126257 (0x00290001) was loaded again!! I rmmoded all the modules and manually modprobed them back in and the correct versions loaded. How can I correct this now. It is the root of the problem and now virtualbox 6 works but I need to get the correct versioned modules loaded. Any ideas on how the old versions are getting added?
Ok you can mark this solved. The issue was self inflicted. I had manually added the modules to mkinitcpio.conf way back in the early Artix days because they weren't loading by themselves at the time. Once I removed them from mkinitcpio.conf and regenerated the config and rebooted, the proper modules loaded automagically.
I have the same kind of issues, just because I am using the LTS kernel. Currently 4.19.
Impossible to get the package virtualbox-host-modules-artix installed (non DKMS) because it is always depending on the last version of the kernel. Currently 4.20.
Because I use docker, I am forced (and I prefer) using LTS kernel.
So it forces you to install DKMS version for virtualbox-host-dkms.
and It NEVER works. NEVER.
In jaruary all of the sudden it worked on LTS. I was quite happy.
But this never lasts, and each time I want to quickly test an ISO, constantly I have to spend time to figure out about the DKMS mess for virtualbox.
Because in the meantime the LTS kernel was updated, & the DKMS gets broken.
Would it be diffcult to rebuild the package virtualbox-host-modules-artix on LTS kernel instead ?
Thx
Update:
I downgraded in my cache to the following version, and it worked (that version of January that actually worked on DKMS on LTS)
Check the cached packages of january:
ls -al /var/cache/pacman/pkg/virtualbox*
then
version=6.0.2-1
sudo pacman -U /var/cache/pacman/pkg/virtualbox-$version-x86_64.pkg.tar.xz /var/cache/pacman/pkg/virtualbox-host-dkms-$version-x86_64.pkg.tar.xz
then
modprobe vboxdrv
modprobe vboxnetadp
modprobe vboxnetflt
modprobe vboxpci
Obviously no need to reboot.
I am not sure, maybe just doing the following remove/install may be sufficient
dkms remove vboxhost/6.0.2_OSE -k 4.19.24-1-lts
dkms install vboxhost/6.0.4_OSE -k 4.19.24-1-lts
I will try next time there's a kernel update
I use no artix kernel, i use archlinux's linux-zen kernel, and newest virtualbox with dkms (virtualbox virtualbox-ext-oracle virtualbox-guest-dkms virtualbox-guest-iso virtualbox-host-dkms).
I have no problem with virtualbox and all works without any problems. You can try this soution too.
I can't.
as I said earlier.
Because I want to stick with the LTS kernel.
Because it is better when you use docker on your laptop like me.
It should still works with archlinux linux-lts and linux-lts-headers instead linux-zen ;-)
the most important word in your answer being "SHOULD".
:D
% virtualbox
/usr/lib/virtualbox/VirtualBox: error while loading shared libraries: libdouble-conversion.so.3.0.0: cannot open shared object file: No such file or directory
% pacman -Qs virtualbox
local/virtualbox 6.0.4-4
local/virtualbox-host-dkms 6.0.4-4
% pacman -Ss double-conversion
world/double-conversion 3.1.2-1 [installed]
double-conversion broke qt5-base, what is now fixed in qt5-base-5.12.1-2.1-x86_64. after update should all again work.
virtualbox depends on qt5-base