Package Details: linux-lqx 6.11.7.lqx1-2

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: 161
Popularity: 2.41
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-11-08 21:09 (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: 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 .. 84 85 86 87 88 89 90 91 92 93 94 .. 121 Next › Last »

damentz commented on 2013-12-20 21:35 (UTC)

kleku, when this package updates, can you try again? I made a change I was waiting to bundle with 3.12.6 (bundling updates together prevents massive number of updates and work for package maintainers). You'll have to wait though for shivik to update this package. Basically, I removed the Intel P-State cpufreq driver (final confirmation was Valve citing it as a problem for smooth performance on Steam), set ondemand as default governor, and set the ondemand sampling down factor to 10 (increases throughput during high load). My suspicion was that the Intel P-State cpufreq driver wasn't properly saving power when it could. You should be better off with ondemand.

kleku commented on 2013-12-20 11:08 (UTC)

Powertop on my notebook with standard kernel: The battery reports a discharge rate of 10.2 W and with -lqx kernel: The battery reports a discharge rate of 20.1 W :/ I'm using TLP.

damentz commented on 2013-12-02 07:04 (UTC)

Actually, I'm just on vacation from work and everything else for Thanksgiving. I'll update to 3.12 later this week - I can't responsibly update to 3.12 without having time to both use the kernel for an extended time and respond to feedback.

shivik commented on 2013-12-02 06:52 (UTC)

I think the answer lies below in the comments. damentz: "The only difference is that I do a bit of quality control and respond to feedback. It's hard to do that where there isn't a "product", or something to install and test immediately without wasting an hour of time compiling or figuring out what configuration to use." damentz test stuff to some extent prior to release. I haven't had any problems(even minor) with linux-lqx for more than a year. I don't even have rcu_preempt wrong time accounting and I enable BFS every time. So that would explain the delays to me. Not that it matters so much.It's just an enthusiast thing. I don't mind waitng :)

PerfectGentleman commented on 2013-12-02 04:38 (UTC)

I just wonder if LQX and Zen share the same codebase, why Zen is 3.12.2 and LQX is still 3.11.9 ?

damentz commented on 2013-12-02 02:24 (UTC)

Well, this package only has a 1 liter engine, so driving up hills is a hit or miss.

PerfectGentleman commented on 2013-12-02 00:05 (UTC)

why so slow?

ilikenwf commented on 2013-11-22 05:24 (UTC)

Just reminding folks that LQX and Zen share the same codebase, LQX just uses a more optimized config than a default kernel config....

shivik commented on 2013-11-21 06:18 (UTC)

No problem.Glad it worked.

saburouta commented on 2013-11-21 02:39 (UTC)

That was it, of course. Sorry I made you quote yourself. I thought it would be enough to nuke the packer* dirs in /tmp. Tarball worked.

« First ‹ Previous 1 .. 84 85 86 87 88 89 90 91 92 93 94 .. 121 Next › Last »