it seems I have to use a workaround for this problem; by adding "SigLevel = Never" ...not the best solution but it works so I'm happy
about the "intel-ucode" thing, I didnt know/notice as I have skylake cpu so thankfully it hasn't affected me
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 the kernel and compiled modules. |
Upstream URL: | https://git.staropensource.de/JeremyStarTM/aur-linux-clear |
Keywords: | clear clearlinux intel kernel linux |
Licenses: | GPL-2.0-only |
Provides: | KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
Submitter: | metak |
Maintainer: | JeremyStarTM |
Last Packager: | JeremyStarTM |
Votes: | 74 |
Popularity: | 0.49 |
First Submitted: | 2018-01-18 21:47 (UTC) |
Last Updated: | 2025-04-04 21:08 (UTC) |
it seems I have to use a workaround for this problem; by adding "SigLevel = Never" ...not the best solution but it works so I'm happy
about the "intel-ucode" thing, I didnt know/notice as I have skylake cpu so thankfully it hasn't affected me
@ahjolinna I can't help with the repo since that is the limitation with archlinux support in opensuse build service. I reported that issue years ago. ;-) https://github.com/openSUSE/obs-build/issues/129 https://github.com/openSUSE/obs-build/issues/319 Basically, build service rebuilds packages even when that's not actually necessary and thus pkgver-pkgrel don't change but the package is now 'corrupt'. It's safe to just install it with pacman -U. Although, this kernel builds fast even on my old machine.
As for "intel-ucode", there's a bug opened, known issues, debian and redhat also reverted to that older version, and intel removed the 20180108 tarball from their site. https://bugs.archlinux.org/task/57067?project=1&string=intel-ucode
I think your repo is "broken" ...at least repo key (Remote key not fetched correctly from keyserver.) and same goes with the pkgs, I get "invalid or corrupted package (PGP signature)" when I tried to install them directly
PS. is there a reason why you are using the older "intel-ucode" pkgs compare to whats is in arch repos?
[home_metakcahura_kernel_Arch_Extra_standard]
SigLevel = Never
Server = http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/$arch
quiet console=tty0 console=ttyS0,115200n8 cryptomgr.notests initcall_debug intel_iommu=igfx_off kvm-intel.nested=1 no_timer_check noreplace-smp page_alloc.shuffle=1 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs,f2fs tsc=reliable rw
@OneObsession Sorry about that, copy/pasta wrong pkgbuild file. Fixed, but I didn't bumped the pkgrel.
Hi,
is there a reason why you changed "make ${MAKEFLAGS} LOCALVERSION= bzImage modules" to "make ARCH=x86_64 LOCALVERSION= CONFIG_DEBUG_SECTION_MISMATCH=y ${MAKEFLAGS}"? I think bzImage and modules should be kept.
It's not enabled in this kernel.
https://github.com/clearlinux-pkgs/linux/blob/2b74305ca208db647bc7ff1e1d4e64b337195975/config#L1939
Using llvm2 hook with this kernel reports following errors:
==> ERROR: module not found: `dm_cache'
==> ERROR: module not found: `dm_cache_smq'
Pinned Comments
JeremyStarTM commented on 2024-08-06 19:37 (UTC) (edited on 2025-02-03 12:44 (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-
_use_current
: Will use the configuration of the running kernel, if the running kernel is compiled withIKCONFIG_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 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 the PKGBUILD file for a list of all subarches). Default is41
/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 theMGENERIC_CPU
subarch. Must be a number between1
and4
(click for more information)-
_debug
: Force enables debug options when set toy
, force disables debug options when set ton
or uses the config defaults when unset-
_show_compile
: Enables verbose-er compilation output and displays all executingmake
targets. Enabled by default, unset for 'pv' outputAll 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 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.