Package Details: linux-ck 6.11.8-1

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)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 307 Next › Last »

laenco commented on 2019-10-30 21:51 (UTC) (edited on 2019-10-30 21:53 (UTC) by laenco)

@kwe could you check ~/.config/modprobed.db for presence of "fou"/"fou6" modules?

The question is "If localmodconfig is unable to detect fou or is it a modprobed-db detection problem"?.

kwe commented on 2019-10-30 21:28 (UTC)

@graysky I am building linux-ck with modprobed-db, and for some reason, I always end up with those configuration options being disabled. I have to re-enable them manually every single time.

graysky commented on 2019-10-30 20:11 (UTC) 

% uname -r
5.3.8-1-ck

% zgrep CONFIG_NET_FOU /proc/config.gz
CONFIG_NET_FOU=m
CONFIG_NET_FOU_IP_TUNNELS=y

Should be there as a module. Building wireguard-dkms on CK works for me:

# pacman -S wireguard-dkms
resolving dependencies...
looking for conflicting packages...

Packages (2) dkms-2.7.1-1  wireguard-dkms-0.0.20191012-1

Total Download Size:   0.24 MiB
Total Installed Size:  1.75 MiB

:: Proceed with installation? [Y/n] 
:: Retrieving packages...
 wireguard-dkms-0.0.20191012-1-x86_64            245.7 KiB  3.43 MiB/s 00:00 [############################################] 100%
(2/2) checking keys in keyring                                               [############################################] 100%
(2/2) checking package integrity                                             [############################################] 100%
(2/2) loading package files                                                  [############################################] 100%
(2/2) checking for file conflicts                                            [############################################] 100%
:: Processing package changes...
(1/2) installing dkms                                                        [############################################] 100%
Optional dependencies for dkms
    linux-headers: build modules against the Arch kernel [installed]
    linux-lts-headers: build modules against the LTS kernel
    linux-zen-headers: build modules against the ZEN kernel
    linux-hardened-headers: build modules against the HARDENED kernel
(2/2) installing wireguard-dkms                                              [############################################] 100%
:: Running post-transaction hooks...
(1/2) Arming ConditionNeedsUpdate...
(2/2) Install DKMS modules
==> dkms install wireguard/0.0.20191012 -k 5.3.7-arch1-2-ARCH
==> dkms install wireguard/0.0.20191012 -k 5.3.8-1-ck

Kr1ss commented on 2019-10-30 19:41 (UTC)

FWIW, I'm also setting that option manually, hence I'd support @air-g4p's request. Thx again for maintaining this btw !

Cheers !

air-g4p commented on 2019-10-30 19:36 (UTC)

@graysky - wireguard-dkms failed to build on CK with this output:

http://ix.io/20kT

I asked the devs at #wireguard about this failure, and was told I needed to enable: CONFIG_NET_FOU

(FOU = foo over udp)

After enabling that and rebuilding linux-ck --> Success.

Per Jason's (zx2c4), the lead wireguard dev, suggestion, can you please enable CONFIG_NET_FOU by default on linux-ck?

Thanks graysky

graysky commented on 2019-10-27 14:46 (UTC) (edited on 2019-10-29 20:42 (UTC) by graysky)

@timo - OK... that is likely because your .config got tweaked due to your CC= line. I opened a flyspray shown below. See it for a solution: https://bugs.archlinux.org/task/64315

timo_capa commented on 2019-10-27 14:03 (UTC)

@graysky What I did was add CC=clang before make in the PKGBUILD to use Clang as compiler.

What worked was using makepkg for compiling till it gets stuck, and then end it with make modules_install and make install from the src folder. Doesn't give a package for pacman, but works.

I've tried linux-pf the same way, though that got stuck at the same place :)

graysky commented on 2019-10-27 12:34 (UTC)

@simona - the recent failure of dkms is due to the fact that there are both a newer version of the toolchain and of the dkms packages in [testing] currently. The advice I have been given is that it always a good idea to build the kernel against [testing] to prevent version mismatch errors when toolchain packages come out of [testing] and into [core].

I need to figure out what the best option is now.

@timo_capa - I am not sure how you go about building in Clang... I am using the official Arch devtools for clean chroot building. Are you patching the kernel source with ck1?

simona commented on 2019-10-27 11:52 (UTC)

==> dkms install vboxhost/6.0.14_OSE -k 5.3.7-1-ck-skylake Error! Bad return status for module build on kernel: 5.3.7-1-ck-skylake (x86_64)

« First ‹ Previous 1 .. 22 23 24 25 26 27 28 29 30 31 32 .. 307 Next › Last »