Welcome!

The kernel problem with recent updates has been solved. Find the solution here

Important information
-- Required MX 15/16 Repository Changes
-- Information on torrent hosting changes
-- Information on MX15/16 GPG Keys
-- Spectre and Meltdown vulnerabilities

News
-- Introducing our new Website
-- MX Linux on social media: here

Current releases
-- MX-18.3 Point Release release info here
-- Migration Information to MX-18 here
-- antiX-17.4.1 release info here

New users
-- Please read this first, and don't forget to add system and hardware information to posts!
-- Here are the Forum Rules

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

Report Bugs, Issues and non- package Requests
User avatar
manyroads
Forum Guide
Forum Guide
Posts: 1749
Joined: Sat Jun 30, 2018 6:33 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#11

Post by manyroads » Fri May 10, 2019 6:03 pm

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
You do not have the required permissions to view the files attached to this post.
Pax vobiscum,
Mark Rabideau - http://many-roads.com - Reg. Linux User #449130
bspwm MX-18.3 kernel: 5.1.11-antix.1-amd64-smp
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 19820
Joined: Fri Dec 15, 2006 8:07 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#12

Post by Stevo » Fri May 10, 2019 8:11 pm

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...


User avatar
manyroads
Forum Guide
Forum Guide
Posts: 1749
Joined: Sat Jun 30, 2018 6:33 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#13

Post by manyroads » Fri May 10, 2019 8:15 pm

Stevo wrote:
Fri May 10, 2019 8:11 pm
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... :bawling:
Pax vobiscum,
Mark Rabideau - http://many-roads.com - Reg. Linux User #449130
bspwm MX-18.3 kernel: 5.1.11-antix.1-amd64-smp
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 19820
Joined: Fri Dec 15, 2006 8:07 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#14

Post by Stevo » Fri May 10, 2019 8:18 pm

Your make.log is very odd :confused:

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.

User avatar
JayM
Forum Guide
Forum Guide
Posts: 1780
Joined: Tue Jan 08, 2019 4:47 am

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#15

Post by JayM » Fri May 10, 2019 8:24 pm

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.
Please read How To Ask For Help and How to Break Your System.
MX User Manual: hold down ALT and press F1. Further information may be found in the MX Wiki.

User avatar
manyroads
Forum Guide
Forum Guide
Posts: 1749
Joined: Sat Jun 30, 2018 6:33 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#16

Post by manyroads » Fri May 10, 2019 8:50 pm

JayM wrote:
Fri May 10, 2019 8:24 pm
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.
Pax vobiscum,
Mark Rabideau - http://many-roads.com - Reg. Linux User #449130
bspwm MX-18.3 kernel: 5.1.11-antix.1-amd64-smp
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

User avatar
manyroads
Forum Guide
Forum Guide
Posts: 1749
Joined: Sat Jun 30, 2018 6:33 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#17

Post by manyroads » Fri May 10, 2019 8:52 pm

Stevo wrote:
Fri May 10, 2019 8:18 pm
Your make.log is very odd :confused:

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. :lion:
Pax vobiscum,
Mark Rabideau - http://many-roads.com - Reg. Linux User #449130
bspwm MX-18.3 kernel: 5.1.11-antix.1-amd64-smp
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

User avatar
Stevo
Forum Veteran
Forum Veteran
Posts: 19820
Joined: Fri Dec 15, 2006 8:07 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#18

Post by Stevo » Fri May 10, 2019 8:59 pm

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.

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 5120
Joined: Wed Jul 12, 2006 4:05 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#19

Post by timkb4cq » Fri May 10, 2019 9:04 pm

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.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
manyroads
Forum Guide
Forum Guide
Posts: 1749
Joined: Sat Jun 30, 2018 6:33 pm

Re: Virtualbox 5&6 - MX/antiX kernel conflicts

#20

Post by manyroads » Fri May 10, 2019 9:05 pm

Stevo wrote:
Fri May 10, 2019 8:59 pm
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.
Pax vobiscum,
Mark Rabideau - http://many-roads.com - Reg. Linux User #449130
bspwm MX-18.3 kernel: 5.1.11-antix.1-amd64-smp
"For every complex problem there is an answer that is clear, simple, and wrong." H. L. Mencken

Post Reply

Return to “Bugs and Non-Package Requests Forum”