Package Details: linux-lqx 6.8.5.lqx1-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-lqx
Description: The Linux Liquorix kernel and modules
Upstream URL:
Keywords: bbr2 bfq futex pds proton zen
Licenses: GPL-2.0-only
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 158
Popularity: 1.54
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-04-11 13:22 (UTC)

Dependencies (19)

Required by (11)

Sources (3)

Pinned Comments

damentz commented on 2020-08-31 15:22 (UTC) (edited on 2021-12-21 18:25 (UTC) by damentz)

Official binaries of linux-lqx, linux-lqx-headers, and linux-lqx-docs are now available:

Signing key import instructions: sudo pacman-key --keyserver hkps:// --recv-keys 9AE4078033F8024D && sudo pacman-key --lsign-key 9AE4078033F8024D

Latest Comments

1 2 3 4 5 6 .. 120 Next › Last »

damentz commented on 2024-01-15 16:36 (UTC)

@xiota that's a red herring, htmldocs just creates html documentation using sphinx. The non html files are still there and are perfectly usable and preferred by many.

xiota commented on 2024-01-13 03:43 (UTC)

linux-lqx-docs needs to be removed from pkgname array when _htmldocs_enable is empty.

vlad1.96 commented on 2024-01-07 22:27 (UTC)

@damentz yes, I confirm, everything has become fine.

In addition to this, I did not write about it, but the warning disappeared when generating the UKI.

This warning didn't affect anything, and there was nothing in the logs, so I didn't think it was necessary to write about it earlier.

Thank you very much @damentz!

Anarconda commented on 2024-01-07 20:41 (UTC)

Everything seems to be ok with latest version

└──> amarcord #  dmesg | grep jitter
└──> amarcord #  dmesg | grep bpf
[    0.375484] LSM: initializing lsm=capability,yama,bpf
[    3.144390] systemd[1]: bpf-lsm: LSM BPF program attached
amarcord # 

Thank you very much. Regards.

damentz commented on 2024-01-07 19:51 (UTC)

Right, please try the latest kernel. The previous one needed resolve_btfids included in the package for DKMS to build out-of-tree kernels correctly. Latest kernel now includes it.

Anarconda commented on 2024-01-07 19:12 (UTC)

I built the kernel from AUR and the problem with the display manager is what @vlad1.96 says there's not nvidia.ko.* not in /lib/modules/.

vlad1.96 commented on 2024-01-07 19:03 (UTC) (edited on 2024-01-07 19:14 (UTC) by vlad1.96)

@Anarconda @damentz hid_bpf error and bpf-lsm failed disappear and system is booting (except nvidia), but the nvidia dkms module is not installed.

Error! Bad return status for module build on kernel: 6.6.10-lqx1-3-lqx (x86_64)

Consult /var/lib/dkms/nvidia/545.29.06/build/make.log for more information.

==> WARNING: `dkms install --no-depmod nvidia/545.29.06 -k 6.6.10-lqx1-3-lqx' exited 10

if my localization interferes with reading. I can change it to English and repeat it again

damentz commented on 2024-01-07 18:53 (UTC) (edited on 2024-01-07 19:01 (UTC) by damentz)

@Anarconda, are you building with the AUR or using the binary package? I'm currently booted into the package built through CI.

Also, you can boot into another kernel and check logs from your previous boot with journalctl -b -1 (add -k for just kernel logs). If you're not using systemd, I'm assuming it'll be in a bunch of files in /var/log.

EDIT: It appears I need to restore a commit:

New version is already on the way if you prefer binary build.

Anarconda commented on 2024-01-07 18:36 (UTC)

@damentz It doesn't boot. Even when system is accessible from another tty the messages stop after show that net is up. No display manager, just stop there.

damentz commented on 2024-01-07 16:40 (UTC)

Can ya'll try the latest release? I made a few changes:

  1. Enable some missing DRBG algorithms (hash and counter block mode)
  2. Enabled the latent entropy GCC plugin to force more entropy at boot
  3. Re-enabled kernel debugging with BTF (required as per
  4. Enabled module compression with ZSTD, switched kernel image to ZSTD compression as well

I can verify the hid_bpf and bpf-lsm errors are gone, but I don't have any systems triggering the jitterentropy error to confirm if my changes helped.