Arch Linux User Repository

Important update
I have updated and renamed some settings envvars. Please check your scripts, aliases, brain memory or whatever you use to store your build command and update them accordingly. Please read the description in the PKGBUILD file instead of the short summary in the pinned comment on the AUR or in the README in the repository as some important details important to this update are only found inside the PKGBUILD.

Information comment
This comment provides useful information about this package. Make sure to read it through, you won't regret it.

Repository URL
This package is hosted at sos!git. If you want to contribute to the package, you can do it here: https://git.staropensource.de/JeremyStarTM/aur-linux-clear

Issue handling
Please only submit issues in the package's repository if they aren't bug reports about the package or help requests. Please keep them to the AUR only. This prevents unnecessary signups.

Updates
I usually publish updates 0-3 days after a kernel release, depending on how busy I am.
If I however get wind of security-relevant updates or any vulnerabilities I will try to update the kernel as soon as possible and write a comment about the vulnerability/update. So make sure to subscribe to this package's comment mailing list.

PKGBUILD environment variable customization
The PKGBUILD file supports customization via environment variables. Here's a list of all of them:
- _makemenuconfig: Invokes make menuconfig (ncurses-based default configuration menu) before compilation starts
- _makenconfig: Invokes make nconfig (ncurses-based nicer configuration menu) before compilation starts
- _makexconfig: Invokes make xconfig (X11-based GUI configuration menu) before compilation starts
- _reuse_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _reuse_file: Will use the configuration file named kconfig contained in the PKGBUILD file's directory
- _update_kconfig_on_reuse: Specifies whether the kernel configuration shall be updated when using any of the 'reuse*' flags
- _copyfinalconfig: Copies the final kernel configuration into the repository root as kconfig-new before compilation starts
- _localmodcfg: Only compiles modules found in modprobed-db's database (which decreases compilation time and kernel size)
- _use_llvm_lto: Compiles the kernel with LLVM instead of GCC. Should work, if not open an issue
- _subarch: Specifies the subarchitecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 41 (Generic x86-64), which is compatible with all amd64 processors. Must be a number
- _use_llvm_lto: Enables compilation with LLVM. Untested but should work. If not write a comment on the AUR.
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the GENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug_kernel: Force enables kernel debugging options when set to y, force disables debug options when set to n or relies on the kconfig when unset
- _debug_script: Enables debugging for the PKGBUILD file

All of these variables just need to be set for them to apply, except for _subarch, _subarch_microarch and _debug_kernel. For more information please check their documentation inside the PKGBUILD file

GPG errors
If makepkg complains about invalid PGP keys, try running this command first: gpg --locate-keys torvalds@kernel.org gregkh@kernel.org sashal@kernel.org benh@debian.org. This command only needs to be executed once.

Build tool
If you want a dead simple way to compile this package, you can try out my build tool. It includes a few no nonsense changes to the kernel configuration and allows you to configure the PKGBUILD file in a simple manner and decrease build time. And if you don't want that, using makepkg as-is works fine too.

Is it possible to enable Zswap support (CONFIG_ZSWAP, CONFIG_ZPOOL, CONFIG_ZBUD, CONFIG_Z3FOLD, CONFIG_FRONTSWAP) and CONFIG_CLEANCACHE, like Arch kernels?

@Enverex I think it's best to leave it like it is now (taken from linux-ck package and graysky2 patch). By default the _subarch is empty and it will detect/enable optimizations for your cpu family.
The binary in my repo is built with generic_cpu optimizations. You could create a script or something?

#!/bin/bash

git checkout PKGBUILD
git pull
sed -i 's|^_subarch.*|_subarch=27|' PKGBUILD
makepkg -Ccrs

Any chance of making CONFIG_MNATIVE the default (rather than CONFIG_MCORE2) or having some way of enabling it without having to manually edit the PKGBUILD? (e.g. so that the package can be updated and keep this setting without manual intervention).

@enihcam I don't mind at all, but I hope it won't be flagged out-of-date again if it's not following kernel.org releases. ;-)

@metak again, this package is great. people using this package should vote for it. :)

this is only a suggestion. Personally i think it might be too frequent for compiling the kernel because the rapidly increasing version. i think it might be good to slow down a little bit.

Rather than watching www.kernel.org, maybe you want to release a version only when this RSS is updated: https://github.com/clearlinux-pkgs/linux/releases.atom

what do you think?

@big_bun Sorry for late reply, I've been busy. I really don't want to deviate too much from default upstream. (only when needed to comply with archlinux packaging for example)

@metak could you also add l2tp/pptp module in the next build? I think this should enable them: https://github.com/scaleway/kernel-tools/pull/143/commits/381264d671060a26fdfcf6245ea417d85bc371b0

@A.J If you have SecureBoot disabled then you simply use this boot parameter module.sig_unenforce to allow loading unsigned kernel modules. Otherwise you'll have to build your kernel with CONFIG_MODULE_SIG_FORCE disabled.

@metak could you elaborate , is it boot option or build option ??

@A.J Look below in comments for my comment to @Osleg about option to allow unsigned modules.