update-initramfs does not fully create initrd for new kernel

I seem to be having a bizarre problem installing a new custom kernel. update-initramfs fails during dpkg -i with: update-initramfs: Generating /boot/initrd.img-5.15.7-hardened1-test1 find: ‘/tmp/user/0/mkinitramfs_gHxWMQ/lib/modules/5.15.7-hardened1-test1/kernel’: No such file or directory Generating grub configuration file ... Found linux image: /boot/vmlinuz-5.15.7-hardened1-r7 Found initrd image: /boot/initrd.img-5.15.7-hardened1-r7 Found linux image: /boot/vmlinuz-5.15.7-hardened1-test1 Found initrd image: /boot/initrd.img-5.15.7-hardened1-test1 Found linux image: /boot/vmlinuz-5.10.0-10-amd64 Found initrd image: /boot/initrd.img-5.10.0-10-amd64 done The r7 kernel builds and installs perfectly fine, but the test1 installs with a find: ‘/tmp/user/0/mkinitramfs_gHxWMQ/lib/modules/5.15.7-hardened1-test1/kernel’: No such file or directory error. The only difference between the .configs is: 29c29 CONFIG_LOCALVERSION="-test1" 39c39 # CONFIG_KERNEL_GZIP is not set 45c45 CONFIG_KERNEL_ZSTD=y 787c787 CONFIG_MODULE_FORCE_UNLOAD=y 802,803c802,803 # CONFIG_MODULE_COMPRESS_XZ is not set > CONFIG_MODULE_COMPRESS_ZSTD=y I even tried a slightly newer kernel (5.15.27) and older (5.10.104) with the same results. Trying to boot into the kernel drops the boot to a initramfs prompt (without USB keyboard functionality) after failing to find the root LVM. The initrd images also have very different sizes for the minimal changes made: 9.7M initrd.img-5.15.7-hardened1-r7 (working) 9.1M initrd.img-5.15.7-hardened1-test1 (broke) Doing a diff between the two with lsinitrd produces this, suggesting that the initrd does indeed lack a huge number of modules. 346,399c346 5.15.7-hardened1-test1 Anyone seen this before? I found one results through google but a solution was never provided. I'm running Devuan Chimaera (Debian 11 base) with: initramfs-tools=0.140 & dpkg=1.20.9