From: Chad Carlin <chad@otg.dallas.sgi.com>
To: linux@cthulhu.engr.sgi.com
Subject: Re: What kernel to use to install RH on a R4400 ?
Date: Wed, 03 Feb 1999 11:37:22 -0600 [thread overview]
Message-ID: <36B88952.4F3E1CAE@roctane.dallas.sgi.com> (raw)
In-Reply-To: 19990203043951.D3920@uni-koblenz.de
Ralf,
Got a chance to try again last night using a i686 as a bootserver. I got the
same aieee message. Will get you my hinv and my particular register dump.
Chad
ralf@uni-koblenz.de wrote:
> On Tue, Feb 02, 1999 at 03:51:47PM +0100, Alexander Graefe wrote:
>
> > I got as far as booting Linux via bootp on my Indy, but after the
> > remote root-fs is mounted, the kernel dies with an "Aieee" and
> > something about irq request handler.
>
> Ouch. It was actually supposed to work on Indys, regardless of the processor
> type. Since it's no longer working things must somewhow got broken again.
> I'll try to fix it but it's going to be hairy since I don't have an R4400SC
> processor module.
>
> > I tried booting with the 2.1.131-Kernel from ftp.linux.sgi.com, but
> > that one doesn't try to mount the root-fs via NFS.
> >
> > What kernel should I use to actually see a prompt on my Indy ?
>
> Can you send me:
>
> - the exact screen output. Especially the register dump following the
> Aiee message is important.
> - the output of the hinv command. Hinv is an IRIX command.
>
> > Quidquid latine dictum sit, altum viditur.
>
> In nomeni patrii et filiae et spiritus pinguini ;-)
>
> Ralf
--
-----------------------------------------------------
Chad Carlin Special Systems
Silicon Graphics Inc. 972.205.5911
Pager 888.754.1597 VMail 800.414.7994 X5344
chad@sgi.com http://reality.sgi.com/chad
-----------------------------------------------------
"flying through hyper space ain't like dusting crops, boy"
next prev parent reply other threads:[~1999-02-03 17:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-02 14:51 What kernel to use to install RH on a R4400 ? Alexander Graefe
1999-02-02 18:20 ` Chad Carlin
1999-02-02 18:30 ` Shrijeet Mukherjee
1999-02-02 19:12 ` Chad Carlin
1999-02-03 3:42 ` ralf
1999-02-02 20:26 ` Jonas Vis
1999-02-02 18:21 ` Alex deVries
1999-02-03 3:39 ` ralf
1999-02-03 17:37 ` Chad Carlin [this message]
1999-02-04 14:46 ` Alexander Graefe
1999-02-05 2:48 ` ralf
1999-02-05 4:51 ` Alexander Graefe
1999-02-05 21:26 ` Thomas Bogendoerfer
1999-02-05 21:42 ` Chad Carlin
1999-02-12 3:04 ` Chad Carlin
1999-02-12 10:16 ` Thomas Bogendoerfer
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=36B88952.4F3E1CAE@roctane.dallas.sgi.com \
--to=chad@otg.dallas.sgi.com \
--cc=chad@sgi.com \
--cc=linux@cthulhu.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