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.25
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 .. 214 215 216 217 218 219 220 221 222 223 224 .. 307 Next › Last »

graysky commented on 2013-05-08 20:33 (UTC)

@andre - My bad... thought I pulled the offending outdated patch from this (the alsa fix). I just reuploaded 3.9.1-0 overwriting the old one. Please download it again and it should build.

andre.vmatos commented on 2013-05-08 20:11 (UTC)

I'm trying to compile 3.9.1, but it's failing with: ... patching file sound/usb/usx2y/usx2yhwdeppcm.c patching file include/sound/emu10k1.h Reversed (or previously applied) patch detected! Skipping patch. 1 out of 1 hunk ignored -- saving rejects to file include/sound/emu10k1.h.rej patching file sound/pci/emu10k1/emu10k1_main.c Reversed (or previously applied) patch detected! Skipping patch. 4 out of 4 hunks ignored -- saving rejects to file sound/pci/emu10k1/emu10k1_main.c.rej Any ideas?

graysky commented on 2013-05-08 20:07 (UTC)

@Andre - I see. I can tell you that the nvidia-304xx and virtualbox modules do not show anything bad in my dmesg; both of these have not been compiled against 3.8.12. I did have to rebuild the broadcom-wl-ck module however.

andre.vmatos commented on 2013-05-08 20:01 (UTC)

Hmm, IMHO, I think he means that 3rd-part modules (e.g. virtualbox) compiled for 3.8 series are showing errors, often symbol errors, upon insertion, avoiding it to load properly in 3.8.12, even when a compilation for 3.8 series are supposed to be binary-compatible with all 3.8 series (symbols and binary compatibility should change only in major (3.x) upgrades, requiring a recompilation or even patching).

graysky commented on 2013-05-08 20:00 (UTC)

Meant to post this link to the pre-release of 3.9.1-ck which is nearly 100 %. It is just missing the official yet-to-be-released BFQ which Paolo tells me should not be different from the current release which patches into 3.9 just fine. http://repo-ck.com/PKG_source/linux-ck-next/linux-ck-3.9.1-0.src.tar.gz

graysky commented on 2013-05-08 19:55 (UTC)

Thanks for that link, andre. I guess I do not know what tpowa meant by his comment, "module breaker." https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024896.html

andre.vmatos commented on 2013-05-08 19:46 (UTC)

This warnings isn't related with binary modules in 3.8.12, but with mkinitcpio 0.14: https://mailman.archlinux.org/pipermail/arch-dev-public/2013-May/024864.html

graysky commented on 2013-05-08 19:27 (UTC)

Bump to v3.8.12-1 Changelog: https://lkml.org/lkml/2013/5/8/12 Commit: Notes: Tpowa noted that the 3.8.12 release is a "binary module breaker" which I assume explains the mkinitcpio output when it built my fallback image: ==> WARNING: Possibly missing firmware for module: aic94xx ==> WARNING: Possibly missing firmware for module: bfa Dunno the scope of this and how it will affect users.

graysky commented on 2013-05-07 19:14 (UTC)

OK. The ck1 patchset for 3.9 has gone gold. We are just waiting for Paolo to do the same with the BFQ set and are on track for a release any time now. For those who can't wait: http://repo-ck.com/PKG_source/linux-ck-next/linux-ck-3.9-0.src.tar.gz

Det commented on 2013-05-04 20:59 (UTC)

@Kalrish, was it fair for kernel.org to be attacked :)?

« First ‹ Previous 1 .. 214 215 216 217 218 219 220 221 222 223 224 .. 307 Next › Last »