Package Details: linux-lqx 6.10.10.lqx2-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: 159
Popularity: 0.31
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-09-15 19:57 (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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 121 Next › Last »

sir_lucjan commented on 2019-01-14 15:25 (UTC)

I don't support aur-helpers.

Please use makepkg instead yay.

simona commented on 2019-01-14 15:20 (UTC)

==> Uscita dall'ambiente di fakeroot. ==> Compilazione terminata: linux-lqx 4.19._-1 (lun 14 gen 2019 14:12:33 CET) ==> Pulizia in corso... caricamento dei pacchetti in corso... errore: '/home/simona/.cache/yay/linux-lqx/linux-lqx-4.19.15_1-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto errore: '/home/simona/.cache/yay/linux-lqx/linux-lqx-docs-4.19.15_1-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto errore: '/home/simona/.cache/yay/linux-lqx/linux-lqx-headers-4.19.15_1-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto

sir_lucjan commented on 2019-01-13 17:11 (UTC)

Please paste a log with error.

simona commented on 2019-01-12 10:54 (UTC)

compile but at the end do not create package...

Agafron commented on 2018-12-21 20:37 (UTC)

@damentz, I can`t initialize rules on this kernel, any comand had answer 'No chain/target/match by that name', Its after update on 4.19-lqx? on the custom kernel iptables works ok. OS manjaro. which info can I give you to fix this problem?

damentz commented on 2018-12-21 18:10 (UTC)

@Agafron, there shouldn't be anything different with iptables on liquorix. On my work laptop, I'm able to use UFW to block incoming connections besides those to port 22, and sshuttle to create poor mans VPNs utilizing iptables to redirect traffic.

Maybe you forgot to initialize your rules?

Agafron commented on 2018-12-19 20:25 (UTC)

@damentz, hi! I have some problems with iptables on this version

sudo iptables -L

iptables: No chain/target/match by that name.

what parameters affect it?

damentz commented on 2018-12-01 20:42 (UTC)

@Filip98, I'll re-enable hierarchical scheduling once Paolo corrects an oops when it's enabled. You can see the progress on the bfq-iosched google group here: https://groups.google.com/forum/#!topic/bfq-iosched/5wkrbgXf4VM

Filip98 commented on 2018-11-27 23:00 (UTC)

This kernel seems to have an issue with libvirt(Qemu/KVM) http://i64.tinypic.com/30m9ul3.jpg http://i65.tinypic.com/oqg1ow.jpg I've digged a little bit around the net: https://forums.whonix.org/t/solved-cant-start-the-new-14-whonix-vms-libvirterror-unsupported-configuration-block-i-o-tuning-is-not-available-on-this-host/5664 and looks like it requires the following to be enabled in the kernel: CONFIG_BLK_CGROUP CONFIG_CFQ_GROUP_IOSCHED CONFIG_BLK_DEV_THROTTLING I switched to my alternative kernel and it runs fine, I didn't recompile to confirm that this fixes the issue tho

damentz commented on 2018-11-20 14:43 (UTC) (edited on 2018-11-20 15:21 (UTC) by damentz)

@Terence, I briefly experimented again with 1000hz but it was a huge drain on battery life. MuQSS 0.173 (and possibly 0.180 with 4.19), doesn't support tickless idle correctly, and ends up feeding cpufreq with bad idle data. The periodic forces cpufreq to ingest idle time accounting data, letting the cpu properly rest while idle, but the periodic tick prevents the CPU from staying in the CPU's lowest state (C6 / C7). It's measurable, and I mentioned some data points in my commit reverting back to 250hz here:

https://github.com/damentz/liquorix-package/commit/070398c973863e03dc384e578e27f58d9f05c607

Until I figure out a better compromise with 1000hz, you'll need to manually go in on every build and raise the frequency to 1000hz for your system. It's perfectly fine for desktops but a huge problem on laptops. Both my personal and work laptops lose about 20%-30% battery life for idle / casual loads. In my testing, 250hz preserves cpu temperatures as well as tickless idle, so that'll work for now.

Also, I re-enabled IRQ time accounting as it seems that it was originally added so that the process scheduler (CFS in this case), had more accurate data about how much cpu time each task consumed. It should have some benefits for MuQSS as well.

« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 121 Next › Last »