Package Details: linux-ck 6.11-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.92
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-09-19 13:04 (UTC)

Dependencies (14)

Required by (6)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 307 Next › Last »

graysky commented on 2017-12-17 09:56 (UTC)

@air-g4p - Yes, the failure is due to user intervention being required to select a sub-arch. Please try 4.14.16-3 in which the _subarch variable should take care of this use case.

air-g4p commented on 2017-12-17 06:21 (UTC)

Hi graysky,

In the event you are not aware, your linux-ck 4.14.6-2 AUR fails to build in a clean chroot, using: extra-x86_64-build.

Your immediately prior release also failed to build using either extra-x86_64-build or makechrootpkg -c -r $CHROOT.

We know for a fact your AUR is broken because when discussing this linux-ck build failure on #archlinux, another experienced AUR user also replicated the same extra-x86_64-build failure on his system.

I have pasted my entire build run for your review at: https://bpaste.net/show/3c5c3d9ea326. That paste URL will remain valid for one month.

Additionally, for those users willing to employ this approach, I can confirm your AUR can be successfully built and installed with: makepkg -si.

I hope you are able to determine, and correct, whichever part(s) of your code is/are causing the build failure, as many of us strongly prefer to build AURs exclusively within a clean chroot environment.

Thank you for providing an otherwise excellent alternative kernel. Your effort is immensely appreciated.

Cheers,

air|g4p

eduardoeae commented on 2017-12-16 12:48 (UTC)

Works OK now. Thanks!

graysky commented on 2017-12-16 11:36 (UTC)

@edu and sha - Please try now.

Shaikh commented on 2017-12-16 08:03 (UTC)

I encountered the same problem as @eduardoeae.

eduardoeae commented on 2017-12-16 03:17 (UTC)

Your packages (from repo-ck.com) are failing with "missing required signature". I have been using them for months without problem. Also tried re-adding your key (pacman-key -r 5EE46C4C && pacman-key --lsign-key 5EE46C4C) as the site suggests, but still not working.

pedrogabriel commented on 2017-11-26 22:29 (UTC)

You plan to include the new runqueue patch?

johnnybegood commented on 2017-11-25 17:44 (UTC)

Thanks a lot for the ck patches for bfq-sq!!! :)

Osleg commented on 2017-11-25 16:21 (UTC)

Kernel panic solved, was unrelated to kernel itself

Osleg commented on 2017-11-25 13:44 (UTC)

Also this since upgrade to >4.14 Kernel panic with "No working init found" http://storage9.static.itmages.com/i/17/1125/h_1511617326_7762244_e6000b236e.jpg Any idea what could be the cause?

« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 307 Next › Last »