From: Magnus Damm <eramdam@kieray1.p.y.ki.era.ericsson.se>
To: linuxppc-dev@lists.linuxppc.org
Subject: FADS860 nfsroot
Date: Tue, 9 Feb 1999 13:12:53 +0100 (MET) [thread overview]
Message-ID: <199902091212.NAA23161@kieray1> (raw)
Anyone else with embedded 860 linux that has problems with nfsroot?
The zImage.fads-2.1.127 hangs for me right when it's supposed to display
"bash#"
My MBX-board works just fine with nfsroot connected to the same server.
I haven't made any deep investigation about the FADS case above yet,
but I suspect that it is the same problem as I've got with my ADS board.
It booted with initrd and I could even mount nfs with "mount -t nfs".
But nfsroot didn't work.
I've made some printouts to see what happens when "/bin/sh" is loaded,
and run the new kernel on both the MBX and the ADS board.
They start doing the same thing but after a while the ADS code goes wild
and opens some directory and differs completly from the MBX board.
Then it hangs.
I've thought that my crosscompiler
(ppc-linux-gnu-gcc -dumpversion gives egcs-2.91.57)
was a bit buggy, but now when I've downloaded the zImage directly from the
embedded directory and my board hangs, I don't know what to belive...
It might be my FADS board that sucks?
I've got a PILOT motherboard and a PILOT 860Tboard.
On the list the 12-Jan Dan Malek tells us that his FADS board has problems
using anything else than initrd.
I'm using a hacked version fadsrom which uses a msdos partitiontable
instead of OSF to boot the zImage.fads-2.1.127 from a compact flash card.
Anyone with similar problems?
Anyone out there with a ADS-board?
TIA /
Magnus
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-02-09 12:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199902091212.NAA23161@kieray1 \
--to=eramdam@kieray1.p.y.ki.era.ericsson.se \
--cc=linuxppc-dev@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.