Package Details: linux-lqx 6.14.3.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: 165
Popularity: 2.09
First Submitted: 2011-08-08 16:08 (UTC)
Last Updated: 2025-04-20 18:28 (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 .. 39 40 41 42 43 44 45 46 47 48 49 .. 122 Next › Last »

sir_lucjan commented on 2017-02-20 22:13 (UTC)

[lucek@lucek ~]$ uname -a Linux lucek 4.9.11-1-lqx #1 ZEN SMP PREEMPT Mon Feb 20 22:59:38 CET 2017 x86_64 GNU/Linux [lucek@lucek ~]$ pacman -Qs linux-lqx local/linux-lqx 4.9.11-1 A desktop oriented kernel and modules with Liquorix patches local/linux-lqx-docs 4.9.11-1 Kernel hackers manual - HTML documentation that comes with the linux-lqx kernel local/linux-lqx-headers 4.9.11-1 Header files and scripts to build modules for linux-lqx. [lucek@lucek ~]$ systemctl status display-manager ● lightdm-plymouth.service - Light Display Manager Loaded: loaded (/usr/lib/systemd/system/lightdm-plymouth.service; enabled; ve Active: active (running) since pon 2017-02-20 23:09:55 CET; 1min 59s ago Main PID: 397 (lightdm) Tasks: 4 (limit: 4915) CGroup: /system.slice/lightdm-plymouth.service ├─397 /usr/bin/lightdm └─409 /usr/lib/xorg-server/Xorg :0 -seat seat0 -auth /run/lightdm/roo lut 20 23:09:54 lucek systemd[1]: Starting Light Display Manager... lut 20 23:09:55 lucek systemd[1]: Started Light Display Manager. lut 20 23:09:58 lucek lightdm[442]: pam_unix(lightdm-greeter:session): sessio lut 20 23:10:07 lucek lightdm[568]: pam_unix(lightdm:session): session opened As you can see....

whoami commented on 2017-02-20 20:40 (UTC)

I'm don't found linux-bfq in repos/aur/wiki, so I'm compile linux-ck. It's boot properly immediately. With default /etc/mkinitcpio.conf. $ systemctl status boot.mount ● boot.mount - /boot Loaded: loaded (/etc/fstab; generated; vendor preset: disabled) Active: active (mounted) since Mon 2017-02-20 23:34:23 MSK; 4min 58s ago Where: /boot What: /dev/sdc2 Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 273 ExecMount=/usr/bin/mount /dev/disk/by-uuid/8fd6580e-35ab-4edf-a0be-b0dcfe691 Tasks: 0 (limit: 4915) CGroup: /system.slice/boot.mount $ uname -a Linux atmxz 4.9.11-1-ck #1 SMP PREEMPT Mon Feb 20 23:23:26 MSK 2017 x86_64 GNU/Linux It's soooo faaaast if compared with default arch kernel. It's just WOW effect.

sir_lucjan commented on 2017-02-20 10:24 (UTC)

Could you try with another kernel, for example linux-bfq?

whoami commented on 2017-02-19 20:14 (UTC)

u can scroll my msgs

sir_lucjan commented on 2017-02-19 19:57 (UTC)

Show me: ls -l /boot

whoami commented on 2017-02-19 19:48 (UTC)

Works for me on default kernel. Error msg only can't mount /boot. And running Single Mode. ls -l /boot empty on boot in linux-lqx. I compile it as makepkg -sifC # systemctl status boot.mount ● boot.mount - /boot Loaded: loaded (/etc/fstab; generated; vendor preset: disabled) Active: failed (Result: exit-code) since Sat 2017-02-18 22:22:59 MSK; 2min 25s ago Where: /boot What: /dev/disk/by-uuid/8fd6580e-35ab-4edf-a0be-b0dcfe691886 Docs: man:fstab(5) man:systemd-fstab-generator(8) Process: 305 ExecMount=/usr/bin/mount /dev/disk/by-uuid/8fd6580e-35ab-4edf-a0be-b0dcfe691886 /boot -t ext2 -o rw,relatime,block_validity,barrier,user_xattr,acl (code=exited, status=32) Feb 18 22:22:59 atmxz systemd[1]: Mounting /boot... Feb 18 22:22:59 atmxz systemd[1]: boot.mount: Mount process exited, code=exited status=32 Feb 18 22:22:59 atmxz systemd[1]: Failed to mount /boot. Feb 18 22:22:59 atmxz systemd[1]: boot.mount: Unit entered failed state. $ ls -lA /boot/ total 46736 drwxr-xr-x 6 root root 1024 Feb 18 22:37 grub -rw-r--r-- 1 root root 14881152 Feb 18 22:54 initramfs-linux-fallback.img -rw-r--r-- 1 root root 15447532 Feb 19 19:34 initramfs-linux-lqx-fallback.img -rw-r--r-- 1 root root 3954396 Feb 19 19:34 initramfs-linux-lqx.img -rw-r--r-- 1 root root 4072024 Feb 18 22:53 initramfs-linux.img drwx------ 2 root root 12288 Feb 18 08:02 lost+found -rw-r--r-- 1 root root 4863776 Feb 6 15:01 vmlinuz-linux -rw-r--r-- 1 root root 4428576 Feb 19 19:18 vmlinuz-linux-lqx /boot/grub/grub.cfg (generate as # grub-mkconfig -o /boot/grub/grub.cfg ... menuentry 'Arch Linux' --class arch --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-bd56223e-d6fd-4170-bb6c-f7de646ac28d' { load_video set gfxpayload=keep insmod gzio insmod part_gpt insmod ext2 set root='hd2,gpt2' if [ x$feature_platform_search_hint = xy ]; then search --no-floppy --fs-uuid --set=root --hint-bios=hd2,gpt2 --hint-efi=hd2,gpt2 --hint-baremetal=ahci2,gpt2 8fd6580e-35ab-4edf-a0be-b0dcfe691886 else search --no-floppy --fs-uuid --set=root 8fd6580e-35ab-4edf-a0be-b0dcfe691886 fi echo 'Loading Linux linux-lqx ...' linux /vmlinuz-linux-lqx root=UUID=bd56223e-d6fd-4170-bb6c-f7de646ac28d rw quiet echo 'Loading initial ramdisk ...' initrd /initramfs-linux-lqx.img } ... /etc/fstab # /dev/sdc4 UUID=bd56223e-d6fd-4170-bb6c-f7de646ac28d / ext4 rw,relatime,data=ordered 0 1 # /dev/sdc2 UUID=8fd6580e-35ab-4edf-a0be-b0dcfe691886 /boot ext2 rw,relatime,block_validity,barrier,user_xattr,acl 0 2 ...

sir_lucjan commented on 2017-02-19 18:14 (UTC)

I know this "depmod error" but I don't have problem with booting. Did you try with another kernels? Could you show me error's message?

whoami commented on 2017-02-19 18:11 (UTC)

No I'm not try 4.9.7 cause I'm new guy with this kernel. Should I do this?

sir_lucjan commented on 2017-02-19 17:31 (UTC)

Can anyone confirm this 'boot error'?

sir_lucjan commented on 2017-02-19 17:26 (UTC)

https://bbs.archlinux.org/viewtopic.php?id=219904