LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "yah" <hay8888@21cn.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: not found init
Date: Tue, 04 Sep 2001 10:21:03 +0200	[thread overview]
Message-ID: <20010904082108.6AD4610CC2@denx.denx.de> (raw)
In-Reply-To: Your message of "Tue, 04 Sep 2001 15:41:09 +0800." <ZD989095845890.21633@webmail1.inner-21cn.com>


In message <ZD989095845890.21633@webmail1.inner-21cn.com> you wrote:
>
> Hi. I use linuxppc_2_4 from penguinppc.org. I rebuild the
> kernel,and use it to boot my board(mcp750).It said 'Kernel panic: No
> init found. Try passing init= option to kernel'.I didn't find the
> item about CONFIG_SASH and CONFIG_SASH_PATH. /dev/console and

These are no config options of the standard  Linux  kernel;  you  can
find these extensions in the source trees on our FTP server, but they
were  never  generally  accepted  because you can do more or less the
same by specitying an "init=" boot option.

> /bin/init exist. and I didn't cut out the lib. I use 'root=/dev/ram0'
> in kernel command line. What's wrong? Could you give me some advice?

Not with the little information you provide. Try running a statically
linked shell instead of init. For instance,  add  /bin/sash  to  your
ramdisk  image,  and  pass  "init=/bin/sash"  as boot argument to the
Linux kernel.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
When the bosses talk about improving  productivity,  they  are  never
talking about themselves.

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2001-09-04  8:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-04  7:41 not found init yah
2001-09-04  8:21 ` Wolfgang Denk [this message]

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=20010904082108.6AD4610CC2@denx.denx.de \
    --to=wd@denx.de \
    --cc=hay8888@21cn.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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