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.

sorry for the noop question , but i couldn't get nvidia-dkms working and when i modprobe it i get :

modprobe: ERROR: could not insert 'nvidia': Required key not available

@ltsdw Thank you for reporting back. I don't use bluetooth at all so I never paid too much attention to it, but it seems that quite a few people do use it so I'll enable the crypto_user module in next update.

@metak yeah, exactly, bluetooth working like a charm after enabling CONFIG_CRYPTO_USER. I also enabled CONFIG_BT_ATH3K for precaution, but I'm actually using btusb. It's only needed set CONFIG_CRYPTO_USER to get bluetooth working.

@ltsdw Sorry, I'm a bit busy right now. After checking again I'll have to enable user_crypto with next update to comply with arch packaging.

bluez package in arch /usr/lib/modules-load.d/bluez.conf needs this module crypto_user at boot time.

Edit: can you build this kernel with CONFIG_CRYPTO_USER option enabled and check if bluetooth is working properly?

I'll try CONFIG_BT_ATH3K

@metak really is in the comments, thanks. One more thing, it's directly linked with the fact if bluetooth works or not?

@ltsdw If you need user_crypto module then you'll have to enable it CONFIG_CRYPTO_USER since this .config doesn't. I mentioned this somewhere in comments bellow.

This module is built in stock arch kernel though.

Having problem with bluez, if I uncomment user_crypto line in /usr/lib/modules-load.d/bluez.conf will fail to load systemd-modules-load at boot, basicly journalctl acuses not finding user_crypto module. Works well in arch's kernel, some idea?

@enihcam I will probably enable it by default with next update.

@E5ten No, but the kernel has to be packaged differently if you want to use clr-boot-manager.

Is it required to use clr-boot-manager with the clear kernel?