@damentz yes, I found the problem was in my configuration for the keyservers. Thanks the same!
Search Criteria
Package Details: linux-lqx 5.17.11.lqx1-1
Package Actions
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 muqss proton zen |
Licenses: | GPL2 |
Provides: | VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
Submitter: | akurei |
Maintainer: | sir_lucjan (damentz) |
Last Packager: | damentz |
Votes: | 144 |
Popularity: | 2.21 |
First Submitted: | 2011-08-08 16:08 (UTC) |
Last Updated: | 2022-05-25 18:45 (UTC) |
Dependencies (11)
- coreutils (coreutils-git, coreutils-selinux, coreutils-hybrid)
- initramfs (mkinitcpio-git, dracut-git, booster-wip-git, booster-git, booster, dracut, mkinitcpio)
- kmod (kmod-git, kmod-minimal-git)
- bc (bc-gh) (make)
- cpio (cpio-git) (make)
- libelf (elfutils-git, libelf-minimal-git) (make)
- pahole (pahole-git) (make)
- python (python38, python37, python3.7, nogil-python, python311, python39, python36) (make)
- linux-firmware (linux-firmware-iwlwifi-git, linux-libre-firmware, linux-firmware-git, linux-firmware-uncompressed) (optional) – firmware images needed for some devices
- sof-firmware (optional) – firmware images needed for Sound Open Firmware capable devices
- wireless-regdb (wireless-regdb-git, wireless-regdb-pentest) (optional) – to set the correct wireless channels of your country
Required by (5)
- linux-lqx-docs
- linux-lqx-headers
- mozillavpn (requires WIREGUARD-MODULE)
- piavpn-bin (requires WIREGUARD-MODULE) (optional)
- piavpn-manual-git (requires WIREGUARD-MODULE)
Sources (3)
Latest Comments
lnoferin commented on 2022-05-08 13:16 (UTC)
damentz commented on 2022-05-07 23:31 (UTC)
@lnoferin, sounds like the keyserver was down or your network connection is blocking access. The ability pull down keys is also required for adding third party repos unless you disable signing.
We can't solve your network issues, so that's something you'll need to figure out on your end.
lnoferin commented on 2022-04-28 10:34 (UTC) (edited on 2022-04-28 10:34 (UTC) by lnoferin)
@sir_lucjan Tried but it failed:
gpg --recv-keys 9AE4078033F8024D && gpg --lsign-key 9AE4078033F8024D
gpg: keyserver receive failed: Connection refused
sir_lucjan commented on 2022-04-28 09:41 (UTC) (edited on 2022-04-28 09:41 (UTC) by sir_lucjan)
@lnoferin
Try gpg --recv-keys 9AE4078033F8024D && gpg --lsign-key 9AE4078033F8024D
as normal user.
lnoferin commented on 2022-04-28 09:37 (UTC)
I cannot build the package on a manjaro because this error:
pamac build linux-lqx 1 ✘ 1m 3s
Preparing...
Cloning linux-lqx build files...
Generating linux-lqx information...
Checking linux-lqx dependencies...
Resolving dependencies...
Checking inter-conflicts...
To build (1):
linux-lqx 5.17.5.lqx1-1 AUR
Edit build files : [e]
Apply transaction ? [e/y/N] y
Building linux-lqx...
==> Making package: linux-lqx 5.17.5.lqx1-1 (gio 28 apr 2022, 11:00:20)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found linux-5.17.tar.xz
-> Found linux-5.17.tar.sign
-> Found 5.17-9.tar.gz
==> Validating source files with sha512sums...
linux-5.17.tar.xz ... Passed
linux-5.17.tar.sign ... Skipped
5.17-9.tar.gz ... Passed
==> Verifying source file signatures with gpg...
linux-5.17.tar ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!
Error: Failed to build linux-lqx
I followed the pinned comment in this page but nothing changed:
pacman-key --keyserver hkps://keyserver.ubuntu.com --recv-keys 9AE4078033F8024D && pacman-key --lsign-key 9AE4078033F8024D
gpg: key 9AE4078033F8024D: "Steven Barrett <steven@liquorix.net>" not changed
gpg: Total number processed: 1
gpg: unchanged: 1
-> Locally signed 1 keys.
==> Updating trust database...
gpg: next trustdb check due at 2022-05-02
damentz commented on 2022-04-08 22:37 (UTC)
I failed over to using my build scripts on my local system. Liquorix repo is up-to-date again. Builds are performed clean room in docker and produce the same artifacts as my cloud build project.
damentz commented on 2022-04-08 20:33 (UTC)
If anyone's wondering why the official packages are not updated, I'm working with AWS support on my account that does the binary builds, my ability to run CodeBuild projects got randomly revoked. I'll post a notification once the builds are back online and liquorix.net repository updated.
damentz commented on 2022-03-09 13:00 (UTC)
Sorry about that, I had a short deadline to push out an update and this one was more complicated due to a breakage with PDS. In my rush, I missed adding the patch in git itself, but didn't notice due to the way my docker builds work for Debian and Ubuntu.
New update is out, appears to be building. Builds for Debian and Ubuntu ran yesterday successfully so I'm assuming this one is good too.
AlPiotrowicz commented on 2022-03-09 11:54 (UTC)
Confirming the error reported by @Borov
Borov commented on 2022-03-09 10:06 (UTC)
Please check
Patching sources with v5.16.13-lqx2.patch patch: **** Can't open patch file /home/user/.cache/yay/linux-lqx/src/liquorix-package-5.16-15/linux-liquorix/debian/patches/zen/v5.16.13-lqx2.patch : No such file or directory
AlPiotrowicz commented on 2022-01-31 21:24 (UTC)
Confirming it works
sir_lucjan commented on 2022-01-31 21:00 (UTC)
Try running makepkg -Rs unless you have deleted the src and pkg directories
AlPiotrowicz commented on 2022-01-31 20:51 (UTC)
@sir_lucjan Is it possible to resume the failed (in the place it failed that matter) compilation some easy way?
sir_lucjan commented on 2022-01-31 20:21 (UTC)
Let us know if it works.
Nie ma za co :D
AlPiotrowicz commented on 2022-01-31 20:20 (UTC)
@sir_lucjan Dzieki za ekspresowy fix :)
sir_lucjan commented on 2022-01-31 20:13 (UTC) (edited on 2022-01-31 20:14 (UTC) by sir_lucjan)
@AlPiotrowicz
Sorry for the mistake, I reversed the last change.
P.S Komunikaty błędów zgłaszaj jednak po angielsku, nie każdy developer mówi w naszym rodzimym języku :D
AlPiotrowicz commented on 2022-01-31 20:00 (UTC) (edited on 2022-01-31 20:17 (UTC) by AlPiotrowicz)
Hello, I experience:
==> Rozpoczynanie package_linux-lqx-headers()...
Installing build files...
install: cannot stat 'tools/bpf/resolve_btfids/resolve_btfids': No such file or directory
==> BŁĄD: Wystąpił błąd w package_linux-lqx-headers().
Przerywam...
Probably PKGBUILD needs one more if statement
Althorion commented on 2022-01-16 17:59 (UTC)
The current version patches and builds correctly. No idea what, if anything, was wrong with the previous one…
damentz commented on 2022-01-13 23:58 (UTC) (edited on 2022-01-14 00:16 (UTC) by damentz)
@Althorion mine also patches and begins building: https://asciinema.org/a/TF3wyZrzjJyIR0PIa5fYtnqii
Maybe github is sending you a different version of the tagged archive? That or your ISP is intercepting your download and sending you something else.
EDIT: In your asciinema, I see that your makepkg passes the integrity checks, so most likely your system is corrupting the extracted contents when extracting either archive.
sir_lucjan commented on 2022-01-12 21:34 (UTC)
I can not confirm.
Althorion commented on 2022-01-12 21:14 (UTC) (edited on 2022-01-12 21:14 (UTC) by Althorion)
@damentz I am. I’ve both tried makepkg --clean
, and removing the folder and cloning the package from scratch. Previous versions still build fine, if I check them out instead.
That’s how it looks on my end: https://asciinema.org/a/yTnewHGbNu194zTECKgrwfGob
damentz commented on 2022-01-12 17:34 (UTC)
@theriddick, I missed your last comment; Liquorix uses PDS as the process scheduler with a 1000hz tick rate and 2ms scheduler deadline, so depending on how prone latte dock is to race conditions (things happening out of order, artificial delays on errors, etc), Latte Dock will initialize slower. It might be worth your time to submit a bug report since it's most certainly an assumption depending on an order of operations CFS guarantees most of the time, but is invalid with PDS.
MuQSS (and as an extension PDS), tends to expose programs with bugs in multithreading far more often than CFS. This goes for buggy kernel drivers too. Fortunately, things have gotten a lot better than when MuQSS was first introduced and PDS appears to overall have less show stopping bugs than its predecessor.
damentz commented on 2022-01-12 17:29 (UTC)
@Althorion, are you building from a clean environment? Last automated build ran successfully 21 hours ago: https://github.com/damentz/linux-lqx/commit/b43feff428245e1639d7ef495b188e5a9b08f66c
Althorion commented on 2022-01-12 17:09 (UTC)
The current version (5.15.14.lqx1-1) fails to patch properly: https://gist.github.com/Althorion/6a3db24017eb805a70b1ffd79af0e8a2
theriddick commented on 2021-11-02 03:53 (UTC) (edited on 2021-11-02 03:54 (UTC) by theriddick)
I notice that latte-dock takes a few extra seconds to load with this kernel. Not a show stopper but just a odd curiosity issue. Also my wireless keyboard is disabled for a few seconds on login also (happens with default kernel), wonder if that is related to something.
(These things don't happen with xanmod btw)
damentz commented on 2021-11-02 03:18 (UTC)
@theriddick, once Liquorix is rebased to 5.15, it will have it.
In the meantime, looks like there's a DKMS package that gets you the same functionality but a different module name, ntfs3
: https://aur.archlinux.org/packages/ntfs3-dkms/
theriddick commented on 2021-11-02 02:50 (UTC) (edited on 2021-11-02 03:53 (UTC) by theriddick)
Guessing this does not include NTFS3? (yes using ntfs3-dkms atm)
JoseskVolpe commented on 2021-10-10 19:21 (UTC)
¡It works, thanks! ÛwÛ
damentz commented on 2021-09-27 01:10 (UTC)
@JoseskVolpe, what happens when you read the pinned comment and follow its instructions?
JoseskVolpe commented on 2021-09-27 01:02 (UTC)
¿Can't we have a pre-compiled package? This takes forever to compile every update lol
brunomiguel commented on 2021-09-25 17:38 (UTC)
I was able to build it in a clean chroot. The error, though, persisted with a normal build. Yet, after rebooting, it built normally.
damentz commented on 2021-09-25 15:47 (UTC) (edited on 2021-09-25 15:48 (UTC) by damentz)
@brunomiguel, most likely a unique configuration on your system is breaking the build. I recommend trying to build in a new vanilla system, chroot, or container.
The binary builds (as listed in the pinned comment), always build from clean room using the official Arch Linux docker image and have had no issues. Same goes for when I test using local builds on my desktop.
If you want to run Liquorix but can't build for some reason, I highly recommend you using the official Liquorix repository for Arch.
brunomiguel commented on 2021-09-25 15:43 (UTC) (edited on 2021-09-25 16:37 (UTC) by brunomiguel)
@vp1981 I have 12GB of RAM and 200GiB of disk space (with only 55GB used, more than enough to compile this kernel). I even monitored the RAM and disk space used when compiling and it never ran out of RAM or disk space.
update: i can build it in a clean chroot
vp1981 commented on 2021-09-25 09:08 (UTC)
@brunomiguel, wild guess: do you have enough memory? Free space?
brunomiguel commented on 2021-09-23 02:45 (UTC)
I made no changes, I'm using the original PKGBUILD
vp1981 commented on 2021-09-23 02:04 (UTC)
Hello brunomiguel.
I have just built linux-lqx with GCC. Are you using exactly the same PKGBUILD and config as the AUR package or did you add/change something yourself?
brunomiguel commented on 2021-09-23 01:30 (UTC)
I'm building the latest version but I get the following error
ZSTD22 arch/x86/boot/compressed/vmlinux.bin.zst
CC arch/x86/boot/compressed/misc.o
FATAL: modpost: drivers/net/wwan/rpmsg_wwan_ctrl: sizeof(struct rpmsg_device_id)=32 is not a modulo of the size of section __mod_rpmsg__<identifier>_device_table=120.
Fix definition of struct rpmsg_device_id in mod_devicetable.h
make[1]: *** [scripts/Makefile.modpost:150: modules-only.symvers] Erro 1
make: *** [Makefile:1770: modules] Erro 2
damentz commented on 2021-09-20 00:35 (UTC)
@vp1981, that is correct, Liquorix now uses PDS. It's spiritually very similar to MuQSS.
From my early testing, single threaded performance is much higher than MuQSS, but multithreaded performance suffers a bit. However, the delta is not big enough to be an issue for Liquorix's target behavior and the single threaded performance is arguably more important for common activities most people do on their systems.
vp1981 commented on 2021-09-19 23:48 (UTC)
So, there is no more MUQSS, right?
vp1981 commented on 2021-08-22 12:40 (UTC)
Hello. Something strange is going on with key servers. I couldn't find key 9AE4078033F8024D on keyserver.ubuntu.com but found it on keys.openpgp.org, didn't try to import it using that server though.
damentz commented on 2021-06-22 01:15 (UTC)
Wow, that's unfortunate. I just updated the instructions to use keyserver.ubuntu.com
instead.
arnamak commented on 2021-06-22 00:03 (UTC)
It would appear that, as of today, the keyserver listed in the pinned comment no longer works.
According to the status page for sks-keyservers.net, this is due to further GDPR takedown requests.
Is there an alternate keyserver we can use?
damentz commented on 2021-06-07 14:55 (UTC)
Yes, that is strange. This issue would come back occasionally when updates were pulled from upstream Arch, but that was due to pulling a function that would try to dynamically determine the kernel version.
This time around nothing like that is happening, but whatever is determining the version isn't pulling from $pkgver like it should.
@sirlucjan, do you have any ideas? Maybe upstream Arch has already deviated and we need to pull its updates.
ryshglene commented on 2021-06-07 06:07 (UTC)
Upgraded to 5.12.9.lqx2-1, and yet the kernel name remains 5.12.9-lqx1-1-lqx
?
damentz commented on 2021-06-05 22:02 (UTC) (edited on 2021-06-05 22:02 (UTC) by damentz)
Kido commented on 2021-06-05 16:25
RTL8111/8168/8411 is broken in linux-lqx 5.12.9.lqx2-1
What is broken about these devices and since which kernel?
Kido commented on 2021-06-05 21:25 (UTC)
RTL8111/8168/8411 is broken in linux-lqx 5.12.9.lqx2-1
freenestor commented on 2021-03-11 02:55 (UTC)
makepkg hangs at
... Removing scripts/mod/modpost.o Removing scripts/mod/file2alias.o Removing scripts/mod/sumversion.o Removing scripts/kconfig/confdata.o Removing scripts/kconfig/preprocess.o Removing scripts/kconfig/expr.o Removing scripts/kconfig/util.o Removing scripts/kconfig/parser.tab.o Removing scripts/kconfig/symbol.o Removing scripts/kconfig/lexer.lex.o Removing scripts/kconfig/conf.o Stripping build tools... #hangs here
Any idea?
Willy1992 commented on 2021-03-08 14:49 (UTC)
@damentz yeah i saw it, recompiled with default config and it works, seems like using my current kernel config broke it, perhaps i need to take a look with nconfig
damentz commented on 2021-03-07 19:59 (UTC)
@Willy1992, the binaries built successfully 2 hours ago (check pinned comment). Are you not using the configuration in the AUR package?
Willy1992 commented on 2021-03-07 19:42 (UTC)
A few hours ago compiled succesfully 5.11-3, but 5.11-4 fails with:
kernel/sched/MuQSS.c:141:36: error: 'CONFIG_SHARERQ' undeclared here (not in a function); did you mean 'CONFIG_SPARSE_IRQ'? 141 | static int rqshare __read_mostly = CONFIG_SHARERQ; / Default RQSHARE_MC / | ^~~~~~~~~~~~~~ | CONFIG_SHMEM
brunomiguel commented on 2021-03-05 09:56 (UTC)
I've installed this kernel a few minutes ago, but I can't get it to boot (I'm using GRUB, if that's relevant, and compressing the images with LZ4 -1). In GRUB, it doesn't pass the "Loading initial ramdisk ..." message, although the file is the correct place.
sir_lucjan commented on 2021-02-10 19:26 (UTC)
Binutils 2.36.1 should be released soon and the bug may be fixed there. I haven't checked, but if someone wants to, she/he should look through the sources.
lewiji commented on 2021-02-10 18:59 (UTC)
@sir_lucjan thanks for the link, I will follow that bug.
I do use qemu/virtmanager as well but use Virtualbox sometimes for some specific old Win95/Win3.1 games and software as the integration is much better.
For now I can just use another kernel version for that until they've figured it out. Cheers.
sir_lucjan commented on 2021-02-10 12:10 (UTC)
I'm definitely not sure about that, which is why I wrote "probably" :) I haven't used VB for years so I personally haven't encountered this error.
https://github.com/xanmod/linux/issues/125
Perhaps it will go better with virt-manager? It's also a GUI program, so there's always an alternative.
Anarconda commented on 2021-02-10 12:06 (UTC)
@sir_lucjan Are you sure about that? In my /var/lib/dkms/vboxhost you can see this:
drwxr-xr-x 1 root root 144 10.02.2021 08:17 6.1.18_OSE/ lrwxrwxrwx 1 root root 33 08.02.2021 21:48 kernel-5.10.14-arch1-1-x86_64 -> 6.1.18_OSE/5.10.14-arch1-1/x86_64/ lrwxrwxrwx 1 root root 46 08.02.2021 13:47 kernel-5.10.14-hardened1-1-hardened-x86_64 -> 6.1.18_OSE/5.10.14-hardened1-1-hardened/x86_64/ lrwxrwxrwx 1 root root 36 08.02.2021 21:46 kernel-5.10.14-zen1-1-zen-x86_64 -> 6.1.18_OSE/5.10.14-zen1-1-zen/x86_64/
In other words, for my other installed kernels the module it's been created.
sir_lucjan commented on 2021-02-10 11:48 (UTC)
Probably the bug has to do with the latest binutils. Similar problems occur on other kernels as well.
lewiji commented on 2021-02-10 11:45 (UTC)
Same issue as Anarconda, the make.log says:
DKMS make.log for vboxhost-6.1.18_OSE for kernel 5.10.14-lqx2-1-lqx (x86_64)
Wed 10 Feb 11:41:21 GMT 2021
make: Entering directory '/usr/lib/modules/5.10.14-lqx2-1-lqx/build'
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetadp/linux/VBoxNetAdp-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetadp/VBoxNetAdp.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/linux/VBoxNetFlt-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/VBoxNetFlt.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/SUPR0IdcClient.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/linux/SUPDrv-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/SUPR0IdcClientComponent.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrv.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/linux/SUPR0IdcClient-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvGip.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvSem.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPLibAll.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/alloc-r0drv.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/initterm-r0drv.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/memobj-r0drv.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/mpnotification-r0drv.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/powernotification-r0drv.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/linux/assert-r0drv-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/linux/alloc-r0drv-linux.o
CC [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/r0drv/linux/initterm-r0drv-linux.o
/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: .text+0x7: indirect jump found in RETPOLINE build
/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: supdrvTracerProbeFireStub() is missing an ELF size annotation
/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o: warning: objtool: missing symbol for insn at offset 0x0
make[2]: *** [scripts/Makefile.build:279: /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o] Error 255
make[2]: *** Deleting file '/var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv/SUPDrvTracer.o'
make[2]: *** Waiting for unfinished jobs....
LD [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetadp/vboxnetadp.o
LD [M] /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxnetflt/vboxnetflt.o
make[1]: *** [scripts/Makefile.build:496: /var/lib/dkms/vboxhost/6.1.18_OSE/build/vboxdrv] Error 2
make: *** [Makefile:1801: /var/lib/dkms/vboxhost/6.1.18_OSE/build] Error 2
make: Leaving directory '/usr/lib/modules/5.10.14-lqx2-1-lqx/build'
Anarconda commented on 2021-02-10 07:22 (UTC)
Usually vboxhost module is build correctly but with 5.10.14 series I'm getting this:
==> dkms install --no-depmod -m vboxhost -v 6.1.18_OSE -k 5.10.14-lqx2-1-lqx Error! Bad return status for module build on kernel: 5.10.14-lqx2-1-lqx (x86_64) Consult /var/lib/dkms/vboxhost/6.1.18_OSE/build/make.log for more information. ==> Warning, `dkms install --no-depmod -m vboxhost -v 6.1.18_OSE -k 5.10.14-lqx2-1-lqx' returned 10
What can I do? Thanks in advance.
damentz commented on 2021-01-30 18:13 (UTC)
@Anarconda, the .12 update was pretty small with no block patches. You might have a bad drive that only sometimes has issues at boot. I recommend checking the smart data on your drives to see if anything is primed to fail soon.
Anarconda commented on 2021-01-30 17:32 (UTC)
Just to let you know the following messages are shown by dmesg with .12
"[ 161.707995] ata8.00: failed command: READ FPDMA QUEUED [ 161.707999] ata8.00: cmd 60/00:18:20:b7:84/0a:00:2c:00:00/40 tag 3 ncq dma 1310720 in res 40/00:20:20:c1:84/00:00:2c:00:00/40 Emask 0x10 (ATA bus error) [ 161.708000] ata8.00: status: { DRDY } [ 161.708001] ata8.00: failed command: READ FPDMA QUEUED [ 161.708004] ata8.00: cmd 60/00:20:20:c1:84/02:00:2c:00:00/40 tag 4 ncq dma 262144 in res 40/00:20:20:c1:84/00:00:2c:00:00/40 Emask 0x10 (ATA bus error)"
reverting to .11 messages are gone. Thanks for your efforts.
gardotd426 commented on 2020-12-31 05:06 (UTC) (edited on 2020-12-31 05:17 (UTC) by gardotd426)
This is likely a Virtualbox issue, not a linux-lqx issue. They have to have their modules be able to be built against this version of the kernel. Usually with custom kernels it takes a bit. I've noticed it for well over a year when using kernels like linux-zen, linux-tkg, etc., and sometimes even regular linux, for the first few versions of a new kernel (like up to X.Y.7 or so)
Angel_Caido commented on 2020-12-31 04:40 (UTC) (edited on 2020-12-31 04:41 (UTC) by Angel_Caido)
Virtualbox Machines not working properly after upgrading to the most recent version of Linux-lqx [5.10 and up].
Loading modules: modprobe: FATAL: Module vboxnetadp not found in directory /lib/modules/5.10.4-lqx1-1-lqx
modprobe: FATAL: Module vboxnetflt not found in directory /lib/modules/5.10.4-lqx1-1-lqx
modprobe: FATAL: Module vboxdrv not found in directory /lib/modules/5.10.4-lqx1-1-lqx
Anarconda commented on 2020-12-29 08:12 (UTC)
I can confirm messages are gone. Thanks again.
damentz commented on 2020-12-29 01:58 (UTC)
@Anarconda, next release (5.10.3.lqx2-1), should fix it. The issue appears to be a BPF feature that depends on userspace tool built with the kernel. The error itself is completely benign otherwise.
sir_lucjan commented on 2020-12-29 01:41 (UTC) (edited on 2020-12-29 01:42 (UTC) by sir_lucjan)
@Anarconda
Currently, the package is managed by the creator of patchset liquorix, damentz, co-maintainer. I will let him know if it still does not work. Unfortunately - I don't use patchset liquorix but my solutions. I haven't observed this error at my system and we will have to look into it if the problem persists - currently AUR notifications come with a very long delay.
Anarconda commented on 2020-12-28 20:41 (UTC)
@sir_lucjan. After update to version 5.10.3 and reboot I can read the following message:
libbpf: failed to find valid kernel BTF libbpf: Error loading vmlinux BTF: -3 libbpf: failed to load object 'iterators_bpf' libbpf: failed to load BPF skeleton 'iterators_bpf': -3 Failed to load could be due to wrong endianness
What can I do solve this? Thanks in advance. Regards.
sir_lucjan commented on 2020-12-14 14:48 (UTC)
@Anarconda
It is NOT obsolete. The lqx patchset will only appear when a new MUQSS is released.
damentz commented on 2020-11-25 02:47 (UTC)
error: required key missing from keyring
both downloading from custom repo and compiling from source tells me i dont have pgp keys
@bonkmaykrq, have you tried getting the keys? The pinned comment gives you the template to start with. If you can't figure it out, I recommend using the binaries and following the key import instructions pinned as the first comment.
bonkmaykrq commented on 2020-11-24 16:25 (UTC)
error: required key missing from keyring
both downloading from custom repo and compiling from source tells me i dont have pgp keys
LibbleGlobGlob commented on 2020-11-15 04:42 (UTC)
@damentz Eyy, that worked really well! I also fixed some changes in the conf where I used systemd hook instead of the udev and the cat compression for "faster boot time" that didn't really worked for me. Thanks !
damentz commented on 2020-11-14 19:13 (UTC)
@LibbleGlobGlob, that sounds like you're missing autofs4 in your initramfs. Try adding the module to your mkinitcpio.conf and rebuilding with mkinitcpio -P.
LibbleGlobGlob commented on 2020-11-14 08:40 (UTC)
I'm getting a "Failed to insert module 'autofs4': No such file or directory" during boot. But it is functional and works as expected. How do I get rid of this message though?
gardotd426 commented on 2020-10-31 13:16 (UTC)
It's not "incompatible." It works fine, the only thing missing is CUDA.
Even then, you can get full functionality back if you use TK-Glitch's nvidia-all PKGBUILD, CUDA and all.
@samuk190 the real issue is likely that you haven't rebuilt your Nvidia drivers after installing a new kernel version. You always have to do this, when going from 5.8 to 5.9, etc.
Re-install the Nvidia drivers. If that doesn't work, use https://github.com/frogging-family/nvidia-all
sir_lucjan commented on 2020-10-31 12:44 (UTC)
samuk190 commented on 2020-10-31 12:18 (UTC)
Error: nvidia fb hangs on boot. Manjaro "mikah"
I guess its something related with nvidia but I tested this kernel on xubuntu before and I didnt have any issues.
damentz commented on 2020-09-28 15:05 (UTC)
@xuanruiqi, should be fixed in next release, you can look at this github issue for reference: https://github.com/zen-kernel/zen-kernel/issues/182
xuanruiqi commented on 2020-09-28 14:27 (UTC)
OK, I found the GitHub issue: https://github.com/zen-kernel/zen-kernel/issues/182. Apparently you can't enable AMD microcode support w/o enabling Intel microcode support. Weird.
xuanruiqi commented on 2020-09-28 14:25 (UTC)
I'm getting this while trying to compile the kernel:
ld: arch/x86/kernel/cpu/microcode/core.o: in function `reload_store':
core.c:(.text+0x166): undefined reference to `force_ucode_load'
ld: core.c:(.text+0x196): undefined reference to `force_ucode_load'
ld: arch/x86/kernel/cpu/microcode/core.o: in function `reload_store.cold':
core.c:(.text.unlikely+0x22): undefined reference to `force_ucode_load'
ld: core.c:(.text.unlikely+0xa4): undefined reference to `force_ucode_load'
ld: core.c:(.text.unlikely+0xda): undefined reference to `force_ucode_load'
Anyone having the same problem?
damentz commented on 2020-09-23 15:56 (UTC)
@thaewrapt, added cpio back to makedepends.
thaewrapt commented on 2020-09-23 11:48 (UTC)
thaewrapt commented on 2020-09-23 11:46 (UTC) (edited on 2020-09-23 11:46 (UTC) by thaewrapt)
Failed to build without cpio
:
make[1]: *** [kernel/Makefile:145: kernel/kheaders_data.tar.xz] Error 127
make: *** [Makefile:1750: kernel] Error 2
make: *** Waiting for unfinished jobs....
asasione commented on 2020-09-18 11:52 (UTC) (edited on 2020-09-18 11:52 (UTC) by asasione)
I am getting a systemd error on this kernel, I'm using the official binaries: Failed to find module 'autofs4'
damentz commented on 2020-09-13 01:21 (UTC)
The modules required for Anbox are now included, but there's still more instructions. Read the wiki: https://wiki.archlinux.org/index.php/Anbox
enihcam commented on 2020-09-12 17:59 (UTC)
according to changelog, Anbox support is added. How to enable it?
sir_lucjan commented on 2020-09-06 13:25 (UTC)
Paste log with errors.
duff commented on 2020-09-06 13:23 (UTC) (edited on 2020-09-06 13:24 (UTC) by duff)
Latest Version (2020-09-05 14:29) does not build :(
CC [M] fs/xfs/scrub/agheader_repair.o CC [M] fs/xfs/scrub/bitmap.o AR fs/built-in.a CC [M] fs/xfs/scrub/repair.o LD [M] fs/xfs/xfs.o ==> FEHLER: Ein Fehler geschah in build(). Breche ab... error making: linux-lqx (linux-lqx linux-lqx-docs linux-lqx-headers)
enihcam commented on 2020-09-03 23:44 (UTC)
sir, that was a long while ago. i don't see why cpio break the build.
btw, one of the reasons i like this package is that PKGBUILD content is clean and neat. :)
sir_lucjan commented on 2020-09-03 13:59 (UTC)
I remember that cpio was added in response to this request:
https://aur.archlinux.org/pkgbase/linux-lqx/?O=50&PP=10#comment-702055
damentz commented on 2020-09-03 13:56 (UTC)
You're probably right, I don't see them in the official PKGBUILD for linux
. I'll remove them on the next update and specify package(s) that are actually required, liked base-devel
.
enihcam commented on 2020-09-03 13:39 (UTC)
Two unnecessary makedepends: 'inetutils' 'cpio' ?
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
commented on 2020-05-28 06:09 (UTC)
I installed the kernel and the headers from Manjaro Pamac but I don't get an option to choose it when booting
coremanfrank commented on 2020-05-11 03:02 (UTC)
this is worked for me $ gpg --keyserver keyserver.ubuntu.com --recv-key 38DBBDC86092693E
damentz commented on 2020-05-06 20:11 (UTC)
Ok great, glad you got it working.
Fenrihr commented on 2020-05-06 19:48 (UTC)
@damentz the problem was the pacman GUI in Manjaro ... i resolved with in the terminal (but i not remember how at this momment)
damentz commented on 2020-05-06 19:43 (UTC) (edited on 2020-05-06 19:50 (UTC) by damentz)
@Fenrihr, did you do any research on what that output means?
Fenrihr commented on 2020-05-02 11:31 (UTC)
Hi! i'm getting the msg: "the key ABAF11C65A2970B130ABE3C479BE3E4300411886 could not be imported"
henrik_er commented on 2020-03-13 09:21 (UTC)
@damentz
Wasn't aware that they were interconnected. Thanks!
damentz commented on 2020-03-13 07:23 (UTC)
henrik_er commented on 2020-03-13 06:00 (UTC)
Hi @sir_lucjan and @damentz I am relatively new to kernel compiling, but any reason the "make ..." in the PKGBUILD cannot be changed to "make -j$(nproc) ..." I have modified it manually at each update, and it greatly improves the compilation speed as it utilizes all cores. I have not seen any issues.
sir_lucjan commented on 2020-02-08 11:01 (UTC)
@j1simon
No. Liquorix patch must be applied to the kernel 5.X, not 5.X.Y
j1simon commented on 2020-02-08 09:48 (UTC)
If it's 5.5.2, shouldn't it download that version of the kernel repository and not 5.5 (as it does now)?
==> Making package: linux-lqx 5.5.2_1-1 (Sat Feb 8 10:46:24 2020)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading linux-5.5.tar.xz...
Initializing download: https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.xz
File size: 110713660 bytes
Opening output file linux-5.5.tar.xz.part
Starting download
....
Downloaded 105.585 Megabyte(s) in 1 second(s). (79320.54 KB/s)
-> Downloading linux-5.5.tar.sign...
Initializing download: https://cdn.kernel.org/pub/linux/kernel/v5.x/linux-5.5.tar.sign
File size: 983 bytes
Opening output file linux-5.5.tar.sign.part
Starting download
.....
Downloaded 983 byte(s) in 0 second(s). (9.58 KB/s)
-> Downloading 5.5-3.tar.gz...
Initializing download: https://github.com/damentz/liquorix-package/archive/5.5-3.tar.gz
...
frogec commented on 2019-12-10 08:26 (UTC)
I had problems with gpg keys not importing (I stoped the command after 20 minutes). When installing with yay first decline importing of the keys.
==> PGP keys need importing ==> Import? [Y/n] n
Than it will give you the following error:
linux-5.3.tar ... FAILED (unknown public key <KEY>)
==> ERROR: One or more PGP signatures could not be verified! Error downloading sources: linux-lqx
Use command to add key:
$ gpg --recv-key <KEY>
Retry installing. The verification passed for me.
Freso commented on 2019-12-08 01:04 (UTC) (edited on 2019-12-08 01:06 (UTC) by Freso)
@gardotd426 That error is not related to this package, but something on your system.
gardotd426 commented on 2019-12-07 21:59 (UTC)
Can't install this for the life of me:
==> Import? [Y/n] y
:: Importing keys with gpg......
gpg: key 79BE3E4300411886: 150215 signatures not checked due to missing keys
gpg: error writing keyring '/home/matt/.gnupg/pubring.kbx': Provided object is too large
gpg: key 79BE3E4300411886: keyblock too large, retrying with self-sigs-only
gpg: key 79BE3E4300411886: public key "Linus Torvalds <torvalds@kernel.org>" imported
gpg: Total number processed: 1
gpg: imported: 1
==> Error: Problem importing keys
bparsons commented on 2019-12-04 14:40 (UTC)
FWIW, I've worked through the suspend/resume issues with 5.4 on my Thinkpad P50. Let me know if I can help.
Freso commented on 2019-12-02 23:56 (UTC)
@digitalone See the commit message: https://aur.archlinux.org/cgit/aur.git/commit/?h=linux-lqx&id=e935f4ddfb8f
digitalone commented on 2019-12-02 23:16 (UTC)
Why you downgraded to 5.3?
gardotd426 commented on 2019-11-22 05:39 (UTC)
This might be a bit nitpicky (but also kind of funny), but the PKGBUILD near the end when it lists the devs, it says "Linux Torvalds"
Agafron commented on 2019-11-05 23:08 (UTC)
@sir_lucjan , thanks! now i must refuse lqx, waitin for sync, on arch I have no cross, because laziness see into, sorry
sir_lucjan commented on 2019-11-05 17:21 (UTC)
@Agafron:
I checked Manjaro repositories a moment ago and the required versions of kmod and mkinitcpio are not even in the unstable repository. What's more, Manjaro developers have rebuilt these packages in their own way and at this point most AUR kernels are completely incompatible with Manjaro.
sir_lucjan commented on 2019-10-31 19:16 (UTC)
1) This is the right thing to do. Extramodules have been abandoned in Arch IN KERNEL and transferred to individual drivers and modules. At least it looks like it.
2) No. I used to use Virtualbox once, but I don't need to build any module for a long time now.
Agafron commented on 2019-10-31 19:14 (UTC) (edited on 2019-10-31 19:15 (UTC) by Agafron)
I don't have nvidia so I'm not able to check how and if it will work.
ok, have you r8186 or any driver which need build separately?
Agafron commented on 2019-10-31 19:12 (UTC)
See on PKGBUILD from Arch repos
I do, but_extradir="/usr/lib/modules/$(</usr/src/linux/version)/extramodules"
stay
sir_lucjan commented on 2019-10-31 18:12 (UTC)
@Agafron
Yes, extramodules was dropped.
See on PKGBUILD from Arch repos - I don't have nvidia so I'm not able to check how and if it will work.
Agafron commented on 2019-10-31 18:00 (UTC) (edited on 2019-10-31 18:02 (UTC) by Agafron)
@sir_lucjan, if I understand right, i can modify PKGBUILD for nvidia-dkms https://git.archlinux.org/svntogit/packages.git/tree/trunk/PKGBUILD?h=packages/nvidia-390xx,
I'll need change path /usr/src/linux on /usr/src/linux-lqx
but I don`t know where i need put build driver modules?
Dir "extramodules" is in out?
sir_lucjan commented on 2019-10-30 23:36 (UTC)
The packages are more likely to go to Manjaro but when - I have no idea. Maybe it will take a few days, maybe a few weeks - not more, I think. I mean the new mkinitcpio rather surely and the kmod patched by Archa also but one hundred percent surety can not be. On the example of extramodules you can see that the changes are not always accepted 100%.
Agafron commented on 2019-10-30 23:31 (UTC)
right)
Agafron commented on 2019-10-30 23:29 (UTC)
I think, That philosophy in manjaro, not so far from philosophy in Arch and will be synchronized))
sir_lucjan commented on 2019-10-30 23:26 (UTC) (edited on 2019-10-30 23:26 (UTC) by sir_lucjan)
New kmod and mkinitcpio will introduce new hooks in place of the existing ones. Therefore, the old ones are removed as redundant. As Manjaro will not have this for some time, neither initramfs nor depmods will be built. This will make it impossible to install and run the kernel. So it is better to keep this in mind. I don't do it out of malice - but the priority is to support Arch Linux, which is quite understandable, right?
Agafron commented on 2019-10-30 23:19 (UTC) (edited on 2019-10-30 23:21 (UTC) by Agafron)
ok, thanks, I'll keep it on mind
sir_lucjan commented on 2019-10-30 23:14 (UTC)
By the way, new kmod and mkinitcpio will soon appear in the stable repos. This will force the introduction of changes that will prevent the use of kernels from AUR in Manjaro until the moment when these packages do not appear in the Manjaro repository. So keep this in mind.
Although the kernel should compile without any problems and the problem will occur only during the installation.
sir_lucjan commented on 2019-10-30 23:06 (UTC) (edited on 2019-10-30 23:09 (UTC) by sir_lucjan)
Do you use Manjaro? Well, I'm not going to maintain compatibility with Manjaro just with Arch Linux. Arch abandoned extramodules so linux-lqx also. So if you want to continue using kernel from AUR then you have two choices:
1) You're using Arch and that's it.
2) You're modifying PKGBUILDs from Arch Linux repo and that's it.
Agafron commented on 2019-10-30 23:02 (UTC) (edited on 2019-10-30 23:04 (UTC) by Agafron)
nvidia driver, PKGBUILD https://pastebin.com/SZSwPn3v
r8168 driver, - https://pastebin.com/0np3pCjB
PS OS manjaro
sir_lucjan commented on 2019-10-30 22:49 (UTC)
Arch abandoned the extramodules so all the kernels were synchronized with the stock. I don't know which driver you're installing, but check out the new philosophy in Arch. If you tell me what you want to install, there may be a solution.
sir_lucjan commented on 2019-10-30 22:45 (UTC)
Agafron commented on 2019-10-30 22:43 (UTC) (edited on 2019-10-30 22:43 (UTC) by Agafron)
I'm trying to build a driver, but it gives an error:
cat: /usr/lib/modules/extramodules-lqx/version: No such file or directory
Filip98 commented on 2019-10-23 17:13 (UTC)
@damentz, "I choose a lazy person to do a hard job. Because a lazy person will find an easy way to do it." something like... this?: https://textuploader.com/1khof (forgot the standard platform) It lacks sed commands to modify linux-lqx's PKGBUILD into a new one for the bin version but this beta should build linux-lqx minus not importing the pgp keys atm
damentz commented on 2019-10-22 14:39 (UTC)
@Filip98, purely out of laziness. If you can point me to a guide that utilizes some type of chroot to build AUR packages and how to host them properly, I'll take a look. I'd prefer the binaries to be on liquorix.net for trust reasons.
Filip98 commented on 2019-10-22 08:31 (UTC)
This package has been available for a while but there's no -bin version, is there any specific reason? if not would it be okay for me to set up a linux-lqx-bin package? presumably using the precompiled ones for e.g Ubuntu isn't the solution.
damentz commented on 2019-10-22 01:34 (UTC)
@XopmoH, looks like you ran out of disk space or you got filesystem corruption in the middle of the build. Make sure your build directory has enough space.
@zebulon, Liquorix prefers MuQSS over CFS for process scheduling and has major other configuration differences to the "linux-zen" kernel. You can run a diff on the two configurations to see. Some of the more obvious differences are on https://liquorix.net
sir_lucjan commented on 2019-10-21 19:48 (UTC) (edited on 2019-10-21 19:49 (UTC) by sir_lucjan)
Did you use some kind of aur-helper? Besides, why do you associate a compilation error with a browser error? It never happened to me - and I've compiled thousands of kernels already - that a compilation error would cause some kind of regression on a running system... I don't think it's an exaggeration, so I ask you honestly - what does it have to do with the compilation error?
XopmoH commented on 2019-10-21 19:36 (UTC) (edited on 2019-10-21 19:40 (UTC) by XopmoH)
It did not work to build this core! An error occurred during installation from AUR:
Assembler message:
Error: couldn't open /tmp/ccWnsYb5.s to read: Not found file or directory
make[2]: *** [scripts/Makefile.build:279: fs/btrfs/extent-tree.o] Error 1
make[1]: *** [scripts/Makefile.build:489: fs/btrfs] Error 2
make: *** [Makefile:1081: fs] Error 2
After that, when I opened the browser in full screen, a message popped up: "An error occurred and the system could not recover. You need to end the session and log in again."
Screenshots with a build error and a full-screen error can be viewed here: https://mega.nz/#F!4WgCxYpC!zquOhI2U8fqLTp5yv3KpCQ
zebulon commented on 2019-10-21 07:06 (UTC)
Hi, first thank you very much for your excellent contribution. One question though: what is the difference between linux-zen and linux-lqx? Looking at the Github sources, I am struggling understanding which patches or settings differ from linux-zen. Thanks a lot in advance.
toki1990 commented on 2019-09-05 23:44 (UTC)
@damentz "_makegconfig=1" worked. new window(included menu config) opened
damentz commented on 2019-09-05 23:43 (UTC)
@toki1990, this comment section is not AUR helper technical support. Try using the official arch wiki article[1] to install linux-lqx, then you can ask for help in the Arch support forums if you run into trouble.
[1] https://wiki.archlinux.org/index.php/Arch_User_Repository
toki1990 commented on 2019-09-05 23:15 (UTC)
@damentz I'm using pamac-manager for aur installation. i tried "enable _makemenuconfig=" , "_makemenuconfig=enable" enable_makemenuconfig=Y and more in PKGBUILD. I cant see config menu. Can u teach me step by step.
damentz commented on 2019-09-05 20:48 (UTC)
@toki1990, enable _makemenuconfig= in PKGBUILD and set the cpu architecture to your own, or use native. The kernel Make scripts ignore your environment's configuration for good reason.
toki1990 commented on 2019-09-05 18:07 (UTC)
Hi @damentz, i'm edited makepkg.conf. I'm set "-march=x86-64 -mtune=native". Is it enough for build for special architure. I'm reading "-march -mtune" method is cancelled. How i can optimize my build for amd zen (ryzen r7 1700)
Democrab commented on 2019-08-30 16:09 (UTC)
@damentz, Thank you very much for the updates and extra information, I really appreciate it.
damentz commented on 2019-08-30 16:03 (UTC)
@Democrab, Valve's fsync patch set was merged on v5.2.10-lqx2. Seems like the discussion died down so I went ahead and merged it instead of waiting for the next version. You can see more details in the zen-kernel github issue: https://github.com/zen-kernel/zen-kernel/issues/150
damentz commented on 2019-08-16 22:33 (UTC)
@Democrab
I'm waiting for a second version of the patches in this issue: https://github.com/zen-kernel/zen-kernel/issues/150
There's a lot of discussion about them so I'd rather merge the v2 rather than v1.
Democrab commented on 2019-08-15 20:43 (UTC)
Given the amount of desktop users who game and the fact that this is orientated for desktop users, is there any chance of incorporating Valve's fsync kernel patches into this? I've been adding them in myself with great success in the games I've been playing via Proton.
damentz commented on 2019-07-27 19:28 (UTC)
@wailord284, just added the cpio make dependency and bumped the version.
wailord284 commented on 2019-07-27 18:39 (UTC)
Hi, Can you please add cpio as a dependency? I get this error without it:
./kernel/gen_kheaders.sh: line 77: cpio: command not found make[1]: [kernel/Makefile:132: kernel/kheaders_data.tar.xz] Error 127 make[1]: Waiting for unfinished jobs....
Thank you
Arzte commented on 2019-06-23 23:11 (UTC)
Thanks for looking into it! I appropriate it greatly!!
damentz commented on 2019-06-23 23:06 (UTC)
Done, just pushed out a new commit. No need to bump the pkgrel since the change is technically a no-op if you use makepkg. Any new build of this package will include the change, so yay users should get the benefits immediately.
sir_lucjan commented on 2019-06-23 22:46 (UTC)
@damentz:
Sure. We could drop pkgver() if you want.
damentz commented on 2019-06-23 22:44 (UTC)
@sir_lucjan, I separated the commit to change pkgver() from the update to the version updates, so we're still tracking the latest version of Liquorix despite your revert.
According to the wiki, if you define a pkgver() function, it'll be used to automatically update pkgver on execution of makepkg with the code you define. How about we just delete the function entirely then? I don't use that code myself, so all it does is interfere with the value I put into pkgver.
sir_lucjan commented on 2019-06-23 22:25 (UTC)
@Freso
Currently pkgver() generates the correct version number because regardless of the position in PKGBUILD it starts anyway after the prepare() function where these values are declared. If prepare() was following pkgver() then you would be absolutely right. pkgver() is before prepare() in PKGBUILD only for cosmetic reasons and it doesn't matter for the operation; anyway it is after prepare() and before build().
Freso commented on 2019-06-23 21:57 (UTC)
I don’t think $_minor
and $_patchrel
get carried over from prepare()
to other functions (such as pkgver()
). You may need to define them again inside pkgver()
.
sir_lucjan commented on 2019-06-23 20:46 (UTC)
@Freso
I've reverted https://aur.archlinux.org/cgit/aur.git/commit/?h=linux-lqx&id=962414a35862
.
pkgver() dosen't work properly; I've downgrade lqxpatchset (-13 --> -11) and pkgver() doesn't set a proper pkgver.
@damentz
Please check your mailbox.
Freso commented on 2019-06-23 20:32 (UTC)
If all pkgver()
does is return $pkgver
, why not just remove the pkgver()
function entirely? The pkgver()
is a helper function to set $pkgver
, so it makes no sense to have it set $pkgver
to $pkgver
…
Arzte commented on 2019-06-13 21:41 (UTC)
Sure! Using makepkg, if you do your build in a separate command, it'll build using the wrong version.
As an example, makepkg --cleanbuild --nobuild
followed by makepkg --clean --force --noextract --noprepare
will cause the second command to use the wrong version (because it "updates" it to 5.1._-1 from 5.1.9_4-1)
sir_lucjan commented on 2019-06-13 21:04 (UTC)
@Arzte
We don't support yay and aur-helpers.
Please use a makepkg.
Arzte commented on 2019-06-13 21:01 (UTC) (edited on 2019-06-13 21:05 (UTC) by Arzte)
Heya this package is currently broken when using the AUR helper yay. Yay runs functions separately (Eg prepare separate from build) and so any variable set in say prepare aren't kept for later on. This means that when this is building because _minor and _patchrel are set in prepare, this package can't currently be installed using yay, as it builds under a weird version.
An example of this would be with version 5.1.9_4-1 of this package, yay will error out when trying to install it, because makepkg would've built it under 5.1._-1, instead of 5.1.9_4-1.
(The yay issue discussing this is here) https://github.com/Jguer/yay/issues/893
To clarify this is because the variables are in separate functions, so they don't carry on when the PKGBUILD functions are executed separately with makepkg.
Democrab commented on 2019-06-04 13:24 (UTC)
I've been building/using this kernel for a few months on Manjaro, using an AUR Helper with zero problems in that entire timeframe. Any problems that @megapro17 is having are related to his specific system.
Thank you for maintaining this.
damentz commented on 2019-05-14 02:01 (UTC)
@Agafron, thanks for the feedback.
Agafron commented on 2019-05-07 17:38 (UTC)
@megapro17, @damentz, I build this kernel on manjaro, distributive haven`t problems with compiling
Terence commented on 2019-03-08 16:07 (UTC)
@damentz ok great thanks. BTW don't forget to check your matrix client from time to time ;)
damentz commented on 2019-03-08 15:14 (UTC)
@Terence, I merged the patches into 4.20/master on Zen Kernel yesterday. Next release of Liquorix will include them.
Terence commented on 2019-03-07 15:04 (UTC) (edited on 2019-03-07 19:01 (UTC) by Terence)
@sir_lucjan @damentz would it be possible to merge bfq-mq v10 into the kernel? The new version seems to greatly improve throughput performances but only made it for inclusion into 5.2
sir_lucjan commented on 2019-02-06 10:29 (UTC)
@megapro17
I've compiled with makepkg.
Please fix your hands. And if it possible, your system too.
sir_lucjan commented on 2019-02-06 10:21 (UTC)
@megapro17
We don't support Manjaro. That PKGBUILD doesn't use wget so..... problem exists between keyboard and chair.
damentz commented on 2019-02-05 21:45 (UTC)
@simona, Have you tried submitting your build errors to the yay maintainers? Makepkg is the core Arch utility for building AUR packages. If your helper is creating new problems that makepkg does not cause, then the AUR helper has a bug.
Also, looking at yay's github issue page, I'm seeing open issues about yay trying to install packages for the wrong architecture after building: https://github.com/Jguer/yay/issues/844
When we say we don't support AUR helpers, it's because our AUR package comment section is not for AUR helper tech support. That belongs in forums that the developers of the AUR helpers provide support, like their github or AUR package page.
@megapro17, Have you opened up a thread on the Manjaro forum? If only Manjaro users are unable to build a package in the AUR, then there's something specific to Manjaro that's causing it. You should provide them feedback to they can look into it. I'm sure other Manjaro users would benefit too.
megapro17 commented on 2019-02-05 17:26 (UTC)
I tried to install this kernel on fresh manjaro, and it just frozen after wget phase. Maintainer please fix your hands. And if it possible, package too.
sir_lucjan commented on 2019-01-16 11:47 (UTC) (edited on 2019-01-16 11:49 (UTC) by sir_lucjan)
The problem IS your aur helper. I've compiled with makepkg:
LOG: https://pastebin.com/wiRRhGff
Packages:
$ ls
4.19-10.tar.gz PKGBUILD linux-lqx-4.19.15_1-2-x86_64.pkg.tar.xz linux-lqx-headers-4.19.15_1-2-x86_64.pkg.tar.xz linux.preset
60-linux.hook config.last linux-lqx-4.19.15_1-2-x86_64.pkg.tar.xz.sig linux-lqx-headers-4.19.15_1-2-x86_64.pkg.tar.xz.sig pkg
90-linux.hook linux-4.19.tar.sign linux-lqx-docs-4.19.15_1-2-x86_64.pkg.tar.xz linux.install src
99-linux.hook linux-4.19.tar.xz linux-lqx-docs-4.19.15_1-2-x86_64.pkg.tar.xz.sig linux.install.pkg
So.... please try with makepkg or "will simply stop using this kernel"
Cheers!
simona commented on 2019-01-16 11:11 (UTC)
the problem is any aur helper I use and this is probably not a bug in the helper. all the other packages (and I use a lot of them) work perfectly with all my aur helper (sporadically someone does not work with some specific aur helper). although it is legitimate to ignore this specific problem, more generally I do not think it is right to declare war on aur helpers as if they were absolute evil. therefore I will simply stop using this kernel or wait for the problem to be "alone" over time. good day.
sir_lucjan commented on 2019-01-14 15:25 (UTC)
I don't support aur-helpers.
Please use makepkg instead yay.
simona commented on 2019-01-14 15:20 (UTC)
==> Uscita dall'ambiente di fakeroot. ==> Compilazione terminata: linux-lqx 4.19._-1 (lun 14 gen 2019 14:12:33 CET) ==> Pulizia in corso... caricamento dei pacchetti in corso... errore: '/home/simona/.cache/yay/linux-lqx/linux-lqx-4.19.15_1-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto errore: '/home/simona/.cache/yay/linux-lqx/linux-lqx-docs-4.19.15_1-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto errore: '/home/simona/.cache/yay/linux-lqx/linux-lqx-headers-4.19.15_1-1-x86_64.pkg.tar.xz': impossibile trovare o leggere il pacchetto
sir_lucjan commented on 2019-01-13 17:11 (UTC)
Please paste a log with error.
simona commented on 2019-01-12 10:54 (UTC)
compile but at the end do not create package...
Agafron commented on 2018-12-21 20:37 (UTC)
@damentz, I can`t initialize rules on this kernel, any comand had answer 'No chain/target/match by that name', Its after update on 4.19-lqx? on the custom kernel iptables works ok. OS manjaro. which info can I give you to fix this problem?
damentz commented on 2018-12-21 18:10 (UTC)
@Agafron, there shouldn't be anything different with iptables on liquorix. On my work laptop, I'm able to use UFW to block incoming connections besides those to port 22, and sshuttle to create poor mans VPNs utilizing iptables to redirect traffic.
Maybe you forgot to initialize your rules?
Agafron commented on 2018-12-19 20:25 (UTC)
@damentz, hi! I have some problems with iptables on this version
sudo iptables -L
iptables: No chain/target/match by that name.
what parameters affect it?
damentz commented on 2018-12-01 20:42 (UTC)
@Filip98, I'll re-enable hierarchical scheduling once Paolo corrects an oops when it's enabled. You can see the progress on the bfq-iosched google group here: https://groups.google.com/forum/#!topic/bfq-iosched/5wkrbgXf4VM
Filip98 commented on 2018-11-27 23:00 (UTC)
This kernel seems to have an issue with libvirt(Qemu/KVM) http://i64.tinypic.com/30m9ul3.jpg http://i65.tinypic.com/oqg1ow.jpg I've digged a little bit around the net: https://forums.whonix.org/t/solved-cant-start-the-new-14-whonix-vms-libvirterror-unsupported-configuration-block-i-o-tuning-is-not-available-on-this-host/5664 and looks like it requires the following to be enabled in the kernel: CONFIG_BLK_CGROUP CONFIG_CFQ_GROUP_IOSCHED CONFIG_BLK_DEV_THROTTLING I switched to my alternative kernel and it runs fine, I didn't recompile to confirm that this fixes the issue tho
damentz commented on 2018-11-20 14:43 (UTC) (edited on 2018-11-20 15:21 (UTC) by damentz)
@Terence, I briefly experimented again with 1000hz but it was a huge drain on battery life. MuQSS 0.173 (and possibly 0.180 with 4.19), doesn't support tickless idle correctly, and ends up feeding cpufreq with bad idle data. The periodic forces cpufreq to ingest idle time accounting data, letting the cpu properly rest while idle, but the periodic tick prevents the CPU from staying in the CPU's lowest state (C6 / C7). It's measurable, and I mentioned some data points in my commit reverting back to 250hz here:
https://github.com/damentz/liquorix-package/commit/070398c973863e03dc384e578e27f58d9f05c607
Until I figure out a better compromise with 1000hz, you'll need to manually go in on every build and raise the frequency to 1000hz for your system. It's perfectly fine for desktops but a huge problem on laptops. Both my personal and work laptops lose about 20%-30% battery life for idle / casual loads. In my testing, 250hz preserves cpu temperatures as well as tickless idle, so that'll work for now.
Also, I re-enabled IRQ time accounting as it seems that it was originally added so that the process scheduler (CFS in this case), had more accurate data about how much cpu time each task consumed. It should have some benefits for MuQSS as well.
Agafron commented on 2018-11-19 19:30 (UTC)
@sir_lucjan, ok, thanks!
sir_lucjan commented on 2018-11-19 19:26 (UTC)
Agafron commented on 2018-11-19 19:24 (UTC)
@sir_lucjan, ok, need I reinstall package?
$ uname -r
4.18.19-lqx1-1-lqx
sir_lucjan commented on 2018-11-19 19:12 (UTC)
Agafron commented on 2018-11-19 19:06 (UTC)
@damentz, I have some diff of versions:
1 aur/linux-lqx 4.18.19_2-2 [installed: 4.18.20_1-1] (114) (1,86)
A desktop oriented kernel and modules with Liquorix patches
2 aur/linux-lqx-docs 4.18.19_2-2 [installed: 4.18.20_1-1] (114) (1,86)
Kernel hackers manual - HTML documentation that comes with the linux-lqx.
3 aur/linux-lqx-headers 4.18.19_2-2 [installed: 4.18.20_1-1] (114) (1,86)
Its PKGBUILD mistake?
damentz commented on 2018-11-18 18:39 (UTC) (edited on 2018-11-18 18:40 (UTC) by damentz)
@Terence, that's good information. While you were comparing results, I was measuring the overhead of 1000hz vs 250hz.
With 250hz, the timer consumes about 2-3ms, every second. Increasing this to 1000hz almost quadruples it. At idle, the timer tick consumes 8ms/s, but 5ms/s when the system is under full load (highest frequency). 8ms is less than 1% of the cpu usage of one core on a processor.
On the flip-side, one change I made with switching to 250hz is to re-instate a sampling down factor on ondemand. While the system is idle, it consumes about 3-5ms/s worth of processing to determine the next frequency. While the system is under full load, or near full load, ondemand consumes less than 1ms/s.
One thing I was wondering if you could try is adding rqshare=mc
to your kernel parameters. Liquorix is currently configured with smt runqueue sharing, which improves throughput by looking for tasks in the order of cache locality. This might be influencing your underruns in a bad way.
Terence commented on 2018-11-18 15:22 (UTC)
@damentz I tried your suggestion but it didn't seem to improve things. I have between 3 and 4 times less xruns when using 1000Hz tick rate compared to the now default 250Hz. My test settings were a sample rate of 48000 Hz with 64 as the buffer size giving a latency of 1.3ms. I used the performance governor. I normally use 128 as the buffer size but I increased it in order to get more frequent xruns. An other observation is the schedutil is closer to the performance governor in terms of xruns at 1000Hz but there is a bigger gap between both at 250Hz.
I'm still wondering if it wouldn't make sense to keep 250hz as the default as my usage is quite an edge case I would say.
damentz commented on 2018-11-17 19:15 (UTC)
@Terence, try setting rr_interval back to 3 in /proc/sys/kernel. If that doesn't help, then it's the kernel tick frequency.
And thanks for reporting. Con has mentioned that the kernel tick frequency shouldn't matter and that MuQSS is "tickless". This may prove the opposite and that you still need a high frequency tick rate to support soft-realtime applications properly.
Let me know which of the two settings helps you the most - I'll update the configuration accordingly.
Terence commented on 2018-11-16 12:27 (UTC)
@damentz your changes introduced by https://github.com/damentz/liquorix-package/commit/d51bd77f2719e43528898a4db06af34aafd22bdf while being saner defaults degrades realtime audio/midi performances (more frequent xruns). Would only changing back the tick to 1000hz locally enough?
sir_lucjan commented on 2018-11-13 19:47 (UTC)
@Agafron:
Because 4.18.18-lqx patchset includes 4.18.18 from upstream.
Agafron commented on 2018-11-13 19:43 (UTC) (edited on 2018-11-13 19:49 (UTC) by Agafron)
Downloading linux-4.18.tar.xz
_major=4.18
_srcname=linux-${_major}
.........
source=("https://www.kernel.org/pub/linux/kernel/v4.x/${_srcname}.tar.xz"
Why is downloading linux-4.18.tar.xz instead of linux-4.18.18.tar.xz?
CybeX commented on 2018-11-13 10:00 (UTC) (edited on 2018-11-13 10:00 (UTC) by CybeX)
If anyone has an issue in building the kernel relating to:
Verifying source file signatures with gpg...
linux-4.18.tar ... FAILED (unknown public key 79BE3E4300411886)
==> ERROR:</font> One or more PGP signatures could not be verified!
Use the following:
gpg --keyserver hkps://pgp.mit.edu --recv-keys 79BE3E4300411886
gaougalos commented on 2018-11-10 17:16 (UTC)
When installing this kernel i get ERROR: module not found: `usbhid'
mapcode.mind commented on 2018-10-11 20:40 (UTC)
i'm happy to report that the package compiled and installed successfully. @damentz : your comment is informative; I didn't know that having not used makepkg before. I was unsuccessfully trying to edit the PKGBUILD variables to make it create the correct file. Thanks a lot for your input.
@sir_lucjan : about manjaro not being arch, i know that. I was thinking of using manjaro as a stepping stone towards arch, coming from a debian system. But, i have no complaints with the system i have now. Nor can i figure out a compelling enough reason to switch. In fact, this is the first issue i have had with aur since i installed manjaro, and i am pretty sure that this was an issue with aur helper yay and not manjaro itself. Thanks a lot for your comments and suggestions; they were really helpful.
damentz commented on 2018-10-11 20:29 (UTC) (edited on 2018-10-11 20:29 (UTC) by damentz)
There's probably multiple reasons why makepkg -sric
solved your problem:
-s
= --syncdeps - installs missing dependencies
-c
= --clean - removes artifacts and work directories before building
-r
= --rmdeps - removes installed dependecies required for build
It could just be you were missing dependencies and your work directory was dirty, had previous folders and files that were interfering with your build.
sir_lucjan commented on 2018-10-11 20:04 (UTC)
Manjaro != Arch
AUR is designed for Arch, not Manjaro
mapcode.mind commented on 2018-10-11 20:00 (UTC)
i am running manjaro and have base-devel already installed. You know it's really surprising, but this time i tried makepkg -sric
, the first line was what it is supposed to be :
==> Making package: linux-lqx 4.18.13_1-1 (Fri 12 Oct 2018 01:21:27 IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading linux-4.18.tar.xz...
I guess it would work this time. I'll let you know after it finishes compiling. Thank you for the makepkg suggestion.
sir_lucjan commented on 2018-10-11 19:50 (UTC) (edited on 2018-10-11 19:51 (UTC) by sir_lucjan)
Do you use Arch Linux or fork? Do you install base-devel? I've installed linux-lqx without problem:
mapcode.mind commented on 2018-10-11 19:49 (UTC)
i just tried makepkg
and the first line itself is instructive :
➜ linux-lqx git:(master) ✗ makepkg
==> Making package: linux-lqx 4.18._-1 (Fri 12 Oct 2018 01:17:44 IST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Found linux-4.18.tar.xz
-> Found linux-4.18.tar.sign
-> Found 4.18-16.tar.gz
-> Found 60-linux.hook
-> Found 90-linux.hook
-> Found 99-linux.hook
-> Found linux.preset
==> Validating source files with sha512sums...
linux-4.18.tar.xz ... Passed
linux-4.18.tar.sign ... Skipped
4.18-16.tar.gz ... Passed
60-linux.hook ... Passed
90-linux.hook ... Passed
99-linux.hook ... Passed
linux.preset ... Passed
==> Verifying source file signatures with gpg...
linux-4.18.tar ... Passed
==> Extracting sources...
-> Extracting linux-4.18.tar.xz with bsdtar
^C
==> ERROR: Aborted by user! Exiting...
sir_lucjan commented on 2018-10-11 19:46 (UTC) (edited on 2018-10-11 19:48 (UTC) by sir_lucjan)
Try with makepkg.
git clone https://aur.archlinux.org/linux-lqx.git
cd linux-lqx.git
makepkg -sric
https://wiki.archlinux.org/index.php/Arch_User_Repository#Installing_packages
mapcode.mind commented on 2018-10-11 19:44 (UTC)
i am using aur helper yay
. I edit the PKGBUILD to use nconfig
at times and to set use_Current=y
.
sir_lucjan commented on 2018-10-11 19:43 (UTC) (edited on 2018-10-11 19:45 (UTC) by sir_lucjan)
Do you use aur helpers or makepkg?
I don't support aur-helpers. Try with makepkg.
mapcode.mind commented on 2018-10-11 19:41 (UTC) (edited on 2018-10-11 19:43 (UTC) by mapcode.mind)
@sir_lucjan : i was able to install linux-lqx with yay until now. I'd try using makepkg if the issue persists.
here are the logs for the latest build i tried:
-> Adding symlink...
-> Fixing permissions...
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "linux-lqx-headers"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Starting package_linux-lqx-docs()...
-> Installing documentation...
-> Adding symlink...
-> Fixing permissions...
==> Tidying install...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "linux-lqx-docs"...
-> Generating .PKGINFO file...
-> Generating .BUILDINFO file...
-> Generating .MTREE file...
-> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: linux-lqx 4.18._-1 (Fri 12 Oct 2018 01:06:46 IST)
==> Cleaning up...
loading packages...
error: '/home/mapcode/.cache/yay/linux-lqx/linux-lqx-4.18.13_1-1-x86_64.pkg.tar.xz': could not find or read package
error: '/home/mapcode/.cache/yay/linux-lqx/linux-lqx-headers-4.18.13_1-1-x86_64.pkg.tar.xz': could not find or read package
sir_lucjan commented on 2018-10-11 15:07 (UTC)
@ mapcode.mind
You should use makepkg.
damentz commented on 2018-10-11 14:41 (UTC)
@mapcode.mind, try the latest version.
mapcode.mind commented on 2018-10-11 14:17 (UTC) (edited on 2018-10-11 14:18 (UTC) by mapcode.mind)
➜ ~ yay -Syua
:: Searching AUR for updates...
:: 2 Packages to upgrade.
2 aur/linux-lqx 4.18._-1 -> 4.18.12_2-2
1 aur/linux-lqx-headers 4.18._-1 -> 4.18.12_2-2
==> Packages to not upgrade: (eg: 1 2 3, 1-3, ^4 or repo name)
==> ^C⏎
This is the output after i manually installed the .pkg.tar.xz. I'll recompile the kernel and paste logs.
sir_lucjan commented on 2018-10-11 10:35 (UTC)
I can not confirm:
sir_lucjan commented on 2018-10-11 10:35 (UTC)
I can not confirm:
mapcode.mind commented on 2018-10-11 08:19 (UTC)
i wish i could, but then i'll have to recompile it. But, i remember that the build process finished successfully, and a linux-lqx-4.18.-1.pkg.tar.xz file was created. But, at the final step, when this .pkg.tar.xz file was to be installed, the script looked for linux-lqx-4.18.12_2-2.pkg.tar.xz, couldn't find it, and exited with error. I manually was able to install the linux-lqx-4.18.-1.pkg.tar.xz file then with pacman - U.
sir_lucjan commented on 2018-10-10 21:51 (UTC)
Could you paste logs?
mapcode.mind commented on 2018-10-10 21:47 (UTC) (edited on 2018-10-10 21:48 (UTC) by mapcode.mind)
i am facing some issues when installing it. Somehow the versioning is not being assigned properly in the pkgbuild. the pkgbuild builds it as 4.18._-1 instead of 4.18.12_2-2, and then exits complaining at the last installation stage that it couldn't find 4.18.12_2-2.
I was able to manually install the .pkg.tar.xz files
Terence commented on 2018-10-10 16:33 (UTC)
@sir_lucjan https://pastebin.com/V2R4vS2r
sir_lucjan commented on 2018-10-10 15:22 (UTC)
@damentz
I'll test
damentz commented on 2018-10-10 15:11 (UTC)
@sir_lucjan
I don't see a problem keeping linux-lqx-docs, it's just htmldocs that's the problem.
Check your email, I sent you a patch to disable htmldocs by default, and allow one to enable it as they need it.
sir_lucjan commented on 2018-10-10 14:23 (UTC) (edited on 2018-10-10 14:29 (UTC) by sir_lucjan)
@damentz
Probably I'll drop docs package, so tell me what you think.
damentz commented on 2018-10-10 14:17 (UTC)
@sir_lucjan, @Terence's comment reminded me - why don't we just turn off htmldocs? They were added to the primary Arch linux PKGBUILD, but I genuinely don't think enough people use it to make it a build requirement. At least, they only existed in the docs package just a month or two ago, I don't think anyone will care if we turn them back off.
sir_lucjan commented on 2018-10-10 12:15 (UTC)
@ Terence
Please look at:
makedepends=(xmlto kmod inetutils bc libelf git python-sphinx graphviz)
Could you paste logs?
Terence commented on 2018-10-10 12:03 (UTC)
@sir_lucjan Please add texlive-latexextra to the makedepends otherwise generation of documentation fails.
sir_lucjan commented on 2018-09-21 10:11 (UTC)
@ Dill
OK. Damentz has updated sources. Please read pinned comment.
DIlI commented on 2018-09-21 05:48 (UTC) (edited on 2018-09-21 05:49 (UTC) by DIlI)
@sir_lucjan
Verified config.amd64 NOT SUCCESSFUL Could you please fix it? Thank you!
ronoverdrive commented on 2018-09-20 23:02 (UTC)
Have the CPUFreq drivers been removed? I've been unable to change governors or adjust the ondemand ramp up settings and the drivers don't seem to be present even though I have them all check marked in XConfig.
Terence commented on 2018-09-08 18:54 (UTC)
@sir_lucjan: simona is probably using an aur helper and has also modified the config through one of the config tools available in the PKGBUILD, he just needs to delete the file (and make a backup if necessary).
sir_lucjan commented on 2018-09-08 13:15 (UTC)
@simona
I can not confirm:
[lucjan@archlinux ~]$ export LANG=C
[lucjan@archlinux ~]$ git cl aur:linux-lqx
Cloning into 'linux-lqx'...
remote: Enumerating objects: 1097, done.
remote: Counting objects: 100% (1097/1097), done.
remote: Compressing objects: 100% (527/527), done.
remote: Total 1097 (delta 639), reused 1017 (delta 570)
Receiving objects: 100% (1097/1097), 351.51 KiB | 3.38 MiB/s, done.
Resolving deltas: 100% (639/639), done.
[lucjan@archlinux ~]$ cd linux-lqx
[lucjan@archlinux linux-lqx]$ makepkg -sr --sign
==> Making package: linux-lqx 4.18.6-1 (Sat Sep 8 15:14:30 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading linux-4.18.tar.xz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 917 0 --:--:-- --:--:-- --:--:-- 917
100 97.0M 100 97.0M 0 0 3810k 0 0:00:26 0:00:26 --:--:-- 3771k
-> Downloading linux-4.18.tar.sign...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 1022 0 --:--:-- --:--:-- --:--:-- 1022
100 455 100 455 0 0 1350 0 --:--:-- --:--:-- --:--:-- 1350
-> Downloading 4.18.6-1.patch.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 625k 100 625k 0 0 598k 0 0:00:01 0:00:01 --:--:-- 598k
-> Downloading config.amd64...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 201k 100 201k 0 0 246k 0 --:--:-- --:--:-- --:--:-- 246k
-> Found 60-linux.hook
-> Found 90-linux.hook
-> Found 99-linux.hook
-> Found linux.preset
==> Validating source files with sha512sums...
linux-4.18.tar.xz ... Passed
linux-4.18.tar.sign ... Skipped
4.18.6-1.patch.gz ... Passed
config.amd64 ... Passed
60-linux.hook ... Passed
90-linux.hook ... Passed
99-linux.hook ... Passed
linux.preset ... Passed
==> Verifying source file signatures with gpg...
linux-4.18.tar ... Passed
==> Extracting sources...
-> Extracting linux-4.18.tar.xz with bsdtar
sir_lucjan commented on 2018-09-08 13:12 (UTC)
- Please read first comment
- Only english!!!
simona commented on 2018-09-08 12:28 (UTC)
==> Validazione di source file con sha512sums... linux-4.18.tar.xz ... Verificato linux-4.18.tar.sign ... Ignorato 4.18.6-1.patch.gz ... Verificato config.amd64 ... NON RIUSCITO
sir_lucjan commented on 2018-09-08 11:17 (UTC)
Bump to 4.18.6-1.
PS. Latest commit got its name wrong, my bad.
Terence commented on 2018-09-03 15:34 (UTC) (edited on 2018-09-05 12:13 (UTC) by Terence)
sir_lucjan commented on 2018-08-24 18:09 (UTC)
Done
damentz commented on 2018-08-24 17:56 (UTC)
@sir_lucjan,
@Terence is correct here, if you update the package, you need to bump pkgrel. It may install the same kernel, but the package is now distinctly different and does at least one thing different, and thus is a different version.
sir_lucjan commented on 2018-08-24 17:42 (UTC)
@Terence
Please look at: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=c3b5e10f9b704742e282a03803482c81e75dee5f
Did you see?
sir_lucjan commented on 2018-08-24 17:38 (UTC)
@Terence
I'll bump pkgrel later.
Terence commented on 2018-08-24 17:36 (UTC)
@damentz @sir_lucjan I'm not saying pkgrel needs to be 3 to match the lqxrel but because the PKGBUILD has been modified by 5c3a7fec1607
and thus needs to have its pkgrel updated.
damentz commented on 2018-08-24 17:13 (UTC)
@Terence
The pkgrel variable determines the version of the package, which gets incremented on every update. The lqxrel variable is used to find the liquorix release / patch to pull everything the package needs. It's only coincidental that they're identical at times.
sir_lucjan commented on 2018-08-24 16:36 (UTC)
@Terence Why? pkgrel != lqxrel
Terence commented on 2018-08-24 16:35 (UTC)
@sir_lucjan doesn't 5c3a7fec1607
needs pkgrel=3 ?
sir_lucjan commented on 2018-08-22 12:47 (UTC)
@Terence
Nope.
pkgbase=linux-lqx
# pkgname=('linux-lqx' 'linux-lqx-headers' 'linux-lqx-docs')
_major=4.17
_minor=17
pkgver=${_major}.${_minor}
_srcname=linux-${_major}
pkgrel=2
lqxrel=3
Terence commented on 2018-08-22 12:42 (UTC) (edited on 2018-08-22 12:42 (UTC) by Terence)
@sir_lucjan you forgot to bump to 4.17.17-3 :)
Filip98 commented on 2018-08-08 11:04 (UTC)
Thank you for the responses :).
damentz commented on 2018-07-20 17:00 (UTC) (edited on 2018-07-20 17:03 (UTC) by damentz)
@Filip98, you're probably compiling the kernel with one thread, check the recommendations here : https://wiki.archlinux.org/index.php/makepkg#Parallel_compilation
markusk commented on 2018-07-20 16:57 (UTC)
@Filip98: The compile time can be quite a while on slow/medium hardware and therefore it "is normal for that kind of hardware". You can speed it up a bit by using ccache (https://wiki.archlinux.org/index.php/Ccache).
Lubuntu is faster as your were most likely where using a precompiled package from some kernel-repo (launchpad?). The AUR system is source based in most of the cases.
Filip98 commented on 2018-07-20 13:22 (UTC)
It seems to be compiling itself for hours with a list of the kernel files e.g "CC [M] sound/.../*.o" going at it one by one, Is this normal behavior? I'm reluctant to think about repeating this for each update. This wasn't the case while I was using Lubuntu, I'm using aurman if it matters.
damentz commented on 2018-06-27 15:26 (UTC)
@sir_lucjan, thanks for the heads up
@DungSherlock, 'pkg' will use the Liquorix configuration used in the binary kernels from liquorix.net, while old will take your running configuration and execute 'make oldconfig', asking you to select options for new or updated menu items. If you're comfortable with the latter and are only interested in the kernel sources, then 'old' is the way to go. If you want the behavior you get from Liquorix binary kernels (Debian Sid, the major Ubuntu's), then choose 'pkg.
A commonly used option, since you're building from source, is to actually choose 'm'. This will let you adjust the 'pkg' configuration before the build starts. One advantage of this is you can optimize the kernel for your processor, giving you some marginal gains depending on what you're using the kernel for.
DungSherlock commented on 2018-06-27 15:13 (UTC)
Different build option _config="pkg" and _config="old"? What is advice?
sir_lucjan commented on 2018-06-27 10:08 (UTC) (edited on 2018-06-27 10:11 (UTC) by sir_lucjan)
@damentz
Probably MuQSS doesn't work properly with 4.16.17.
damentz commented on 2018-06-27 03:47 (UTC)
@sir_lucjan, please keep the patch at 4.16.16-2 for now, there's a stable patch in 4.16.17+ that's preventing some of my own systems from booting, but I currently don't have the time to figure out why only Arch is affected.
Seeing as how Arch itself has already moved to 4.17, it might be best to update linux-lqx once there's a 4.17 release - that'll probably include the fix.
markusk commented on 2018-05-07 13:51 (UTC)
@sir_lucjan : thx for looking into it. i cleaned out all my download caches and build locations and now it works ... odd ...
sir_lucjan commented on 2018-05-07 12:41 (UTC)
@markusk
I can't confirm:
[lucjan@archlinux roboczy-3]$ export LANG=C
[lucjan@archlinux roboczy-3]$ git clone https://aur.archlinux.org/linux-lqx.git
Cloning into 'linux-lqx'...
remote: Counting objects: 985, done.
remote: Compressing objects: 100% (491/491), done.
remote: Total 985 (delta 561), reused 909 (delta 494)
Receiving objects: 100% (985/985), 300.70 KiB | 1.65 MiB/s, done.
Resolving deltas: 100% (561/561), done.
[lucjan@archlinux roboczy-3]$ cd linux-lqx
[lucjan@archlinux linux-lqx]$ mkaurball
==> Making package: linux-lqx 4.16.7-1 (Mon May 7 14:35:37 CEST 2018)
==> Retrieving sources...
-> Downloading linux-4.16.tar.xz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 1379 0 --:--:-- --:--:-- --:--:-- 1379
100 98.2M 100 98.2M 0 0 2174k 0 0:00:46 0:00:46 --:--:-- 3411k
-> Downloading linux-4.16.tar.sign...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 178 100 178 0 0 912 0 --:--:-- --:--:-- --:--:-- 912
100 455 100 455 0 0 1146 0 --:--:-- --:--:-- --:--:-- 1146
-> Downloading 4.16.7-1.patch.gz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 644k 100 644k 0 0 624k 0 0:00:01 0:00:01 --:--:-- 625k
-> Downloading config.amd64...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 202k 100 202k 0 0 227k 0 --:--:-- --:--:-- --:--:-- 227k
-> Found 60-linux.hook
-> Found 90-linux.hook
-> Found 99-linux.hook
-> Found linux.preset
==> Validating source files with sha512sums...
linux-4.16.tar.xz ... Passed
linux-4.16.tar.sign ... Skipped
4.16.7-1.patch.gz ... Passed
config.amd64 ... Passed
60-linux.hook ... Passed
90-linux.hook ... Passed
99-linux.hook ... Passed
linux.preset ... Passed
==> Verifying source file signatures with gpg...
linux-4.16.tar ... Passed
==> Entering fakeroot environment...
==> Creating source package...
-> Adding PKGBUILD...
-> Generating .SRCINFO file...
-> Adding 60-linux.hook...
-> Adding 90-linux.hook...
-> Adding 99-linux.hook...
-> Adding linux.preset...
-> Adding install file (linux.install)...
-> Compressing source package...
==> Leaving fakeroot environment.
==> Source package created: linux-lqx (Mon May 7 14:36:39 CEST 2018)
sir_lucjan commented on 2018-05-06 16:52 (UTC)
linux-lqx from github:
damentz commented on 2018-05-06 16:15 (UTC)
Hi navjack27,
Intel p-states are disabled deliberately because they return lower frequencies than ondemand during multicore loads, and keep the processor frequency / voltage ramped up too high during idle loads with MuQSS. Due to the nature of how MuQSS works, you'll almost never benefit from TurboBoost 3.0's single core boost speeds, since MuQSS is more likely to reschedule task on a neighboring logical or physical core than CFS is.
You have the option to change the configuration of the AUR package before building using menuconfig - you can always force enable it yourself if your particular system.
sir_lucjan commented on 2018-05-06 16:01 (UTC)
@navjack27
Please report @damentz.
navjack27 commented on 2018-05-06 15:59 (UTC)
PLEASE enable intel p-states in the .config. There shouldn't be any reason why my laptop is limited to 1800MHz. This is a serious oversight. I'm going through the rest of the .config and will point out any other inconsistencies with modern computing.
sir_lucjan commented on 2018-04-27 19:42 (UTC) (edited on 2018-04-27 19:43 (UTC) by sir_lucjan)
@ Plexcon
- In English, mate, in English
- Please read previous comments.
Plexcon commented on 2018-04-27 19:39 (UTC) (edited on 2018-04-27 19:43 (UTC) by Plexcon)
==> Verificando las firmas de las fuentes con gpg... linux-4.15.tar ... HA FALLADO (clave pública desconocida 79BE3E4300411886) ==> ERROR: ¡No se ha podido verificar alguna de las firmas PGP!
<hr>gpg --recv-keys 79BE3E4300411886
damentz commented on 2018-04-18 17:36 (UTC) (edited on 2018-04-18 17:37 (UTC) by damentz)
@sxyzy1016
I updated the configuration last night with the recommendations in the wiki. The latest update @sir_lucjan pushed includes the change.
Commit: https://github.com/damentz/liquorix-package/commit/120495ce3a04bbbc9da6d7890dadea7510ebdcd0
sir_lucjan commented on 2018-04-17 11:00 (UTC)
@sxyzy1016
Please mail to damentz.
sxyzy1016 commented on 2018-04-17 04:04 (UTC)
Maybe should set "CONFIG_EFIVAR_FS=y" and "CONFIG_EFI_VARS=n" in .config file. Always got into a mount error " unknow filesystem type 'efivarfs' " at the very beginning of booting up.
sir_lucjan commented on 2018-03-08 15:11 (UTC) (edited on 2018-03-08 15:15 (UTC) by sir_lucjan)
@Ashraaf
My bad. Fixed
https://github.com/sirlucjan/workbench/commit/259323142e2bcbf4e797e73b05e618e16b523139
Ashraaf commented on 2018-03-08 15:01 (UTC) (edited on 2018-03-08 15:02 (UTC) by Ashraaf)
warning: cannot resolve "linux-lqx", a dependency of "linux-lqx-test-headers"
warning: cannot resolve "linux-lqx", a dependency of "linux-lqx-test-docs"
Does the test version really need to depend on main version?
bruceutut commented on 2018-03-04 06:28 (UTC)
I use linux-lqx with ath10k driver, and wlan driver seems unable to load.
demsg shows logs for linux-lqx: [ 66.527476] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2 [ 66.527490] ath10k_pci 0000:01:00.0: Falling back to user helper [ 127.967562] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-6.bin failed with error -2 [ 127.967565] ath10k_pci 0000:01:00.0: Falling back to user helper
Official kernel reports error too, but driver successfully loads. Logs here,
dmesg for official kernel: [ 2.895267] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:01:00.0.bin failed with error -2 [ 2.895313] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/cal-pci-0000:01:00.0.bin failed with error -2 [ 2.895979] ath10k_pci 0000:01:00.0: Direct firmware load for ath10k/QCA9377/hw1.0/firmware-6.bin failed with error -2 [ 2.898589] ath10k_pci 0000:01:00.0: qca9377 hw1.0 target 0x05020000 chip_id 0x003820ff sub 17aa:4035 [ 2.898597] ath10k_pci 0000:01:00.0: kconfig debug 1 debugfs 1 tracing 1 dfs 0 testmode 0 [ 2.900001] ath10k_pci 0000:01:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7 [ 2.965420] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 8aedfa4a
sir_lucjan commented on 2018-03-01 00:20 (UTC)
@kotajacob
Please try again.
kotajacob commented on 2018-03-01 00:11 (UTC)
Is the http://liquorix.net/ website down for anyone else? That might need updated if it is...
simona commented on 2018-02-11 14:20 (UTC)
For some strange thing "pacaur -S linux-lqx" fail check while "yaourt -S linux-lqx" was ok....
sir_lucjan commented on 2018-01-29 21:56 (UTC)
@Mthw
not out of date until lqx for 4.15.x is released.
sir_lucjan commented on 2018-01-18 11:51 (UTC)
@gaougalos
No.
gaougalos commented on 2018-01-18 08:02 (UTC)
Is there a repo for this package?
sir_lucjan commented on 2018-01-12 20:25 (UTC)
@cokomoko
Try makepkg. I support only makepkg.
cokomoko commented on 2018-01-12 20:21 (UTC)
@damentz
I am using yaourt.
I do not think I'm experiencing full disk or file system corruption.
tmpfs 3.9G 1.1G 2.9G 27% /tmp
damentz commented on 2018-01-12 19:40 (UTC)
@cokomoko
"sha512_mb.o: file not recognized: Dosya biçemi tanınmıyor"
Maybe you have a full disk or filesystem corruption?
sir_lucjan commented on 2018-01-12 19:38 (UTC) (edited on 2018-01-12 19:39 (UTC) by sir_lucjan)
@cokomoko
Do you use yaourt, pacaur or makepkg?
Please use English.
cokomoko commented on 2018-01-12 19:36 (UTC)
CC [M] arch/x86/crypto/sha256-mb/sha256_mb.o AS [M] arch/x86/crypto/sha256-mb/sha256_mb_mgr_flush_avx2.o CC [M] arch/x86/crypto/sha256-mb/sha256_mb_mgr_init_avx2.o AS [M] arch/x86/crypto/sha256-mb/sha256_mb_mgr_submit_avx2.o AS [M] arch/x86/crypto/sha256-mb/sha256_x8_avx2.o LD [M] arch/x86/crypto/sha256-mb/sha256-mb.o AR arch/x86/crypto/sha512-mb/built-in.o CC [M] arch/x86/crypto/sha512-mb/sha512_mb.o AS [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_flush_avx2.o CC [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_init_avx2.o AS [M] arch/x86/crypto/sha512-mb/sha512_mb_mgr_submit_avx2.o AS [M] arch/x86/crypto/sha512-mb/sha512_x4_avx2.o LD [M] arch/x86/crypto/sha512-mb/sha512-mb.o arch/x86/crypto/sha512-mb/sha512_mb.o: file not recognized: Dosya biçemi tanınmıyor make[3]: [scripts/Makefile.build:560: arch/x86/crypto/sha512-mb/sha512-mb.o] Error 1 make[2]: [scripts/Makefile.build:573: arch/x86/crypto/sha512-mb] Error 2 make[1]: [scripts/Makefile.build:573: arch/x86/crypto] Error 2 make: [Makefile:1032: arch/x86] Error 2
Where's the problem?
sir_lucjan commented on 2018-01-06 22:05 (UTC)
@hydranix
Did you try with 4.14.12?
hydranix commented on 2018-01-04 02:16 (UTC) (edited on 2018-01-04 13:30 (UTC) by hydranix)
I keep getting error during kernel build related to arrays overflowing in loops.
Anybody familiar with why this might be? I've been trying to track it down for a while now.
Various files fail with "array subscript is above array bounds"
simona commented on 2018-01-03 22:44 (UTC)
Using yaourt instead of pacaur problem was solved.
sir_lucjan commented on 2018-01-02 11:36 (UTC) (edited on 2018-01-02 11:38 (UTC) by sir_lucjan)
@simona Please paste full log. Please use English. Did you understand me?
sir_lucjan commented on 2017-12-29 15:56 (UTC)
@simona
Please paste full log. Please use English.
simona commented on 2017-12-29 15:53 (UTC)
==> ERRORE: Uno o più file non hanno superato il controllo di validità!
sir_lucjan commented on 2017-12-25 16:20 (UTC)
@hobbledehoy899 4.14.8-3 is the newest lqx patch: https://liquorix.net/sources/
sir_lucjan commented on 2017-12-09 16:45 (UTC) (edited on 2017-12-09 17:25 (UTC) by sir_lucjan)
Damentz sometimes updates sources and checksums do not match. Please let me know.
sir_lucjan commented on 2017-12-09 16:42 (UTC) (edited on 2017-12-14 20:53 (UTC) by sir_lucjan)
I know :P
damentz has updated sources -->
4.14.4-2.patch.gz 2017-12-08 20:54
config.amd64 2017-12-08 20:43
I'll update ASAP. Be patient
markusk commented on 2017-12-09 16:32 (UTC)
Hi
i can confirm he config.amd64 error ! config.amd64 ... FAILED
sir_lucjan commented on 2017-12-04 11:00 (UTC)
If you have your custom config - no. If you don't have - yes.
VoltureX commented on 2017-12-03 15:11 (UTC)
Do I need config.amd64 or is everything there just by downloading the kernel and patch? Thanks. Volt.
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