Package Base Details: linux-lqx

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only, click to copy)
Keywords: bbr2 bfq futex muqss proton zen
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 142
Popularity: 2.45
First Submitted: 2011-08-08 16:08
Last Updated: 2021-12-02 01:33

Pinned Comments

damentz commented on 2020-08-31 15:22

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; done

td123 commented on 2011-11-22 21:49

There is a good reason those patches do get applied to the arch kernel (fix freezes on certain hardware).

The arch kernel does the compression also, so I think it's safe to say that this kernel should be using _compress_modules="yes" for all cases.
I can't think of a reason why you wouldn't want this.

The problem with creating another linux-lqx pkg in the aur is that it would be a duplicate.

I guess for now, I will just try reworking the PKGBUILD and see what you guys think before posting it here...

shivik commented on 2011-11-22 19:23

I'm kind of against this.
The main idea is to get the base kernel with the liquorix patchset applied only.
As for the options - almost all of the other AUR kernels have those and they're kind of useful sometimes.
Maybe _compress_modules is useless...
A PKGBUILD cleanup would be nice though

Your ideas are by no means bad,but I think this package should be left the way it is.
Maybe you should create a new kernel based on the -lqx one and realize your ideas.

shivik commented on 2011-11-22 19:15

I'm kind of against this.
The main idea is to get the base kernel with the liquorix patchset applied only.
As for the options - almost all of the other AUR kernels have those and they're kind of useful sometimes.
Maybe _compress_modules is useless...
A PKGBUILD cleanup would be nice though

Your ideas are by no means bad,but I think this package should be left the way it is.
Maybe you should create a new kernel based on the -lqx one and realize your ideas.

td123 commented on 2011-11-22 18:14

I'll try to rebase this kernel against the latest linux in [core].
My current thoughts are what to do about patches that get applied?
Also, I'm planning on removing some if not all of the options provided at the top: _menu, _config, _compress_modules
And general cleanup of the PKGBUILD so that future maintenance would be a lot easier.

Does anyone have any opinions for or against this?
If I can't update the PKGBUILD in about a week, I will just give up since that will probably mean I don't have enough time to figure all of this out.

shivik commented on 2011-10-31 06:29

I tried it - 18 hours running already with no problems.
I can update the PKGBUILD here if there's no one else to do it.

shivik commented on 2011-10-31 06:29

I tried it - 18 hours running already with no problems.
I can update the PKGBUILD here if there's no one else to do it.

Anonymous comment on 2011-10-30 23:13

anyone tried substituting the 8 patch for the 6 this PKGBUILD calls for? I'd try but exams taking up soo much time...
Anyhow thanks.

damentz commented on 2011-10-29 21:05

You might want to look at this post: http://techpatterns.com/forums/about1917.html

LVM requires you to have at least three numbers in your kernel version. For instance, 3.0-6.dmz.1-liquorix-amd64 broke support for LVM and other disk layer user space, but adding in a second 0 for compatibility (3.0.0-6.dmz.1-liquorix-amd64) with the old 2.6.n format works around this bug.

You can check with `uname -r`, make sure you have three numbers in the kernel version (3.0.0 for instance). I suspect that you only need to modify your package scripts to accommodate this change.

akurei commented on 2011-10-29 20:51

When using linux-lqx, I am not able to snapshot a lvm volume. Also while booting, there are error messages like "hey i cannot find your LVM volumes, but i will let you boot anyway". This problem only appears on linux-lqx. All other kernels work fine. I double, triple, quadruple-checked the .config files for dm_*, and still this error persists. I simply cannot run my LVM Backupscript when I am running the lqx kernel.

My lvm backupscript:
URL: http://paste.pocoo.org/show/aImN9jXMM6kXIlZx8Xwy/
RAW: http://paste.pocoo.org/raw/aImN9jXMM6kXIlZx8Xwy/

damentz commented on 2011-10-29 20:45

You're the first to report this bug, can you tell me more about it on the Liquorix forums?