Package Details: linux-lqx-headers 6.8.7.lqx2-1

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only, click to copy)
Package Base: linux-lqx
Description: Headers and scripts for building modules for the Linux Liquorix kernel
Upstream URL: https://liquorix.net/
Keywords: bbr2 bfq futex pds proton zen
Licenses: GPL-2.0-only
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 158
Popularity: 1.33
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-04-19 15:10 (UTC)

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 .. 111 112 113 114 115 116 117 118 119 120 Next › Last »

shivik commented on 2011-11-22 19:15 (UTC)

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 (UTC)

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 (UTC)

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.

<deleted-account> commented on 2011-10-30 23:13 (UTC)

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 (UTC)

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 (UTC)

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 (UTC)

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

« First ‹ Previous 1 .. 111 112 113 114 115 116 117 118 119 120 Next › Last »