Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: ralf@uni-koblenz.de
To: William Ellis <bellis@cerf.net>
Cc: Linux porting team <linux@cthulhu.engr.sgi.com>
Subject: Re: boot problem
Date: Thu, 15 Jan 1998 01:26:22 +0100	[thread overview]
Message-ID: <19980115012622.51359@uni-koblenz.de> (raw)
In-Reply-To: <34BD4F3E.7F86@cerf.net>; from William Ellis on Wed, Jan 14, 1998 at 03:50:22PM -0800

On Wed, Jan 14, 1998 at 03:50:22PM -0800, William Ellis wrote:

> I'm working with a Challenge S, R5000 (Allegedly the same
> hardware as an Indy without a graphics card)
> 
> Initially booting via tftp with various errors, I am
> now trying to just get the sash boot -f to work.
> I have tried several of the applicable precompiled kernels 
> at ftp.linux.sgi.com/pub/test all with similar errors:
> 
> Standalone Shell SGI Version 6.2 ARCS   Mar  9, 1996 (32 Bit)
> sash: boot -f /vmlinux root=/dev/sda1
> 1278928+236160 entry: 0x8800250c
> newport_probe: read back wrong value ;-(
> 
> What is the newport_probe?  The only non-stock thing about
> the machine is it has a fddi card in it, (which I do not
> need to get going for linux).  Could this error be an effect
> of the fddi card being present, or that there is no graphics
> card present?  Or am I missing something else all together?

No, the FDDI card is just being ignored by Linux.  The problem is
indeed the fact that the newport GFX card isn't installed.  I'll
take a look at it when I have time for more than one breath
per minute ...

Thinking about it, the kernel should only try to touch the gfx hardware
at all, if the ARC environment variable ``console'' is unset.  If you
want to run from a serial console, then the variable's value should be
either ``d1'' or ``d2'' for the first rsp. second serial interface.
I suppose IRIX just defaults to serial console because it knows that
a Challenge S is headless or after a failed probe for gfx hardware.

William, what is the recommended way to recognice whethere a machine
is a Indy or Challenge S?  Probing for a GFX card or checking via
ARC firmware?

  Ralf

  parent reply	other threads:[~1998-01-15  0:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-01-14 23:50 boot problem William Ellis
1998-01-14 23:55 ` Ariel Faigon
1998-01-14 23:55   ` Ariel Faigon
1998-01-14 23:58 ` Shrijeet Mukherjee
1998-01-15  0:00 ` Charles Marker
1998-01-15  0:00   ` Charles Marker
1998-01-15  0:11 ` Eric Kimminau
1998-01-15  0:26 ` ralf [this message]
1998-01-15  0:56   ` William J. Earl
1998-01-15  5:15     ` ralf
1998-01-15  6:10       ` William J. Earl
1998-01-15  0:34 ` Alan Cox
1998-01-15  0:34   ` Alan Cox

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=19980115012622.51359@uni-koblenz.de \
    --to=ralf@uni-koblenz.de \
    --cc=bellis@cerf.net \
    --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