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.

crypto_user module not found in package after successful build.
Anything am i doing wrong ?

@metak Yes, after turbo3 patch is removed the package can be built again. :) I have also left this comment in the github.

@enihcam That's probably due to the patch turbo3-scheduler.patch in latest commit. No problems on my machine or in repo build. You can try building with that patch disabled to check?

ld: kernel/sched/fair.o: in function select_task_rq_fair': fair.c:(.text+0x61a): undefined reference tobest_core' ld: fair.c:(.text+0x628): undefined reference to `second_best_core' make[1]: [Makefile:1032: vmlinux] Error 1 make: [Makefile:1001: autoksyms_recursive] Error 2 ==> ERROR: A failure occurred in build(). Aborting... ==> ERROR: Makepkg was unable to build linux-clear. ==> Restart building linux-clear ? [y/N] ==> ------------------------------------

4.19.3-1 has no such problem.

this is not related with the package, but I like to update my problem with module that was resolved after recompile the kernel habilitating preemption. Again, thanks.

@metak Yeah, I have module.sig_unenforce as boot parameter... anyway much obliged.

@ltsdw What you described sounds more like an issue with yay than this package. The package is properly built and you can manually install the binary.

Edit: as for your edit, have you checked the third point in the sticky comment for dkms modules?

@metak so, everything seems be 'ok', nothing appears when I was compiling, none error, the only thing that differs the linux-headers builded from aur (my cached headers from build 19917744) is the size from that one on your repo (19404108). The log build says that installing headers, but when I tried install something for example, whit dkms, says "Your kernel headers for kernel 4.19.2-2-clear cannot be found" so I have to install manually or from my cache or from your binary. (I don't know if it matters but I'm using yay)

Edit: I think this is not related to the package itself, but look what @iwfinger said on this issue that I opened on github:

"Your kernel headers and the compiler version MUST match exactly. "SMP mod_unload" is not the same as "SMP preempt mod_unload". I have never seen this problem as most of my kernels are self-generated, which sidesteps this problem. I'm not sure how to fix it."

You can check on this link: https://github.com/lwfinger/rtl8188eu/issues/270

Do you have idea what can I do?

@ltsdw Sorry for late reply. I couldn't reproduce your issue. The package builds fine on my machine and in clean chroot. You'll have to provide more details. Build logs etc.
Have you compared the headers package from my repo with your built binary for differences to make sure your built package is okay?

And every module that I tried install I get something like this for example:

[ 2725.823458] 8188eu: version magic '4.19.2-2-clear SMP mod_unload ' should be '4.19.2-2-clear SMP preempt mod_unload '