Package Details: linux-lqx 6.14.3.lqx1-1

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only, click to copy)
Package Base: linux-lqx
Description: The Linux Liquorix kernel and modules
Upstream URL: https://liquorix.net/
Keywords: bbr2 bfq futex pds proton zen
Licenses: GPL-2.0-only
Provides: UKSMD-BUILTIN, VHBA-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 165
Popularity: 2.01
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2025-04-20 18:28 (UTC)

Dependencies (19)

Required by (12)

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: 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

Latest Comments

« First ‹ Previous 1 .. 82 83 84 85 86 87 88 89 90 91 92 .. 122 Next › Last »

<deleted-account> commented on 2014-01-29 20:31 (UTC)

5160298ee23bead800b918dec8306af6a14ccb112d3c34f6438019bdfe0dedad6fb4894d3a7058610c153414a3d30f383ce34494ba5d5f6f95cb6ce3b6372489 3.12.9-2.patch.gz

<deleted-account> commented on 2014-01-29 20:26 (UTC)

==> Validating source files with sha512sums 3.12.9-2.patch.gz ... FAILED

shivik commented on 2014-01-28 19:26 (UTC)

linux-lqx.install gets overwritten every time the package is built,so not really a problem. If you build the package you'll get a linux-lqx.install with KERNEL_VERSION 3.12.9-1 (or whatever the current version)

<deleted-account> commented on 2014-01-28 10:36 (UTC)

need to FIX - > KERNEL_VERSION=3.12.8-1-lqx in linux-lqx.install

shivik commented on 2014-01-18 07:46 (UTC)

There is an option now in PKGBUILD for those who wish to use BFS. Just set _use_BFS to "yes" and you're good to go.

damentz commented on 2014-01-18 01:44 (UTC)

joko, CFS has less functional bugs than BFS. After a few years of going back and forth due to new random bugs, I decided to stick to CFS and work with it instead. One nice feature of CFS that BFS doesn't have is autogrouping, taking advantage of cgroups to share CPU bandwidth more fairly. This is most obvious when building software with multiple threads - the build tool will be grouped and will be treated as a single process, preventing a DoS on your own system. This is important for desktops where increased latency through interactivity is considered a big problem. Lastly, since BFS has been released, many of the bugs that once infested CFS have been fixed. If you read benchmarks, there's no drastic difference between the two schedulers. That leaves behavior, which I don't believe is really an issue anymore. I can be building a kernel, watching youtube, and playing an intensive AAA game at the same time and I can't tell the difference. The only difference with BFS is that you have access to sched_batch, which you can use to lower the priority of a build program that uses multiple threads. In CFS, you have auto grouping, which solves that problem nicely without any action of the user. So there you go, that's the reality of CFS vs BFS. Behavior is mostly identical and throughput is close enough to not matter.

joko commented on 2014-01-18 00:04 (UTC)

Hello, does this kernel use the BFS scheduler? I have compiled this package quickly via yaourt and it seems it doesn't: $ dmesg | grep scheduler [ 0.636725] io scheduler noop registered [ 0.636725] io scheduler deadline registered [ 0.636743] io scheduler cfq registered [ 0.636757] io scheduler bfq registered (default) [ 0.702179] CFS CPU scheduler. Any reason why it is not used?

KairiTech commented on 2014-01-12 21:27 (UTC)

Appreciate your efforts. I'll keep working at it to find an easier way to keep track of the mobo-specific kernels I create. Thanks again for your efforts.

shivik commented on 2014-01-12 20:09 (UTC)

I did a pacman -Rns linux-lqx prior to installing the rebuilt linux-lqx(with the custom name). Maybe this has something to do.I mean if you haven't done that yourself... This is all I can think of for now. Making that work for your case turns out to be beyond my knowledge. Next step is a completely modified PKGBUILD just for your needs.