From: Roland Dreier <roland@topspin.com>
To: Brian Waite <waite@skycomputers.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: NFS root woes: No init found
Date: 04 Dec 2002 14:27:46 -0800 [thread overview]
Message-ID: <52bs41besd.fsf@topspin.com> (raw)
In-Reply-To: <200212041635.31861.waite@skycomputers.com>
>>>>> "Brian" == Brian Waite <waite@skycomputers.com> writes:
Brian> Hi, I am attempting to boot up a custom PPC board and
Brian> having problems with the NFS Root. the board has a single
Brian> 74xx PPC and Galileo memory controller. What happens is
Brian> everything looks good until I attempt to read init from the
Brian> NFS root. Then I get the message No init found. I have
Brian> tried the obvious things such as changing init for a
Brian> staticly linked executable, to no avail. I have enabled NFS
Brian> debug and it looks like I have mounted the remote fs just
Brian> fine.
One thing that sometimes helps in debugging these problems is to use
an ethernet sniffer to see what your target is really getting from the
NFS server. You can use something like "tcpdump -vvv -s 1500", or
something fancier like ethereal. Then you can see whether the target
ever even tries to read the init file, etc.
Best,
Roland
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-12-04 22:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-04 21:35 NFS root woes: No init found 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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2002-12-07 1:36 Pagnotta, Chris
2002-12-07 11:02 ` Wolfgang Denk
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=52bs41besd.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=waite@skycomputers.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).