Package Details: linux-ck 4.17.11-6

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only)
Package Base: linux-ck
Description: The Linux-ck kernel and modules with the ck1 patchset featuring MuQSS CPU scheduler v0.172
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL2
Provides: linux-ck=4.17.11
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 387
Popularity: 3.252935
First Submitted: 2011-07-22 14:51
Last Updated: 2018-08-14 15:42

Pinned Comments

graysky commented on 2018-08-04 11:26

I am unable to patch into 4.17.12+ due to changes upstream... need to fix before updating the PKGBUILD:

Hunk #1 FAILED at 185.
Hunk #2 succeeded at 473 (offset -1 lines).
1 out of 2 hunks FAILED -- saving rejects to file
kernel/sched/cpufreq_schedutil.c.rej

Latest Comments

1 2 3 4 5 6 ... Next › Last »

Jeffrey4l commented on 2018-08-16 04:36

Could you enable

CONFIG_CGROUP_CPUACCT=y

in config in default?

This is need for docker stats and systemd-cgtop

sir_lucjan commented on 2018-08-14 20:47

@simona:

https://aur.archlinux.org/cgit/aur.git/commit/?h=linux-ck&id=7574ccd5abcc

simona commented on 2018-08-14 20:40

4.17.11-6 ? what change?

keepitsimpleengr commented on 2018-08-13 16:17

:: installing nvidia-utils (396.51-1) breaks dependency 'nvidia-utils=396.45' required by nvidia-ck-sandybridge

simona commented on 2018-08-11 17:53

ok :-))) thx.

graysky commented on 2018-08-11 10:11

@simona - See the pinned post from Aug 4th.

simona commented on 2018-08-11 08:13

stopped to 4.17.11?

gee commented on 2018-08-11 03:35

Oh it's pkgbase, got it!

Yeah I'm running it, but the changes were made in bluetooth that I have not tested much, and schedutils that I don't use. If you look at the patch you'll see it is just a 3-way manual diff, nothing fancy.

graysky commented on 2018-08-10 18:56

@gee - Thanks, any feedback (assuming you're running that patched code)? I passed CK your proposal for review. To your question, just rename the pkgbase from linux-ck to linux-whatever-you-want

sispus commented on 2018-08-10 10:28

@ sir_lucjan

thank you, but I think I don't understand what to do. I did:

sudo pacman-key --recv-key 38DBBDC86092693E

it replied:

gpg: bad data signature from key 8396F1D05506E82D: Wrong key usage (0x19, 0x2)

gpg: bad data signature from key 20E8A9C77716EB4F: Wrong key usage (0x19, 0x2)

I did also that without realizing "wrong key usage" warning:

sudo pacman-key --lsign-key 38DBBDC86092693E

Now when I repeat above command (--recv-key) it says: Remote key not fetched correctly from keyserver.

I don't know if these info is helpful. If not, I'm sorry...

edit: I found this from a forum and solved: gpg --recv-keys 38DBBDC86092693E