All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brendan Simon <bsimon@ctam.com.au>
Cc: linuxppc-embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: linuxppc-embedded: /bin/sh wont run from nfsroot.
Date: Thu, 16 Dec 1999 09:40:34 +1100	[thread overview]
Message-ID: <385818E1.D64FCFD6@ctam.com.au> (raw)
In-Reply-To: 385774B8.3405494B@iname.com


Jim Chapman wrote:

> Make sure your 860 is a rev C part or higher. If it isn't, forget trying
> to use the cache.
>
> Your CPU is a regular 8xx, not a 'P' (performance) variant, right? The
> latter has "optimized" cache hardware that isn't (yet?) supported by
> linuxppc.

It's an XPC860SRZP50C1.  I have another board with no ethernet which has an
XPC860ZP33C1 or an XPC860DEZP25A3 (this is on an older board).

The XPC860SRZP50C1 is a SAR processor though we are not using any of the SAR
capabilities on this board.  I hope this processor is fine.


> Do you have a /bin/sh on your initrd? You'll need the shared libraries
> too.

I think the one I have is statically linked so I shouldn't need any shared
libraries.  It is the one that is in the mbx-root-min.tgz file.  The shell works
fine if I use initrd so it should work fine from an nfsroot (I would assume).


> Also, try running your NFS server in the foreground in a debug mode if
> it isn't being used by other hosts. This will display exactly what files
> are being accessed. You should see lots of directories, shared libraries
> etc being read. I use
>
> # rpc.nfsd -F -d call
>
> but obviously kill any running nfsd first.

Now there is a good idea.  It's so obvious.  Why didn't I think of that.
Thanks.

Brendan Simon.


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

  parent reply	other threads:[~1999-12-15 22:40 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-12-15  5:55 linuxppc embedded boot problems Brian Kuschak
1999-12-15  5:22 ` linuxppc-embedded: /bin/sh wont run from nfsroot Brendan Simon
1999-12-15 11:00   ` Jim Chapman
1999-12-15 18:56     ` Alan Mimms
1999-12-15 20:09       ` Dan Malek
1999-12-15 21:27         ` Richard Hendricks
1999-12-15 21:37           ` Alan Mimms
1999-12-15 22:13             ` Dan Malek
1999-12-16 14:52             ` Richard Hendricks
1999-12-15 19:24     ` Dan Malek
1999-12-15 23:10       ` linuxppc-embedded: memory map question Brendan Simon
1999-12-16  9:37       ` linuxppc-embedded: programs wont run from nfsroot Brendan Simon
1999-12-15 22:40     ` Brendan Simon [this message]
1999-12-16  0:24     ` linuxppc-embedded: /bin/sh " Brendan Simon
1999-12-16  2:17       ` Brendan Simon
1999-12-15 19:11   ` Dan Malek
     [not found]   ` <ot66y035bv.fsf@thinktwice.zoftcorp.dk>
1999-12-15 22:29     ` Brendan Simon
1999-12-15 19:06 ` linuxppc embedded boot problems Dan Malek
1999-12-15 22:56   ` Brendan Simon
1999-12-16  5:03     ` Dan Malek

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=385818E1.D64FCFD6@ctam.com.au \
    --to=bsimon@ctam.com.au \
    --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 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.