1Explaining the dreaded "No init found." boot hang message
4OK, so you've got this pretty unintuitive message (currently
located    5in init/main.c) and are wondering what the H*** went
wrong.    6Some high-level reasons for failure (listed roughly
in order of execution)    7to load the init binary are:    8A)
Unable to mount root FS    9B) init binary doesn't exist on
rootfs   10C) broken console device   11D) binary exists but
dependencies not available   12E) binary cannot be loaded
14Detailed explanations:   150) Set "debug" kernel parameter (in
bootloader config file or CONFIG_CMDLINE)   16   to get more
detailed kernel messages.   17A) make sure you have the correct
root FS type   18   (and root= kernel parameter points to the
correct partition),   19   required drivers such as storage
hardware (such as SCSI or USB!)   20   and filesystem (ext3,
jffs2 etc.) are builtin (alternatively as modules,   21   to be
pre-loaded by an initrd)   22C) Possibly a conflict in console=
setup --> initial console u