Well something really weird, now I can't boot even to rescue with linux-clear. Logs are clean but laptop seems to get stuck at last stage.
Search Criteria
Package Details: linux-clear-headers 6.12.6-1
Package Actions
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.50 |
First Submitted: | 2018-01-18 21:47 (UTC) |
Last Updated: | 2024-12-23 00:00 (UTC) |
Dependencies (12)
- pahole (pahole-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (make)
- git (git-gitAUR, git-glAUR) (make)
- libelf (elfutils-gitAUR) (make)
- pahole (pahole-gitAUR) (make)
- perl (perl-gitAUR) (make)
- python (python37AUR, python311AUR, python310AUR) (make)
- tar (tar-gitAUR, busybox-coreutilsAUR) (make)
- xz (xz-gitAUR) (make)
- zstd (zstd-gitAUR, zstd-staticAUR) (make)
Required by (0)
Sources (5)
Latest Comments
« First ‹ Previous 1 .. 45 46 47 48 49 50 51 52 Next › Last »
Osleg commented on 2018-04-20 21:17 (UTC)
metak commented on 2018-04-19 23:31 (UTC)
@Osleg Yes, the easier choice is to not use initrd /intel-ucode.img (clr default), otherwise the build would fail and require some adjustments/patching.
Osleg commented on 2018-04-19 19:40 (UTC)
Hm, I just realized that linux-clear also has ucode built in so we either should not initrd /intel-ucode.img or should not compile it with clear... I think first option is better to follow intel's kernel as close as possible.
Osleg commented on 2018-04-19 19:32 (UTC)
@metak unfortunately I have no idea. The boot process goes well until the end and it stuck when starting to load graphical.target. I could boot into single user mode but that doesn't help in any way :/
And yay for the module.sig_unenforce, will try that... in recovery mode tho :(
metak commented on 2018-04-12 18:21 (UTC) (edited on 2018-04-12 18:22 (UTC) by metak)
@Osleg Do you have any idea what might be the problem? Btw, clr-team introduced new patch in their latest commit called Add boot option to allow unsigned modules
so that's why I removed that sed line from pkgbuild.
+Add module.sig_unenforce boot parameter to allow loading unsigned kernel
+modules. Parameter is only effective if CONFIG_MODULE_SIG_FORCE is
+enabled and system is *not* SecureBooted.
https://github.com/clearlinux-pkgs/linux/commit/347ebb59a916a6fd112663d68e0b72623f6994f7
Osleg commented on 2018-04-12 07:21 (UTC)
Just to be exact, it stopped working even before update back when it was 4.15.15
Osleg commented on 2018-04-12 07:20 (UTC)
Have no idea what happened but the kernel stopped working for me. It reaches target graphical and then laptop hangs. :/
metak commented on 2018-04-07 14:21 (UTC)
@Osleg I disabled CONFIG_MODULE_SIG_FORCE by default and if anyone wants to turn it on just comment that line in pkgbuild.
Osleg commented on 2018-04-07 05:43 (UTC)
The main issue with modules not loading is that clear
has CONFIG_MODULE_SIG
and CONFIG_MODULE_SIG_FORCE
enabled.
Meaning most of the "custom" modules won't load.
The workaround that I'm using for that is to sign those modules manually as described here https://www.kernel.org/doc/html/v4.10/admin-guide/module-signing.html
Tho I think it might be a good idea to disable CONFIG_MODULE_SIG_FORCE or at least provide a config for PKGBUILD to disable it for those who want. as this setting is good for hardened kernel for servers and such. For desktop machines, especially for developers, this setting provides nothing but pain :)
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 thePKGBUILD
.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
: Invokesmake menuconfig
(ncurses-based default configuration menu) before compilation starts-
_makenconfig
: Invokesmake nconfig
(ncurses-based nicer configuration menu) before compilation starts-
_makexconfig
: Invokesmake 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 withIKCONFIG_PROC
-
_reuse_file
: Will use the configuration file namedkconfig
contained in thePKGBUILD
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 askconfig-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 thePKGBUILD
file for a list of all subarches). Default is41
(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 theGENERIC_CPU
subarch. Must be a number between1
and4
(click for more information)-
_debug_kernel
: Force enables kernel debugging options when set toy
, force disables debug options when set ton
or relies on the kconfig when unset-
_debug_script
: Enables debugging for thePKGBUILD
fileAll 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 thePKGBUILD
fileGPG 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.