From: Mark Hatle <fray@mvista.com>
To: Toni Van Remortel <t.vanremortel@ha.be>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: EP405 Kernel Panic
Date: Wed, 02 Apr 2003 09:23:04 -0600 [thread overview]
Message-ID: <3E8B0058.4030503@mvista.com> (raw)
In-Reply-To: <20030402140215.47965273.t.vanremortel@ha.be>
This comes up weekly on the mailing list, if you search the archives you'll find
the canned response:
Make sure you have all of the libraries required by your shell. If there are
missing libraries it will return back no init found.
Use objdump or ldd to get a list of the required libraries. (At the minimum you
will need /lib/ld.so and /lib/libc.so.) Alternative is to statically link your
shell.
--Mark
> RAMDISK: Compressed image found at block 0
> Freeing initrd memory: 1771k freed
> VFS: Mounted root (ext2 filesystem) readonly.
> Freeing unused kernel memory: 76k init
> Kernel panic: No init found. Try passing init= option to kernel.
>
>
> So as you can see, the kernel parameters are root=/dev/ram
> init=/bin/bash, but why does the kernel panic on No init!?
> /bin/bash does exist in the initrd.
>
> Anybody an idea where to look?
>
> # file bin/bash
> bin/bash: ELF 32-bit MSB executable, PowerPC or cisco 4500, version 1 (SYSV), for GNU/Linux 2.2.5, dynamically linked (uses shared libs), stripped
> Needed libs are in /lib.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-04-02 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-02 12:02 EP405 Kernel Panic Toni Van Remortel
2003-04-02 15:23 ` Mark Hatle [this message]
2003-04-03 8:26 ` Toni Van Remortel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3E8B0058.4030503@mvista.com \
--to=fray@mvista.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=t.vanremortel@ha.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).