Package Base Details: linux-lqx

Git Clone URL: https://aur.archlinux.org/linux-lqx.git (read-only, click to copy)
Submitter: akurei
Maintainer: sir_lucjan (damentz)
Last Packager: damentz
Votes: 126
Popularity: 2.49
First Submitted: 2011-08-08 16:08
Last Updated: 2020-01-18 20:48

Latest Comments

« First ‹ Previous ... 9 10 11 12 13 14 15 16 17 18 19 ... Next › Last »

Terence commented on 2018-08-24 16:35

@sir_lucjan doesn't 5c3a7fec1607 needs pkgrel=3 ?

sir_lucjan commented on 2018-08-22 12:47

@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

@sir_lucjan you forgot to bump to 4.17.17-3 :)

Filip98 commented on 2018-08-08 11:04

Thank you for the responses :).

damentz commented on 2018-07-20 17:00

@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

@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

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

@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

Different build option _config="pkg" and _config="old"? What is advice?

sir_lucjan commented on 2018-06-27 10:08

@damentz

Probably MuQSS doesn't work properly with 4.16.17.