https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/114 got merged after some iterations. This can be a breaking change. To restore the previous behavior, call `apply_add_modules` without arguments after a `manual_add_modules` call.
I checked all Ubuntu source packages that call manual_add_modules for possible regressions:
``` ac100-tarball-installer amd64-microcode aoetools asahi-scripts autopkgtest bcachefs-tools bcache-tools bilibop bootcd brltty casper clevis cloud-initramfs-tools cryptsetup dmraid flashcache fsprotect fuse fuse3 initramfs-tools initramfs-tools-ubuntu-core intel-microcode librem-ec-acpi live-boot ltsp lvm2 miniramfs multipath-tools mythbuntu-diskless nbd nvidia-graphics-drivers-384 olpc-xo1 open-infrastructure-system-boot open-infrastructure-system-tools open-iscsi open-vm-tools osk-sdl r8168 rapiddisk s390-tools sysconfig tcos thin-provisioning-tools unl0kr v86d zfcpdump-kernel zfs-linux ```
amd64-microcode and initramfs-tools have following snippet:
``` if dpkg --compare-versions "${version}" lt 4.4 ; then manual_add_modules microcode && { # force_load has broken semanthics when the .ko file is missing find "${DESTDIR}/${MODULESDIR}" -type f -print | grep -qc '/microcode\.ko$' && { verbose "modular microcode driver detected" force_load microcode } } fi ```
Ubuntu 16.04 LTS "Xenial Xerus" comes with Linux 4.4. Let's assume that we do not support kernel version < 4.4 in Ubuntu 24.04 LTS "Noble Numbat".
miniramfs just uses parts from initramfs-tools and need to call `apply_add_modules`.
https:/ /salsa. debian. org/kernel- team/initramfs- tools/- /merge_ requests/ 114 got merged after some iterations. This can be a breaking change. To restore the previous behavior, call `apply_add_modules` without arguments after a `manual_ add_modules` call.
I checked all Ubuntu source packages that call manual_add_modules for possible regressions:
``` installer -tools tools-ubuntu- core graphics- drivers- 384 ture-system- boot ture-system- tools ng-tools
ac100-tarball-
amd64-microcode
aoetools
asahi-scripts
autopkgtest
bcachefs-tools
bcache-tools
bilibop
bootcd
brltty
casper
clevis
cloud-initramfs
cryptsetup
dmraid
flashcache
fsprotect
fuse
fuse3
initramfs-tools
initramfs-
intel-microcode
librem-ec-acpi
live-boot
ltsp
lvm2
miniramfs
multipath-tools
mythbuntu-diskless
nbd
nvidia-
olpc-xo1
open-infrastruc
open-infrastruc
open-iscsi
open-vm-tools
osk-sdl
r8168
rapiddisk
s390-tools
sysconfig
tcos
thin-provisioni
unl0kr
v86d
zfcpdump-kernel
zfs-linux
```
amd64-microcode and initramfs-tools have following snippet:
``` add_modules microcode && { /${MODULESDIR} " -type f -print | grep -qc '/microcode\.ko$' && {
force_ load microcode
if dpkg --compare-versions "${version}" lt 4.4 ; then
manual_
# force_load has broken semanthics when the .ko file is missing
find "${DESTDIR}
verbose "modular microcode driver detected"
}
}
fi
```
Ubuntu 16.04 LTS "Xenial Xerus" comes with Linux 4.4. Let's assume that we do not support kernel version < 4.4 in Ubuntu 24.04 LTS "Noble Numbat".
miniramfs just uses parts from initramfs-tools and need to call `apply_ add_modules` .