Package Base Details: linux-ck

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only)
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 408
Popularity: 5.399647
First Submitted: 2011-07-22 14:51
Last Updated: 2019-06-16 14:52

Packages (2)

Latest Comments

« First ‹ Previous ... 8 9 10 11 12 13 14 15 16 17 18 ... Next › Last »

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: https://pastebin.com/WDVt52ZB

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.

Thanks

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.

graysky commented on 2018-08-09 21:06

Yes, the naming schema has changed. I will push some updates shortly.

graysky commented on 2018-08-09 19:29

All - I think I have all the kinks ironed out of the new PKGBUILD structure. We are still unfortunately in the position of ck1 not patching into 4.17.12-current so we seem stuck on 4.17.11. Good news is that 4.18.0 should be released this weekend and CK is likely to work on that rather than doing so to an EOL kernel (4.17.x series).

I just pushed 4.17.11-4 with a few minor tweaks. Builds and runs fine for me. Please d/l and test.

@Saren - Fixed the NUMA issue in -4. Please try.

Saren commented on 2018-08-07 17:42

Hi, my system needs NUMA support, and changing _NUMAdisable=y to _NUMAdisable= still disables NUMA support on 4.17.11-3. I have already compiled the kernel twice and I am sure I have changed that line. It was totally fine before the major PKGBUILD format change.

artafinde commented on 2018-08-07 11:29

Yeah if only they provide a checksum and/or signed packages :)

graysky commented on 2018-08-07 11:03

https://github.com/archlinux/linux/releases