Virtualbox 5&6 - MX/antiX kernel conflicts [SOLVED]

[manyroads]

So here is what I get... not good news. :lipsrsealed:

Code: Select all

mark@mark-dell:~
$ sudo dpkg-reconfigure virtualbox-dkms

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 6.0.6
Kernel:  4.19.0-1-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-1-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-1-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-1-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxpci.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-1-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod...

DKMS: uninstall completed.

------------------------------
Deleting module version: 6.0.6
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-6.0.6 DKMS files...
Building for 4.19.0-1-amd64 5.0.0-14.1-liquorix-amd64
Building initial module for 4.19.0-1-amd64
Done.

vboxdrv:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-1-amd64/updates/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-1-amd64/updates/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-1-amd64/updates/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/4.19.0-1-amd64/updates/

depmod...

DKMS: install completed.
Building initial module for 5.0.0-14.1-liquorix-amd64
Error! Bad return status for module build on kernel: 5.0.0-14.1-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/6.0.6/build/make.log for more information.
[....] Unloading VirtualBox kernel modules... vboxnetadp vboxnetflt vboxpci vbox[ o. 
[....] Loading VirtualBox kernel modules... vboxdrv vboxnetflt vboxnetadp vboxpc[.ok 

Here's the make.log

make.log

[Stevo]

But I get this with the same package and kernel:

Code: Select all

 sudo dpkg-reconfigure virtualbox-dkms

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 6.0.6
Kernel:  5.0.0-14.1-liquorix-amd64 (x86_64)
-------------------------------------

Status: Before uninstall, this module version was ACTIVE on this kernel.

vboxdrv.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-14.1-liquorix-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetadp.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-14.1-liquorix-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxnetflt.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-14.1-liquorix-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.


vboxpci.ko:
 - Uninstallation
   - Deleting from: /lib/modules/5.0.0-14.1-liquorix-amd64/updates/
 - Original module
   - No original module was found for this module on this kernel.
   - Use the dkms install command to reinstall any previous module version.

depmod.......

DKMS: uninstall completed.

------------------------------
Deleting module version: 6.0.6
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-6.0.6 DKMS files...
Building for 5.0.0-14.1-liquorix-amd64
Building initial module for 5.0.0-14.1-liquorix-amd64
Done.

vboxdrv:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.0.0-14.1-liquorix-amd64/updates/

vboxnetadp.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.0.0-14.1-liquorix-amd64/updates/

vboxnetflt.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.0.0-14.1-liquorix-amd64/updates/

vboxpci.ko:
Running module version sanity check.
 - Original module
   - No original module exists within this kernel
 - Installation
   - Installing to /lib/modules/5.0.0-14.1-liquorix-amd64/updates/

depmod...

[manyroads]

But I get this with the same package and kernel:

Code: Select all

 sudo dpkg-reconfigure virtualbox-dkms[...]

I have no idea why things after 4.19 do not like my PC...

[Stevo]

Your make.log is very odd

Code: Select all

make: Entering directory '/usr/src/linux-headers-5.0.0-14.1-liquorix-amd64'
arch/x86/Makefile:179: CONFIG_X86_X32 enabled but no binutils support
./scripts/gcc-version.sh: line 26: gcc: command not found
./scripts/gcc-version.sh: line 27: gcc: command not found
make: gcc: Command not found
make: gcc: Command not found
make: gcc: Command not found
make: gcc: Command not found
Can't exec "gcc": No such file or directory at /usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation)
  CC [M]  /var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/linux/SUPDrv-linux.o
/bin/sh: 1: gcc: not found
scripts/Makefile.build:276: recipe for target '/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/linux/SUPDrv-linux.o' failed

I don't know why it's looking for x86 and X32 there, but it can't find the correct gcc compiler for that architecture, which is correct--you have amd64.

[JayM]

You probably have remnants of all the VB attempted installations all over the place on your system now, that are interfering with each other. I suggest you do a removal and purge in apt of everything VB-related, then do a file system search and manually delete or rename everything that has to do with VB that's still there (except of course any virtual machines in $HOME that you want to keep), reboot, then install from the repo.

[manyroads]

You probably have remnants of all the VB attempted installations all over the place on your system now, that are interfering with each other. I suggest you do a removal and purge in apt of everything VB-related, then do a file system search and manually delete or rename everything that has to do with VB that's still there (except of course any virtual machines in $HOME that you want to keep), reboot, then install from the repo.

I scrubbed all the old stuff manually... I did as you suggested several times.

[manyroads]

Your make.log is very odd

Code: Select all

make: Entering directory '/usr/src/linux-headers-5.0.0-14.1-liquorix-amd64'
arch/x86/Makefile:179: CONFIG_X86_X32 enabled but no binutils support
./scripts/gcc-version.sh: line 26: gcc: command not found
./scripts/gcc-version.sh: line 27: gcc: command not found
make: gcc: Command not found
make: gcc: Command not found
make: gcc: Command not found
make: gcc: Command not found
Can't exec "gcc": No such file or directory at /usr/share/perl5/Dpkg/Arch.pm line 165.
dpkg-architecture: warning: cannot determine CC system type, falling back to default (native compilation)
  CC [M]  /var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/linux/SUPDrv-linux.o
/bin/sh: 1: gcc: not found
scripts/Makefile.build:276: recipe for target '/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/linux/SUPDrv-linux.o' failed

I don't know why it's looking for x86 and X32 there, but it can't find the correct gcc compiler for that architecture, which is correct--you have amd64.

I know... I don't understand that either. Let me know which gcc I should have and I'll delete every other one I find.

[Stevo]

I wouldn't touch gcc with a 10 meter pole. I don't think that's the problem, but am stumped.

I do have the 5.2.28 virtualbox packages figured out and building, as well as finished the updated guest-additions-iso and ext-pack installer packages. The ext-pack required I update the sha256 hash for the downloaded file, plus check to make sure the license auto-sign key was still the same by manually downloading and agreeing, but those are sorted.

[timkb4cq]

I would re-install build-essential just to be sure something isn't missing/corrupted.
It should bring in everything required to build those modules.

[manyroads]

I wouldn't touch gcc with a 10 meter pole. I don't think that's the problem, but am stumped.

I do have the 5.2.28 virtualbox packages figured out and building, as well as finished the updated guest-additions-iso and ext-pack installer packages. The ext-pack required I update the sha256 hash for the downloaded file, plus check to make sure the license auto-sign key was still the same by manually downloading and agreeing, but those are sorted.

It does seem peculiar that it works for 4.19 but nothing newer.