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

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.

@bruceutut I'll try replicating this issue when I get some free time, but in the meantime, you could upload full build logs and the built 'bad' package somewhere for me to take a look.

@metak

Actually, I can build correct package using makepkg command. Or yay/pikaur something.

But the bad package using extra-x86_64-build command, on local machine or my building machine.

The bad package does not have crypto_user and xz compression module is not enabled as well.

Thanks for your patience :)

@bruceutut crypto_user should be built since this pkgbuild enables it. It's in /usr/lib/modules/4.20.6-1-clear/kernel/crypto/crypto_user.ko.xz, both on my local build and in clean chroot for repo.
Have you checked your build log? You haven't provided any info.

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?