RTR3InitEx failed with rc=-1912 (rc=-1912)

[Ralf Mardorf]

On Fri, 22 Jan 2021 11:33:02 -0800, Bob wrote:
>On 2021-01-22 10:41, Ralf Mardorf via ubuntu-users wrote:
>
>> Is the package "dkms" installed?
>> 
>> If so run
>> 
>>   dkms status  
>
>robert at MARS:~$ dkms status
>virtualbox, 6.1.14, 5.8.0-36-generic, x86_64: installed
>virtualbox, 6.1.14, 5.8.0-38-generic, x86_64: installed
>virtualbox, 6.1.14, 5.8.0-40-generic, x86_64: installed
>robert at MARS:~$
>
>So it appears that a VirtualBox update did not update everything that 
>was necessary.
>
>VirtualBox shows it is at "6.1.16_Ubuntu r140961"
>
>How to fix this?  I am running Ubuntu 20.10.

Modules could be in different locations.

On Arch Linux the Virtualbox modules are in
/lib/modules/KERNEL_VERSION/kernel/misc/ .

On Ubuntu it might be a different place, but it's likely
/lib/modules/KERNEL_VERSION/kernel/SOMEWHERE or
/lib/modules/KERNEL_VERSION/SOMEWHERE .

IOW if needed you could run

 sudo rm -i /PATH_AS_MENTIONED_ABOVE/vbox*

but first try removing them using dkms, since when running rm, you
might need to rm also something in a place such as maybe /var/lib/dkms/
(on Arch Linux, might be different on Ubuntu ;).

The dkms command likely is

 sudo dkms remove virtualbox/6.1.14 --all

(JFTR for Oracle it probably would be

sudo dkms remove vboxhost/6.1.14_non_OSE --all)

To build the kernels reinstall the Virtualbox package/s, since Oracle
might not build using dkms and from Ubuntu repositories they
automatically should get build using dkms.

Probably the modules were kept by removing the Virtualbox
package/s without the --purge option. Maybe they would be even kept,
when purging. I still have no idea why upgrading from official
repositories should cause a version mismatch. I only could imagine a
a package remove issue, but not an issue related to a full-upgrade.