Arch Linux User Repository

Proposal update
The package has been updated to 6.11.7 (clr 6.11.6-1477), and with that landlock support has been enabled the package source moved to https://git.staropensource.de/JeremyStarTM/linux-clear.

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

Repository URL
This package is hosted at sos!git. If you want to contribute to the package, you can do it here: https://git.staropensource.de/JeremyStarTM/aur-linux-clear

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 file supports customization via environment variables. Here's a list of all of them:
_makemenuconfig: Invokes make menuconfig (ncurses-based default configuration menu) before compilation starts
_makenconfig: Invokes make nconfig (ncurses-based nicer configuration menu) before compilation starts
_makexconfig: Invokes make xconfig (X11-based 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.

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

Issue handling
Please only submit issues in the package's repository if they aren't bug reports about the package or help requests. Please keep them to the AUR only. Tihs prevents unnecessary signups.

Build tool
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 file in a simple manner and decrease build time. And if you don't want that, using makepkg as-is works fine too.

hey @metak, there's this weird bug I have with _subarch=44: I was using _subarch=40 before, but with 6.3.8 I decided to reread the PKGBUILD, and I saw that MNATIVE_INTEL option is now 44, and not 40. so I did env _localmodcfg=y _subarch=44 _use_current=y _use_llvm_lto=y _debug=n paru -S linux-clear linux-clear-headers, and makepkg gets stuck, looping over the choice[1-41?]: 44 part. so what _subarch do I need to define for MNATIVE_INTEL optimizations?

@ZhangHua I personally like the current naming scheme more

Can you consider using 6.x.x-clear1-1 as the kernel release name instead 6.x.x-1-clear? I think the former is more like archlinux's name pattern.

@Moviuro Create your custom .config file and next time you're updating minor release use _use_current?

Launching makepkg with the following options: _subarch=13 _localmodcfg=1 makepkg -sriCfc will consistently bug me about modules that I don't want, and this has been going on for at least a dozen releases, e.g.:

BT8XX GPIO abuser (GPIO_BT8XX) [N/m/y/?] (NEW)

I really just want to answer always NO to those, how do I do that?

@Gonzo2028 The compiler patch 20230105 already has znver4, but you need gcc-13 or llvm-16 which are not available in repos. If you're building them yourself you should seen znver4 available for you to choose when it asks you for processor family.

can you please add znver4? Thank you.

@tydynrain NO_HZ section section of config file is the same as the default in arch kernel. Have you tried building it in clean chroot?

I was finally able to get 6.2.10-1 to build successfully, after many tries and lots of experimentation. By disabling CONFIG_NO_HZ in the timer subsystem section the error that I posted in my previous comment no longer appears and the kernel builds fine.

This kernel usually builds fine, now it's failing with the following error:

CC arch/x86/kernel/cpu/intel_epb.o

arch/x86/kernel/cpu/intel_epb.c:171:2: error: call to undeclared function 'sched_set_itmt_power_ratio'; ISO C99 and later do not support implicit function declarations [-Werror,-Wimplicit-function-declaration] sched_set_itmt_power_ratio(256 - val * 2, cpu); ^ arch/x86/kernel/cpu/intel_epb.c:171:2: note: did you mean 'sched_set_itmt_core_prio'?

./arch/x86/include/asm/topology.h:189:20: note: 'sched_set_itmt_core_prio' declared here static inline void sched_set_itmt_core_prio(int prio, int core_cpu) ^ 1 error generated.

make[4]: *** [scripts/Makefile.build:252: arch/x86/kernel/cpu/intel_epb.o] Error 1

make[3]: *** [scripts/Makefile.build:504: arch/x86/kernel/cpu] Error 2

make[2]: *** [scripts/Makefile.build:504: arch/x86/kernel] Error 2

make[1]: *** [scripts/Makefile.build:504: arch/x86] Error 2

make: *** [Makefile:2021: .] Error 2

==> ERROR: A failure occurred in build().

Aborting...