Arch Linux User Repository

Important update
I have updated and renamed some settings envvars. Please check your scripts, aliases, brain memory or whatever you use to store your build command and update them accordingly. Please read the description in the PKGBUILD file instead of the short summary in the pinned comment on the AUR or in the README in the repository as some important details important to this update are only found inside the PKGBUILD.

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

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. This prevents unnecessary signups.

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.

PKGBUILD environment variable customization
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
- _reuse_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _reuse_file: Will use the configuration file named kconfig contained in the PKGBUILD file's directory
- _update_kconfig_on_reuse: Specifies whether the kernel configuration shall be updated when using any of the 'reuse*' flags
- _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 open an issue
- _subarch: Specifies the subarchitecture to compile for (see the PKGBUILD file for a list of all subarches). Default is 41 (Generic x86-64), which is compatible with all amd64 processors. Must be a number
- _use_llvm_lto: Enables compilation with LLVM. Untested but should work. If not write a comment on the AUR.
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the GENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug_kernel: Force enables kernel debugging options when set to y, force disables debug options when set to n or relies on the kconfig when unset
- _debug_script: Enables debugging for the PKGBUILD file

All of these variables just need to be set for them to apply, except for _subarch, _subarch_microarch and _debug_kernel. For more information please check their documentation inside the PKGBUILD file

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.

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.

OK, I figured out the problem is LLVM LTO. It's broken on this version. If you're using it, maybe it's wise to disable for the time being.

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