From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Eric Melville <m_thrope@rigelfore.com>,
Joan Eslinger <wombat@kilimanjaro.engr.sgi.com>
Cc: Alex deVries <adevries@engsoc.carleton.ca>,
SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: able to bootp/NFS-install/reboot R4400SC Indy
Date: Sat, 20 Feb 1999 01:52:51 +0100 [thread overview]
Message-ID: <19990220015251.A3878@alpha.franken.de> (raw)
In-Reply-To: <36CBB931.D552C44@rigelfore.com>; from Eric Melville on Wed, Feb 17, 1999 at 10:54:41PM -0800
On Wed, Feb 17, 1999 at 10:54:41PM -0800, Eric Melville wrote:
> wait a sec, this is almost identical to mine! R4400 revision 6.0 ... the
> only difference i see is that mine was 200 mhz. what's up with this?
> please, i'd love to get this thing booted so that i can start helping
> with the porting efforts!
I doubt, that your problem is clock rate related. What does your
NFS root look like. Are you using the HardHat root filesystem ?
What type of NFS box are you using ?
Thomas.
--
This device has completely bogus header. Compaq scores again :-|
It's a host bridge, but it should be called ghost bridge instead ;^)
[Martin `MJ' Mares on linux-kernel]
next prev parent reply other threads:[~1999-02-20 1:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-17 6:27 able to bootp/NFS-install/reboot R4400SC Indy Joan Eslinger
1999-02-17 6:43 ` Eric Melville
1999-02-17 7:08 ` Alex deVries
1999-02-17 7:14 ` Joan Eslinger
1999-02-18 6:54 ` Eric Melville
1999-02-20 0:52 ` Thomas Bogendoerfer [this message]
1999-02-20 10:08 ` Eric Melville
[not found] ` <9902181451.ZM96@chaos.boston.sgi.com>
1999-02-20 10:04 ` Eric Melville
1999-02-22 18:14 ` Chad Carlin
1999-02-22 22:56 ` Eric Melville
1999-02-23 2:23 ` Mark A. Zottola
[not found] ` <19990223000909.B502@uni-koblenz.de>
1999-02-23 1:28 ` Chad Carlin
1999-02-23 5:20 ` Chad Carlin
1999-02-23 6:21 ` Alex deVries
1999-02-23 15:51 ` Chad Carlin
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=19990220015251.A3878@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=adevries@engsoc.carleton.ca \
--cc=linux@cthulhu.engr.sgi.com \
--cc=m_thrope@rigelfore.com \
--cc=wombat@kilimanjaro.engr.sgi.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