Package Details: linux-clear 6.8.6-1

Git Clone URL: https://aur.archlinux.org/linux-clear.git (read-only, click to copy)
Package Base: linux-clear
Description: The Clear Linux kernel and modules
Upstream URL: https://github.com/clearlinux-pkgs/linux
Keywords: clear clearlinux intel kernel
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Submitter: metak
Maintainer: metak
Last Packager: metak
Votes: 71
Popularity: 1.88
First Submitted: 2018-01-18 21:47 (UTC)
Last Updated: 2024-04-13 16:57 (UTC)

Dependencies (12)

Required by (5)

Sources (5)

Pinned Comments

metak commented on 2022-03-27 13:44 (UTC) (edited on 2022-04-02 13:20 (UTC) by metak)

The PKGBUILD file supports a few different configurable build-time options:
  • _makenconfig Tweak kernel options prior to a build via nconfig. Pseudo-graphical menu based on ncurses. 1 2
  • _localmodcfg Only compile active modules to VASTLY reduce the number of modules built and the build time.
  • Please read arch wiki page for detailed explanation on how to use it.
  • _subarch Enable additional optimization/tuning for kernel builds by adding more micro-architectures options. Default is Generic-x86-64 number 36 if nothing else is selected.
  • PKGBUILD file with the list of architectures
  • graysky kernel_compiler_patch
  • _use_current Use the current kernel's .config file. Enabling this option will use the .config of the RUNNING kernel rather than the ARCH defaults. Useful when the package gets updated and you already went through the trouble of customizing your config options. NOT recommended when a new kernel is released, but again, convenient for package bumps.
  • _use_llvm_lto Compile the kernel with LLVM/Clang.
  • _debug Enable y some additional debug features present in arch kernel, but not in Clear upstream. n to force disable or leave empty to ignore.
Lastly, build the kernel by setting your environment variable env _subarch=40 _localmodcfg=y.

metak commented on 2018-01-22 01:49 (UTC) (edited on 2021-12-01 12:47 (UTC) by metak)

1. Binaries available in my repo: http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/x86_64/
[home_metakcahura_kernel_Arch_Extra_standard]
SigLevel = Never
Server = http://download.opensuse.org/repositories/home:/metakcahura:/kernel/Arch_Extra_standard/$arch
THIS IS OPTIONAL:
2. After install adjust your boot cmd line. ClearLinux uses clr-boot-manager which takes care of that. This is upstream default:
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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 47 Next › Last »

ZhangHua commented on 2023-06-18 04:47 (UTC) (edited on 2023-06-18 04:48 (UTC) by ZhangHua)

@metak There is not any improvement on performance, just following arch's name pattern. Take packages in official repo as examples, linux package is 6.3.8-arch1-1, linux-zen package is 6.3.8-zen1-1-zen,linux-rt package is 6.3.0.11.realtime1-1-rt, linux-hardened is 6.1.33-hardened1-1-hardened. So personally I think we can use 6.3.8-clear1-1 or 6.3.8-clear1-1-clear to also follow this pattern. But I don't mind either way too, so it just depends you if change this kernel release name.

metak commented on 2023-06-17 08:41 (UTC)

@k1gen Use 40 since llvm in arch repos is outdated and latest znver4 and emeraldrapids are not supported/detected unlike with gcc.

@ZhangHua What would be the benefit of that? I don't really mind either way...

seqfault commented on 2023-06-16 21:57 (UTC)

hey @metak, there's this weird bug I have with _subarch=44: I was using _subarch=40 before, but with 6.3.8 I decided to reread the PKGBUILD, and I saw that MNATIVE_INTEL option is now 44, and not 40. so I did env _localmodcfg=y _subarch=44 _use_current=y _use_llvm_lto=y _debug=n paru -S linux-clear linux-clear-headers, and makepkg gets stuck, looping over the choice[1-41?]: 44 part. so what _subarch do I need to define for MNATIVE_INTEL optimizations?

seqfault commented on 2023-06-16 17:30 (UTC)

@ZhangHua I personally like the current naming scheme more

ZhangHua commented on 2023-06-14 04:57 (UTC)

Can you consider using 6.x.x-clear1-1 as the kernel release name instead 6.x.x-1-clear? I think the former is more like archlinux's name pattern.

metak commented on 2023-05-12 13:05 (UTC) (edited on 2023-05-12 13:05 (UTC) by metak)

@Moviuro Create your custom .config file and next time you're updating minor release use _use_current?

Moviuro commented on 2023-05-07 09:43 (UTC)

Launching makepkg with the following options: _subarch=13 _localmodcfg=1 makepkg -sriCfc will consistently bug me about modules that I don't want, and this has been going on for at least a dozen releases, e.g.:

BT8XX GPIO abuser (GPIO_BT8XX) [N/m/y/?] (NEW)

I really just want to answer always NO to those, how do I do that?

metak commented on 2023-04-22 10:23 (UTC)

@Gonzo2028 The compiler patch 20230105 already has znver4, but you need gcc-13 or llvm-16 which are not available in repos. If you're building them yourself you should seen znver4 available for you to choose when it asks you for processor family.

Gonzo2028 commented on 2023-04-21 21:47 (UTC)

can you please add znver4? Thank you.

metak commented on 2023-04-21 19:50 (UTC)

@tydynrain NO_HZ section section of config file is the same as the default in arch kernel. Have you tried building it in clean chroot?

« First ‹ Previous 1 2 3 4 5 6 7 8 9 .. 47 Next › Last »