![]() ![]() ![]() rwxr-xr-x 1 root root 8.3K Nov 18 16:22 fixup4db.dat rwxr-xr-x 1 root root 5.3K Nov 18 16:22 fixup4.dat rwxr-xr-x 1 root root 3.2K Nov 18 16:22 fixup4cd.dat rwxr-xr-x 1 root root 2.5K Apr 26 14:40 boot.scr rwxr-xr-x 1 root root 67 Apr 26 14:40 boot.mk rwxr-xr-x 1 root root 52K Nov 18 16:22 bootcode.bin rwxr-xr-x 1 root root 2.4K Apr 26 14:40 boot.cmd The director contents are drwxr-xr-x 3 root root 16K. Mkimage: Can’t open initramfs-5.15.35-ipfire.img: No such file or directory Mkimage -A arm -T ramdisk -C lzma -d initramfs-5.15.35-ipfire.img uInit-5.15.35-ipfire Special thanks go to for his efforts on investigating on this front. We sincerely apologize for inconveniences caused by this error. 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ģ2-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īy this command, a regeneration of the initial ramdisk is forced, including the correct kernel version. ![]() 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.ĭue 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.ĪRM users are therefore strongly advised to run an additional command after having installed Core Update 167, but before rebooting. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |