MX Linux Forum

You are also not really clear about whonix, since it also runs in a virtual machine, and may insist on its own version of virtualbox. So it's also still a really prime suspect.

You may have to set MX to install recommended packages by default if you want to use third-party repos.


That was ...

OK so not the fault of whonix, after a kernel update it happened again, could not run any VM because the dkms driver was not availably.

The fix was to reinstall virtualbox-dkms, seems like the kernel updating did not pull through the dkms from this already installed package?

Did a restart now to ...

@rambo919 Couldn't help but notice your MX repos. Is there a reason you have test enabled?
Whenever I want to try a newer version of a program, I just use MXPI and go to the test tab.


I honestly cannot remember.... I think there was a bit of a toggle when I disabled deb-multimedia because of ...

Somehow bots doing hacking is not so fun as when hacktivists do it themselves.... skynet might not be coming for the meatbags as yet but it does seem to be coming for their communication systems.

OK I think I have to lay the blame on whonix here.... thought it was a repeat of past kernel problems. The VB deb file removes 5 VB packages including extpack and guest iso. The whonix installer downgrades this again to 7.0.20 and reinstalls the removed packages, both this and upgrading again to 7.0 ...

It runs but when you try to start a VM it complains that virtualbox-dkms needs to be installed. I see there are single manual install deb files for bookworm for the latest VB (7.1.8 ) which specifically adds support for this kernel but the one in the repo's is still 7.0.22.

But installing this will ...

I almost miss the old BSOD's in a twisted way.... they ruined it's usefulness with Vista.

It actually became funny getting a BSOD (and sometimes a temporary one?) just for ejecting a CD too quickly.

No, because my computer runs fine on the stock kernel and also on the previous kernel which it was only after an update of the kernel that this issue occurred on.

This is what is called a regression, a bug introduced by an update. Updates are supposed to improve but sometimes they do the ...

Stevo wrote: Wed Apr 09, 2025 4:48 pm vhba-module-update.zipHere's the latest update attached:

Many thanks.

Would it not make more sense to identify what hardware exactly is causing this issue? It could be any rando i/o subsystem, if it is on the motherboard a bios update could solve it though I have no shortage of rants and ravings about how utterly useless bios changelogs are for figuring out what ...