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.

@metak Would you mind setting

NTFS3_FS=y
NTFS3_LZX_XPRESS=y
NTFS3_FS_POSIX_ACL=y

by default? Is there a specific reason NTFS3 is not enabled?

@metak Much thanks!

@xuanruiqi Thanks for pointing it out. I did applied those chnages in 5.7.2-1, but for some reason I removed them in subsequent commit? I'll add them back again and see.

There are some discrepancies with the upstream PKGBUILD that I see could use a fix.

For example,

echo "Stripping vmlinux..."
  strip -v $STRIP_STATIC "$builddir/vmlinux"

is missing (so vmlinux is not stripped, it seems).

Also, the upstream uses make all to build the kernel instead of make bzImage . The other difference I notice is the command used to install modules:

make INSTALL_MOD_PATH="$pkgdir/usr" INSTALL_MOD_STRIP=1 modules_install

in the upstream.

Thank you a lot for your work maintaining this package! It just seemed that the upstream PKGBUILD changed a bit in the mean time without getting noticed.

@xuanruiqi The package installation size is 64,83 MiB and for headers it's 127,95 MiB for binaries in my repo. Both are smaller in size than default kernel/headers packages. I try to keep my PKGBUILD files as close to upstream linux package as possible.

I just found that this package, when installed, is very large. On my system, for example, it is 666M in size, as opposed to 78M for the regular kernel. It seems that It seems that the blame is on:

/usr/lib/modules/5.14.12-1-clear/build/vmlinux

The reason seems to be that this file is not stripped, as is done in the official kernel. In addition, there are some more discrepancies between this package's PKGBUILD and the upstream linux PKGBUILD. I would like to recommend that the PKGBUILD be revised to match the upstream linux PKGBUILD.

@Gonzo2028 Add fsync/futex patches to sources in PKGBUILD file and build the package. You can get them at these two locations:

https://github.com/Frogging-Family/linux-tkg/tree/master/linux-tkg-patches/5.14

https://github.com/xanmod/linux-patches/tree/master/linux-5.14.y-xanmod/futex2

Can anyone tell me how to add the fsync-patch for/from steam?

@metak: I installed linux-clear-current (5.14.rc7). I reported here, not on linux-clear-current, sorry.

@guiodic Well arch kernel is already on 5.14 while this one is still on 5.13. If you can please try linux-clear-bin from my repo just so we can rule out any possible changes introduced in this pkgbuild?