Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 388
Popularity: 3.992916
First Submitted: 2011-07-22 14:51
Last Updated: 2018-08-14 15:42

Packages (2)

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

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 ... Next › Last »

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

sir_lucjan commented on 2018-08-10 09:53

@ sispus

sispus commented on 2018-08-10 09:49

I couldn't install it to manjaro xfce. linux-4.17.11.tar ... FAILED (unknown public key 38DBBDC86092693E) ==> ERROR: One or more PGP signatures could not be verified!

gee commented on 2018-08-10 08:29

@graysky, I've patched ck's patch to build with .14, it was fairly easy, hopefully I made no mistake:

Unrelated, but how do I easily get this package to be named similarly to the one I'd get from your repo, in my case -haswell?

melcor333 commented on 2018-08-09 23:20

@graysky - I'll try thanks

EDIT: Perfect! Working as intended. Thanks a lot! :)

melcor333 commented on 2018-08-09 23:18

Hi, since last 2 updates I'm unable to boot to GUI, because of nvidia isn't found in kernel modules. I get this error during install:

==> ERROR: module not found: nvidia' ==> ERROR: module not found:nvidia_modeset' ==> ERROR: module not found: nvidia_uvm' ==> ERROR: module not found:nvidia_drm'

I have nvidia-ck and linux-ck-headers installed. Is there anything I'm doing wrong?

GPU is Nvidia GTX960. Before this everything worked flawlessly.


graysky commented on 2018-08-09 21:16

@melcor333 - broadcom and nvidia-* have been updated. Please try and reported back. broadcom and nvidia-340xx work for me on my test box.