Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Eric Melville <m_thrope@rigelfore.com>
To: sgi <linux@cthulhu.engr.sgi.com>
Subject: Re: 200mhz indy
Date: Sun, 18 Jul 1999 12:18:17 -0700	[thread overview]
Message-ID: <37922879.C3136AE3@rigelfore.com> (raw)
In-Reply-To: 19990628131216.C735@uni-koblenz.de

ok, this morning i successfully booted my r4400 rev. 6.0 indy! thanks
for the help... but now i've got a problem installing it. i'm a little
low on disk space for the whole hardhat archive. i was thinking i could
dump the rpms to a cd and then hook me external scsi cdrom to the indy,
however the root fs for hardhat setup seems to be missing mount, plus i
don't know if the redhat installer can be "tricked" like that (i have NO
redhat experience).

-E

> > i have an r4400 revision 6 200mhz indy. i tried to get linux working at
> > about the time the 2.2.1 kernel was released, but it wouldn't go. any
> > chance i'd have better luck now?
> 
> Yes, we've fixed a bug freeing memory used by the PROMs and I'm almost
> certain that this bug caused your 6.0 machine to freeze.
> 
> Iff that still doesn't help, could you do some experiment for me?  I want
> to know if the problem is really related to the CPU version 6.0 and you
> seem to have multiple Indys.  Could just try and put the R4400 6.0 module
> into the Indy which seems to be fine with Linux and report your findings?

  reply	other threads:[~1999-07-18 19:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-25 17:33 200mhz indy Eric Melville
1999-06-28 11:12 ` Ralf Baechle
1999-07-18 19:18   ` Eric Melville [this message]
1999-07-19 13:30     ` Edwin Hakkennes
1999-07-19 13:30       ` Edwin Hakkennes
1999-07-19 22:00       ` Ralf Baechle
1999-07-19 22:17         ` Alex deVries
1999-07-20 22:49           ` Ralf Baechle

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=37922879.C3136AE3@rigelfore.com \
    --to=m_thrope@rigelfore.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