From: "Mark A. Zottola" <asnmaz01@asc.edu>
To: Eric Melville <m_thrope@rigelfore.com>
Cc: chad@sgi.com, SGI Linux <linux@cthulhu.engr.sgi.com>
Subject: Re: able to bootp/NFS-install/reboot R4400SC Indy
Date: Mon, 22 Feb 1999 20:23:48 -0600 [thread overview]
Message-ID: <36D21134.B11129C1@asc.edu> (raw)
In-Reply-To: 36D1E0B9.F62F10E4@rigelfore.com
Actually we are running into the same problem as we attempt to port Linux to the
Indigo2. Does anyone know where we can get the list of errata for the R4400
revision 6.0? That info is not currently available upon SGI's web pages... Any
pointers to this information (or a copy of same) would be greatly appreciated!
Mark
Eric Melville wrote:
> does your hinv say R4400 revision 6.0? if so, let me know which kernel
> you've booted, because i havn't found any that don't hang during boot :(
>
> -E
>
> > I got my 200MHz R4400 working too. Yes it actually boots. I guess you guys
> > weren't making all this stuff up after all.
--
*********
Mark A. Zottola Alabama Research and Education Network
119 Rust Research Center Nichols Research Corporation
University of Alabama-Birmingham VOICE: (205) 934-3893
Birmingham, AL 35294 EMAIL: asnmaz01@csimail.asc.edu
next prev parent reply other threads:[~1999-02-23 2:21 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
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 [this message]
[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=36D21134.B11129C1@asc.edu \
--to=asnmaz01@asc.edu \
--cc=chad@sgi.com \
--cc=linux@cthulhu.engr.sgi.com \
--cc=m_thrope@rigelfore.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