Arch Linux User Repository

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
- _use_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _optimize_defconfig: Applies package maintainer-picked configuration changes to your defconfig. Only takes effect with _use_current being enabled
- _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/MGENERIC_CPU (Generic x86-64), which is compatible with all amd64 processors. Must be a number or subarch name
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the MGENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset

All of these variables just need to be set for them to apply, except for _subarch and _debug. 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.

@Osleg I disabled CONFIG_MODULE_SIG_FORCE by default and if anyone wants to turn it on just comment that line in pkgbuild.

The main issue with modules not loading is that clear has CONFIG_MODULE_SIG and CONFIG_MODULE_SIG_FORCE enabled. Meaning most of the "custom" modules won't load. The workaround that I'm using for that is to sign those modules manually as described here https://www.kernel.org/doc/html/v4.10/admin-guide/module-signing.html

Tho I think it might be a good idea to disable CONFIG_MODULE_SIG_FORCE or at least provide a config for PKGBUILD to disable it for those who want. as this setting is good for hardened kernel for servers and such. For desktop machines, especially for developers, this setting provides nothing but pain :)

https://arstechnica.com/gadgets/2018/02/intel-releases-new-spectre-microcode-update-for-skylake-other-chips-remain-in-beta/

But I don't see the microcode for linux on Intel's website yet.

@PythonNut Yes, "CONFIG_CRYPTO_USER" is not set by default.

On many arch systems, this will cause systemd-modules-load to fail because the crypto_user module is not available.

@volfyd The srpm thing was a temporary solution. I filled the issue on github and they've updated the git repo which was out of date for two weeks or so.

Now, I've switched to the official kernel tarball/patch and fetching clearlinux patches via git.

(NOTICE: NEED TO IMPORT THE GPG KEYS FOR THIS )

This should save a bit of bandwidth and cause less problems. ;-)

==> Retrieving sources... -> Downloading linux-4.14.15-515.src.rpm... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found

Looks like 516 is already out.

@ahjolinna nvidia? Sorry, but no. Never had/used any nvidia cards so I wouldn't be able to test anything.

"dm_cache & dm_cache_smq"? I answered this one in my first comment below. It's not enabled by default. It's marked as experimental in kernel.

Here's a patch you can try that enables it. Add it to sources in pkgbuild file and rebuild the package.

https://pastebin.com/dDuzv2ux

why isn't the "dm_cache & dm_cache_smq" enabled in the kernel conf?, as I get module not found error