Package Details: linux-ck 6.12.1-1

Git Clone URL: https://aur.archlinux.org/linux-ck.git (read-only, click to copy)
Package Base: linux-ck
Description: The Linux kernel and modules with ck's hrtimer patches
Upstream URL: https://wiki.archlinux.org/index.php/Linux-ck
Licenses: GPL-2.0-only
Provides: KSMBD-MODULE, VIRTUALBOX-GUEST-MODULES, WIREGUARD-MODULE
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.24
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-23 13:58 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 80 81 82 83 84 85 86 87 88 89 90 .. 307 Next › Last »

graysky commented on 2017-02-28 21:16 (UTC)

@cooljay - It's not in the official ARCH kernel either. I simply mirror ARCH's config (with the ck changes). The module has either been dropped upstream or we aren't configured to build it... you might wanna open up a flyspray against the kernel. When I look at the 4.9 -> 4.10 commit, I don't see that we dropped the config option containing 'serial' though: https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=192b948e730c25abf0269068755ef934486aec54

cooljay032 commented on 2017-02-28 20:19 (UTC)

seems the lirc_serial driver missing!?! -- Unit systemd-modules-load.service has begun starting up. Feb 28 21:07:41 vdr systemd-modules-load[801]: Inserted module 'acpi_cpufreq' Feb 28 21:07:41 vdr systemd-modules-load[801]: modprobe: ERROR: could not find module by name='lirc_serial' Feb 28 21:07:41 vdr systemd-modules-load[801]: modprobe: ERROR: could not insert 'lirc_serial': Unknown symbol in module, or unknown parameter (see dmesg) Feb 28 21:07:41 vdr systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE Feb 28 21:07:41 vdr systemd[1]: Failed to start Load Kernel Modules.

SuperIce97 commented on 2017-02-28 00:29 (UTC)

@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 (UTC)

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 (UTC) (edited on 2017-02-28 00:14 (UTC) by mrkline)

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 (UTC)

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 (UTC)

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 (UTC) (edited on 2017-02-26 00:25 (UTC) by QuartzDragon)

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

« First ‹ Previous 1 .. 80 81 82 83 84 85 86 87 88 89 90 .. 307 Next › Last »