Package Details: linux-ck 6.11.10-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.127180
First Submitted: 2011-07-22 14:51 (UTC)
Last Updated: 2024-11-26 13:15 (UTC)

Dependencies (14)

Required by (7)

Sources (6)

Latest Comments

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 308 Next › Last »

sir_lucjan commented on 2019-11-03 13:11 (UTC)

@toki1990

It's not a linux-ck problem, it's Manjaro. Due to recent updates in Arch Linux (kmod and mkinitcpio) hooks are no longer provided in kernel only in kmod (depmod-hook) and mkinitcpio (mkinitcpio-install and mkinitcpio remove). Unfortunately, at the moment, as a Manjaro user you will not install most of the current AUR kernels and the problem lies solely with your distribution, i.e. Manjaro.

toki1990 commented on 2019-11-03 13:02 (UTC)

I'm manjaro stable repo user. linux-ck 5.3.8-4 not booting. I'm tried linux-slim 5.3.8-2 custom kernel same problem. Xanmod 5.3.8-1 not doing this. Because problem is this:

"Updating linux-xanmod initcpios... ==> Building image from preset: /etc/mkinitcpio.d/linux-xanmod.preset: 'default' -> -k /boot/vmlinuz-linux-xanmod -c /etc/mkinitcpio.conf -g /boot/initramfs-linux-xanmod.img ==> Starting build: 5.3.8-xanmod6-1-xanmod -> Running build hook: [base] -> Running build hook: [udev] -> Running build hook: [autodetect]...."

Xanmod custom kernel doing this last of compilation. Linux-ck 5.3.8-4 not doing this.

graysky commented on 2019-11-01 20:46 (UTC)

@Superice - Yes, I am ignoring that particular change. For example, the substitution will make _srcver=5.3.8-arch1 in this case whereas this package will be 5.3.8-1-ck which is fine for me.

SuperIce97 commented on 2019-11-01 20:39 (UTC) (edited on 2019-11-01 20:40 (UTC) by SuperIce97)

The pkgver and _srcver variables changed in the main linux package:

pkgver=5.3.8.1
_srcver=${pkgver%.*}-arch${pkgver##*.}

graysky commented on 2019-11-01 18:48 (UTC)

@sir_lucjan - Good catch, thanks. Fixed in 5.3.8-4.

sir_lucjan commented on 2019-11-01 18:09 (UTC)

@graysky

As far as I can see, you forgot to change one line.

-  echo "$_kernelname" > localversion.20-pkgname
+  echo "${pkgbase#linux}" > localversion.20-pkgname

air-g4p commented on 2019-10-31 13:36 (UTC) (edited on 2019-10-31 14:34 (UTC) by air-g4p)

@graysky,

It was interesting to see how much 'heat' my wireguard-dkms post generated, and perhaps several of us wireguard-dkms and -ck users have learned some important tips.

Bottom line = tldr version - no action is required provided that: the fou, ip_tunnel and wire modules are found within lsmod and/or modprobed-db list if you run modprobed-db.

Those 3 modules were NOT loaded within MY modprobed-db list, which was quite surprising, given that I have run wireguard-dkms and modprobed-db for a VERY LONG time!

However, once I re-ran: modprobed-db store, it found the three new modules.

Of course, during a subsequent, clean, rebuild of linux-ck, wireguard-dkms was successfully installed.

Thanks for your input graysky, and to the others who offered their comments.

laenco commented on 2019-10-30 22:38 (UTC) (edited on 2019-10-30 22:39 (UTC) by laenco)

@kwe: OK. I'll try to explain.

  1. localmodconfig disables every module, that not exactly listed in provided file

  2. the file modprobed.db filling automatically only by modules that are in memory when modprobed-db service runs.

  3. fou module did not get into the modprobed.db for some reason

  4. But it is needed as indirect dependency for wireguard-dkms

  5. when you build kernel with localmodconfig - fou module become disabled

  6. And consequent build of wireguard-dkms fails.

As I can see - the most simple way to fix such a problem - is to add fou/fou6 modules into modprobed.db manually.

Or - load them and run modprobed-db.service for the same thing.

Blame me, if I wrong, cause there is more coffee than blood in veins)

« First ‹ Previous 1 .. 21 22 23 24 25 26 27 28 29 30 31 .. 308 Next › Last »