Package Details: linux-ck 4.16.10-1

Git Clone URL: (read-only)
Package Base: linux-ck
Description: The Linux-ck kernel and modules with the ck1 patchset featuring MuQSS CPU scheduler v0.171
Upstream URL:
Licenses: GPL2
Provides: linux-ck=4.16.10
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 384
Popularity: 5.465286
First Submitted: 2011-07-22 14:51
Last Updated: 2018-05-20 22:52

Latest Comments

Morganamilo commented on 2018-05-22 04:32

Is there a reason for the linux-ck=4.16.10 provide? All packages automatically provide their own name.

zebulon commented on 2018-05-02 06:24

@graysky: thanks. Do you mean 4.16.6-2? There is no -3 in the repository.

graysky commented on 2018-05-01 23:31

@sir_l - CK1 includes the nvidia patch (0003) and I bumped linux-rc to 4.16.7 which includes 0004 so I accidentally omitted it.... fixing in 4.16.6-3, thanks.

sir_lucjan commented on 2018-05-01 21:03


Probably you forgot about other patches:


  2. (added: 4.16.7-rc1).

graysky commented on 2018-05-01 20:56

@sir_lucjan - Yes, I thought I diffed that out >:( ... fixed now but since I have been building the repo packages, I don't want to bump the pkgver and start all over.

@zebulon - Thanks for reporting. Please try now.

sir_lucjan commented on 2018-05-01 20:51


You should remove

  install -Dt "${_builddir}/drivers/media/dvb-core" -m644 drivers/media/dvb-core/*.h

from headers()



zebulon commented on 2018-05-01 20:47

Hi, packaging fails with this error:

==> Starting package_linux-ck-headers()... install: cannot stat 'drivers/media/dvb-core/*.h': No such file or directory ==> ERROR: A failure occurred in package_linux-ck-headers(). Aborting...

Or am I doing something wrong? The only option I used is Skylake optimisations, but I do not think this is relevant.

sir_lucjan commented on 2018-04-11 14:47


You should ask Con.

simona commented on 2018-04-10 08:13

4.16? soon?

Dennis commented on 2018-03-24 07:14

Today receiving the key just worked and the packages updated as well without issues. Must have been a network issue elsewhere.

@vp1981: The missing sudo on the second command was just an oversight on my part when I prepared a cleaned up, condensed message for posting here. In reality I ran all commands in a root shell and only added sudo in front for the log here to make it clear that I was running those commands as root.

All comments