Arch Linux User Repository

The PKGBUILD supports customization via environment variables. Here's a list of all of them:
_makemenuconfig: Invokes make menuconfig (default configuration menu) before compilation starts
_makenconfig: Invokes make nconfig (nicer configuration menu) before compilation starts
_makexconfig: Invokes make xconfig (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
_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 write a comment
_subarch: Specifies the sub architecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 40 (Generic-x86-64), which is \compatible with all amd64 processors. Must be a number
_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.

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 in a simple manner and decrease build time. And if you don't want that, using makepkg as-is works fine too.

Kernel has been updated and is now maintained again.

Thank you metak for creating this package in the first place.

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

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?