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 .. 43 44 45 46 47 48 49 50 51 52 53 .. 308 Next › Last »

sir_lucjan commented on 2018-07-11 23:01 (UTC)

@ graysky

No.

graysky commented on 2018-07-11 20:35 (UTC)

Can anyone else confirm that 4.17.6 causes errors relating to mounting disks.

bezirg commented on 2018-06-28 08:50 (UTC)

Proposed change in PKGBUILD:

Note that the
# generic (default) option is 24.

to ====>

Note that the
# generic (default) option is 26.

bezirg commented on 2018-06-28 08:45 (UTC)

On linux-ck 4.17.3-1 makepkg error:

==> Verifying source file signatures with gpg...
    linux-4.17.tar ... FAILED (unknown public key 79BE3E4300411886)
    patch-4.17.3 ... FAILED (unknown public key 38DBBDC86092693E)
==> ERROR: One or more PGP signatures could not be verified!

graysky commented on 2018-06-25 13:14 (UTC)

I asked for a timeline for 4.17-ck1. I will update the [repo-ck] thread when I hear back. Doesn't make too much sense to go though heroic measures to troubleshoot if 4.17-ck1 is just around the corner. I believe 4.16.x will be EOL'ed shortly as well.

CK expects 4.17-ck1 in a few days so it's not worth trying to unfuck 4.16-ck1 to fit into 4.16.17 or 4.16.18 IMO.

graysky commented on 2018-06-24 21:07 (UTC)

Yea, it's confirmed that 4.16.17-1 doesn't play well with ck's patchset. I asked for a timeline for 4.17-ck1. I will update the [repo-ck] thread when I hear back. Doesn't make too much sense to go though heroic measures to troubleshoot if 4.17-ck1 is just around the corner. I believe 4.16.x will be EOL'ed shortly as well.

Tjuh commented on 2018-06-24 18:36 (UTC)

Same problem as the others, just a black screen during boot, ditto with the pre built pkg from the repo ck.

nTia89 commented on 2018-06-24 10:24 (UTC)

me too. 4.16.17-2 stucks just after boot selection. I am on broadwell, compiled with native and P6_NOP. Downgraded

graysky commented on 2018-06-23 05:37 (UTC)

@zero - Yes, I am having this problem as well.

zerophase commented on 2018-06-22 23:45 (UTC) (edited on 2018-06-22 23:54 (UTC) by zerophase)

Anyone else getting stuck after the boot loader with the last update? Don't believe I have any logs since the system stalls early in boot.