Orange Pi5 kernel

^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  1) Explaining the "No working init found." boot hang message
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  2) =========================================================
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  3) :Authors: Andreas Mohr <andi at lisas period de>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  4)           Cristian Souza <cristianmsbr at gmail period com>
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  5) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  6) This document provides some high-level reasons for failure
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  7) (listed roughly in order of execution) to load the init binary.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  8) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300  9) 1) **Unable to mount root FS**: Set "debug" kernel parameter (in bootloader
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 10)    config file or CONFIG_CMDLINE) to get more detailed kernel messages.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 11) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 12) 2) **init binary doesn't exist on rootfs**: Make sure you have the correct
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 13)    root FS type (and ``root=`` kernel parameter points to the correct
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 14)    partition), required drivers such as storage hardware (such as SCSI or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 15)    USB!) and filesystem (ext3, jffs2, etc.) are builtin (alternatively as
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 16)    modules, to be pre-loaded by an initrd).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 17) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 18) 3) **Broken console device**: Possibly a conflict in ``console= setup``
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 19)    --> initial console unavailable. E.g. some serial consoles are unreliable
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 20)    due to serial IRQ issues (e.g. missing interrupt-based configuration).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 21)    Try using a different ``console= device`` or e.g. ``netconsole=``.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 22) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 23) 4) **Binary exists but dependencies not available**: E.g. required library
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 24)    dependencies of the init binary such as ``/lib/ld-linux.so.2`` missing or
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 25)    broken. Use ``readelf -d <INIT>|grep NEEDED`` to find out which libraries
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 26)    are required.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 27) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 28) 5) **Binary cannot be loaded**: Make sure the binary's architecture matches
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 29)    your hardware. E.g. i386 vs. x86_64 mismatch, or trying to load x86 on ARM
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 30)    hardware. In case you tried loading a non-binary file here (shell script?),
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 31)    you should make sure that the script specifies an interpreter in its
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 32)    shebang header line (``#!/...``) that is fully working (including its
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 33)    library dependencies). And before tackling scripts, better first test a
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 34)    simple non-script binary such as ``/bin/sh`` and confirm its successful
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 35)    execution. To find out more, add code ``to init/main.c`` to display
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 36)    kernel_execve()s return values.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 37) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 38) Please extend this explanation whenever you find new failure causes
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 39) (after all loading the init binary is a CRITICAL and hard transition step
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 40) which needs to be made as painless as possible), then submit a patch to LKML.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 41) Further TODOs:
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 42) 
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 43) - Implement the various ``run_init_process()`` invocations via a struct array
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 44)   which can then store the ``kernel_execve()`` result value and on failure
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 45)   log it all by iterating over **all** results (very important usability fix).
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 46) - Try to make the implementation itself more helpful in general, e.g. by
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 47)   providing additional error messages at affected places.
^8f3ce5b39 (kx 2023-10-28 12:00:06 +0300 48)