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.

@metak it looks like this issue will be fixed in LVM2. I'm not sure why it only affects me on linux-clear, though...

@aorth Seems like this issue is already reported upstream. LVM Clearlinux takes a long time to shut down

@metak yeah I saw that thread. They seem to conclude that it's something related to LVM, and I am indeed using LVM on LUKS, though for me the issue only happens on linux-clear. The screen is black with a blinking cursor and eventually (maybe 90 seconds, I should actually time it) it says something about failing to unmount oldroot and then it reboots.

Edit: thanks @metak. I won't spam here anymore. Nice to know I'm not alone and that someone has even reported it upstream. For reference, here is the message that is spammed after the cursor blinks for ~90 seconds and it finally reboots:

[  116.123456] sd-umoun[1040]: Failed to unmount /oldroot: Device or resource busy
[  116.123456] sd-umoun[1041]: Failed to unmount /oldroot/dev: Device or resource busy
[  117.123457] reboot: Restarting system

@aorth Have you checked this thread? https://www.reddit.com/r/archlinux/comments/b6hbca/need_some_help_figuring_out_why_my_system_hangs/

Does anyone get a blinking cursor for about one minute on shutdown? It's the one annoying thing that causes me to stop running linux-clear. Not sure if it's a systemd job waiting or something...

@ltsdw Thanx. Seems like it's already fixed by clear team in 5.0.1-716.

@metak done!

@ltsdw Can you please report this issue upstream?

This was enabled on the config by the clear's devs, but this is causing a error message on boot:

kvm: already loaded the other module

According to gentoo's documentation this is due to both intel and amd kvm module beeing enabled on the kernel compiling CONFIG_KVM_AMD and CONFIG_KVM_INTEL:

https://wiki.gentoo.org/wiki/QEMU#.22kvm:_already_loaded_the_other_module.22

Recompiling the kernel only with respective module for my processor resolved problem. In my case CONFIG_KVM_INTEL

@phantomas 1. The upstream patches failed to apply because you tried to re-build the package without cleaning the src dir.
2. That part of the pkgbuild file is taken from linux-ck package. Every custom kernel in aur pretty much has it the same. I guess if you wanted you could change the line to yes "" | make localmodconfig for defaults.