Package Details: linux-ck 6.11.10-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.23
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Dependencies (14)

Required by (7)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 67 68 69 70 71 72 73 74 75 76 77 .. 308 Next › Last »

graysky commented on 2017-09-06 19:44 (UTC) (edited on 2017-09-06 19:45 (UTC) by graysky)

@archzz - please do not flag out of date until ck releases a patchset suitable for the 4.13.0 series.

graysky commented on 2017-09-05 16:21 (UTC)

Due to x.69 being pushed to [extra]. Updated now.

keepitsimpleengr commented on 2017-09-05 16:09 (UTC)

nvidia-ck-k10: installing nvidia-utils (384.69-1) breaks dependency 'nvidia-utils=384.59'

hotty commented on 2017-08-26 16:05 (UTC)

Since it is weekend and I finally had some time I found the culprit in the form of my internal sd-card reader. If I have a sd-card inserted udev times out resulting in a blinking cursor. Without a card linux-ck boots successful. Also inserting a card after booting does not detect the sd-card but instead crashes systemd-udev with the kernel blaming the error on block/elevator.c Using an external card-reader works. To report the bug and send in the full error message, is it an bug in udev or in ck?

Tharbad commented on 2017-08-22 19:00 (UTC)

It's appears that there's a conflict between scsi_mod.use_blk_mq=0 and any of the multi queue I/O schedulers. So either set scsi_mod.use_blk_mq to 1 or use the "none" scheduler. Choosing option n2 makes this kernel worthless. I haven't tried it yet. Found it here: https://bbs.archlinux.org/viewtopic.php?pid=1730573#p1730573

vp1981 commented on 2017-08-22 12:21 (UTC)

@hotty, @Tharbad, guys would you mind to provide more details? For example, your system configuration (HDD/SSD, FS), kernel cmdline, what queue scheduler do you use and etc. And don't forget that graysky only build the kernel with CK patches, so report any problems to CK, https://ck-hack.blogspot.com/.

Tharbad commented on 2017-08-22 12:08 (UTC)

System freezes sometime during the graphical login. CPU is at 100%. ctrl+alt+F# and magic keys don't work.

hotty commented on 2017-08-20 21:23 (UTC)

Still got a non-bootable kernel, both from here or from repo-ck freezes at boot since version 4.12.7. Normal arch kernel boots without any issues. Just a blinking cursor and after 2 minutes it shows "Triggering uevents" but thats it.

graysky commented on 2017-08-17 19:13 (UTC)

I bumped to 4.12.8-1 but will hold on building for [repo-ck] until CK verifies the recent merges (github) will not be released to ck3 any time soon.

mrkline commented on 2017-08-15 21:38 (UTC) (edited on 2017-08-15 21:44 (UTC) by mrkline)

@graysky: See https://groups.google.com/forum/#!msg/bfq-iosched/j4QUK4IPOhw/CY1LmmhcAwAJ, as previously mentioned - apparently other kernel devs have removed compile-time scheduler defaults. I've been able to "fix" it for now with a udev rule, slightly modified from what @vp1981 posted: ACTION=="add|change", KERNEL=="sd[a-z]", ATTR{queue/scheduler}="bfq" (The wildcard was causing several false positives and errors to show up in the system log while booting.)

« First ‹ Previous 1 .. 67 68 69 70 71 72 73 74 75 76 77 .. 308 Next › Last »