Package Details: linux-lqx 6.10.11.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: 160
Popularity: 1.30
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-09-20 17:12 (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 .. 83 84 85 86 87 88 89 90 91 92 93 .. 121 Next › Last »

KairiTech commented on 2014-01-09 00:42 (UTC)

As suggested I appended -M5A99X_EVO in the PKGBUILD instead of running xconfig but got the error below instead: ==> Finished making: linux-lqx-M5A99X_EVO 3.12.6-1 (Wed Jan 8 19:37:51 EST 2014) ==> Installing package linux-lqx-M5A99X_EVO with pacman -U... loading packages... resolving dependencies... looking for inter-conflicts... Packages (1): linux-lqx-M5A99X_EVO-3.12.6-1 Total Installed Size: 0.00 MiB :: Proceed with installation? [Y/n] Y (1/1) checking keys in keyring [##############################] 100% (1/1) checking package integrity [##############################] 100% (1/1) loading package files [##############################] 100% (1/1) checking for file conflicts [##############################] 100% (1/1) checking available disk space [##############################] 100% (1/1) installing linux-lqx-M5A99X_EVO [##############################] 100% >>> Updating module dependencies. Please wait ... >>> Generating initial ramdisk, using mkinitcpio. Please wait... ==> Building image from preset: /etc/mkinitcpio.d/linux-lqx.preset: 'default' -> -k /boot/vmlinuz-linux-lqx -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lqx.img ==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-lqx' ==> Building image from preset: /etc/mkinitcpio.d/linux-lqx.preset: 'fallback' -> -k /boot/vmlinuz-linux-lqx -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-lqx-fallback.img -S autodetect ==> ERROR: specified kernel image does not exist: `/boot/vmlinuz-linux-lqx' :: linux-lqx cleaned

shivik commented on 2014-01-08 06:24 (UTC)

What about it? I just tried it out of curiosity. Removed nvidia, nvidia-lqx, installed nvidia-dkms, reboot, works.

ilkyest commented on 2014-01-08 01:15 (UTC)

What about the correct way to make nvidia driver working with this kernel? nvidia-dkms?

shivik commented on 2014-01-07 18:01 (UTC)

Basically you want to change -lqx to -lqx-M5A99X_EVO, right? So instead of changing -lqx in xconfig try and change _kernelname in PKGBUILD to -lqx-M5A99X_EVO and see what happens. I haven't tested or given it much thought, but give it a go. It will either work or it won't :)

KairiTech commented on 2014-01-07 15:20 (UTC)

I use the "local" modprobed_db option to compile only the modules required for my mobo but this generates the error below during the re-creation of the initramfs. Funny thing is I am still able to boot without any issues even though I am using LVM2. depmod: ERROR: could not open directory /lib/modules/3.12.6-1-lqx: No such file or directory depmod: FATAL: could not search modules: No such file or directory Running build hook: [lvm2] module not found: `dm-snapshot' module not found: `dm-mirror' I'm sure it has something to do with the fact that I append '-M5A99X_EVO' to the ‘-lqx’ kernel version when I run xconfigure. I do end up with the modules directory below but mkinitcpio does seem able to find it and I thought that the package file would be renamed too but it isn't. /lib/modules/3.12.6-1-lqx-M5A99X_EVO/ /lib/modules/extramodules-3.12-lqx/ So my question is should I change the kernel version to include my mobo name in some other way?

KairiTech commented on 2014-01-07 15:05 (UTC)

shivik commented on 2013-12-27 12:56 (UTC)

This happens when damentz updates lqx with the same version. 3.12.6-1 updated to 3.12.6-1,but different checksums. 3.10.22-1.patch.gz 2013-12-24 03:21 1.0M 3.12.6-1.patch.gz 2013-12-24 03:21 794K config.i386 2013-12-24 03:21 156K config.amd64 2013-12-24 03:21 152K 3.10.22-1.patch.gz 2013-12-27 01:03 1.0M 3.12.6-1.patch.gz 2013-12-27 01:03 794K config.i386 2013-12-27 01:03 156K config.amd64 2013-12-27 01:03 152K I check a few times a day.

PerfectGentleman commented on 2013-12-27 10:43 (UTC)

==> Validating source files with sha512sums... linux-3.12.tar.xz ... Passed 3.12.6-1.patch.gz ... FAILED config.i386 ... Passed config.amd64 ... Passed linux-lqx.preset ... Passed ==> ERROR: One or more files did not pass the validity check!