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 

@xuanruiqi Have you tried compiling with SYSFB_SIMPLEFB disabled?

After update to 5.17.3-clear, I have the weird problem that I can't get my screen to initialize anymore. I don't have this problem with the stock Arch kernel. Tried a lot of reconfigurations and recompilations, but still I get stuck on:

fb0 switching to i915 from efi vga

every boot. I wonder if anyone is able to reproduce this at all...

@FiestaLake #Patch0110 is already commented in spec file so it's skipped, but I had to manually disable raid6.patch because spec file only commented rpm macro part #%patch0129 and forgot patch source line.

@metak Shouldn't you also remove patch0110? It's commented on linux5.17 update now.

EDIT: I guess it's not getting applied now.

@metak You'd better just leave the option for some people that requested a option of the entire debug flags enabled other than him.

@rayzorben tho @metak won't add the option for it, you can easily edit PKGBUILD to add an extra option for it. Just look through the PKGBUILD to see how the system works.

@FiestaLake I get it now. Thanks. But, as you've already pointed out using _use_current on stock arch kernel will get you way more extra options. Pretty much you're on your own then. Not supported.

My main question is still should I just remove the _debug option completely from PKGBUILD file? Does anyone find it useful? And, with next update I'll just apply change mentioned bellow for resolve_btfids.
If anyone has DEBUG_INFO_BTF_MODULES enabled and resolve file is generated, it will be installed.

@rayzorben But you have to notice that _use_current is intended to be passed in the environment booted with this clear kernel, not the arch kernel.

_use_current: Use the current kernel's .config file. Enabling this option will use the .config of the RUNNING kernel rather than enabling some arch kernel's configs on the top of the clear's default. 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.

@metak I think you can just add a _no_debug option that disables debug configs.

What he wanted to say is that when we build the kernel using the arch kernel's config (by passing _use_current in the env booted with the arch kernel), debug configs are enabled whether _debug is passed or not (I guess).

@metak i'm honestly not sure. I was just thinking I want those debug flags off even if arch has them on, so I would like to just do _debug=n and have it turn those kernel flags off.

@rayzorben If I'm getting this right then I should just remove the debug option and just check in PKGBUILD file for resolve_btfids if the file exists & install it? (not native English speaker)

    # required when DEBUG_INFO_BTF_MODULES is enabled
    if [ -f tools/bpf/resolve_btfids/resolve_btfids ]; then
        install -Dt "$builddir/tools/bpf/resolve_btfids" tools/bpf/resolve_btfids/resolve_btfids
    fi