Core Update 167 requires additional step for ARM users before rebooting

Hi,

unfortunately, there is still a quirk present in Core Update 167, affecting installations running on ARM: Because the packaged initial ramdisk for u-boot was missing in the update, ARM installations stall on booting after the upgrade, since the kernel version in the ramdisk differs from the actually installed kernel.

Due to capacity constraints and some core developers being unavailable during the QA phase, this bug was unfortunately not fixed while Core Update 167 has still been in testing.

ARM users are therefore strongly advised to run an additional command after having installed Core Update 167, but before rebooting. On 64-bit ARM (aarch64), it is:

cd /boot && mkimage -A arm64 -T ramdisk -C lzma -d initramfs-5.15.35-ipfire.img uInit-5.15.35-ipfire 

32-bit ARM systems require this command instead:

cd /boot && mkimage -A arm -T ramdisk -C lzma -d initramfs-5.15.35-ipfire.img uInit-5.15.35-ipfire 

By this command, a regeneration of the initial ramdisk is forced, including the correct kernel version.

We sincerely apologize for inconveniences caused by this error.

Special thanks go to @arne_f for his efforts on investigating on this front.

Thanks, and best regards,
Peter Müller

4 Likes