Package Base Details: linux-lqx

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only)
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 124
Popularity: 1.55
First Submitted: 2011-08-08 16:08
Last Updated: 2019-12-06 14:52

Latest Comments

« First ‹ Previous ... 3 4 5 6 7 8 9 10 11 12 13 ... Next › Last »

Agafron commented on 2018-12-21 20:37

@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

@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

@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

@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

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

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

Agafron commented on 2018-11-19 19:30

@sir_lucjan, ok, thanks!

sir_lucjan commented on 2018-11-19 19:26

@Agafron

I don't think so.

https://github.com/damentz/liquorix-package/commit/51704fbc01fd69274ce2c236fa2d180276d6aa60

https://github.com/damentz/liquorix-package/commit/7dd11beb3448cb3bca3b175566022d96bb35db46

Agafron commented on 2018-11-19 19:24

@sir_lucjan, ok, need I reinstall package?

$ uname -r

4.18.19-lqx1-1-lqx

sir_lucjan commented on 2018-11-19 19:12

Agafron:

No.

https://github.com/damentz/liquorix-package/commit/7dd11beb3448cb3bca3b175566022d96bb35db46