Arch Linux User Repository

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
- _use_current: Will use the configuration of the running kernel, if the running kernel is compiled with IKCONFIG_PROC
- _optimize_defconfig: Applies package maintainer-picked configuration changes to your defconfig. Only takes effect with _use_current being enabled
- _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/MGENERIC_CPU (Generic x86-64), which is compatible with all amd64 processors. Must be a number or subarch name
- _subarch_microarch: Specifies the microarchitecture to compile for. Only applies to and is required by the MGENERIC_CPU subarch. Must be a number between 1 and 4 (click for more information)
- _debug: Force enables debug options when set to y, force disables debug options when set to n or uses the config defaults when unset
- _show_compile: Enables verbose-er compilation output and displays all executing make targets. Enabled by default, unset for 'pv' output

All of these variables just need to be set for them to apply, except for _subarch and _debug. 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.

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.

I must be doing something wrong. I have the db file from modprobed-db, and I put its path at line 18 in the PKGBUILD. It still starts building a bunch of amd drm stuff, at which point I kill the build, after ~19 minutes. CPU is an i7-12800H. Nvidia GPU

oddpuck: It only took about twenty minutes on my gaming hardware, with the "performance" cpu scheduler on the linux-lts kernel. Oh and I gave makepkg a nice level of -20.

oddpuck: update from 6.7.9 to 6.7.10 with env _use_current=y _subarch=44 _localmodcfg=y _debug=n paru -S linux-clear linux-clear-headers took exactly 14 minutes on an undervolted i5-8350U

How long does it normally take to build?

@NaNpsycho This package tracks Clear Linux kernel package that is still on 6.6.* series. When they rebase the patches and update to 6.7 so will this package.