Arch Linux User Repository

Official binaries of linux-lqx, linux-lqx-headers, and linux-lqx-docs are now available: https://wiki.archlinux.org/index.php/Unofficial_user_repositories#liquorix

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

When using the localmodconfig option, it does not set CONFIG_NLS_CODEPAGE_437(This was causing problems with efi)

It should go without saying, if you change the config your "warranty" is voided. You're on your own as soon as you deviate from the defaults. There's a reason the prebuilt binary works, it uses the default configuration defined in the PKGBUILD.

it's also doing this CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/sbin/init", which is different from CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/usr/lib/systemd/systemd"

By default, /sbin/init is a symlink to /usr/lib/systemd/systemd.

I have now got it now to mount efi and get to graphical environment by manually setting config options. But still have problems with Network and mounting other filesystems. Still probably missing config options.

Your problems are self inflicted. If the defaults don't work, I'm happy to help, but you're turning off config options then surprised when things don't work.

I am not using the comment section as tech support. Please do not make insinuations.

Yes you are, you are asking for support for mistakes you're making. The issue is you think it's the PKGBUILD's fault when you're the one making alterations by not using the Liquorix config unaltered.

@Damentz

I am not using the comment section as tech support. Please do not make insinuations.

I am reporting problems with the package/build.

Here are more concrete examples:

When using the localmodconfig option, it does not set CONFIG_NLS_CODEPAGE_437(This was causing problems with efi)

The only drm related config it sets is CONFIG_DRM_PANEL_ORIENTATION_QUIRKS=y

it's also doing this CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/sbin/init"

which is different from CONFIG_SECURITY_TOMOYO_ACTIVATION_TRIGGER="/usr/lib/systemd/systemd"

I have now got it now to mount efi and get to graphical environment by manually setting config options. But still have problems with Network and mounting other filesystems. Still probably missing config options.

I have not encountered these issues with other kernels that I have compiled.

I will take note of Building in a clean environment. But I dont see how it affects the settings I mentioned.

The liquorix.net build is a clean room docker build of the package without any previous state.

Arch_User: You are the only person having issues with the AUR build, so something on your system is different that is causing the failure. I recommend you try building from a fresh install, from the official Arch Linux docker image, or from a chroot: https://wiki.archlinux.org/title/DeveloperWiki:Building_in_a_clean_chroot.

The comment section for this package is not a technical support forum, so please use the Arch Linux forums if you continue to have issues.

It still wasn't working with the previous 2 updates. Was still messing up EFI and DRM.

This time with 6.9.3, it fails with all dkms modules. Won't even build them.

I have 6.9.3.arch1-1 custom compiled and working. But the same doesn't happen with this lqx kernel.

The question is: What's the difference between this AUR package/PKGBUILD and the one from liquorix.net? That one at least works. What config/scripts/sources are used there, such that it works there but not here?

@damentz There is nothing wrong with my initramfs, It works with every other custom kernel I have compiled and currently running. I also have liquorix installed from liquorix.net, that one works fine as well.

This one compiles fine, but works only partially.

There is something wrong with the scripts/patches that makes it fail with nvidia,nfs,network manager etc etc.

archdevlab, There's not really "optimized" for Arch Linux, but the config is optimized best for responsiveness and interactivity. The alternative scheduler has most of the impact while some deviations in config from Zen Kernel make the rest of the difference.

Arch_User, That sounds like your initramfs image is busted, if nothing's working and random things are failing to load, it's because the init system couldn't get access to modules on your filesystem to support your hardware, IMO. You can probably get help on bbs.archlinux.org; troubleshooting issues like that isn't in scope of comments on an AUR package.

Can someone confirm that this works on Arch with Nvidia? I have tried several times but it just doesn't work. It fails to mount stuff, fails with efi, fails with nfs, fails with Network Manager and fails to start gui with nvidia modules.

Yes I have built the dkms modules with the liquorix kernel. Lsmod shows them loaded, but nothing happens. It stops after graphical.target. You can ctrl+alt+f2/3/4/5/6 but not 7

Hi while Lqx and Zen kernel patches are almost the same what about the config you use. His the config from liquorix package optimized for Archlinux? What would be the main difference? Thanks!

@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.