MX Linux Forum

Posted: **Fri Dec 06, 2024 9:39 pm**

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

Code: Select all

echo "deb http://mxrepo.com/mx/repo/ bookworm ahs-staging" | sudo tee /etc/apt/sources.list.d/ahs-staging.list
sudo apt update

at the moment, the kernel and above packages are the only new thing in ahs-staging that isn't already in ahs, so

Code: Select all

sudo apt dist-upgrade

then disable the ahs-staging repo

Code: Select all

sudo rm /etc/apt/sources.list.d/ahs-staging.list
sudo apt update

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.

Code: Select all

 kvm.enable_virt_at_load=0

Posted: **Sat Dec 07, 2024 12:40 am**

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.

Posted: **Sat Dec 07, 2024 6:26 am**

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.

Posted: **Sat Dec 07, 2024 7:01 am**

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.

Posted: **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.

Posted: **Sat Dec 07, 2024 3:00 pm**

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.

Posted: **Sat Dec 07, 2024 3:15 pm**

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.

Posted: **Sat Dec 07, 2024 6:52 pm**

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.

Posted: **Sat Dec 07, 2024 11:07 pm**

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.

Posted: **Sun Dec 08, 2024 4:35 am**

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

Posted: **Sun Dec 08, 2024 9:53 am**

Is it possible to make a live USB iso with 6.12 kernel without having it installed and booted? I don't think 6.12 will work on this pc.

Posted: **Sun Dec 08, 2024 11:02 am**

For all users who haven't done yet, this will do it for you:

Code: Select all

echo 'options kvm enable_virt_at_load=0' | sudo tee /etc/modprobe.d/kvm.conf

Posted: **Sun Dec 08, 2024 12:23 pm**

dolphin_oracle wrote: Fri Dec 06, 2024 9:39 pm liquorix 6.12 is available in ahs-staging.

Is the kernel still available?

Code: Select all

sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1
  libdrm2 libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
  libxatracker2 mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers
The following packages will be upgraded:
  nvidia-detect
1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Need to get 156 kB of archives.
After this operation, 5,120 B of additional disk space will be used.
Do you want to continue? [Y/n]

QSI: (I removed the staging repo when I didn't see the 6.12 Liquorix kernel mentioned)

Code: Select all

Snapshot created on: 20241207_0516
System:
  Kernel: 6.12.3-x64v3-xanmod1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.0 clocksource: tsc
    avail: hpet,acpi_pm parameters: BOOT_IMAGE=/boot/vmlinuz-6.12.3-x64v3-xanmod1 root=UUID=<filter>
    ro quiet init=/lib/systemd/systemd
  Desktop: Fluxbox v: 1.3.7 with: tint2 tools: avail: light-locker vt: 7 dm: LightDM v: 1.32.0
    Distro: MX-23.4_fluxbox_x64 Libretto May 19 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required>
    uuid: <superuser required> UEFI: American Megatrends LLC. v: A.F0 date: 10/11/2023
CPU:
  Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
    built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
    microcode: 0xA20120E
  Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache: L1: 1024 KiB desc: d-16x32
    KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
  Speed (MHz): avg: 1707 high: 3412 min/max: 550/5084 boost: disabled scaling:
    driver: amd-pstate-epp governor: performance cores: 1: 3398 2: 550 3: 3400 4: 3400 5: 3393
    6: 3394 7: 3398 8: 550 9: 3400 10: 3399 11: 550 12: 550 13: 550 14: 550 15: 550 16: 3412
    17: 3397 18: 550 19: 550 20: 550 21: 550 22: 3392 23: 550 24: 550 25: 550 26: 550 27: 3401
    28: 550 29: 550 30: 550 31: 550 32: 3398 bogomips: 217597
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow mitigation: Safe RET
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
  Type: spectre_v2 mitigation: Retpolines; IBPB: conditional; IBRS_FW; STIBP: always-on; RSB
    filling; PBRSB-eIBRS: Not affected; BHI: Not affected
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
    driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
    gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-1 empty: DP-2, DP-3, HDMI-A-1, Writeback-1
    bus-ID: 0b:00.0 chip-ID: 1002:73df class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
    unloaded: fbdev dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
  Monitor-1: DP-1 mapped: DisplayPort-0 model: HP X27q serial: <filter> built: 2021
    res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
    ratio: 16:9 modes: max: 2560x1440 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi device: 1 drv: swrast
    surfaceless: drv: radeonsi x11: drv: radeonsi inactive: gbm,wayland
  API: OpenGL v: 4.6 vendor: amd mesa v: 23.1.2-1~mx23ahs glx-v: 1.4 es-v: 3.2 direct-render: yes
    renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.59 6.12.3-x64v3-xanmod1)
    device-ID: 1002:73df memory: 11.72 GiB unified: no
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
    speed: 16 GT/s lanes: 16 bus-ID: 0b:00.1 chip-ID: 1002:ab28 class-ID: 0403
  Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
    pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 14:00.4 chip-ID: 1022:1487 class-ID: 0403
  API: ALSA v: k6.12.3-x64v3-xanmod1 status: kernel-api tools: alsactl,alsamixer,amixer
  Server-1: PipeWire v: 1.2.2 status: active with: 1: pipewire-pulse status: active
    2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Wi-Fi 6E AX210/AX1675 2x2 [Typhoon Peak] driver: iwlwifi v: kernel pcie: gen: 2
    speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
  IF: wlan0 state: up mac: <filter>
  Info: services: NetworkManager,wpa_supplicant
Drives:
  Local Storage: total: 8.64 TiB used: 1.08 TiB (12.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 102000WD temp: 28.9 C scheme: GPT
  ID-2: /dev/nvme1n1 maj-min: 259:2 vendor: Western Digital model: WDS500G1X0E-00AFY0
    size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD
    serial: <filter> fw-rev: 613000WD temp: 32.9 C scheme: GPT
  ID-3: /dev/sda maj-min: 8:0 vendor: Seagate model: ST8000DM004-2CX188 size: 7.28 TiB
    block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5425 serial: <filter>
    fw-rev: 0001 scheme: GPT
  ID-4: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 EVO 500GB size: 465.76 GiB
    block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD serial: <filter>
    fw-rev: 1B6Q scheme: GPT
Partition:
  ID-1: / raw-size: 465 GiB size: 456.63 GiB (98.20%) used: 13.52 GiB (3.0%) fs: ext4
    dev: /dev/nvme1n1p2 maj-min: 259:4
  ID-2: /boot/efi raw-size: 779 MiB size: 777.5 MiB (99.80%) used: 288 KiB (0.0%) fs: vfat
    dev: /dev/nvme1n1p1 maj-min: 259:3
Swap:
  Kernel: swappiness: 15 (default 60) cache-pressure: 50 (default 100) zswap: no
  ID-1: swap-1 type: partition size: 64 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdb2
    maj-min: 8:18
Sensors:
  System Temperatures: cpu: 27.9 C mobo: N/A gpu: amdgpu temp: 35.0 C mem: 34.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Repos:
  Packages: pm: dpkg pkgs: 2265 libs: 1172 tools: apt, apt-get, aptitude, nala, synaptic pm: rpm
    pkgs: 0
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
    1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/debian.list
    1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
    2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
  Active apt repos in: /etc/apt/sources.list.d/mx.list
    1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
    2: deb http://la.mxrepo.com/mx/repo/ bookworm ahs
  Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
    1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
  Active apt repos in: /etc/apt/sources.list.d/xanmod-release.list
    1: deb [signed-by=/usr/share/keyrings/xanmod-archive-keyring.gpg] http://deb.xanmod.org releases main
  Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
    1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Info:
  Memory: total: 32 GiB available: 31.26 GiB used: 2.03 GiB (6.5%)
  Processes: 483 Power: uptime: 6m states: freeze,mem,disk suspend: deep avail: s2idle wakeups: 0
    hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.45 GiB Init: systemd
    v: 252 target: graphical (5) default: graphical tool: systemctl
  Compilers: gcc: 12.2.0 Client: shell wrapper v: 5.2.15-release inxi: 3.3.35
Boot Mode: UEFI

Posted: **Sun Dec 08, 2024 1:20 pm**

I also want to note, though we do have all the other packages listed in there also for MX 21, I was unable to backport the new Sid nvidia-driver for MX 21, since the precompiled binary blobs provided in it by Nvidia require openssl 3, which is not in Bullseye and seems impracticable to backport for it.

If you have a machine with nice open drivers, you should be able to use the kernel, even on MX 21.

Posted: **Sun Dec 08, 2024 4:41 pm**

siamhie wrote: Sun Dec 08, 2024 12:23 pm

dolphin_oracle wrote: Fri Dec 06, 2024 9:39 pm liquorix 6.12 is available in ahs-staging.

Is the kernel still available?

Code: Select all

sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages have been kept back:
  libdrm-amdgpu1 libdrm-common libdrm-intel1 libdrm-nouveau2 libdrm-radeon1
  libdrm2 libegl-mesa0 libgbm1 libgl1-mesa-dri libglapi-mesa libglx-mesa0
  libxatracker2 mesa-va-drivers mesa-vdpau-drivers mesa-vulkan-drivers
The following packages will be upgraded:
  nvidia-detect
1 upgraded, 0 newly installed, 0 to remove and 15 not upgraded.
Need to get 156 kB of archives.
After this operation, 5,120 B of additional disk space will be used.
Do you want to continue? [Y/n]

I'm a moron. I didn't bother to search in MXPI for Liquorix under the enabled tab.

I also had no problems with my 8814 driver.

Code: Select all

"Building module:"
"Cleaning build area..."
""
"'make' clean; 'make' -j16 KVER=6.12.1-1-liquorix-amd64 KSRC=/lib/modules/6.12.1-1-liquorix-amd64/build all; if [[ -x /usr/sbin/kmodsign ]]; then kmodsign sha512 MOK.priv MOK.der 8814au.ko; fi..."
"."
"."
""
"Cleaning build area..."
""
"8814au.ko.xz:"
"Running module version sanity check."
"- Original module"
"- No original module exists within this kernel\n - Installation"
"- Installing to /lib/modules/6.12.1-1-liquorix-amd64/updates/dkms/"
"depmod..."
"."
"."
""
"dkms: autoinstall for kernel: 6.12.1-1-liquorix-amd64."
"/etc/kernel/postinst.d/initramfs-tools:\nupdate-initramfs: Generating /boot/initrd.img-6.12.1-1-liquorix-amd64"

Posted: **Tue Dec 10, 2024 8:29 am**

@Stevo I see in the changelog for 6.12-4 this note:

Code: Select all

Revert all changes for the zstd switch for kernel and module compression.

what's the story there? I feel like I should know, but I can't remember.

Posted: **Wed Dec 11, 2024 5:34 pm**

dolphin_oracle wrote: Tue Dec 10, 2024 8:29 am @Stevo I see in the changelog for 6.12-4 this note:
Code: Select all
Revert all changes for the zstd switch for kernel and module compression.
what's the story there? I feel like I should know, but I can't remember.

Bookworm supports the zstd compression, but not Bullseye. Since Tim fixed the backports for gcc-10, I switched back to xz for both versions to be consistent. It matches what Debian does, and the kernel is smaller when installed, anyway.

I am backporting the new Sid 6.12.3 kernel. I have not yet checked whether the older Nvidia drivers have had more recent updates in Sid, or maybe they just work as is since their last updates in October, but it looks like moving 6.12 into AHS main is getting closer!

A poster on the Liquorix forums said the kvm.conf VBox trick didn't work for them--I wonder what's going on there. https://techpatterns.com/forums/about3095.html

Posted: **Wed Dec 11, 2024 6:00 pm**

the file needs to be /etc/modprobe.d/kvm.conf, not /etc/modules.d/kvm.conf - with that, I could also get xanmod's 6.12.4 running, along with Virtualbox.

Posted: **Wed Dec 11, 2024 6:20 pm**

the option will be in mx-tweak shortly. just waiting on a few more translations.

Posted: **Wed Dec 11, 2024 6:29 pm**

Stevo wrote: Wed Dec 11, 2024 5:34 pm Bookworm supports the zstd compression, but not Bullseye. Since Tim fixed the backports for gcc-10, I switched back to xz for both versions to be consistent. It matches what Debian does, and the kernel is smaller when installed, anyway.

I've actually - in order to check the LiveInitrd - reverted back your revert to zst-modules compression. Mainly b/c busybox in live-boot is not supporting zstd, I wanted to verify our kmod trick on the live-intrd would work also with zstd as well as does with xz. This was done together a secureboot-test with a signing all modules with a mok-signing key, so both worked.

Posted: **Wed Dec 11, 2024 7:46 pm**

Could anyone test the July rev of the 390xx legacy driver build currently in AHS with 6.12? Sid just added a patch in November, and I have some doubts it could have fixed a broken 6.12 build, so we might have to wait. If it's OK, moving to main could be around the corner.

Code: Select all

nvidia-graphics-drivers-legacy-390xx (390.157-9) unstable; urgency=medium

  * Backport nv_get_kern_phys_address() changes from 555.42.02 to fix kernel
    module build with gcc-14 on arm*.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 04 Nov 2024 09:16:04 +0100

nvidia-graphics-drivers-legacy-390xx (390.157-8) unstable; urgency=medium

  * Backport CONFIG_MITIGATION_RETPOLINE changes from 470.256.02.
  * Backport follow_pfn changes from 550.90.07 to fix kernel module build for
    Linux 6.10.
  * bug-script: Report 'apt-cache policy' (535.183.06-1).

 -- Andreas Beckmann <anbe@debian.org>  Fri, 26 Jul 2024 22:29:09 +0200

Posted: **Wed Dec 11, 2024 9:52 pm**

Stevo wrote: Wed Dec 11, 2024 7:46 pm Could anyone test the July rev of the 390xx legacy driver build currently in AHS with 6.12? Sid just added a patch in November, and I have some doubts it could have fixed a broken 6.12 build, so we might have to wait. If it's OK, moving to main could be around the corner.
Code: Select all
nvidia-graphics-drivers-legacy-390xx (390.157-9) unstable; urgency=medium

  * Backport nv_get_kern_phys_address() changes from 555.42.02 to fix kernel
    module build with gcc-14 on arm*.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 04 Nov 2024 09:16:04 +0100

nvidia-graphics-drivers-legacy-390xx (390.157-8) unstable; urgency=medium

  * Backport CONFIG_MITIGATION_RETPOLINE changes from 470.256.02.
  * Backport follow_pfn changes from 550.90.07 to fix kernel module build for
    Linux 6.10.
  * bug-script: Report 'apt-cache policy' (535.183.06-1).

 -- Andreas Beckmann <anbe@debian.org>  Fri, 26 Jul 2024 22:29:09 +0200

ahs legacy 390 does not build. (390.157-8~mx23ahs)

Posted: **Wed Dec 11, 2024 11:20 pm**

dolphin_oracle wrote: Wed Dec 11, 2024 9:52 pm
Stevo wrote: Wed Dec 11, 2024 7:46 pm Could anyone test the July rev of the 390xx legacy driver build currently in AHS with 6.12? Sid just added a patch in November, and I have some doubts it could have fixed a broken 6.12 build, so we might have to wait. If it's OK, moving to main could be around the corner.
Code: Select all
nvidia-graphics-drivers-legacy-390xx (390.157-9) unstable; urgency=medium

  * Backport nv_get_kern_phys_address() changes from 555.42.02 to fix kernel
    module build with gcc-14 on arm*.

 -- Andreas Beckmann <anbe@debian.org>  Mon, 04 Nov 2024 09:16:04 +0100

nvidia-graphics-drivers-legacy-390xx (390.157-8) unstable; urgency=medium

  * Backport CONFIG_MITIGATION_RETPOLINE changes from 470.256.02.
  * Backport follow_pfn changes from 550.90.07 to fix kernel module build for
    Linux 6.10.
  * bug-script: Report 'apt-cache policy' (535.183.06-1).

 -- Andreas Beckmann <anbe@debian.org>  Fri, 26 Jul 2024 22:29:09 +0200
ahs legacy 390 does not build. (390.157-8~mx23ahs)

Yeah, I had my doubts based on the changelog. The rest of the drivers, except for nvidia-driver 535, are similarly outdated.

Hopefully having 6.12 in Sid will light a fire there.

Posted: **Thu Dec 12, 2024 6:29 am**

dolphin_oracle wrote: Wed Dec 11, 2024 6:20 pm the option will be in mx-tweak shortly. just waiting on a few more translations.

169 has two issues:

no capital start of the sentence, and virtualbox is spelled wrong.

Posted: **Thu Dec 12, 2024 6:43 am**

Eadwine Rose wrote: Thu Dec 12, 2024 6:29 am
dolphin_oracle wrote: Wed Dec 11, 2024 6:20 pm the option will be in mx-tweak shortly. just waiting on a few more translations.
169 has two issues:

no capital start of the sentence, and virtualbox is spelled wrong.

Oops

Posted: **Thu Dec 12, 2024 7:42 am**

@Eadwine Rose new string should be up, if not now, soon.

that particular text is a tooltip.

Posted: **Thu Dec 12, 2024 7:51 am**

Thanks :)

Posted: **Tue Jul 15, 2025 2:28 pm**

I can report some progress

with my issue of Plasma Wayland locking up after login. With kernel 6.15.2-1-liquorix-amd64 #1 ZEN SMP PREEMPT_DYNAMIC liquorix 6.15-1~mx23ahs (2025-06-18), which I signed with a MOK, I am now *unable* to login (login failed) rather than having a full lockup, as I reported viewtopic.php?t=85235 a couple days ago.

Posted: **Tue Jul 15, 2025 4:06 pm**

That might have something to do with the revoked Wayland upgrade in the repos.

Posted: **Thu Jul 17, 2025 11:58 am**

Is there a workaround, @Stevo such as uninstall the revoked/reinstall the non-revoked? Or is that still under development? If there's a script I could test, I'd be happy to.

Posted: **Thu Jul 17, 2025 12:15 pm**

amlo wrote: Thu Jul 17, 2025 11:58 am Is there a workaround, @Stevo such as uninstall the revoked/reinstall the non-revoked? Or is that still under development? If there's a script I could test, I'd be happy to.

It's now fixed.

Since we know nothing about your system without a QSI, I, for one, can't guess what a solution for your issue might be.

Posted: **Thu Jul 17, 2025 9:23 pm**

There is a new 6.12.38 ahs kernel that appeared in the repo today. I installed it and now have problems. Should I start a new thread or post the problems here?

Posted: **Fri Jul 18, 2025 4:49 am**

Start a new thread please, this is a status forum. Thanks.

MX Linux Forum

AHS users: Liquorix kernel 6.12 in ahs-staging

AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging

Re: AHS users: Liquorix kernel 6.12 in ahs-staging