MX Linux Forum

liquorix 6.12 is available in ahs-staging.

Packages for virtualbox, broadcom-sta (wl wifi drivers), nvidia-driver 535 are also in ahs-staging, with updates to allow their kernel modules to build on 6.12.

If you want to try them out, you'll need to enable the ahs-staging repo, which is not mirrored.

to enable ahs-staging
at the moment, the kernel and above packages are the only new thing in ahs-staging that isn't already in ahs, so
then disable the ahs-staging repo
I'm honestly not sure how long these will stew in ahs-staging before we release them into ahs main. Let us know any feedback.


Edit


Virtualbox and maybe VMware users will need the following boot parameter.

Followed above instructions at approx 1515Hrs and all went good, rebooted, the Bluetooth, music player, Spectacle screenshooter, Gimp all seemed to be A OK.
@dolphin_oracle Thanks for the thread/post
@Stevo Thank you for all the work you do.

was going to post an image clicked on P Add image to post then got this

Warning
Suspected Phishing
This website has been reported for potential phishing.

Phishing is when a site attempts to steal sensitive information by falsely presenting as a safe source.

Just letting you know

can always post image another time if I don't forget.

Currently 6.12 kernels require an extra boot switch "kvm.enable_virt_at_load=0", or Virtual Box won't run. This is for any 6.12 kernel, not just Liquorix, unless a maintainer adds a little code patch to disable the new behavior. That seems to break KVM working out of the box, though...and loading and unloading the kvm module on the fly seems too easy a solution for that not to be suggested. I'm sure they didn't miss that.

seems like Virtualbox 7.1.4.2 somehow can coexist with the standard settings of kernel 6.12, as they wrote in the Arch forum:

https://bbs.archlinux.org/viewtopic.php?id=301155

Edit: Seems like the Arch Linux guys adjusted the Virtualbox package - Could not find anything in the Oracle release notes.

for virtualbox, rather than a grub boot code, make a file under /etc/modprobe.d with the following contents
and that will cover things.

thanks to @Stevo for uncovering the module option.

dolphin_oracle wrote: Sat Dec 07, 2024 2:47 pm for virtualbox, rather than a grub boot code, make a file under /etc/modprobe.d with the following contents

Code: Select all

options kvm enable_virt_at_load=0

and that will cover things.

thanks to @Stevo for uncovering the module option.

I miss a +1 function here - should a 6.12 Kernel come around, it should be made sure to get this info out again.

Name that file kvm.conf just to make sure. It will also cover the current xanmod 6.12 and future Debian 6.12 and higher kernels.

Surprised that the leet Arch users missed that one simple trick.

I had to import the 7.0.22 virtual box source, Debian's still at 7.0.20, which won't build its modules on 6.12

All the Debian 7.0.20 patches still worked for 7.0.22, though.

so, did the upgrade to Kernel 6.12, along with the other packages from ahs-staging. However, instead of deleting the ahs-staging.list file, I disabled the source in the repo manager (so, it's easier to switch it back on when needed).

Also, the tip with the /etc/modprobe.d/kvm.conf worked out; VirtualBox startet up as expected.

Tested with some more of our AHs DKMS drivers, though I don't have the hardware:

rtl8814au-dkms: successful build and install

rtl8812au-dkms: successful build and install

rtl8821ce-dkms: successful build and install

rtl8821cu-dkms: stops build because the kernel has an internal driver already;)

Also, v4l2loopback-dkms builds and installs.

So, we only need to wait for Debian upstream to get the older proprietary Nvidia drivers updated if possible, and then backport them.

From 6.11.10 it just gave me 24 updates. I unchecked the staging repo as well. Is it just me or does my pc actually work better? 6.12.1 liqourix even sounds right. You guys are awesome. Thank You