All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chad Carlin <chad@dallas.sgi.com>
To: ralf@uni-koblenz.de, Alexander Graefe <nachtfalke@usa.net>,
	adevries@engsoc.carleton.ca
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: What kernel to use to install RH on a R4400 ?
Date: Thu, 11 Feb 1999 21:04:58 -0600	[thread overview]
Message-ID: <36C39A50.6EE8E619@dallas.sgi.com> (raw)
In-Reply-To: 19990205034821.A620@uni-koblenz.de

Ralf and all,

Now I'm in a jam. I can't use these instructions:

irix-indy #./mke2fs drive
irix-indy #./installer drive
  cjwsh> MAKEDEV
  cjwsh> cpio root-be-0.04.cpio
  [piles of cpio extraction information]
  cjwsh> exit
  [ a moderately lengthy pause, and possibly a bus error -- don't worry
    about it ]
 irix-indy #

to make the root filesystem on the indy because I can't make the device files
with proper major|minor numbers from the installer utility from IRIX. Since
nfsroot directive does not work on .131 and R4400 doesn't work on any other
kernels, I think I'm up against a brick wall. Anyone have any ideas.

Any chance of fixing nfsroot in the .131 kernel? I think that might get me
there.

Bootless,
Chad

ralf@uni-koblenz.de wrote:

> On Thu, Feb 04, 1999 at 03:46:37PM +0100, Alexander Graefe wrote:
>
> > On Wed, Feb 03, 1999 at 04:39:51AM +0100, ralf@uni-koblenz.de wrote:
> >
> > >  - the exact screen output.  Especially the register dump following the
> > >    Aiee message is important.
> >
> > kernel 2.1.100 (the one from the HardHat.tgz)
>
> 2.1.100 is known to fail on R4400.  This is supposed to be fixed in .131
> which is why I'm worried about the other bug report.  Your case is obvious -
> use a newer kernel.
>
>   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"

  parent reply	other threads:[~1999-02-12  3:13 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
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 [this message]
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=36C39A50.6EE8E619@dallas.sgi.com \
    --to=chad@dallas.sgi.com \
    --cc=adevries@engsoc.carleton.ca \
    --cc=chad@sgi.com \
    --cc=linux@cthulhu.engr.sgi.com \
    --cc=nachtfalke@usa.net \
    --cc=ralf@uni-koblenz.de \
    /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.