sun4i - Can't start /init (initramfs issue?)

myxal · February 15, 2020 at 1:35 PM

Trying to get the MELE A1000 box up and running, the kernel panics when trying to start the early userspace: mybuild_klog.txt

Code

[    3.301289] Run /init as init process
[    3.307300] Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004
[    3.314970] ---[ end Kernel panic - not syncing: Attempted to kill init! exitcode=0x00000004 ]---

I built the image myself, from jernej 's mele branch (PROJECT=Allwinner ARCH=arm DEVICE=A20 UBOOT_SYSTEM=mele make image). I'm unable to confirm that the KERNEL file contains a valid initramfs. I have found initramfs.cpio among the build artefacts, and that does look like it should work:

/bin/sh links to /usr/bin/busybox
busybox present, compiled for 32bit ARM EABI5
/init script present

Any suggestions how to troubleshoot this, or what else I should check?

Building whole image with DEBUG=yes?
Adding set -x at the very beginning of init and rebuilding an image with this change?

I'm new to building LibreELEC, what would I need to clean to make either of these changes apply in the resulting image?

**jernej** · February 16, 2020 at 9:20 AM Official Post

Quote from myxal

what would I need to clean to make either of these changes apply in the resulting image?

for second one you need just to rebuild busybox package, but for first one I suggest you rebuild whole image.

**jernej** · February 16, 2020 at 9:22 AM Official Post

uh, A10 is Cortex-A8, but A20 is Cortex-A7. So probably A10 really needs new device type with proper CPU settings. I'll rework project a bit and upload new test image.

sun4i - Can't start /init (initramfs issue?)

Similar Threads

How helpful will this be to getting LibreELEC on allwinner android boxes?

Tanix TX6