MX Package Installer and Debian 4.9.0-7-amd64 kernel

[ChrisUK]

Just for information:

From memory, other kernels installed via MXPI, also setup VirtualBox drivers etc - I just installed the aforementioned kernel using MXPI, and needed to set up VirtualBox, as no access to shared folders on host. It's not a problem, as it's just a matter of typing

Code: Select all

sudo /sbin/vboxconfig

in the terminal, but I figured newbies might be a bit wary of doing it manually.

[dolphin_oracle]

Thanks. This hasn't been a problem for debians main kernel in the past but maybe it's safer to setup the same autorebuild for it.

[Stevo]

Users that installed the MX or Debian VBox packages* can also run

Code: Select all

sudo dpkg-reconfigure virtualbox-dkms

to make sure the kernel modules are built. There are some reports on the Debian forums that the Nvidia DKMS driver also wasn't rebuilt during the kernel update, leaving some users staring at the dreaded black screen.

* which is what the MX Package installer provides.

[dolphin_oracle]

i''m updating mx-pi's lists to force rebuild of dkms packages for all kernel options

users can also run this command manually

Code: Select all

/usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh

[ChrisUK]

You both deciphered my gibberish

I've just noticed that I described the problem, but the wrong symptom. The shared folder access was due to me updating to the latest firejail... I hadn't deleted the link to Virtualbox in /usr/local/bin/. The symptom was no access to VMs, which you've now fixed for future upgrades with the rebuild (Maybe worth adding a link to the rebuild script or the one-liner in MX Tweak? Just in case a user breaks any manual kernel installs.)

[Richard]

Well the first command didn't work.

Code: Select all

$ sudo dpkg-reconfigure virtualbox-dkms
------------------------------
Deleting module version: 5.2.10
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.10 DKMS files...
Building for 4.17.0-1-amd64
Building initial module for 4.17.0-1-amd64
Error! Bad return status for module build on kernel: 4.17.0-1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.10/build/make.log for more information.
[ ok ] Unloading VirtualBox kernel modules....
[FAIL] Loading VirtualBox kernel modules...[....] No suitable module for running kernel found ... failed!
 failed!
invoke-rc.d: initscript virtualbox, action "restart" failed.
richard@T430:/media
$ 

[Richard]

... and the second seems to have failed also:

Code: Select all

$ sudo /usr/share/mx-packageinstaller-pkglist/rebuild_dkms_packages.sh

-------- Uninstall Beginning --------
Module:  broadcom-sta
Version: 6.30.223.271
Kernel:  4.15.0-1-amd64 (x86_64)
-------------------------------------

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

wl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.15.0-1-amd64/updates/dkms/
 - 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...

Backing up initrd.img-4.15.0-1-amd64 to /boot/initrd.img-4.15.0-1-amd64.old-dkms
Making new initrd.img-4.15.0-1-amd64
(If next boot fails, revert to initrd.img-4.15.0-1-amd64.old-dkms image)
update-initramfs......

DKMS: uninstall completed.

-------- Uninstall Beginning --------
Module:  broadcom-sta
Version: 6.30.223.271
Kernel:  4.17.0-1-amd64 (x86_64)
-------------------------------------

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

wl.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.17.0-1-amd64/updates/dkms/
 - 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...

Backing up initrd.img-4.17.0-1-amd64 to /boot/initrd.img-4.17.0-1-amd64.old-dkms
Making new initrd.img-4.17.0-1-amd64
(If next boot fails, revert to initrd.img-4.17.0-1-amd64.old-dkms image)
update-initramfs......

DKMS: uninstall completed.

------------------------------
Deleting module version: 6.30.223.271
completely from the DKMS tree.
------------------------------
Done.
Loading new broadcom-sta-6.30.223.271 DKMS files...
Building for 4.17.0-1-amd64
Building initial module for 4.17.0-1-amd64
Done.

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

depmod...

Backing up initrd.img-4.17.0-1-amd64 to /boot/initrd.img-4.17.0-1-amd64.old-dkms
Making new initrd.img-4.17.0-1-amd64
(If next boot fails, revert to initrd.img-4.17.0-1-amd64.old-dkms image)
update-initramfs......

DKMS: install completed.

-------- Uninstall Beginning --------
Module:  ndiswrapper
Version: 1.61
Kernel:  4.15.0-1-amd64 (x86_64)
-------------------------------------

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

ndiswrapper.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.15.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.

-------- Uninstall Beginning --------
Module:  ndiswrapper
Version: 1.61
Kernel:  4.17.0-1-amd64 (x86_64)
-------------------------------------

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

ndiswrapper.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.17.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: 1.61
completely from the DKMS tree.
------------------------------
Done.
Loading new ndiswrapper-1.61 DKMS files...
Building for 4.17.0-1-amd64
Building initial module for 4.17.0-1-amd64
Done.

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

depmod...

DKMS: install completed.

------------------------------
Deleting module version: 5.2.10
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.10 DKMS files...
Building for 4.17.0-1-amd64
Building initial module for 4.17.0-1-amd64
Error! Bad return status for module build on kernel: 4.17.0-1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox/5.2.10/build/make.log for more information.

-------- Uninstall Beginning --------
Module:  virtualbox-guest
Version: 5.2.10
Kernel:  4.15.0-1-amd64 (x86_64)
-------------------------------------

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

vboxguest.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.15.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.


vboxsf.ko:
 - Uninstallation
   - Deleting from: /lib/modules/4.15.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.15.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.10
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-guest-5.2.10 DKMS files...
Building for 4.17.0-1-amd64
Building initial module for 4.17.0-1-amd64
Error! Bad return status for module build on kernel: 4.17.0-1-amd64 (x86_64)
Consult /var/lib/dkms/virtualbox-guest/5.2.10/build/make.log for more information.
richard@T430:/media
$ 

[Richard]

With the same Vbox error:

Code: Select all

Kernel driver not installed (rc=-1908)

The VirtualBox Linux kernel driver (vboxdrv) is either not loaded or there is a permission problem with /dev/vboxdrv. Please reinstall virtualbox-dkms package and load the kernel module by executing

'modprobe vboxdrv'

as root.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) - The support driver is not installed. On linux, open returned ENOENT. 

[Richard]

So, back to the old tried and true method:

Code: Select all

Thanks to Stevo.

Set up VBox for new kernel as follows:
;; boot the new kernel
;; activate mx test repo (MX Repo Manager is quick)
;; in a terminal, as root:
# apt-get update
# m-a prepare
# apt-get remove virtualbox-dkms
# apt-get install virtualbox-dkms
# modprobe vboxdrv
;; if no error, de-activate mx testrepo
;; execute Virtualbox

and Vbox is running with Win7.

[kmathern]

Well the first command didn't work.

Code: Select all

$ sudo dpkg-reconfigure virtualbox-dkms
------------------------------
Deleting module version: 5.2.10
completely from the DKMS tree.
------------------------------
Done.
Loading new virtualbox-5.2.10 DKMS files...
Building for 4.17.0-1-amd64
Building initial module for 4.17.0-1-amd64
Error! Bad return status for module build on kernel: 4.17.0-1-amd64 (x86_64) ...

I think you need a newer vbox version than 5.2.10 for a 4.17 series kernel.


A patch for 4.17 kernels was added in vbox version 5.2.12, and 5.2.16 is available in the MX-17 testrepo.

Code: Select all

virtualbox (5.2.12-dfsg-3) unstable; urgency=medium

  * debian/patches/fixes_for_4.17.patch
    from opensuse: fix build with kernel 4.17 (LP: #1776671)

 -- Gianfranco Costamagna <locutusofborg@debian.org>  Thu, 14 Jun 2018 10:09:21 +0200

edit: nevermind, I see you installed the testrepo version.