Search Criteria
Package Details: linux-ck 6.11.8-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/linux-ck.git (read-only, click to copy) |
---|---|
Package Base: | linux-ck |
Description: | The Linux kernel and modules with ck's hrtimer patches |
Upstream URL: | https://wiki.archlinux.org/index.php/Linux-ck |
Licenses: | GPL-2.0-only |
Provides: | KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE |
Replaces: | virtualbox-guest-modules-arch, wireguard-arch |
Submitter: | graysky |
Maintainer: | graysky |
Last Packager: | graysky |
Votes: | 459 |
Popularity: | 0.25 |
First Submitted: | 2011-07-22 14:51 (UTC) |
Last Updated: | 2024-11-15 22:31 (UTC) |
Dependencies (14)
- coreutils (coreutils-gitAUR, busybox-coreutilsAUR, coreutils-hybrid-gitAUR, coreutils-hybridAUR, coreutils-selinuxAUR, coreutils-uutilsAUR)
- initramfs (booster-gitAUR, booster-wip-gitAUR, mkinitcpio-gitAUR, dracut-gitAUR, booster, dracut, mkinitcpio)
- kmod (busybox-coreutilsAUR, kmod-gitAUR)
- bc (bc-ghAUR) (make)
- cpio (cpio-gitAUR) (make)
- gettext (gettext-gitAUR) (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)
- linux-firmware (linux-libre-firmwareAUR, linux-firmware-xzAUR, linux-firmware-amd-staging-um5606-gitAUR, linux-firmware-uncompressedAUR, linux-firmware-gitAUR) (optional) – firmware images needed for some devices
- wireless-regdb (optional) – to set the correct wireless channels of your country
Required by (6)
- ksmbd-tools (requires KSMBD-MODULE)
- linux-ck-headers
- piavpn-bin (requires WIREGUARD-MODULE) (optional)
- piavpn-manual-git (requires WIREGUARD-MODULE)
- virtualbox-guest-utils-nox-svn (requires VIRTUALBOX-GUEST-MODULES)
- virtualbox-guest-utils-svn (requires VIRTUALBOX-GUEST-MODULES)
Sources (6)
- ck-hrtimer-7bdeefd29a299f812f1d14ef7ef46bdb32ed5b6d.tar.gz
- config
- https://github.com/archlinux/linux/releases/download/v6.11.8-arch1/linux-v6.11.8-arch1.patch.zst
- https://www.kernel.org/pub/linux/kernel/v6.x/linux-6.11.8.tar.sign
- https://www.kernel.org/pub/linux/kernel/v6.x/linux-6.11.8.tar.xz
- more-uarches-20241018.tar.gz
Latest Comments
« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 307 Next › Last »
Kr1ss commented on 2019-02-16 17:59 (UTC)
Yep, me too :
zerophase commented on 2019-02-16 17:54 (UTC)
Is 4.20.10 giving anyone else compile errors?
gee commented on 2019-02-15 09:29 (UTC)
It probably is out of focus, but it would be really nice to add this patchset: https://lists.ubuntu.com/archives/kernel-team/2019-January/098018.html
My boot takes 2 sec to test various raid6 algorithms, when I don't even use raid... Being able to specify the algorithm to use would shave that time off and be awesome.
air-g4p commented on 2019-01-17 07:23 (UTC)
@graysky,
Thanks for pointing out my non-Arch standard settings and I forgot there was a new /etc/makepkg.conf.pacnew hanging about. I'm back to standard now.
I see you removed 'subarch 27' from PKGBUILD, and now as expected, linux-ck-4.20.3-1-x86_64.pkg.tar.xz and its headers build without issue.
graysky commented on 2019-01-17 00:50 (UTC)
@air-g4p - As well, your CFLAGS are not the Arch standard... drop
-fstack-protector-strong
per the new makepkg.conf in pacman-5.1.2-2.graysky commented on 2019-01-16 21:07 (UTC) (edited on 2019-01-17 00:51 (UTC) by graysky)
@air-g4p - See the comments in the PKGBUILD and the discussion here in the AUR.
In short, I do not know how to allow the native option to get set via the method used for the other discretely defined options.
air-g4p commented on 2019-01-16 20:35 (UTC)
@graysky,
I'm running an i7 8550U.
Under both /etc/makepkg.conf and ~/chroot/root/etc/makepkg.conf, I have these identical settings:
ARCHITECTURE, COMPILE FLAGS
CARCH="x86_64" CHOST="x86_64-pc-linux-gnu"
-- Compiler and Linker Flags
CPPFLAGS="-D_FORTIFY_SOURCE=2" CFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" CXXFLAGS="-march=native -O2 -pipe -fstack-protector-strong -fno-plt" LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
-- Make Flags: change this for DistCC/SMP systems
MAKEFLAGS="-j8"
-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments" DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"
Is there anything you see in my setup that would drive:
'The build fails with hundreds of instances of:
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 27'
that I mentioned when '_subarch=27' is set?
I normally build linux-ck in a clean chroot without issue, but this infinite loop issue disturbs me.
graysky commented on 2019-01-13 12:11 (UTC)
I remember looking at this a while ago and concluding it isn't possible... prove me wrong :)
air-g4p commented on 2019-01-13 09:37 (UTC)
Hi graysky,
I can confirm the build loop issue zoopp mentioned last month is still present in linux-ck 4.20.1-1.
With this PKGBUILD option set:
27. Native optimizations autodetected by GCC (MNATIVE)
_subarch=27
The build fails with hundreds of instances of:
Support for P6_NOPs on Intel chips (X86_P6_NOP) [N/y/?] (NEW) 27
It appears to me that the only way out of this loop is crtl-c.
Of course, the build proceeds normally with any other appropriate subarch assigned.
graysky commented on 2019-01-12 09:38 (UTC)
@artafinde - ck1 disables NUMA
« First ‹ Previous 1 .. 29 30 31 32 33 34 35 36 37 38 39 .. 307 Next › Last »