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: 361
Popularity: 8.657659
First Submitted: 2011-07-22 14:51
Last Updated: 2017-02-27 22:41

Packages (2)

Latest Comments

SuperIce97 commented on 2017-02-28 00:29

@mrkline That's a bit odd, yeah. nvidia-libgl is now on version 378.13-3 but nvidia-dkms is 378.13-2. You need 378.13-3 for Linux 4.10 support, so I wonder why they haven't pushed that dkms update yet.

mrkline commented on 2017-02-28 00:26

Ah - turns out the patch needed for 4.10 is in nvidia-dkms 378.13-3, which is currently only available in the testing repo. Installing it by hand from https://www.archlinux.org/packages/testing/x86_64/nvidia-dkms/ did the trick.

mrkline commented on 2017-02-28 00:11

nvidia-dkms fails to build against 4.10.1-1. Is there a known workaround? Or do we now have to use nvidia-ck? (I've been using nvidia-dkms with linux-ck for quite a while without any trouble.)

From the build log:

CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/nv-vtophys.o
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c: In function ‘nvidia_cpu_callback’:
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:213:14: error: ‘CPU_DOWN_FAILED’ undeclared (first use in this function)
case CPU_DOWN_FAILED:
^~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:213:14: note: each undeclared identifier is reported only once for each function it appears in
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:220:14: error: ‘CPU_DOWN_PREPARE’ undeclared (first use in this function)
case CPU_DOWN_PREPARE:
^~~~~~~~~~~~~~~~
In file included from /var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:15:0:
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c: In function ‘nv_init_pat_support’:
/var/lib/dkms/nvidia/378.13/build/common/inc/nv-linux.h:391:34: error: implicit declaration of function ‘register_cpu_notifier’ [-Werror=implicit-function-declaration]
#define register_hotcpu_notifier register_cpu_notifier
^
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:258:17: note: in expansion of macro ‘register_hotcpu_notifier’
if (register_hotcpu_notifier(&nv_hotcpu_nfb) != 0)
^~~~~~~~~~~~~~~~~~~~~~~~
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c: In function ‘nv_teardown_pat_support’:
/var/lib/dkms/nvidia/378.13/build/common/inc/nv-linux.h:388:36: error: implicit declaration of function ‘unregister_cpu_notifier’ [-Werror=implicit-function-declaration]
#define unregister_hotcpu_notifier unregister_cpu_notifier
^
/var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.c:283:9: note: in expansion of macro ‘unregister_hotcpu_notifier’
unregister_hotcpu_notifier(&nv_hotcpu_nfb);
^~~~~~~~~~~~~~~~~~~~~~~~~~
CC [M] /var/lib/dkms/nvidia/378.13/build/nvidia/os-interface.o
cc1: some warnings being treated as errors
make[2]: *** [scripts/Makefile.build:294: /var/lib/dkms/nvidia/378.13/build/nvidia/nv-pat.o] Error 1
make[2]: *** Waiting for unfinished jobs....
make[1]: *** [Makefile:1494: _module_/var/lib/dkms/nvidia/378.13/build] Error 2
make[1]: Leaving directory '/usr/lib/modules/4.10.1-1-ck/build'
make: *** [Makefile:81: modules] Error 2

graysky commented on 2017-02-27 22:43

Bump to v4.10.1-1
Changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.10.1
Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

graysky commented on 2017-02-26 11:31

Bump to v4.9.13-1
Changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.13
Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

QuartzDragon commented on 2017-02-26 00:24

Cannot reproduce here, even after many hours of system activity. I also have an Ivy Bridge CPU.

simona commented on 2017-02-25 19:42

Anyone has freeze problem with all CK (CK standard, CK-ivybridge) ?

graysky commented on 2017-02-23 20:32

Bump to v4.9.12-1
Changelog: https://www.kernel.org/pub/linux/kernel/v4.x/ChangeLog-4.9.12
Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

graysky commented on 2017-02-23 20:32

@kyak - Rebuilt a few days ago. Thanks for reporting.

kyak commented on 2017-02-21 18:14

It seems that virtualbox-ck-host-modules-ivybridge requires rebuild:

Failed to insert 'vboxnetadp': Invalid argument
Failed to insert 'vboxnetflt': Invalid argument
Failed to insert 'vboxnetadp': Invalid argument
Failed to insert 'vboxnetflt': Invalid argument


Kernel 4.9.11-1-ck-ivybridge from repo-ck.

All comments