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
- _show_compile: Enables verbose-er compilation output and displays all executing make targets

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.

@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.

kernel build complete without error. but kernel not work over amd ryzen processor. is there a way run over amd ?

It seems that I need the cpio package to correctly build linux-clear. Maybe this is due to some kernel options I enabled, but not sure which ones.

@btd1337 That's for archlinux Trusted Users and Developers, not some random aur maintainers. ;-)

@metak Why you don't use the Arch Servers? Like here: https://pkgbuild.com/

https://wiki.archlinux.org/index.php/DeveloperWiki:Server_configuration

@btd1337 Hey. OpenSUSE Build Service support for archlinux is bad. I reported this issue years ago. https://github.com/openSUSE/obs-build/issues/129
Basically, the build service triggered the package rebuild (after my last commit), but since there's no support for arch to increment pkrel +1 we end up with (invalid or corrupt package (checksum)).
The package itself is fine though. You can install it with pacman -U, but I do realize this is inconvenient. Maybe I should just remove the instructions for binaries if it's causing confusion/problems?

:: File /var/cache/pacman/pkg/linux-clear-5.2.9-6-x86_64.pkg.tar.xz is corrupt (invalid or corrupt package (checksum)).
Do you want to delete it? [Y / n] y
:: File /var/cache/pacman/pkg/linux-clear-headers-5.2.9-6-x86_64.pkg.tar.xz is corrupt (invalid or corrupt package (checksum)).
Do you want to delete it? [Y / n] y
error: failed to submit transaction (invalid or corrupted package)
Errors occurred and therefore no packages were updated.
Error installing repo packages

@btd1337 That's because OpenSUSE Build Service "support" for pgp-signed repositories is broken.
https://bbs.archlinux.org/viewtopic.php?id=240521
https://lists.archlinux.org/pipermail/arch-general/2016-July/041519.html

@metak Just adding the key, this error persists:

error: linux-clear: unsupported signature format
error: linux-clear-headers: unsupported signature format

It's necessary to add SigLevel = Never in order to error message disapear, but this is not a good practice.