I noticed the rootfs has 64-bit executables and the kernel is 32-bit so I have now rebuild the "appfs" partition using 32bit buildroot config and with the same kernel as the buildroot project that creates the signed boot partition.
Here is the appfs /sbin/initHere is lib/ld-linux-armhf.so.3
I have also removed the changes to /init, so there is no encryption.
Here is the contents of /init in the initramfs.
I set root=/dev/mmcblk0p2 in cmdline.txt.
On boot I still get a kernel panic.
Here is the appfs /sbin/init
Code:
$ file sbin/initsbin/init: symbolic link to ../lib/systemd/systemd$ file lib/systemd/systemdlib/systemd/systemd: ELF 32-bit LSB pie executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux-armhf.so.3, for GNU/Linux 5.15.0, stripped
Code:
$ file lib/ld-linux-armhf.so.3 lib/ld-linux-armhf.so.3: ELF 32-bit LSB shared object, ARM, EABI5 version 1 (SYSV), static-pie linked, not stripped
Here is the contents of /init in the initramfs.
Code:
#!/bin/sh# devtmpfs does not get automounted for initramfs/bin/mount -t devtmpfs devtmpfs /dev# use the /dev/console device node from devtmpfs if possible to not# confuse glibc's ttyname_r().# This may fail (E.G. booted with console=), and errors from exec will# terminate the shell, so use a subshell for the testif (exec 0</dev/console) 2>/dev/null; then exec 0</dev/console exec 1>/dev/console exec 2>/dev/consolefiexec /sbin/init "$@"
On boot I still get a kernel panic.
Statistics: Posted by BerryPiUser — Wed Mar 06, 2024 8:37 pm