Package Details: linux-ck-headers 4.9.11-1

Git Clone URL: (read-only)
Package Base: linux-ck
Description: Header files and scripts for building modules for Linux-ck kernel
Upstream URL:
Licenses: GPL2
Provides: linux-ck-headers=4.9.11, linux-headers=4.9.11
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 359
Popularity: 7.940395
First Submitted: 2011-07-22 14:51
Last Updated: 2017-02-18 17:20

Dependencies (5)

Required by (258)

Sources (12)

Latest Comments

Gelmo commented on 2017-02-21 04:58

@dkaylor Thanks for the heads up. I didn't realize this was following the Core release exclusively, and I've removed the flag. Regardless, I'm leaving the PKGBUILD; it builds 4.10 just fine :D

dkaylor commented on 2017-02-20 09:16

@gelmo Please read graysky's wiki for linux-ck before flagging out-of-date.

He's been doing a very good job with this package for years now, your updated PKGBUILD is not needed...

Gelmo commented on 2017-02-20 07:11

Here's a working PKGBUILD for 4.10:

Updated versioning, commented out the upstream patches, commented out the console loglevel patch (implemented now; I got this option presented to me pre-nconfig).

Edit: The loglevel option is now available in nconfig under Kernel Hacking

Edit 2: I also had to comment out the fpu patch on my setup. If you do this, don't forget to comment it out in the sources and prepare sections. Currently writing this from 4.10.0-1-ck, no issues.

graysky commented on 2017-02-18 17:20

Bump to v4.9.11-1

graysky commented on 2017-02-15 22:45

Bump to v4.9.10-1

graysky commented on 2017-02-09 22:34

Bump to v4.9.9-1

cdown commented on 2017-02-08 16:31

@VerruckteFuchs @fekle This is a bug in pacaur. I've just put up a patch to fix it at

VerruckteFuchs commented on 2017-02-06 20:58

@graysky @artafinde A simple makepkg -sri after clearing out the src directory sorted it out. It looks like something broke after pacaur got updated.

artafinde commented on 2017-02-06 20:07

Just follow the wiki:

fekle commented on 2017-02-06 20:00

@graysky to wait and see if other people experience this problem ;) you're right though, just tried installing manually and it worked just fine - oops.

All comments