Package Details: linux-ck 6.9.4-1

Git Clone URL: (read-only, click to copy)
Package Base: linux-ck
Description: The Linux kernel and modules with ck's hrtimer patches
Upstream URL:
Licenses: GPL-2.0-only
Replaces: virtualbox-guest-modules-arch, wireguard-arch
Submitter: graysky
Maintainer: graysky
Last Packager: graysky
Votes: 459
Popularity: 0.33
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-06-13 18:33 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 306 Next › Last »

air-g4p commented on 2022-10-03 05:32 (UTC)

@artafinde - I appreciate your insightful feedback.

If you meant by ignoring the package not found build errors when running extra-x86_64-build: do not use use extra-x86_64-build, I agree because I cannot get past those build errors. If you meant something else, please let me know.

The build and installation did succeed with sudo ccm s, however ccm silently ignored my: PKGBUILD _localmodcfg=/home/<userID>/.config/modprobed.db.

CCM not reading modprobed.db explains why I was treated to another 5+ hour build joyride and why my ccm build folder grew to 20 GiB!

Thanks and cheers...

artafinde commented on 2022-10-02 08:36 (UTC)

@air-g4p: the error you mention 'packages not found linux-ck and linux-ck-headers' can be ignored. The extra-x86_64-build assumes you are building for Arch repos and executes secondary tools to compare the package with the one from the repos. Is this case it's not able to find them in repos (makes sense).

For the second issue it's also expected to not work since the chroot doesn't have your modprobed-db. You'll need to hack the script or check if graysky's clean-chroot-manager supports modprobed-db. Yeah it does take time but if you build it once with generic you can reuse it on your laptop ;)

air-g4p commented on 2022-10-02 07:36 (UTC)

@artafinde - I'm interested to learn if you see the same clean chroot build behavior(s).

If I run extra-x86_64-build, that fails early in the build process with something like 'packages not found linux-ck and linux-ck-headers.'

I've been using graysky's modprobed-db for many years without issue, so I always include: _localmodcfg=/home/<userID>/.config/modprobed.db in the PKGBUILD to reduce compilation time.

However, when I run makechrootpkg -c -r $CHROOT with ^that PKGBUILD, it fails with 'cannot find /home/<userID>/.config/modprobed.db'. I have never seen this failure when running time makepkg -sric.

The only way I can get makechrootpkg -c -r $CHROOT to successfully build and install is to leave _localmodcfg= empty.

However, this massively increases compilation time. On my old laptop, linux-ck compilation time increased from an average of about 1.5 hours to more than 5 hours!

In any event, the Good News is that the build and installation was a success!!

Please let me know when you have a chance.

Thanks and cheers...

artafinde commented on 2022-09-30 16:06 (UTC)

air-g4p: Glad it helped. I was thinking maybe the dkms.conf (or the relevant Makefile for each extra module) wasn't not up to date with 5.19.x kernels. Anyway all well and keep building with clean chroot! :D

air-g4p commented on 2022-09-30 15:22 (UTC)

@artafinde - My apologies if you perceived my response as snarky.

I only think of 'old' as related to code/configs as being deprecated or obsolescent, which as a prominent example, most unfortunately, I am forced to observe, daily, as in: POTUS Joe Biden...

If you have another definition of 'old' as it relates to the 3 dkms.conf files I sent you earlier:, you never explained why they are 'old'. I would be interested to learn about your POV.

In any event, for reasons I still do not understand, building in a clean chroot worked (on my newer laptop, at least); meaning linux-ck compiled and 'dkms installed' without error, as opposed to the multiple 'dkms install' failures I experienced via 'time makepkg -sric'.

Thank you for your input artafinde!

air-g4p commented on 2022-09-30 14:44 (UTC) (edited on 2022-09-30 15:29 (UTC) by air-g4p)

@graysky - noted that you are unfamiliar with dkms.

However I checked all of your (the default) configs related to config DEBUG_INFO_BTF.

AFAICT - ALL appear to be correctly set and in compliance with its dependencies listed here:

Refer to ^lines 339 through 365. I saw no reason to change those configs.

Hoping against hope, I did opt to change the linux-ck build with CLANG, as opposed to the default gcc.

No improvement: compiled without error, but the exact same 4 'dkms install' module errors (I previously documented) re-appeared during installation.

IMHO, the default kernel configs are set correctly - and the choice of the compiler is not relevant to the 4 (out of 4) 'dkms install' module errors I have been seeing of late.

artafinde commented on 2022-09-29 16:21 (UTC)

@air-g4p that's not what I mean by the dkms.conf being old but anyway - fill your boots :)

air-g4p commented on 2022-09-29 16:09 (UTC) (edited on 2022-09-29 16:11 (UTC) by air-g4p)

@artafinde - glad to learn things work correctly on your end.

However, since you earlier assumed: I think maybe the DKMS modules are old and not updated for latest kernels?

I provided the evidence that your assumption is not true on my fully updated, and re-booted, laptops.

What would make you now believe that building in a clean chroot would correct anything?

I build linux-ck with time makepkg -sric as I have been doing for many years!


graysky commented on 2022-09-29 15:21 (UTC)

I am unfamiliar with dkms... can you test your idea about enabling the debug stuff using linux-ck's config and report back?

artafinde commented on 2022-09-29 14:38 (UTC)

@air-g4p I'm able to install linux-ck and zfs-dkms without issues, modules generating without errors. Have you tried building those packages in clean chroot?