[Solved] virtualbox 5.2 (upgrade error) RTR3InitEx failed with rc=-1912 (rc=-1912)

[VirtualYerong]

On ubuntu 16.04,
I met RTR3InitEx failed with rc=-1912 (rc=-1912) when I upgrade virtualbox 5.2.4 to 5.2.6:

virtualbox.png (39.85 KiB) Viewed 14137 times

I downloaded the virtualbox 5.2.6 from official link and I found the official deb is NOT installing virtualbox-qt or virtualbox-dkms anymore though the first time I installed virtualbox it apparently did..

Code: Select all

# Following command installs 5.2.6 while does not install virtualbox-qt or virtualbox-dkms
sudo apt install ./virtualbox-5.2_5.2.6-120293_Ubuntu_xenial_amd64.deb

While installing the fork 5.0 verstion from command line installs virtualbox-qt and virtualbox-dkms automatically:

Code: Select all

# Following command installs virtualbox 5.0
$ sudo apt install virtualbox
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following package was automatically installed and is no longer     required:
  libsdl-ttf2.0-0
Use 'sudo apt autoremove' to remove it.
The following additional packages will be installed:
  virtualbox-dkms virtualbox-qt
Suggested packages:
  vde2 virtualbox-guest-additions-iso
The following packages will be REMOVED:
  virtualbox-5.2
The following NEW packages will be installed:
  virtualbox virtualbox-dkms virtualbox-qt

this strategy sudo apt install virtualbox works well comparatively with support of virtualbox-qt and virtualbox-dkms while I still wants to install 5.2.6 which is the latest version. So basically I prefer not to follow suggestions in the post https://askubuntu.com/questions/900794/ ... 12-rc-1912(which installs the virtualbox 5.0)

It seems this RTR3InitEx failed with rc=-1912 (rc=-1912) error is typical. Any ideas on how to fix this?

[socratis]

Why do you care what gets installed or not? VirtualBox does not need DKMS, and relies on your system's Qt libraries.

Uninstall/delete/purge whatever VirtualBox you have, anything that starts with "Virtual*", "VBox*", "VM*". Reboot.

Install the official version. Done.

[VirtualYerong]

But I mean the problem here is if I install the 5.2.6 virtual then RTR3InitEx failed with rc=-1912 (rc=-1912) error pops out when I start a VM.

Do you know how to deal with this?

[socratis]

I told you already 4 times. Clean up your system!
Did you even read the whole message? You are mixing versions, the Ubuntu one, and the official one.

[VirtualYerong]

Sorry for being careless, I tried to clean up the system with:

Code: Select all

sudo apt purge virtualbox*
sudo rm ~/"VirtualBox VMs" -Rf
 sudo rm ~/.config/VirtualBox/ -Rf
sudo apt  autoremove
# then reboot

Then I rebooted.
After that I install the VB 5.2.6 with command:

Code: Select all

sudo apt install ./virtualbox-5.2_5.2.6-120293_Ubuntu_xenial_amd64.deb

But same error pops out:

virtualbox.png (39.85 KiB) Viewed 14130 times

My dpkg -l virtualbox* | grep ^i output:

Code: Select all

$ dpkg -l virtualbox* | grep ^i
ii  virtualbox-5.2                 5.2.6-120293~Ubuntu~xenial amd64        Oracle VM VirtualBox

I told you already 4 times. Clean up your system!
Did you even read the whole message? You are mixing versions, the Ubuntu one, and the official one.

[VirtualYerong]

I finally fixed this problem with the help of this post: https://askubuntu.com/questions/250573/ ... virtualbox

(Previously I signed the virtualbox with MOK manager )
My modinfo vboxdrv still outputs 5.0 for I installed the fork virtualbox once in a while:

Code: Select all

modinfo vboxdrv

Then we need to delete the modules because I did not like the fact that they were in the dkms folder, there are two steps for doing this:
1. Unload the kernel modules

Code: Select all

sudo rmmod vboxnetadp vboxnetflt vboxpci vboxdrv

2.Delete the module files from /lib/modules/(kernelversion)-generic/updates/dkms, since these vbox* is affecting your latest version of virtualbox (5.1 or later), they should be in misc folder rather than dkms folder.

Code: Select all

sudo -i
# cd /lib/modules/(kernelversion)-generic/updates/dkms
# rm vbox*

After two steps above, run

Code: Select all

sudo /sbin/rcvboxdrv setup

Now modinfo vboxdrv outputs the latest version.
So this means to cleanup virtualbox 5.0 we need these special steps for the reason that modules are relocated.

[socratis]

I wonder if it's the DKMS that was pretty much forcing your system to keep the old version drivers, even if you were trying to remove them...

Thanks for the feedback and thank you for marking it as [Solved]...