Peter,
How do I tell when this makes it into the CU 168 testing build? (The one that Pakfire will pickup & install)
I will can test this on the Raspberry Pi RPi4B and on the FriendlyArm R2S
Jon
On May 12, 2022, at 12:41 PM, Peter Müller peter.mueller@ipfire.org wrote:
On systems that have previously running on testing, kernel 5.15.32 might still be installed. dracut being called with ${KVER} will then build an inital ramdisk for the wrong kernel, as 5.15.32 might still be running, albeit 5.15.35 has been installed due to the Pakfire procedure when upgrading on testing.
Due to lack of hardware, this patch is untested on ARM.
https://lists.ipfire.org/pipermail/development/2022-May/013433.html
Reported-by: Stefan Schantl stefan.schantl@ipfire.org Signed-off-by: Peter Müller peter.mueller@ipfire.org
config/rootfiles/core/168/update.sh | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/config/rootfiles/core/168/update.sh b/config/rootfiles/core/168/update.sh index d21f648dd..7cc8800b2 100644 --- a/config/rootfiles/core/168/update.sh +++ b/config/rootfiles/core/168/update.sh @@ -107,14 +107,14 @@ chmod -v 750 /etc/sudoers.d chmod -v 640 /etc/sudoers.d/*
# Rebuild initial ramdisk to apply microcode updates -dracut --regenerate-all --force +dracut --kver="5.15.35-ipfire" --regenerate-all --force case "$(uname -m)" in armv*)
mkimage -A arm -T ramdisk -C lzma -d /boot/initramfs-${KVER}-ipfire.img /boot/uInit-${KVER}-ipfirerm /boot/initramfs-${KVER}-ipfire.img
mkimage -A arm -T ramdisk -C lzma -d /boot/initramfs-5.15.35-ipfire.img /boot/uInit-5.15.35-ipfirerm /boot/initramfs-5.15.35-ipfire.img ;; aarch64)
mkimage -A arm64 -T ramdisk -C lzma -d /boot/initramfs-${KVER}-ipfire.img /boot/uInit-${KVER}-ipfire
mkimage -A arm64 -T ramdisk -C lzma -d /boot/initramfs-5.15.35-ipfire.img /boot/uInit-5.15.35-ipfire # dont remove initramfs because grub need this to boot. ;;esac
2.35.3