MX Linux Forum

Posted: **Fri Dec 08, 2017 2:15 pm**

We now have Virtual Box 5.2.2, backported from Debian testing, in the MX 17 test repository. Along with the usual load of bugfixes, this notably will fix the driver DKMS builds on 4.14 kernels for both hosts and guests. It also will run fine on older kernels. Since it needs a newer Qt 5 than Jessie provides, it can't be backported to MX 15/16.

Those users will have to use the Oracle version.

During an upgrade, you should be asked to accept a change to a 98-vbclient.conf file. I have only tested accepting the change, and it is running well after doing so and rebooting.

Posted: **Fri Dec 08, 2017 2:20 pm**

Nice, thanks.

Posted: **Sat Dec 23, 2017 2:37 pm**

Now updated Virtual Box, the guest additions iso, and the ext-pack installer to 5.2.4, with sources from Sid. It's working better across different kernels on my system than the version from Oracle, which required me to rebuild the modules after every reboot for some reason.

Posted: **Sun Jan 21, 2018 5:09 pm**

Virtual Box 5.2.6, backported from upstream Debian with the patch to support 4.15 kernels, is now in the test repository, along with matching virtual-guest-iso and virtualbox-ext-pack packages. It was build on standard MX 17, so shouldn't have any issues if we move it to main.

Posted: **Tue Mar 06, 2018 12:42 pm**

Virtual Box 5.2.6 has been moved into main, and the latest 5.2.8 release has taken its place in testing, along with matching versions of virtualbox-guest-iso and virtualbox-ext-pack.

Posted: **Sat Apr 21, 2018 6:53 am**

I have trouble updating today because of Virtualbox:

Code: Select all


Get:4 http://download.virtualbox.org/virtualbox/debian stretch/contrib amd64 virtualbox-5.2 amd64 5.2.10-122088~Debian~stretch [68.1 MB]
Err:4 http://download.virtualbox.org/virtualbox/debian stretch/contrib amd64 virtualbox-5.2 amd64 5.2.10-122088~Debian~stretch
  Hash Sum mismatch
  Hashes of expected file:
   - SHA256:4bb68f03a499ec5bce53d2ac72afe96fc6bcf705204f9ce2569de8e0b39a0aa0
   - SHA1:e0803fa50a290e3eace34590af6fe4ba84d3f047 [weak]
   - MD5Sum:4e011047b5cef2df4632188cc6395d7d [weak]
   - Filesize:68061072 [weak]
  Hashes of received file:
   - SHA256:8a159ff8410475485fff41b749c8617e0549a35053bb362f54ca5adccfc0fa8c
   - SHA1:72758c97d74080668da6fe32f69045fbb7640e3d [weak]
   - MD5Sum:2cb39966bba776ef541baf7cfae85e5e [weak]
   - Filesize:15241824 [weak]
  Last modification reported: Fri, 13 Apr 2018 20:45:42 +0000
Fetched 89.7 MB in 15min 29s (96.5 kB/s)  
E: Failed to fetch http://download.virtualbox.org/virtualbox/debian/pool/contrib/v/virtualbox-5.2/virtualbox-5.2_5.2.10-122088~Debian~stretch_amd64.deb  Hash Sum mismatch
   Hashes of expected file:
    - SHA256:4bb68f03a499ec5bce53d2ac72afe96fc6bcf705204f9ce2569de8e0b39a0aa0
    - SHA1:e0803fa50a290e3eace34590af6fe4ba84d3f047 [weak]
    - MD5Sum:4e011047b5cef2df4632188cc6395d7d [weak]
    - Filesize:68061072 [weak]
   Hashes of received file:
    - SHA256:8a159ff8410475485fff41b749c8617e0549a35053bb362f54ca5adccfc0fa8c
    - SHA1:72758c97d74080668da6fe32f69045fbb7640e3d [weak]
    - MD5Sum:2cb39966bba776ef541baf7cfae85e5e [weak]
    - Filesize:15241824 [weak]
   Last modification reported: Fri, 13 Apr 2018 20:45:42 +0000
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

full upgrade complete (or was canceled)

this terminal window can now be closed (press any key to close)

I'm sure I installed VB using MXPI Popular apps, and I think previously it just enabled the Oracle repo, but now that the packaging team appears to be backporting VB for MX's own repo, should I disable the http://download.virtualbox.org source?

Not sure if this issue would also affect other MX users. This particular install of MX17 was written over an existing MX15/16 partition but preserving /home.

Posted: **Sat Apr 21, 2018 1:10 pm**

You can keep the Oracle repo enabled normally, since the packages stay out of each other's way, but it appears they are having some problems with it. We have 5.2.10 in the test repo now, so you don't need the Oracle one now anyway.

Posted: **Sat Apr 21, 2018 1:18 pm**

asqwerth wrote:I have trouble updating today because of Virtualbox:
I'm sure I installed VB using MXPI Popular apps, and I think previously it just enabled the Oracle repo, but now that the packaging team appears to be backporting VB for MX's own repo, should I disable the http://download.virtualbox.org source?

Not sure if this issue would also affect other MX users. This particular install of MX17 was written over an existing MX15/16 partition but preserving /home.

I'd recommend disable Oracle's source and do purge existing vitualbox bits an pieces
like this

Code: Select all

# apt-get remove --purge virtualbox*

After that do a fresh install using MXPI (MX package installer) of the latest virtualbox 5.2.10-dfsg-2~mx17+1
from the MX-test-repo.
I've installed these packages.

Code: Select all

aptitude search virtualbox | grep ^i
i   virtualbox - x86 virtualization solution - base binaries
i A virtualbox-dkms - x86 virtualization solution - kernel module sources for dkms
i   virtualbox-ext-pack - extra capabilities for VirtualBox, downloader.
i   virtualbox-guest-additions-iso - guest additions iso image for VirtualBox
i   virtualbox-qt - x86 virtualization solution - Qt based user interface

I've done it this ways. All my VirtualBox'es running perfectly! Thanks @Stevo !!

Posted: **Sat Apr 21, 2018 1:28 pm**

Thanks @fehlix (the Cat).

But I'm perfectly happy waiting for 5.2.10 to be moved to Main repo. If the update subsequently goes wonky, then I'll do a full removal and purge. If not, I'm good.

Meanwhile, 5.2.8 works fine.

Posted: **Fri Jul 06, 2018 3:47 pm**

The latest 5.2.14 release, backported from upstream Debian, is now available in the test repo, along with the matching virtualbox-guest-iso and virtualbox-ext-pack packages.

Posted: **Sat Jul 21, 2018 2:07 pm**

Updated to 5.2.16, sourced from Debian Sid, in the test repo. Debian has added their own patch to prevent the guest modules from trying to load on a real hardware install, but it may throw up a message informing the user that they aren't loading.

Posted: **Mon Aug 20, 2018 2:31 pm**

We now have the latest Virtual Box 5.2.18 packages in the test repo. One improvement that stands out is that guests running the 4.17 kernel are now able to build and use its guest modules successfully.

Posted: **Fri Oct 19, 2018 3:42 pm**

Virtual Box 5.2.20 from Sid, along with the matching guest-iso and extension pack installer packages, is now available in our test repository. Changes and fixes include:

This is a maintenance release. The following items were fixed and/or added:

VMM: fixed task switches triggered by INTn instruction (bug #17979)
Storage: fixed connecting to certain iSCSI targets (bug #17507)
Storage: fixed handling of flush requests when configured to be ignored when the host I/O cache is used (bug #17573)
Drag and drop: implemented support for UNC paths (bug #17146)
Drag and drop: fixed resuming operation when restoring from a saved state (bug #17649)
Drag and drop: fixed copying files with long file names (> 248 characters) from guests to Windows hosts (bug #17447)
Drag and drop: fixed handling files with Unicode names on Windows guests (bug #15501)
Drag and drop: fixed copying empty (0-byte) files to / from guests (bugs #14863 + #17443)
Drag and drop: fixed copying over files from hosts to Linux guests (bug #16025)
Networking: restore connectivity for guests bridged to host adapters that were unavailable temporarily (Windows hosts, bug #17090)
Guest Control: fixed hang when using --wait-stdout and/or --wait-stderr (bug #17386). Needs updating Guest Additions
Video recording: fixed starting video recording on VM power up (bug #17307)
Linux Additions: various build fixes for kernel modules on recent distributions, and made sure modules end up in initramfs files
Linux Additions: build fixes for 4.19, thank you Larry Finger
Linux Additions: various small fixes for video driver

Posted: **Sun Nov 11, 2018 6:19 pm**

We now have 5.2.22 in the test repo, backported from Debian Sid, along with the guest-addition-iso and ext-pack packages as usual. Among the standard lot of bug fixes, this version also improves compatibility with the 4.19 kernel.

Posted: **Tue Dec 04, 2018 3:08 pm**

We are moving 5.2.22 to main to support builds on the 4.19 kernel coming with MX 18, but older kernels are still supported.

All users with virtualbox packages will be seeing the upgrades.

Posted: **Thu Jan 17, 2019 6:23 pm**

Virtual Box 5.2.24, backported from upstream Debian, has landed in the test repo. Among the usual bugfixes and the like, this version also fixes building on 4.20 kernels. It's working well so far for me.

I also have the new 6.0.2 sources from Debian Experimental, but if I can build them, they'll go to our own experimental repo.

Posted: **Wed Jan 30, 2019 6:59 pm**

We now have Virtual Box 6.0.4 in the test repo, with 5.2.24 moving to main.

The new version seems to be ignoring theme colors--you can have any GUI color you like as long as it's stark white.

If you are using a dark theme and get white text on that white background, right-click the menu entry, click "Edit Application", and use one of these strings for the command to get black text:

Code: Select all

VirtualBox -style gtk %U

Code: Select all

VirtualBox -style qt %U

Posted: **Fri Feb 01, 2019 11:44 am**

I have installed the Testrepo version of VirtualBox 6 and successfully run my virtual machines. The only issue I have noticed thus far is that the virtualbox (meta) selection does not install all the items I think are required to run VBox. The manually installed items are in this image:

Missing from meta install..png

Here's what V6 looks like on my MX18 Desktop.

VBox 6-1.jpg

VBox 6-2.jpg

Posted: **Fri Feb 01, 2019 12:11 pm**

manyroads wrote: Fri Feb 01, 2019 11:44 am I have installed the Testrepo version of VirtualBox 6 and successfully run my virtual machines.

Looks goot manyroads. Some questions: Is Shared Folder working? And what kernel version do you use? Have you also installed new guest-additions within the linux or windows guests?
Thanks

Posted: **Fri Feb 01, 2019 12:35 pm**

fehlix wrote: Fri Feb 01, 2019 12:11 pm Looks goot manyroads. Some questions: Is Shared Folder working? And what kernel version do you use? Have you also installed new guest-additions within the linux or windows guests?
Thanks

Shared Folders (work fine) tested on Win10-- works normally; virtualbox mx-edu platform ---works normally
My Desktop is using MX 18_x64 kernel: 4.19.3-antix.1-amd64-smpx86

Here's a synaptic shot of what I have installed.

VBox Installed.png

Posted: **Fri Feb 01, 2019 12:40 pm**

I also installed the test repo version 6. I only have Linux guests and did not to have install guest additions per guest. I set up shared folders on a Manjaro KDE Linux guest but could not see shared folders. In the past they appeared in a /media folder, but no such folder exists. To be honest I have not used VBox for some time so maybe another mechanism exists to see shared folders.

Posted: **Fri Feb 01, 2019 4:06 pm**

Manyroads, you don't need to install the guest packages on the host machine, only in MX versions running as guests (and they come with those anyway.)

The only thing extra you need that's not in the metapackage on the host is virtualbox-ext-pack to automatically get and install the matching extension pack. Dependency issues prevented me from adding it to the metapackage.

Posted: **Fri Feb 01, 2019 4:08 pm**

richb wrote: Fri Feb 01, 2019 12:40 pm I also installed the test repo version 6. I only have Linux guests and did not to have install guest additions per guest. I set up shared folders on a Manjaro KDE Linux guest but could not see shared folders. In the past they appeared in a /media folder, but no such folder exists. To be honest I have not used VBox for some time so maybe another mechanism exists to see shared folders.

You do have do set up/build guest additions on the guest if they don't come with them already, like MX does. I suspect that's the problem with Fedora, since the guest additions are non-free, and they don't ship with any non-free stuff at all.

Posted: **Fri Feb 01, 2019 5:47 pm**

Stevo wrote: Fri Feb 01, 2019 4:06 pm Manyroads, you don't need to install the guest packages on the host machine, only in MX versions running as guests (and they come with those anyway.)

The only thing extra you need that's not in the metapackage on the host is virtualbox-ext-pack to automatically get and install the matching extension pack. Dependency issues prevented me from adding it to the metapackage.

I forgot when I found this out... old, bad memory. Time for some new RAM, I guess. :lipsrsealed: But anyway, I have noticed that previous versions of VB seem to get all the privs correct (magically) when the whole boat is loaded. So I just install everything.

Posted: **Sat Feb 02, 2019 11:18 am**

I have to say... VBox 6 works nicely with 4.20 of the kernel.

Posted: **Sun Feb 03, 2019 11:46 pm**

Stevo wrote: Wed Jan 30, 2019 6:59 pm We now have Virtual Box 6.0.4 in the test repo, with 5.2.24 moving to main.

The new version seems to be ignoring theme colors--you can have any GUI color you like as long as it's stark white.

If you are using a dark theme and get white text on that white background, right-click the menu entry, click "Edit Application", and use one of these strings for the command to get black text:
Code: Select all
VirtualBox -style gtk %U
Code: Select all
VirtualBox -style qt %U

UPDATE:
Previously (within the last 7 days) the text was white on white on my Arch-based distro when I used a dark gtk theme.

But I just upgraded my Fedora 28 (formerly Korora 27, so I'm not sure if they had previously added some theming/environment tweaks) to Fedora 29 yesterday, and a few hours ago I installed Virtualbox 6.0.4 directly from Oracle's virtualbox.repo. Had to manually download and install the Extension Pack from Oracle.

I didn't use the Virtualbox -style commands above. The VB theme doesn't follow the system's dark theme but now at least the text displayed in the VB Settings window is black on white background, rather than white on white. Shimmer effect is still present but that's not an issue if the text is now legible.

Dark theme: Ant-Dracula, also tested fine with Arc-Dark,
Kernel: 4.20.5-200.fc29.x86_64

Virtual machine was an MX17.1-beta, and the Shared Folder within continued to automount and work.

Virtualbox version: see screenshot

https://imgur.com/9rK6248

Posted: **Tue Mar 26, 2019 9:38 pm**

Weirdly enough, after fiddling around with qt5ct and setting it to follow the gtk2 theme also, the VBox 6.04 GUI now is mostly dark:

Go figure.

Posted: **Thu Apr 18, 2019 6:32 pm**

The test repo packages have been updated to the latest 6.0.6 release, backported from Sid, along with the -ext-pack and -guest-additions-iso packages.

Posted: **Sat May 11, 2019 6:06 pm**

We now have the newest release of the 5.2 series, 5.2.28, in the experimental repo. We did this to avoid the conflict with 6.0.6 in the test repo. This version will build on 5.0 kernels, and still follows the GTK theming. We also have matching versions of virtualbox-guest-additions-iso and virtualbox-ext-pack there.

I had to go out and generate the sources for this release myself, since Debian and Ubuntu have jumped from 5.2.24 to the 6.X series. Maybe antiX would be interested in this release for the Stretch and Buster versions, though I'll have to re-enable some disabled patches for the upstream version.

The line to add to /etc/apt/sources.list.d/mx.list for the experimental repo is

Code: Select all

deb http://mxrepo.com/mx/experimental/ stretch test \

We'd really like to get this into main, so test reports are welcome.

Posted: **Sat May 11, 2019 6:10 pm**

Stevo wrote: Sat May 11, 2019 6:06 pm We'd really like to get this into main, so test reports are welcome.

Here come da tests

... I'll test away and see what I can break for you!

Posted: **Sat May 11, 2019 6:19 pm**

Stevo wrote: Sat May 11, 2019 6:06 pm
Code: Select all
deb http://mxrepo.com/mx/experimental/ stretch test \
We'd really like to get this into main, so test reports are welcome.

They do not yet appear at my end... I'll try again in a 'bit'.

Posted: **Sun May 12, 2019 8:23 am**

@stevo Here's what happened this morning. After an update using cli-aptiX to the following:

VirtualBox Graphical User Interface Version 5.2.24_Debian r128122
© 2004-2019 Oracle Corporation (Qt5.7.1)

The same problem appears with the 5.0.0 kernel....

btw. the experimental version does not appear anywhere at my end yet. Perhaps it shows up somewhere other than MXPI, synapyic or cli-aptiX :lipsrsealed:

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-guest/5.2.24/build/make.log for more information.
 

Setting up linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
/etc/kernel/header_postinst.d/dkms:
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.

--------the full upgrade follows ---------------

=> apt-get dist-upgrade                                                       
Reading package lists... Done
Building dependency tree       
Reading state information... Done
Calculating upgrade... Done
The following NEW packages will be installed:
  linux-headers-4.19.0-5-amd64 linux-headers-4.19.0-5-common
The following packages will be upgraded:
  linux-headers-amd64 linux-kbuild-4.19 linux-libc-dev virtualbox
  virtualbox-dkms virtualbox-guest-additions-iso virtualbox-guest-dkms
  virtualbox-guest-utils virtualbox-guest-x11 virtualbox-qt
10 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 78.6 MB of archives.
After this operation, 55.6 MB of additional disk space will be used.
Do you want to continue? [Y/n] 
Get:1 https://mirror.us.oneandone.net/linux/distributions/mx/packages/antix/stretch stretch/main amd64 virtualbox-qt amd64 5.2.24-dfsg-4~mx17+1 [8,538 kB]
Get:2 https://mirror.us.oneandone.net/linux/distributions/mx/packages/antix/stretch stretch/main amd64 virtualbox-dkms all 5.2.24-dfsg-4~mx17+1 [691 kB]
Get:3 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo stretch/non-free amd64 virtualbox-guest-additions-iso all 5.2.24-1~mx17+1 [39.3 MB]
Get:4 https://mirror.us.oneandone.net/linux/distributions/mx/packages/antix/stretch stretch/main amd64 virtualbox amd64 5.2.24-dfsg-4~mx17+1 [17.2 MB]
Get:5 https://mirror.us.oneandone.net/linux/distributions/mx/packages/antix/stretch stretch/main amd64 virtualbox-guest-x11 amd64 5.2.24-dfsg-4~mx17+1 [1,078 kB]
Get:6 https://mirror.us.oneandone.net/linux/distributions/mx/packages/antix/stretch stretch/main amd64 virtualbox-guest-utils amd64 5.2.24-dfsg-4~mx17+1 [453 kB]
Get:7 https://mirror.us.oneandone.net/linux/distributions/mx/packages/antix/stretch stretch/main amd64 virtualbox-guest-dkms all 5.2.24-dfsg-4~mx17+1 [612 kB]
Get:8 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo stretch/main amd64 linux-headers-4.19.0-5-common all 4.19.37-1~mx17+1 [8,219 kB]
Get:9 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo stretch/main amd64 linux-kbuild-4.19 amd64 4.19.37-1~mx17+1 [502 kB]
Get:10 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo stretch/main amd64 linux-headers-4.19.0-5-amd64 amd64 4.19.37-1~mx17+1 [748 kB]
Get:11 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo stretch/main amd64 linux-headers-amd64 amd64 4.19+105 [6,672 B]
Get:12 https://mirror.us.oneandone.net/linux/distributions/mx/packages/mx/repo stretch/main amd64 linux-libc-dev amd64 4.19.37-1~mx17+1 [1,186 kB]
Fetched 78.6 MB in 1min 5s (1,193 kB/s)                                        
(Reading database ... 365338 files and directories currently installed.)
Preparing to unpack .../00-virtualbox-qt_5.2.24-dfsg-4~mx17+1_amd64.deb ...
Unpacking virtualbox-qt (5.2.24-dfsg-4~mx17+1) over (5.2.24-dfsg-4~bpo9+1) ...
Preparing to unpack .../01-virtualbox-dkms_5.2.24-dfsg-4~mx17+1_all.deb ...

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 5.2.24
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: 5.2.24
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-dkms (5.2.24-dfsg-4~mx17+1) over (5.2.24-dfsg-4~bpo9+1) ...
Preparing to unpack .../02-virtualbox-guest-additions-iso_5.2.24-1~mx17+1_all.deb ...
Unpacking virtualbox-guest-additions-iso (5.2.24-1~mx17+1) over (5.2.24-1~bpo9+2) ...
Preparing to unpack .../03-virtualbox_5.2.24-dfsg-4~mx17+1_amd64.deb ...
Unpacking virtualbox (5.2.24-dfsg-4~mx17+1) over (5.2.24-dfsg-4~bpo9+1) ...
Preparing to unpack .../04-virtualbox-guest-x11_5.2.24-dfsg-4~mx17+1_amd64.deb ...
Unpacking virtualbox-guest-x11 (5.2.24-dfsg-4~mx17+1) over (5.2.24-dfsg-4~bpo9+1) ...
Preparing to unpack .../05-virtualbox-guest-utils_5.2.24-dfsg-4~mx17+1_amd64.deb ...
Unpacking virtualbox-guest-utils (5.2.24-dfsg-4~mx17+1) over (5.2.24-dfsg-4~bpo9+1) ...
Preparing to unpack .../06-virtualbox-guest-dkms_5.2.24-dfsg-4~mx17+1_all.deb ...

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

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

vboxguest.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-1-amd64/updates/
 - Original module
   - Archived original module found in the DKMS tree
   - Moving it to: /lib/modules/4.19.0-1-amd64/updates/

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


vboxvideo.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.19.0-1-amd64/
rmdir: failed to remove '': No such file or directory
 - 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...

Removing original_module from DKMS tree for kernel 4.19.0-1-amd64 (x86_64)

DKMS: uninstall completed.

------------------------------
Deleting module version: 5.2.24
completely from the DKMS tree.
------------------------------
Done.
Unpacking virtualbox-guest-dkms (5.2.24-dfsg-4~mx17+1) over (5.2.24-dfsg-4~bpo9+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-common.
Preparing to unpack .../07-linux-headers-4.19.0-5-common_4.19.37-1~mx17+1_all.deb ...
Unpacking linux-headers-4.19.0-5-common (4.19.37-1~mx17+1) ...
Preparing to unpack .../08-linux-kbuild-4.19_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-kbuild-4.19 (4.19.37-1~mx17+1) over (4.19.5-2~mx17+1) ...
Selecting previously unselected package linux-headers-4.19.0-5-amd64.
Preparing to unpack .../09-linux-headers-4.19.0-5-amd64_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
Preparing to unpack .../10-linux-headers-amd64_4.19+105_amd64.deb ...
Unpacking linux-headers-amd64 (4.19+105) over (4.19+101) ...
Preparing to unpack .../11-linux-libc-dev_4.19.37-1~mx17+1_amd64.deb ...
Unpacking linux-libc-dev:amd64 (4.19.37-1~mx17+1) over (4.19.5-2~mx17+1) ...
Setting up linux-headers-4.19.0-5-common (4.19.37-1~mx17+1) ...
Processing triggers for mime-support (3.60) ...
Processing triggers for desktop-file-utils (0.23-1) ...
Setting up virtualbox-dkms (5.2.24-dfsg-4~mx17+1) ...
Loading new virtualbox-5.2.24 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/5.2.24/build/make.log for more information.
[....] Unloading VirtualBox kernel modules... vboxnetadp vboxnetflt vboxpci vbox[ o. 
[....] Loading VirtualBox kernel modules... vboxdrv vboxnetflt vboxnetadp vboxpc[.ok 
Setting up virtualbox-guest-dkms (5.2.24-dfsg-4~mx17+1) ...
Loading new virtualbox-guest-5.2.24 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.

vboxguest:
Running module version sanity check.
 - Original module
   - Found /lib/modules/4.19.0-1-amd64/updates/vboxguest.ko
   - Storing in /var/lib/dkms/virtualbox-guest/original_module/4.19.0-1-amd64/x86_64/
   - Archiving for uninstallation purposes
 - Installation
   - Installing to /lib/modules/4.19.0-1-amd64/updates/

vboxsf.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/4.19.0-1-amd64/updates/

vboxvideo.ko:
Running module version sanity check.
Error! Module version 5.2.24_Debian for vboxvideo.ko
is not newer than what is already found in kernel 4.19.0-1-amd64 (5.2.24_Debian).
You may override by specifying --force.

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-guest/5.2.24/build/make.log for more information.
Setting up linux-libc-dev:amd64 (4.19.37-1~mx17+1) ...
Setting up virtualbox-guest-additions-iso (5.2.24-1~mx17+1) ...
Processing triggers for menu (2.1.47+b1) ...
Setting up linux-kbuild-4.19 (4.19.37-1~mx17+1) ...
Processing triggers for bamfdaemon (0.5.3-2) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for systemd (232-25+deb9u11) ...
Setting up linux-headers-4.19.0-5-amd64 (4.19.37-1~mx17+1) ...
/etc/kernel/header_postinst.d/dkms:
Warning: Unable to find an initial ram disk that I know how to handle.
Will not try to make an initrd.
Setting up virtualbox-guest-utils (5.2.24-dfsg-4~mx17+1) ...
Processing triggers for man-db (2.7.6.1-2) ...
Processing triggers for shared-mime-info (1.8-1+deb9u1) ...
Processing triggers for gnome-menus (3.13.3-9) ...
Processing triggers for hicolor-icon-theme (0.15-1) ...
Setting up linux-headers-amd64 (4.19+105) ...
Setting up virtualbox-guest-x11 (5.2.24-dfsg-4~mx17+1) ...
Setting up virtualbox-qt (5.2.24-dfsg-4~mx17+1) ...
Setting up virtualbox (5.2.24-dfsg-4~mx17+1) ...
[....] Unloading VirtualBox kernel modules... vboxnetadp vboxnetflt vboxpci vbox[ o. 
[....] Loading VirtualBox kernel modules... vboxdrv vboxnetflt vboxnetadp vboxpc[.ok 
Processing triggers for libc-bin (2.24-11+deb9u4) ...
Processing triggers for menu (2.1.47+b1) ...
dist-upgrade took 3:09 mm:ss
Creating database ...
database generation took 0.41 seconds

Posted: **Sun May 12, 2019 8:31 pm**

What does "inxi -r" show for your repos?

That experimental line has to be added manually somewhere in one of the /etc/apt/sources.list.d/ *.list files. The logical one would be the mx.list file.

Posted: **Sun May 12, 2019 9:14 pm**

Hi @stevo

It ran fine after I loaded it into the folder/ file you mentioned. However, things remain broken.

$ sudo modprobe vboxdrv
[sudo] password for mark:
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.0.0-14.1-liquorix-amd64

I also ran:

Code: Select all

sudo dpkg-reconfigure virtualbox-dkms
$ sudo dpkg-reconfigure virtualbox-dkms

-------- Uninstall Beginning --------
Module:  virtualbox
Version: 5.2.28
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: 5.2.28
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.28 DKMS files...
Building for 5.0.0-14.1-liquorix-amd64
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/5.2.28/build/make.log for more information.

Posted: **Sun May 12, 2019 9:55 pm**

Stevo wrote: Sun May 12, 2019 8:31 pm What does "inxi -r" show for your repos?

That experimental line has to be added manually somewhere in one of the /etc/apt/sources.list.d/ *.list files. The logical one would be the mx.list file.

@ steveo I ran the following and wonder if it may not indicate my problem(s)....

$ apt-cache search linux-image | grep amd64

Code: Select all

linux-image-4.14.12-antix.1-amd64-smp - Linux kernel, version 4.14.12-antix.1-amd64-smp
linux-image-4.14.12-gnu-antix.1-amd64-smp - Linux kernel, version 4.14.12-gnu-antix.1-amd64-smp
linux-image-4.14.14-antix.1-amd64-smp - Linux kernel, version 4.14.14-antix.1-amd64-smp
linux-image-4.19.25-antix.1-amd64-smp - Linux kernel, version 4.19.25-antix.1-amd64-smp
linux-image-4.20.12-antix.1-amd64-smp - Linux kernel, version 4.20.12-antix.1-amd64-smp
linux-image-4.9.160-antix.1-amd64-smp - Linux kernel, version 4.9.160-antix.1-amd64-smp
linux-image-4.9.170-antix.1-amd64-smp - Linux kernel, version 4.9.170-antix.1-amd64-smp
linux-image-5.0.9-antix.1-amd64-smp - Linux kernel, version 5.0.9-antix.1-amd64-smp
linux-headers-4.9.0-8-amd64 - Header files for Linux 4.9.0-8-amd64
linux-headers-4.9.0-8-rt-amd64 - Header files for Linux 4.9.0-8-rt-amd64
linux-image-4.9.0-8-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-8-amd64-dbg - Debug symbols for linux-image-4.9.0-8-amd64
linux-image-4.9.0-8-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-8-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-8-rt-amd64
linux-headers-4.9.0-9-amd64 - Header files for Linux 4.9.0-9-amd64
linux-headers-4.9.0-9-rt-amd64 - Header files for Linux 4.9.0-9-rt-amd64
linux-image-4.9.0-9-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-9-amd64-dbg - Debug symbols for linux-image-4.9.0-9-amd64
linux-image-4.9.0-9-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-9-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-9-rt-amd64
linux-image-amd64-dbg - Debugging symbols for Linux amd64 configuration (meta-package)
linux-image-rt-amd64 - Linux for 64-bit PCs (meta-package), PREEMPT_RT
linux-image-rt-amd64-dbg - Debugging symbols for Linux rt-amd64 configuration (meta-package)
linux-headers-4.9.0-3-amd64 - Header files for Linux 4.9.0-3-amd64
linux-headers-4.9.0-3-rt-amd64 - Header files for Linux 4.9.0-3-rt-amd64
linux-headers-4.9.0-4-amd64 - Header files for Linux 4.9.0-4-amd64
linux-headers-4.9.0-4-rt-amd64 - Header files for Linux 4.9.0-4-rt-amd64
linux-headers-4.9.0-5-amd64 - Header files for Linux 4.9.0-5-amd64
linux-headers-4.9.0-5-rt-amd64 - Header files for Linux 4.9.0-5-rt-amd64
linux-headers-4.9.0-6-amd64 - Header files for Linux 4.9.0-6-amd64
linux-headers-4.9.0-6-rt-amd64 - Header files for Linux 4.9.0-6-rt-amd64
linux-headers-4.9.0-7-amd64 - Header files for Linux 4.9.0-7-amd64
linux-headers-4.9.0-7-rt-amd64 - Header files for Linux 4.9.0-7-rt-amd64
linux-image-4.9.0-3-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-3-amd64-dbg - Debug symbols for linux-image-4.9.0-3-amd64
linux-image-4.9.0-3-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-3-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-3-rt-amd64
linux-image-4.9.0-4-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-4-amd64-dbg - Debug symbols for linux-image-4.9.0-4-amd64
linux-image-4.9.0-4-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-4-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-4-rt-amd64
linux-image-4.9.0-5-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-5-amd64-dbg - Debug symbols for linux-image-4.9.0-5-amd64
linux-image-4.9.0-5-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-5-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-5-rt-amd64
linux-image-4.9.0-6-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-6-amd64-dbg - Debug symbols for linux-image-4.9.0-6-amd64
linux-image-4.9.0-6-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-6-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-6-rt-amd64
linux-image-4.9.0-7-amd64 - Linux 4.9 for 64-bit PCs
linux-image-4.9.0-7-amd64-dbg - Debug symbols for linux-image-4.9.0-7-amd64
linux-image-4.9.0-7-rt-amd64 - Linux 4.9 for 64-bit PCs, PREEMPT_RT
linux-image-4.9.0-7-rt-amd64-dbg - Debug symbols for linux-image-4.9.0-7-rt-amd64
linux-headers-4.13.0-1-amd64 - Header files for Linux 4.13.0-1-amd64
linux-headers-4.14.0-0.bpo.3-amd64 - Header files for Linux 4.14.0-0.bpo.3-amd64
linux-headers-4.14.0-0.bpo.3-rt-amd64 - Header files for Linux 4.14.0-0.bpo.3-rt-amd64
linux-headers-4.14.0-3-amd64 - Header files for Linux 4.14.0-3-amd64
linux-headers-4.14.0-3-rt-amd64 - Header files for Linux 4.14.0-3-rt-amd64
linux-headers-4.15.0-1-amd64 - Header files for Linux 4.15.0-1-amd64
linux-headers-4.15.0-1-cloud-amd64 - Header files for Linux 4.15.0-1-cloud-amd64
linux-headers-4.18.0-2-amd64 - Header files for Linux 4.18.0-2-amd64
linux-headers-4.18.0-2-cloud-amd64 - Header files for Linux 4.18.0-2-cloud-amd64
linux-headers-4.18.0-2-rt-amd64 - Header files for Linux 4.18.0-2-rt-amd64
linux-headers-4.19.0-1-amd64 - Header files for Linux 4.19.0-1-amd64
linux-headers-4.19.0-1-cloud-amd64 - Header files for Linux 4.19.0-1-cloud-amd64
linux-headers-4.19.0-1-rt-amd64 - Header files for Linux 4.19.0-1-rt-amd64
linux-headers-4.19.0-5-amd64 - Header files for Linux 4.19.0-5-amd64
linux-headers-4.19.0-5-cloud-amd64 - Header files for Linux 4.19.0-5-cloud-amd64
linux-headers-4.19.0-5-rt-amd64 - Header files for Linux 4.19.0-5-rt-amd64
linux-image-4.13.0-1-amd64 - Linux 4.13 for 64-bit PCs
linux-image-4.14.0-0.bpo.3-amd64 - Linux 4.14 for 64-bit PCs
linux-image-4.14.0-0.bpo.3-rt-amd64 - Linux 4.14 for 64-bit PCs, PREEMPT_RT
linux-image-4.14.0-3-amd64 - Linux 4.14 for 64-bit PCs
linux-image-4.14.0-3-rt-amd64 - Linux 4.14 for 64-bit PCs, PREEMPT_RT
linux-image-4.15.0-1-amd64 - Linux 4.15 for 64-bit PCs
linux-image-4.15.0-1-cloud-amd64 - Linux 4.15 for x86-64 cloud
linux-image-4.18.0-2-amd64 - Linux 4.18 for 64-bit PCs
linux-image-4.18.0-2-cloud-amd64 - Linux 4.18 for x86-64 cloud
linux-image-4.18.0-2-rt-amd64 - Linux 4.18 for 64-bit PCs, PREEMPT_RT
linux-image-4.19.0-1-amd64-unsigned - Linux 4.19 for 64-bit PCs
linux-image-4.19.0-1-cloud-amd64-unsigned - Linux 4.19 for x86-64 cloud
linux-image-4.19.0-1-rt-amd64-unsigned - Linux 4.19 for 64-bit PCs, PREEMPT_RT
linux-image-4.19.0-5-amd64-unsigned - Linux 4.19 for 64-bit PCs
linux-image-4.19.0-5-cloud-amd64-unsigned - Linux 4.19 for x86-64 cloud
linux-image-4.19.0-5-rt-amd64-unsigned - Linux 4.19 for 64-bit PCs, PREEMPT_RT
linux-image-amd64 - Linux for 64-bit PCs (meta-package)
linux-image-amd64-signed-template - Template for signed linux-image packages for amd64
linux-image-cloud-amd64 - Linux for x86-64 cloud (meta-package)
mark@mark-dell:~
$

Posted: **Mon May 13, 2019 3:03 pm**

So @stevo I think I can say I found the evidence of what is happening... I'm not certain there is anything I can do (given my current knowledge level). I posted the saga here:

viewtopic.php?f=97&t=50206&p=502180#p502180

Posted: **Mon May 13, 2019 5:00 pm**

You can check if the correct headers are installed for Liquorix:

Code: Select all

apt policy linux-headers-5.0.0*

You can also try reinstalling gcc

Code: Select all

sudo apt install --reinstall gcc

But the error seems unique to your system.

Posted: **Mon May 13, 2019 5:29 pm**

Stevo wrote: Mon May 13, 2019 5:00 pm You can also try reinstalling gcc
Code: Select all
sudo apt install --reinstall gcc
But the error seems unique to your system.

The reinstall seems to have fixed the problem. 5.0.0-14 is now running!

Awesomenesssssssssss.......

Posted: **Sun May 19, 2019 5:18 pm**

We have now updated to Virtualbox 6.0.8 in the test repo and 5.2.30 in the Experimental repo, for those that prefer the 5.2.X series.

Posted: **Sun May 19, 2019 5:29 pm**

I like to use the Oracle packages.

Posted: **Sat Aug 24, 2019 2:29 pm**

it appears to me that the virtualbox 6 configuration for new VM's defaults to vmmware drivers rather than the virtualbox graphics drivers that work with the guest-additions. you can switch this in the "Display" area of the virtualbox VM machine configuration pages.

Posted: **Thu Sep 12, 2019 9:19 pm**

hello Dolphin - I am having ongoing issues with Virtual box and all versions of MX - I saw your advice that stretch had issues with VB 6.xx - but I thought I found a bug in MX19 when it is supposed to have Guest Additions pre loaded - well it did not seem to work for me - messages that said it could not find them and offered to download them - it instantly crashed the MX19 instance. Today I tried to get a damaged (due in part I guess to recent Kernal update bug) and it too won't allow a Guest Additions download - instantly crashing the MX18 instance.

Clearly I can't be sure where the issue is - but I have made major changes to my system - buying a brand new SSD and installing fresh and more stable host OS's (currently using Solus as they had good documentation on how to deploy VB) - I have even tried to stay away from VB in case this is one of the flies in the ointment - and gave Gnome Boxes a whirl - however this seems to be too unreliable and crashes or freezes too often - and MX does not like it much.

there are one of two software packages that are must haves for me - one is Manager.io - which has been bullet proof in previous Linux Flavours - but now with MX having issues in so many areas for me - I just can't get it to work - it will crash in MX18 so there is code that is not Debian compatible for that to work - I wanted so much for MX to be my daily driver - but even these forums are confusing to me - there is no simple link in the software (MX) to report bugs (for either 18.xx or 19.xx) - I am not even sure you will get this message as the thread I have responded to gives me no confirmation of what I am responding to.

Initially I wanted to try to change to the alternate video driver - as you mentioned that VM Ware was the new default in VB 6.xx however in my version of VB (VirtualBox Graphical User Interface Version 6.0.12_Solus r132055) I can't identify which is the VM Ware driver - none say VM Ware - So for me it would have been beneficial to state which one to select as the preferred driver.

Posted: **Thu Sep 12, 2019 9:33 pm**

@ozfossil

on my virtualbox 6, the graphics controller under "Dispaly" in the virtualbox machine settings had defaulted to vmware driver of some sort. I selected VBoxSVGA and it went well.

I can tell you that all official versions of MX have the virtualbox guest additions already installed, although MX17/18 have the older 5.24 version.

screenshot of the VB setting to check.

Posted: **Wed Sep 25, 2019 3:36 pm**

VBox 6.0.12 is also giving me a warning to switch from VboxVGA to the VBoxSVGA graphics if I have 3D acceleration enabled, since support for the first will be dropped in version 6.1.

Posted: **Sun Sep 29, 2019 5:14 am**

Stevo wrote: Wed Sep 25, 2019 3:36 pm VBox 6.0.12 is also giving me a warning to switch from VboxVGA to the VBoxSVGA graphics if I have 3D acceleration enabled, since support for the first will be dropped in version 6.1.

Take the warning seriously.

In my Neon install, I'd already updated VB to 6.1 and when I tried to open my VM for MX16-32bit, it showed an error, with NO settings option to switch to VBoxSVGA.

Luckily I have so many distros on my system, and my MX17/18 installs don't have VB 6.1 yet. So I used the version 6.0+ in MX to set all my VMs to VBoxSVGA, including the MX16 one.

Posted: **Mon Feb 24, 2020 4:09 pm**

We now have updated to the latest Virtual Box 6.1.4 in the MX 17 through 19 test repos (remember that this thread is for MX 17/18).

This is a maintenance release. The following items were fixed and/or added:

Virtualization core: Fixed a rare issue with ICEBP instruction causing guru meditations on Intel hosts (6.1.0 regression; bug #19171)

Virtualization core: Fixed macOS Catalina guests failing to boot after upgrading to 10.15.2 onwards (bug #19188)

GUI: recent NLS integration and bug fixes for GUI and Qt translation tags

USB: Fix isochronous transfers to the VM for xHCI

Serial: Fix buffer handling, avoiding receiving stale data when the receive queue is flushed (bug #18671)

VBoxManage: Restore old --clipboard option for modifyvm command

Linux guest: Support Linux 5.5 (bug #19145)

Linux guest: Shared folder fix for loopback mounting of images

BIOS: Always report non-ATA disks as ready

BIOS: Report EFI support through DMI table (bug 19144)

VGA BIOS: Reduce stack space usage for INT 10h handlers

Posted: **Tue Apr 21, 2020 7:16 pm**

Updated to 6.1.6 in the test repo, backported from Debian Sid. Among other things, this adds support for 5.6 kernels.

Posted: **Fri May 22, 2020 12:25 am**

Now updated to 6.1.8 in our test repo! It's working fine for me so far.

Posted: **Mon Jun 08, 2020 1:02 am**

Updated to 6.1.10 in the test repo. Among other changes, this is supposed to be compatible with the 5.7 kernel.

Posted: **Thu Oct 22, 2020 5:49 pm**

Updated to the latest 6.1.16 in the MX 17 test repo, backported from Debian Sid. Among other improvements, this version will build and work on 5.9 kernels.

This is not a trivial backport, but I documented my tweaks in debian/changelog.

Posted: **Wed Mar 24, 2021 1:46 pm**

Updated 6.1.18 in testing to "-3~mx17+1", which adds a patch from Sid to allow builds on 5.11 kernels. We have 5.11 Liquorix kernels is MX 17/18 test repos...

Posted: **Thu Apr 22, 2021 1:31 pm**

We now have the latest 6.1.20 in the MX 17/18 test repository. Since Repology is flagging our current versions in main as insecure, we'd like to have this in main. It also will support up to and including 5.12 kernels, and fixes a bug that caused very slow performance on some hardware.

It's working fine for me on a 5.10 MX 19 kernel, but we need more testers. Please let us know how it installs with MX Package Installer/ Test Repo tab, and how it performs. Thanks!

Posted: **Wed May 12, 2021 6:31 pm**

Updated to the latest 6.1.22 version, backported from Debian Sid, for the MX 19 and 17 test repos.

MX Linux Forum

MX 17/18 Repository: The Virtual Box Thread

MX 17/18 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread

Re: MX 17/18 Repository: The Virtual Box Thread