Package Details: linux-clear-headers 6.12.6-1

Git Clone URL: https://aur.archlinux.org/linux-clear.git (read-only, click to copy)
Package Base: linux-clear
Description: Linux kernel with patches from Clear Linux which allow for higher performance. This package includes header files and scripts for building kernel modules.
Upstream URL: https://git.staropensource.de/JeremyStarTM/aur-linux-clear
Keywords: clear clearlinux intel kernel linux
Licenses: GPL-2.0-only
Submitter: metak
Maintainer: JeremyStarTM
Last Packager: JeremyStarTM
Votes: 73
Popularity: 0.52
First Submitted: 2018-01-18 21:47 (UTC)
Last Updated: 2024-12-23 00:00 (UTC)

Pinned Comments

JeremyStarTM commented on 2024-12-22 18:24 (UTC) (edited on 2024-12-22 18:24 (UTC) by JeremyStarTM)

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.

JeremyStarTM commented on 2024-08-06 19:37 (UTC) (edited on 2024-12-22 18:20 (UTC) by JeremyStarTM)

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.

Latest Comments

« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 52 Next › Last »

tam1m commented on 2019-10-30 14:09 (UTC) (edited on 2019-10-30 14:09 (UTC) by tam1m)

@metak Ok I didn't know that /usr/lib/modules/<kernel>/build/.config existed. Copying it to another location seems unnecessary, especially since /usr/lib/kernel/.config would nowhere be mentioned in the "Arch World". CONFIG_IKCONFIG is at least enabled by default in arch's linux package. That's why I thought it would be nice to have it in linux-clear, too.

metak commented on 2019-10-30 13:55 (UTC)

@tam1m That's just a packaging difference. In arch kernel there's a copy of kernel config file in -headers package. /usr/lib/modules/<kernel>/build/.config
I can add a line that copies config file like it's in clearlinux package along with enabling ikconfig.

tam1m commented on 2019-10-30 13:41 (UTC) (edited on 2019-10-30 13:42 (UTC) by tam1m)

@metak Sounds good to me. Having it as a module should be enough. Also regarding this comment from the issue tracker, we don't have the /usr/lib/kernel file. At least I don't..

metak commented on 2019-10-30 12:27 (UTC)

@tam1m With next update I can enable CONFIG_IKCONFIG=m (as a module) and CONFIG_IKCONFIG_PROC=y? This was already brought up upstream on ClearLinux issue tracker and they decided not to enable it because not many people use this and it wastes more memory.

niklaszantner commented on 2019-10-30 12:10 (UTC)

@metak

You were right, thanks a lot!

tam1m commented on 2019-10-30 12:07 (UTC) (edited on 2019-10-30 12:07 (UTC) by tam1m)

I think it would be good to enable CONFIG_IKCONFIG_PROC/CONFIG_IKCONFIG by default. Is that something you would consider?

metak commented on 2019-10-30 11:24 (UTC)

@niklaszantner Do you have sha256 and sha512 modules listed in MODULES=() in /etc/mkinitcpio.conf? If you do, try removing them as they're built into the kernel.

niklaszantner commented on 2019-10-30 11:01 (UTC) (edited on 2019-10-30 11:02 (UTC) by niklaszantner)

Am I the only one who gets the following errors past build on install:

  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
  -> Running build hook: [resume]
  -> Running build hook: [filesystems]
  -> Running build hook: [fsck]
==> ERROR: module not found: `sha256'
==> ERROR: module not found: `sha512'
==> Generating module dependencies
==> Creating gzip-compressed initcpio image: /boot/initramfs-linux-clear-fallback.img
==> WARNING: errors were encountered during the build. The image may not be complete.
error: command failed to execute correctly

wan109020 commented on 2019-10-26 15:57 (UTC)

@metak Big thanks for adding them to the package. Can now set kernel.yama.ptrace_scope=1 and apparmor is working properly. No issues encountered so far.

metak commented on 2019-10-26 14:12 (UTC)

@wan109020 In 5.3.7-3, I've enabled Yama, Apparmor, SELinux and TOMOYO security options just like in stock arch kernel. Please test and report.