Arch Linux User Repository

The PKGBUILD file supports a few different configurable build-time options:

• _makenconfig Tweak kernel options prior to a build via nconfig. Pseudo-graphical menu based on ncurses. 1 2
• _localmodcfg Only compile active modules to VASTLY reduce the number of modules built and the build time.
• Please read arch wiki page for detailed explanation on how to use it.
• _subarch Enable additional optimization/tuning for kernel builds by adding more micro-architectures options. Default is Generic-x86-64 number 36 if nothing else is selected.
• PKGBUILD file with the list of architectures
• graysky kernel_compiler_patch
• _use_current Use the current kernel's .config file. Enabling this option will use the .config of the RUNNING kernel rather than the ARCH defaults. Useful when the package gets updated and you already went through the trouble of customizing your config options. NOT recommended when a new kernel is released, but again, convenient for package bumps.
• _use_llvm_lto Compile the kernel with LLVM/Clang.
• _debug Enable y some additional debug features present in arch kernel, but not in Clear upstream. n to force disable or leave empty to ignore.

Lastly, build the kernel by setting your environment variable env _subarch=40 _localmodcfg=y.

1. Binaries available in my repo: http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/

[home_metakcahura_kernel_Arch_Extra_standard]
SigLevel = Never
Server = http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/$arch

THIS IS OPTIONAL:

2. After install adjust your boot cmd line. ClearLinux uses clr-boot-manager which takes care of that. This is upstream default:

quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check noreplace-smp page_alloc.shuffle=1 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs,f2fs tsc=reliable rw 

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

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 ??