Arch Linux User Repository

Proposal update
As I have recently announced, I proposed moving this package's source to my own Forgejo (git forge) instance and creating a push mirror to the AUR. As I haven't received any feedback on the proposal, I will be moving forward and move the repository in the next package update. Again, nothing should change, just where the changes are pushed to. I hope that this change will provide an easier way of contributing (AFAIK there isn't a way to contribute to a package directly or I'm just dumb).

Information comment
This comment provides useful information about this package. Make sure to read it through, you won't regret it.

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.

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. See their descriptions for more information.

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.

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 only needs to be done once.

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

Weird, now the patch suceeds. The kconfig is not fully automated since it is asking for: Studio Evolution SE6X (SND_SE6X) [N/m/?] (NEW)

Has anybody else successfully built the 4.20.12 kernel?

For me it fails somewhere in "Add upstream patches":

tools/arch/riscv/include/uapi/asm/bitsperlong.h already exists!

[...] patching file sound/usb/card.c patching file sound/usb/mixer.c patching file sound/usb/pcm.c patching file sound/usb/quirks-table.h patching file sound/usb/quirks.c patching file sound/usb/stream.c The next patch would create the file tools/arch/riscv/include/uapi/asm/bitsperlong.h, which already exists! Skipping patch. 1 out of 1 hunk ignored patching file tools/bpf/bpftool/common.c patching file tools/bpf/bpftool/json_writer.c patching file tools/bpf/bpftool/map.c patching file tools/bpf/bpftool/prog.c patching file tools/bpf/bpftool/xlated_dumper.c patching file tools/build/Makefile.feature patching file tools/build/feature/Makefile patching file tools/hv/hv_kvp_daemon.c patching file tools/iio/iio_generic_buffer.c patching file tools/include/uapi/asm/bitsperlong.h patching file tools/lib/bpf/bpf.c patching file tools/lib/subcmd/Makefile patching file tools/lib/traceevent/event-parse.c patching file tools/perf/Makefile.config patching file tools/perf/arch/common.c patching file tools/perf/arch/common.h patching file tools/perf/arch/x86/util/intel-pt.c patching file tools/perf/arch/x86/util/kvm-stat.c patching file tools/perf/builtin-script.c patching file tools/perf/builtin-stat.c patching file tools/perf/builtin-timechart.c patching file tools/perf/pmu-events/arch/x86/skylake/skl-metrics.json patching file tools/perf/pmu-events/arch/x86/skylakex/skx-metrics.json patching file tools/perf/tests/attr.py patching file tools/perf/tests/bp_signal.c patching file tools/perf/tests/evsel-tp-sched.c patching file tools/perf/tests/shell/lib/probe_vfs_getname.sh patching file tools/perf/util/callchain.c patching file tools/perf/util/callchain.h patching file tools/perf/util/cs-etm.c patching file tools/perf/util/dso.c patching file tools/perf/util/env.c patching file tools/perf/util/event.c patching file tools/perf/util/evlist.c patching file tools/perf/util/header.c patching file tools/perf/util/machine.c patching file tools/perf/util/machine.h patching file tools/perf/util/parse-events.c patching file tools/perf/util/pmu.c patching file tools/perf/util/probe-file.c patching file tools/perf/util/python.c patching file tools/perf/util/s390-cpumsf.c patching file tools/perf/util/scripting-engines/trace-event-python.c patching file tools/perf/util/session.c patching file tools/perf/util/stat-display.c patching file tools/perf/util/svghelper.c patching file tools/perf/util/thread.h patching file tools/power/x86/intel_pstate_tracer/intel_pstate_tracer.py patching file tools/testing/nvdimm/test/iomap.c patching file tools/testing/selftests/Makefile patching file tools/testing/selftests/android/Makefile patching file tools/testing/selftests/bpf/Makefile patching file tools/testing/selftests/bpf/test_libbpf.sh patching file tools/testing/selftests/bpf/test_progs.c patching file tools/testing/selftests/bpf/test_verifier.c patching file tools/testing/selftests/drivers/dma-buf/Makefile patching file tools/testing/selftests/drivers/dma-buf/udmabuf.c patching file tools/testing/selftests/futex/functional/Makefile patching file tools/testing/selftests/gpio/Makefile patching file tools/testing/selftests/kselftest_harness.h patching file tools/testing/selftests/kvm/Makefile patching file tools/testing/selftests/kvm/x86_64/evmcs_test.c patching file tools/testing/selftests/kvm/x86_64/state_test.c patching file tools/testing/selftests/lib.mk patching file tools/testing/selftests/networking/timestamping/Makefile patching file tools/testing/selftests/seccomp/seccomp_bpf.c patching file tools/testing/selftests/tc-testing/bpf/Makefile patching file tools/testing/selftests/vm/Makefile patching file tools/testing/selftests/x86/protection_keys.c patching file virt/kvm/arm/arm.c patching file virt/kvm/arm/mmio.c patching file virt/kvm/arm/vgic/vgic-mmio.c patching file virt/kvm/arm/vgic/vgic.c patching file virt/kvm/kvm_main.c

Load all the modules that you want eg. modprobe loop, and then run modprobed-db store to create a list of loaded modules.
If you're building this package on top of default arch kernel you have to load loop module first since it's not built into the kernel like with this clear kernel.

@metak Thanks and sorry for my ignorance. I would like to manually add the "loop" module since I would have to reboot to enforce it.

@phantomas Just set it to _localmodcfg=y and that should be it. https://wiki.archlinux.org/index.php/Modprobed-db

What should I enter at localmodcfg?

I would like to use modprobed-db, so

_localmodcfg=~/.config/modprobed-db.conf ??

I tried and seems that it doesn't break anything.

@xuanruiqi You can try it if you want. If you followed the instructions in my pinned comment and it still for some reason doesn't work you can still just reboot to default kernel. It shouldn't break anything.

Thinking about installing this, but wanted to confirm that the extra boot parameters won't break other installed kernels.