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 .. 58 59 60 61 62 63 64 65 66 67 68 .. 307 Next › Last »

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

Yeah It downloads the sources twice and it builds it twice. Just finished compilation using plain old and reliable makepkg, worked like a charm w/o duplication. :) Also, @graysky, was looking for you at IRC but since can't find you I'll ask you here. I have a server that standing idling for no reasons for quite long time and it will keep standing there. Would you like to host the repo-ck.org/$arch there? Cuz afaik lots of people have problems downloading the binary -ck images from your servers. But it's quite anoying to re-build it every time on my machine :) I can give you access to the machine if you'd like?

graysky commented on 2017-11-25 13:05 (UTC)

No idea how yaourt works but if it is running the build function twice, the author of it should be notified as that is wasteful. Are you sure that it isn't just building once, and packaging the kernel then headers? That is how makepkg does it.

Osleg commented on 2017-11-25 12:36 (UTC)

@sir_lucjan Thanks for responding, already found my question in documentation, this PKGBUILD is multi package for both headers and the kernel itself. The question tho is that possible to build both headers and kernel w/o re-downloading and re-building the entire kernel? Right now I'm installing using yaourt. So it download sources twice and building twice. How could I prevent that?

sir_lucjan commented on 2017-11-23 19:40 (UTC)

@Osleg Could you tell us what do you mean?

Osleg commented on 2017-11-23 19:37 (UTC)

I wonder what is the difference between this pkg and linux-ck as their PKGBUILDs are identical

Terence commented on 2017-11-23 15:05 (UTC)

@artafinde @graysky After some more investigations, I figured out those were just warnings with the purpose to warn you they will not be included by default in the kernel, and you can safely ignore them as dkms take care of building them. Thank you very much for your help, I hope this could eventually help someone confused like me.

QuartzDragon commented on 2017-11-23 10:03 (UTC) (edited on 2017-11-23 10:05 (UTC) by QuartzDragon)

Attention @graysky and @everyone: Urgently needed update! FS#56404 - [linux] Using bcache will destroy filesystems (4.14.X) ~ https://bugs.archlinux.org/task/56404 and: 4.14.1-2 patch ~ https://git.archlinux.org/svntogit/packages.git/commit/trunk?h=packages/linux&id=a45f53296994bfbc2581656fa91f81f74fa21b83 I've already updated manually for this.

Terence commented on 2017-11-22 23:11 (UTC)

@artafinde: Thanks for your complete answer. I rigorously followed your advices, booting back to the ARCH kernel and making sure once more dkms modules are blacklisted and not stored, but whatever I do, I still get the same error with localmodconfig when either compiling on ARCH or -ck. I don't understand what's wrong... Note that I also use dkms modules on the regular kernel.

artafinde commented on 2017-11-22 18:05 (UTC)

@Terence: modprobed-db is snapshotting your loaded modules and adds them into a database. Provided you run the system long enough and use it you should have all the modules you are using. localmodconfig is a tool to configure the kernel to use the modules which are currently used from the kernel dkms is using the kernel-headers to create new modules for nvidia/virtualbox etc. During linux-ck compilation and if you have set the localmodconfig parameter in PKGBUILD we load all modules which are referenced in modprobed-db prior to calling localmodconfig. Then kernel is configured according to the loaded modules and compiles etc. If you want to make sure you have a clean modprobed-db follow these steps: 1. clean up modprobed-db from modules which don't belong on kernel (nvidia, vbox etc) 2. add those to IGNORE list (optionally test by calling modprobed-db store nd check they are not added) 3. reboot and load -ARCH kernel (to make sure all the modules are available) 4. edit PKGBUILD and set localmodconfig - compile and install 5. dkms should build new modules (nvidia, vbox, exfat etc) 6. reboot to your new kernel The above process is what I follow and works fine with nvidia, vbox and exfat -dkms packages. As a fallback I have -ARCH kernel always installed.

Terence commented on 2017-11-22 17:42 (UTC) (edited on 2017-11-22 23:07 (UTC) by Terence)

@artafinde sorry I didn't make it clear enough but that's what I did :) To me it's like modprobe-db just loads all the modules it detected has been loaded at some point and then localmodconfig just lsmod, which includes dkms modules... There has to be a way to exclude them.

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