From: Wolfgang Denk <wd@denx.de>
To: "Pagnotta, Chris" <chris.pagnotta@viasat.com>
Subject: Re: NFS root woes: No init found
Date: Sat, 07 Dec 2002 12:02:07 +0100 [thread overview]
Message-ID: <200212071104.FAA32694@lists.linuxppc.org> (raw)
In-Reply-To: Your message of "Fri, 06 Dec 2002 17:36:27 PST." <0509218DDAD7D6118055006008F6D5F6A1E39A@postal.viasat.com>
In message <0509218DDAD7D6118055006008F6D5F6A1E39A@postal.viasat.com> you wrote:
>
> I am having a problem with NFS mounting the root filesystem. It seems that
> init
> is not being executed. However, the problem may be with rootpath not being
> set.
> Should that parameter be set from the kernel command nfsroot=?
What are you talking about?
> Kernel command line: root=/dev/nfs nfsroot=/tftpboot/powerpc-rootfs
> ip=172.25.59
> .11:172.25.59.15::255.255.0.0:vib::off
Your rootpath _is_ set here: you're using "/tftpboot/powerpc-rootfs"
as root directory.
...
> Looking up port of RPC 100003/2 on 172.25.59.15
> Looking up port of RPC 100005/1 on 172.25.59.15
> VFS: Mounted root (nfs filesystem).
And the root filesystem was found and mounted.
> Mounted devfs on /dev
> Freeing unused kernel memory: 212k init
> Kernel panic: No init found. Try passing init= option to kernel.
Are you sure you NEED devfs here? For now I recommend to disable this
option, as it adds just additional complexity. To anlyze what's going
on with your NFS root filesystem, run a network sniffer (like
ethereal) and check wich accesses work, and which are failing.
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Imagination is more important than knowledge. -- Albert Einstein
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-07 11:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-07 1:36 NFS root woes: No init found Pagnotta, Chris
2002-12-07 11:02 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-04 21:35 Brian Waite
2002-12-04 21:48 ` Dan Malek
2002-12-04 22:11 ` Brian Waite
2002-12-04 22:20 ` Wolfgang Grandegger
2002-12-04 22:30 ` Brian Waite
2002-12-04 22:47 ` Jerry Van Baren
2002-12-04 23:03 ` Brian Waite
2002-12-04 22:49 ` Roland Dreier
2002-12-04 22:52 ` Brian Waite
2002-12-04 22:27 ` Roland Dreier
2002-12-04 22:36 ` Brian Waite
2002-12-05 8:50 ` Dan Vatca
2002-12-05 15:20 ` Brian Waite
2002-12-05 15:58 ` Allen Curtis
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=200212071104.FAA32694@lists.linuxppc.org \
--to=wd@denx.de \
--cc=chris.pagnotta@viasat.com \
/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).