Package Details: linux-ck 4.15.5-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.170
Upstream URL:
Licenses: GPL2
Provides: linux-ck=4.15.5
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 377
Popularity: 6.235986
First Submitted: 2011-07-22 14:51
Last Updated: 2018-02-22 22:09

Latest Comments

graysky commented on 2018-02-23 20:41

@RaskAr - I use the ARCH .config as the base for linux-ck making only the changes the ck patchset requires. If this is something shipped with the kernel but silent in the config itself, you can enable it and build with it. If this is an out-of-tree addition, you are free to patch the source and build it.

RaskAr commented on 2018-02-23 19:46

Hello graysky, the config seems to be missing a builtin config for laptop users :

From log : « kernel: psmouse serio3: synaptics: The touchpad can support a better bus than the too old PS/2 protocol. Make sure MOUSE_PS2_SYNAPTICS_SMBUS and RMI4_SMB are enabled to get a better touchpad experience. »

After checking the config it only misses RMI4, which is the successor of the PS2 PROTOCOL, see Would be great to have it enabled !

presianbg commented on 2018-02-19 05:03

bfq-sq is gone again.


PS: Putting "scsi_mod.use_blk_mq=1 " in kernel options is enabling the BFQ MQ scheduler. The selecting it with TLP, works just fine.

PS2: elevator option in the kernel parameters is not recognized.

graysky commented on 2018-02-18 20:35

which processor family should i chose for apollo lake (goldmont) processor Celeron N3450?

Did you try:

garwol commented on 2018-02-17 17:34

which processor family should i chose for apollo lake (goldmont) processor Celeron N3450?

Terence commented on 2018-02-17 16:50

@nTia89 It had to be from my side, it's working fine now with 4.14.20.

nTia89 commented on 2018-02-15 22:02

no problem here with .19 and DKMS

Terence commented on 2018-02-13 20:34

Something with 4.14.19 is making DKMS not working for any driver.

kata198 commented on 2018-02-08 05:03

@QuartzDragon - I applied the 4.14 patch with -F5 (fuzz-level 5, dangerous; requires manual review of every patch but "shoves" things in when at all possible. It even managed to shove some code right into the middle of a comment!), fixed the rejections, added one or two new compat functions as required due to API/ABI changes between .14 and .15, did some basic research into where things moved around and such and applied those changes.

I've done some kernel work in the past, so I like to think I'm somewhat familiar with the layout of things. It shouldn't take too long for you to pick up where things are, thanks to you're friendly General Regular Expression Parser (grep) .

Basically, checked the diff between 4.14 and 4.15 on the core scheduler to see any abi/api changes, and others as they arose ( I remember there being a change in some of the "compat" files which required updates/additions/rewrites beyond what the original patch provided, there may have been others ).

Then just built, and fixed any issues that arise during compile (these can be due to changing where #ifdef wrappers are in the baseline, where the patch may force things into the wrong section, or a linker issue from a missing function, etc.)

I'd say just dive right in! Try to merge 4.14 to 4.15 yourself, basically make it till you break it, or succeed! Probably a good idea to use a virtualbox image for testing rather than your primary system, or what I do on this laptop I am using to type to you right now, which is running arch in a virtualbox on top of windows 10 (work / warrenty reasons) is this: I take a snapshot prior to development, so any damage that gets done I can just roll back and alls good.

Hope this helps, I'm not too sure on what you are looking for specifically, so I tried to keep it general!

I would say just dig in! Try you m

kata198 commented on 2018-02-08 04:46

I mentioned specifically that I didn't know if they were true or not -- I just found a couple articles when searching to see if anyone else had ported it as it was time for me to build a new kernel. I mean no disrespect nor harm toward anybody. @beojan is probably right -- they may have been dated 2007 which I mistook for 2017.

If you've spoken with him and he says he's not -- all the better. But please don't try to make me out to be some sort of demon spreading nonsense -- I specifically said "I don't know if these reports are legitimate or not."

You're free to enjoy the early merge and update I did, or you're free to wait for him to release an official version. I'm still running strong without any issues on my merge, so it seems pretty stable to me.

Again, I apoligize if I've upset anybody, this was not my intent at all.

All comments