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.

Package works great, Just that is it possible to add Yama support? Would like to set the kernel.yama.ptrace_scope=1 as it's the Arch default. https://wiki.archlinux.org/index.php/Security#ptrace_scope

Also, chrome sandbox seems to be more powerful with Yama (chrome://sandbox)

Would also be nice to have Apparmor/SELinux support too

Thanks

@metak It's working for me, as I said, I just blacklisted the nvidiafb module and the nvidia started to work. Thanks.

@rvlobato @astroty Sorry I can't be more helpful with the nvidia because I don't have any nvidia cards.

@astroty The extramodules-clear folder was removed in sync with the stock arch kernel package.

After some searching, it seems that my Nvidia driver was failing to load because of this flag in my /etc/default/grub: pci=nommconf I didn't need to do that in another kernel I have though, so I don't know what might've caused this

Also, is it just me or are these new packages not generating a new extramodules-clear folder?

@calin @metak I was having the same issue, seems that the conflict was between nvidiafb and nvidia, after blacklisting the nvidiafb (the nvidia-dkms blacklist nouveau) the nvidia modules were loaded.

@calin I've already disabled CONFIG_MODULE_SIG_FORCE by default to make it easier and you should not need module.sig_unenforce. Check logs for more clues?

The nvidia drivers fail to load even when using module.sig_unenforce, they used to work, not anymore unfortunately, is anyone else having this issue?

@Elanzer Sorry about that. The pkgbuild file in obs wasn't synced fully and dell smbios should've been enabled long ago (as it is here in aur). The repo binary is already building.

@metak can you compile lts-2018 with CONFIG_DELL_SMBIOS_SMM=y or CONFIG_DELL_SMBIOS_WMI=y?? I dont know which one works for mine. My touchpad is weird with 5.3 so I rolledback to LTS. And with the older kernel i'm getting SMBIOS messages again. My laptop is old and it takes forever to compile a kernel, your binaries are a life-saver. Thanks.

@toki1990 I believe it should work on amd cpus, but I don't have amd cpus to try. If you can post some logs maybe someone can help.