Package Base Details: linux-ck

Git Clone URL: (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 412
Popularity: 3.160422
First Submitted: 2011-07-22 14:51
Last Updated: 2019-09-16 18:30

Packages (2)

Latest Comments

« First ‹ Previous ... 14 15 16 17 18 19 20 21 22 23 24 ... Next › Last »

SilverMight commented on 2018-07-31 21:44

Have a few people with the same issue in the thread:

graysky commented on 2018-07-29 21:49

No idea about CUDA/don't have the hardware. You might try CK's blog or someone might reply to what I think is your bbs thread.

SilverMight commented on 2018-07-29 21:39

Now it works, thanks. Do you know if there's an issue with CUDA? Doesn't seem to initialize on this kernel, but every other kernel works fine for me

graysky commented on 2018-07-29 21:04

Did you pacman -Syyu? Fine for me % pacman -Ss core2-h repo-ck/linux-ck-core2-headers 4.17.11-1 (ck-core2) Header files and scripts for building modules for Linux-ck-core2 kernel Intel Core2/Newer Xeon optimized.

SilverMight commented on 2018-07-29 19:19

Some reason my pacman is trying to fetch 4.10-1 instead of 4.11 from repo-ck, even though I have refreshed the lists.. anyone experiencing this?

Also - is anyone else having an issue with CUDA with this kernel?

sir_lucjan commented on 2018-07-11 23:01

@ graysky


graysky commented on 2018-07-11 20:35

Can anyone else confirm that 4.17.6 causes errors relating to mounting disks.

bezirg commented on 2018-06-28 08:50

Proposed change in PKGBUILD:

Note that the
# generic (default) option is 24.

to ====>

Note that the
# generic (default) option is 26.

bezirg commented on 2018-06-28 08:45

On linux-ck 4.17.3-1 makepkg error:

==> Verifying source file signatures with gpg...
    linux-4.17.tar ... FAILED (unknown public key 79BE3E4300411886)
    patch-4.17.3 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!

graysky commented on 2018-06-25 13:14

I asked for a timeline for 4.17-ck1. I will update the [repo-ck] thread when I hear back. Doesn't make too much sense to go though heroic measures to troubleshoot if 4.17-ck1 is just around the corner. I believe 4.16.x will be EOL'ed shortly as well.

CK expects 4.17-ck1 in a few days so it's not worth trying to unfuck 4.16-ck1 to fit into 4.16.17 or 4.16.18 IMO.