Package Details: linux-lqx 6.11.10.lqx1-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: 161
Popularity: 1.70
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-11-22 16:37 (UTC)

Dependencies (19)

Required by (12)

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 .. 46 47 48 49 50 51 52 53 54 55 56 .. 121 Next › Last »

sir_lucjan commented on 2016-07-12 14:33 (UTC)

Bump to 4.6.4

damentz commented on 2016-07-01 00:40 (UTC) (edited on 2016-07-01 00:42 (UTC) by damentz)

@sir_lucjan I don't specifically remember changing the configuration since the last release, but I do recommend updating the package to use github tags here: https://github.com/damentz/liquorix-package/releases Each tag on github has an associated zip and tar.gz file, like so: https://github.com/damentz/liquorix-package/archive/4.6-3.tar.gz In each of these is the config folder, linux-liquorix/debian/config/kernelarch-x86. I do understand though that this will take time to implement. If I get some free time I'll try my stab at updating the kernel package to use this method. EDIT: Forgot to mention, the patch is also available in the folder, linux-liquorix/debian/patches/zen.

damentz commented on 2016-07-01 00:35 (UTC)

@Junio_Calu Nice catch, I wasn't aware that the graysky2 patches added their own native architecture configuration. I committed a change to the zen source to remove the ZEN specific option since it duplicates the option in graysky2's (which is preferred since it adds more specific architectures). Change commit ID: https://github.com/zen-kernel/zen-kernel/commit/78d08393dc4d868f348a885d66c64cd92942199b Next version of the liquorix package will have this change merged.

sir_lucjan commented on 2016-06-30 08:46 (UTC) (edited on 2016-06-30 08:47 (UTC) by sir_lucjan)

@saburouta Probably damentz has changed config files.

saburouta commented on 2016-06-30 04:32 (UTC)

Is there a reason the config files do not match the checksum array? Does that happen often?

JunioCalu commented on 2016-06-29 02:26 (UTC) (edited on 2016-06-29 02:26 (UTC) by JunioCalu)

damentz, I chose CONFIG_MNATIVE option, so it is also necessary to mark CONFIG_X86_MARCH_NATIVE ?

damentz commented on 2016-06-29 01:22 (UTC)

This patch is already merged per this commit: https://github.com/zen-kernel/zen-kernel/commit/dce22c423602594e2cfc27c19588b9010ff12065 Customize with menuconfig or xconfig and you'll see new options in the processor architecture section.

JunioCalu commented on 2016-06-29 01:20 (UTC) (edited on 2016-06-29 01:23 (UTC) by JunioCalu)

sir_lucjan, could add support to "kernel_gcc_patch" created by graysky2 as an option? https://github.com/graysky2/kernel_gcc_patch

sir_lucjan commented on 2016-06-19 20:32 (UTC)

Bump to 4.6.2-2

damentz commented on 2016-06-19 20:19 (UTC)

Released a new patch that removes CKO from the kernel source, this should fix the build error that eeleater and metak confirmed. Also, I've been pushing my changes to github here: https://github.com/damentz/liquorix-package Each release is tagged and downloadable as a zip or tar.gz file. For instance, the latest release as of this post can be downloaded from this link: https://github.com/damentz/liquorix-package/releases/tag/4.6-3 Inside are the patches and configuration. Just an FYI in case handling github releases through the AUR is easier than tracking the files from http://liquorix.net/sources

« First ‹ Previous 1 .. 46 47 48 49 50 51 52 53 54 55 56 .. 121 Next › Last »