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 

d.e: I don't really know what you are meaning with "config changes [...] are not carried over". All config settings should be applied as make nconfig is the last statement executed in prepare() that is modifying the kernel configuration

But that "overwriting kernel-config options permanently" I can help you with. I am maintaining a personal fork of this package at https://git.staropensource.de/JeremyStarTM/kernel-optimized. Just pass the env variable _copyfinalconfig=y to the PKGBUILD or answer y in the handy buildtool.sh script. After the build completes, execute `mv kconfig-final kconfig" to replace the repository's kernel config with your own. From now on, your kernel config will be used for each future build.

Alternatively, you could modify the PKGBUILD and add that functionality to your own.

I hope that helps ;)

I would like to add kernel module signing, therefore I am following this article. - Would it be possible to integrate the required changes into the PKGBUILD file, maybe?

https://wiki.archlinux.org/title/Signed_kernel_modules

Thank you for the hint. - I have used that, but the config changes done by _makenconfig are not carried over. It is as if I didnt edit the config at all.

I have used _subarch to specify the architecture type, but I have to do that every time.

Is there a possibility to have a config file, where I can add options like _subarch permanently, and also overwrite permanently some kernel-config options?

Some permanent options would be very plesant to have.

d.e: You can modify the kernel config and the subarch by setting "_makenconfig" and "_subarch".

This is a good start, but I would like to be able to set some default .config options, without having to fiddle manually with the package. - Is that somehow possible?

Specifically I want to enable Landlock and Lockdown mode.

Also I have not found a way to set the _subarch by default. - Is there a way to preconfigure such options?

ls-alh: That's weird behaviour. I'm using the normal tmpfs size and it compiles without error. Maybe your tmpfs is filled with stuff before even starting the compilation process, try checking /tmp before compiling. Otherwise I don't know what could be causing this.

Building linux-clear has been failing since 6.8.10 due to filling up /tmp directory. I haven't changed anything about compiling between past successes and new failings. Since failures, I've tried increasing /tmp space from 5.8 GiB to 10 GiB to no avail. It still fills up. I don't use modprobed-db to reduce compile time/space. My system is otherwise up-to-date. Can someone help me debug this?

EDIT: After a successful git clone and `BUILDDIR=/Storage/tmp _subarch=24 makepkg', my otherwise empty /Storage/tmp is now 20GiB...

@odpuck

You need to install modprobed-db from air start the service and then when your compiling a kernel run as root modprobed-db command to load the list of modules to be used, also you have to modify PKBUILD a bit to be ready to accept modprobed.

I built this kernel a million times using modprobe and it only takes 10 minutes tops

oddpuck: I haven't tried using modprobed-db during kernel compilation yet, but maybe it compiles all modules first and then sorts them out during package().

I'll try compiling my custom kernel (which is based on this package) with modprobed-db enabled in a few days, maybe I can confirm my suspicion. I'll definitely post more info here in the coming days.