Package Details: linux-ck 6.11.7-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.32
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-09 16:45 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 162 163 164 165 166 167 168 169 170 171 172 .. 307 Next › Last »

Tjuh commented on 2014-10-10 18:28 (UTC)

Fixed now, thanks. I ran a new modprobed_db with the external hdd on and recompiled.

graysky commented on 2014-10-10 16:25 (UTC)

Odds are that using that option, you did not compile in USB support. I suggest using modprobe-db if you haven't already done so. Boot into a kernel with all modules, load those you will need, ie insert the external USB drive, populate the db and try rebuilding.

Tjuh commented on 2014-10-10 13:34 (UTC)

Yes, localmodcfg=y in the PKGBUILD. The latest linux-ck-haswell kernel works just fine from the repo-ck. The previous kernel v3.16.4-1 works just fine with the same PKGBUILD settings.

graysky commented on 2014-10-10 13:24 (UTC)

Did you modify the PKGBUILD or build with localmodconfig or the like? What happens if you use one of the kernel packages from repo-ck?

Tjuh commented on 2014-10-10 10:20 (UTC)

After compiling the latest linux-ck my external usb hdd is not being recognized anymore. I had no problem with the previous kernel.

graysky commented on 2014-10-09 20:30 (UTC)

Bump to v3.16.5-1 Changelog: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog-3.16.5 Commit: https://wiki.archlinux.org/index.php/Linux-ck/Changelog

synergy commented on 2014-10-08 06:26 (UTC)

@AnAkkk What you're most likely witnessing isn't a bug. By design, BFQ sacrifices throughput for interactivity.