Quote:
Originally Posted by ferrari
|
Would this help?
Quote:
Check if virtualbox-dkms is installed:
If yes, then delete it and install dkms
|
Should I go ahead with this below?
Code:
dpkg -l | grep virtualbox-dkms
sudo apt-get purge virtualbox-dkms && \
sudo apt-get install dkms
Rebuild VirtualBox kernel modules:
sudo /sbin/vboxconfig
Perhaps a case of two separate versions of VirtualBox installed being on my system? What happens to all my vm's if I did this below?:
Code:
sudo apt-get autoremove 'virtualbox*'
checked to see if I have vbox modules loaded:
Code:
──╼ $lsmod | grep vbox
vboxnetadp 28672 0
vboxnetflt 32768 0
vboxdrv 561152 2 vboxnetadp,vboxnetflt
checked to see if correct version below:
Code:
modinfo vboxdrv
filename: /lib/modules/6.0.0-2parrot1-amd64/updates/dkms/vboxdrv.ko
version: 6.1.40_Parrot r154048 (0x00320000)
license: GPL
description: Oracle VM VirtualBox Support Driver
author: Oracle Corporation
srcversion: 013A6B9C7C5CF3C51AF1D12
depends:
retpoline: Y
name: vboxdrv
vermagic: 6.0.0-2parrot1-amd64 SMP preempt mod_unload modversions
parm: force_async_tsc:force the asynchronous TSC mode (int)
Should I remove modules in the dkms folder? Maybe VB 6.1.50 and older places modules in misc while VB 7.0 stores them in dkms folder?
Maybe a case of vb being 32-bit architecture while running 64-bit operation system which can be the cause of this problem? I installed via Oracle site, does it site feed the correct download automatically detecting your 64 bit machine?
Am I meant to be loading any new modules into the kernel. Which kernels which modules?
If the old vboxdrv mod does not get removed with sudo apt autoremove --purge virtualbox*
then I'll have to remove it manually via vboxdrv.ko from "/lib/modules/$(uname -r)/updates/dkms/".r)/updates/dkms/".
I will need your help doing that so as to not dig myself into a deeper hole.