All of lore.kernel.org
 help / color / mirror / Atom feed
From: Selwyn Tang <selwyn@hectrix.com>
To: linux-mtd@lists.infradead.org
Subject: "init not found" after booting GRUB on DOC
Date: Thu, 07 Aug 2003 15:47:12 +0800	[thread overview]
Message-ID: <3F320400.3000002@hectrix.com> (raw)

Dear all,

I followed Karim's book to put the kernel, modules, root filesystem
(including busybox and tinylogin) and GRUB on a DOC and tried booting
it. The kernel loaded successfully but it ended with a kernel panic of
"no init found". I use this statements in my menu.lst:

   title DiskOnChip 2000
   kernel (dc0,0)/boot/vmlinuz-2.4.21-5x86 ro root=/dev/nftla1

I have busybox's init in /sbin and I also tried adding "init=/sbin/init"
to the above statement but with the same result.

The NFTL driver is built-in and it correctly detects my DOC. The kernel 
also successfully mounts the root filesystem (ext3).

How should I configure GRUB in order to load the busybox's init?

advTHANKSance!

Selwyn

             reply	other threads:[~2003-08-07  7:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-07  7:47 Selwyn Tang [this message]
2003-08-07 10:47 ` "init not found" after booting GRUB on DOC David Woodhouse
2003-08-07 13:15   ` Selwyn Tang

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=3F320400.3000002@hectrix.com \
    --to=selwyn@hectrix.com \
    --cc=linux-mtd@lists.infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.