You are not logged in.
I do use one OOT kernel module : vhba (required by cdemu-daemon ).
Until now I had the vhba-module package , but lately I have booted several times to linux-lts for testing things.
I installed vhba-dkms and found to my surprise after compiling the modules the initramfs is regenerated by mkinitcpio .
Since the vhba kernel module is only needed (atleast for my usecase) after booting regenerating initramfs is unnecessary .
Is there a possibilty to stop triggering initrams fs regeneration after dkms has compiled vhba against installed kernels ?
Last edited by Lone_Wolf (2025-06-21 13:21:42)
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online
Never tried this, but I suppose you could get rid of the trigger target
Target = usr/src/*/dkms.conffrom /usr/share/libalpm/hooks/90-mkinitcpio-install.hook?
Offline
Looked into that hook and that target is indeed what triggers the regeneration .
I copied /usr/share/libalpm/hooks/90-mkinitcpio-install.hook to /etc/pacman.d/hooks and removed that trigger from the copy .
re-installing vhba-mdule-dkms didn't trigger mkinitcpio regeneration, so it appears to be working.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Online