Package Base Details: linux-lqx

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only, click to copy)
Keywords: bbr2 bfq futex pds proton zen
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 158
Popularity: 0.95
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2024-05-06 23:51 (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 .. 81 82 83 84 85 86 87 88 89 90 91 .. 120 Next › Last »

KairiTech commented on 2014-01-12 21:27 (UTC)

Appreciate your efforts. I'll keep working at it to find an easier way to keep track of the mobo-specific kernels I create. Thanks again for your efforts.

shivik commented on 2014-01-12 20:09 (UTC)

I did a pacman -Rns linux-lqx prior to installing the rebuilt linux-lqx(with the custom name). Maybe this has something to do.I mean if you haven't done that yourself... This is all I can think of for now. Making that work for your case turns out to be beyond my knowledge. Next step is a completely modified PKGBUILD just for your needs.

KairiTech commented on 2014-01-12 18:00 (UTC)

No errors here either but I end up in emergency mode when I re-boot. I've had it work before without any changes to the kernel version but it doesn't seem to work now.

shivik commented on 2014-01-11 17:48 (UTC)

Yeah, two of my experiments must have mixed up 'cause I made a whole new PKGBUILD just for that and probably installed one on top of the other... I just recompiled and I have what you have,but I have a working system and I got no errors during kernel install - initramfs went fine,etc. I use nvidia driver and it is working. I don't use LVM, so no way to test that. The way this is supposed to work is just let you append a string to the kernel version and everything else should be normal - i.e. no need to mess with your bootloader config. Is your system working with this setup?

KairiTech commented on 2014-01-11 14:01 (UTC)

I don't seem to get extramodules-3.12-lqx-M5A99X_EVO or initramfs-linux-lqx-M5A99X_EVO-fallback.img vmlinuz-linux-lqx-M5A99X_EVO initramfs-linux-lqx-M5A99X_EVO.img ls -l /lib/modules 3.12.6-1-ARCH 3.12.6-1-lqx-M5A99X_EVO extramodules-3.12-ARCH extramodules-3.12-lqx ls /boot EFI initramfs-linux-lqx-fallback.img initramfs-linux-lqx.img vmlinuz-linux-lqx

shivik commented on 2014-01-09 10:09 (UTC)

OK, I added an option _append_kernel_custom_string to the PKGBUILD. Change that to your desire.It works on my system,no errors. Changed, rebuilt the kernel and here's my uname -r now :) [shivik@archenemy ~]$ uname -r 3.12.6-1-lqx-M5A99X_EVO My /lib/modules looks like this now: [shivik@archenemy modules]$ ls 3.12.6-1-ARCH 3.12.6-1-lqx-M5A99X_EVO extramodules-3.12-ARCH extramodules-3.12-lqx-M5A99X_EVO Keep in mind that this changes your /boot kernel and initramfs filenames,so you have to edit your bootloader config file accordingly. [shivik@archenemy boot]$ ls initramfs-linux-fallback.img initramfs-linux.img vmlinuz-linux initramfs-linux-lqx-M5A99X_EVO-fallback.img lost+found vmlinuz-linux-lqx-M5A99X_EVO initramfs-linux-lqx-M5A99X_EVO.img syslinux

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.