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.

@danhyal I'm afraid that's not possible and it kinda defeats the purpose of this package IMO. I already added two patches (cpu optimizations and acs overrides) because they're small and don't change the kernel in radical way. On the other hand -ck patches are much bigger, touch many more files, change a bunch of existing config options, etc. There could also be clashes between -ck and -clear patches... Besides, this kernel is already optimized for desktop/laptop users so I don't really see a point?

Could you make a seperate package with the ck patchset applied? Since most people using this kernel are desktop/laptop users, it would be useful.

@danhyal 5.3.8-4 (clr 5.3.7-853) enable CONFIG_NETFILTER_INGRESS

Could you add the config option CONFIG_NETFILTER_INGRESS

Ah I am running mkinicpio 26 not 27 I will update. Thanks.

_----------- Yes everything is working now.

Thanks again for your time.

@dedguy21 I'm a bit confused as to what you want to achieve? You don't need to do 1) and 2). New version of mkinitcpio=27-1 includes hook and preset files so that not every kernel package has to provide them. Just build this package as any other or use the binaries provided in my repo.

@ metak Apologies for the possible noobie questions....

I have the linux-clear kernel in the /usr/lib/module folder.

1) How can I write the proper compressed image to the /boot folder 2) and the .preset files to the mkinitcpio.d folder

I used yay for installation, should I just git files and run make install?

@dedguy21 Hello. linux-clear package is the "main" kernel, it's the default kernel in clearlinux and clear team focuses the most on it. With that said, linux-clear-current is used mostly for testing purposes when kernel nears towards the latest release candidates (and first .0 release and .1 sometimes) then clear team rebase their patches and test this new kernel. These patches are then moved to linux-clear when everything seems ok. After that they don't update the linux-clear-current much, it's stuck on 5.3.1 and I expect it will get updated with 5.4rc7? I don't know. The kernel .config file is pretty much the same as they try to sync changes between their kernels, the exception being patch for exfat patch and some crypto modules that were introduced in linux-clear.

Yes, I'm maintaining both of them and as you can see they're two separate packages and neither is being abandoned. Use linux-clear and later in kernel development cycle if you want to test the latest rc then try linux-clear-current.

I follow stock arch's kernel way of packaging and those changes were brought by 5.3.8.1-1: Changes for new kmod and mkinitcpio hooks.

First of all I wanted to say thanks for the Clear Linux packages. I always thought if you could marry their kernel with Arch you would have the perfect distro.

So wondering why does linux-clear package has a kernel number higher than linux-clear-current package?

And are you maintaining both packages separately? Or is one being abandoned for the other?

Also, when I install this package, I notice that there isn't an image for this created to the /boot or any .preset in mkinitcpio.d

I located the file in /usr/lib/module

...just wondering if this was done on purpose on your end.

Thanks again