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

[manyroads]

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.

I had done that earlier and now again...

Code: Select all

$ sudo apt install build-essential
[sudo] password for mark: 
Reading package lists... Done
Building dependency tree       
Reading state information... Done
build-essential is already the newest version (12.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

I'll update with any news...

Edit: Same error appears...

Code: Select all

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 

[Stevo]

Edit: corrected gcc version.

You can try a reinstall of the gcc packages

Code: Select all

sudo apt install --reinstall gcc-6 g++-6 cpp-6 gcc

But they worked fine for the other kernels. Stumped...

I think build-essential is a metapackage, so it won't force the reinstall of its dependencies if you reinstall it.

[manyroads]

You can try a reinstall of the gcc packages

Code: Select all

sudo apt install --reinstall gcc-5 g++-5 cpp-5 gcc

But they worked fine for the other kernels. Stumped...

I think build-essential is a metapackage, so it won't force the reinstall of its dependencies if you reinstall it.

I do not have access to any version 5 gcc, cpp or g++ I have versions 4.9 and 6 of each installed but all I see for 5 is doc files.

I used cli apt, synaptic and mxpi... all are devoid of the version 5 code.

[manyroads]

So I think I have determined what the issue is... although there appears to be nothing I can do to fix it. Here are my findings:

When I get a non-functioning VBox on a new kernel I perform the following:

Code: Select all

$ sudo dpkg-reconfigure virtualbox-dkms

When that command is run on (not supported) kernel the following error appears:

Code: Select all

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.
[ ok ] Unloading VirtualBox kernel modules....
[....] Loading VirtualBox kernel modules...[....] No suitable module for running[FAILel found ... failed!

If I try the following command whenever VBox fails:

Code: Select all

$ sudo modprobe vboxdrv

Two conditions arise:

• this command works on supported modules without the need for the above command.

• On a kernel that is (not supported) the error is noted below.

VBox version 5.2.28
4.19.0-1 (supported)
4.19.0-4 (supported)
4.19.4-2 siduction kernel (not supported) modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.19.4-2-siduction-amd64
5.0.0-14 liquorix kernel (not supported) modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.0.0-14.1-liquorix-amd64


VBox version 6.0.6-1 MXPI testrepos
4.19.0-1 (supported)
4.19.0-4 (supported)
4.19.4-2 siduction kernel (not supported) modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/4.19.4-2-siduction-amd64
5.0.0-14 liquorix kernel (not supported) modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.0.0-14.1-liquorix-amd64

So I examined the /lib/modules directory on my machine (where the Fatal Error above occured.
The only modules I have in /lib/modules on my machine are for:
4.9.0.9-amd64
4.19.0-1-amd64
4.19.0-5-amd64
4.19.0-5-cloud-amd64
4.19.0-5-rt-amd64
5.0.0-6.1-liquorix-amd64 (but if I attempt to install this kernel, there are no headers available for it on synaptic; and the kernel is not listed in the testrepos on mxpi)
5.0.0-9.1-liquorix-amd64 (but if I attempt to install this kernel, there are no headers available for it on synaptic; and the kernel is not listed in the testrepos on mxpi)

I'm guessing that this means any kernel not in /lib/modules is effectively unsupported on 6.0.6 of Virtualbox (the version where I examined the /lib/modules folder). If these buggesr are supposed to load somehow, I have no idea how or where they come from...

I hope this helps someone. :lipsrsealed:

[timkb4cq]

You could post the log the error message tells you to consult. It should have clues as to why the module failed to build.

Code: Select all

/var/lib/dkms/virtualbox/6.0.6/build/make.log

[manyroads]

You could post the log the error message tells you to consult. It should have clues as to why the module failed to build.

Code: Select all

/var/lib/dkms/virtualbox/6.0.6/build/make.log

Thanks Tim... I just loaded a kernel that fails and did a clean install. The log follows. Seems that there is some kind of gcc problem, but why with only certain kernels?

Code: Select all

DKMS make.log for virtualbox-6.0.6 for kernel 5.0.0-14.1-liquorix-amd64 (x86_64)
Mon May 13 14:15:13 MDT 2019
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
make[2]: *** [/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/linux/SUPDrv-linux.o] Error 127
make[2]: *** Waiting for unfinished jobs....
  CC [M]  /var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/SUPDrv.o
/bin/sh: 1: gcc: not found
scripts/Makefile.build:276: recipe for target '/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/SUPDrv.o' failed
make[2]: *** [/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/SUPDrv.o] Error 127
  CC [M]  /var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/SUPDrvGip.o
/bin/sh: 1: gcc: not found
scripts/Makefile.build:276: recipe for target '/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/SUPDrvGip.o' failed
make[2]: *** [/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv/SUPDrvGip.o] Error 127
scripts/Makefile.build:492: recipe for target '/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv' failed
make[1]: *** [/var/lib/dkms/virtualbox/6.0.6/build/vboxdrv] Error 2
Makefile:1594: recipe for target '_module_/var/lib/dkms/virtualbox/6.0.6/build' failed
make: *** [_module_/var/lib/dkms/virtualbox/6.0.6/build] Error 2
make: Leaving directory '/usr/src/linux-headers-5.0.0-14.1-liquorix-amd64'

[timkb4cq]

I'm looking at those files and you do have something odd going on.
Please run

Code: Select all

dpkg --print-architecture

and

Code: Select all

uname -m

[manyroads]

I'm looking at those files and you do have something odd going on.
Please run

Code: Select all

dpkg --print-architecture

and

Code: Select all

uname -m

Here's what I get

Code: Select all

dpkg --print-architecture
amd64

Code: Select all

uname -m
x86_64

and just in case...

Code: Select all

$ inxi -F
System:
  Host: mark-dell Kernel: 5.0.0-14.1-liquorix-amd64 x86_64 bits: 64 
  Desktop: Xfce 4.12.3 Distro: MX-18.2_x64 Continuum Feb 9  2019 
Machine:
  Type: Laptop System: Dell product: Latitude E5470 v: N/A 
  serial: <root required> 
  Mobo: Dell model: N/A serial: <root required> UEFI [Legacy]: Dell 
  v: 1.18.6 date: 12/08/2017 
Battery:
  ID-1: BAT0 charge: 49.6 Wh condition: 49.6/62.0 Wh (80%) 
CPU:
  Topology: Dual Core model: Intel Core i5-6300U bits: 64 type: MT MCP 
  L2 cache: 3072 KiB 
  Speed: 500 MHz min/max: 400/3000 MHz Core speeds (MHz): 1: 500 2: 500 
  3: 500 4: 500 
Graphics:
  Device-1: Intel HD Graphics 520 driver: i915 v: kernel 
  Display: x11 server: X.Org 1.19.2 driver: modesetting unloaded: fbdev,vesa 
  resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel HD Graphics 520 (Skylake GT2) 
  v: 4.5 Mesa 18.2.6 
Audio:
  Device-1: Intel Sunrise Point-LP HD Audio driver: snd_hda_intel 
  Sound Server: ALSA v: k5.0.0-14.1-liquorix-amd64 
Network:
  Device-1: Intel Ethernet I219-LM driver: e1000e 
  IF: eth0 state: down mac: 84:7b:eb:44:da:5d 
  Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter 
  driver: ath10k_pci 
  IF: wlan0 state: up mac: 68:14:01:57:3d:df 
  Device-3: Atheros type: USB driver: btusb 
Drives:
  Local Storage: total: 1008.18 GiB used: 576.96 GiB (57.2%) 
  ID-1: /dev/mmcblk0 model: SD32G size: 30.09 GiB 
  ID-2: /dev/sda vendor: Crucial model: CT1050MX300SSD4 size: 978.09 GiB 
RAID:
  Hardware-1: Intel 82801 Mobile SATA Controller [RAID mode] driver: ahci 
Partition:
  ID-1: / size: 952.05 GiB used: 576.96 GiB (60.6%) fs: ext4 dev: /dev/sda1 
  ID-2: swap-1 size: 9.81 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 46.0 C mobo: 38.0 C sodimm: 34.0 C 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 246 Uptime: 1h 37m Memory: 23.22 GiB used: 1.75 GiB (7.5%) 
  Shell: bash inxi: 3.0.33 

[timkb4cq]

That eliminates one possible issue. How about running:

Code: Select all

/usr/src/linux-headers-5.0.0-14.1-liquorix-amd64/scripts/gcc-version.sh -p gcc

[Stevo]

Yes, is this the Liquorix kernel from our test repo, via the package installer?