From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: bellis@cerf.net (William Ellis)
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: boot problem
Date: Wed, 14 Jan 1998 15:55:29 -0800 (PST) [thread overview]
Message-ID: <199801142355.PAA09106@oz.engr.sgi.com> (raw)
In-Reply-To: <34BD4F3E.7F86@cerf.net> from "William Ellis" at Jan 14, 98 03:50:22 pm
:
: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?
:Thanks in Advance, Bill
:
Newport == Indy graphics
So I guess the code should be changed so it doesn't assume
there's a newport hardware.
--
Peace, Ariel
WARNING: multiple messages have this Message-ID (diff)
From: ariel@oz.engr.sgi.com (Ariel Faigon)
To: William Ellis <bellis@cerf.net>
Cc: linux@cthulhu.engr.sgi.com
Subject: Re: boot problem
Date: Wed, 14 Jan 1998 15:55:29 -0800 (PST) [thread overview]
Message-ID: <199801142355.PAA09106@oz.engr.sgi.com> (raw)
Message-ID: <19980114235529.xLe3PBS04MbdO0khukv6O5UbjUmwsmhjPRnp2xf3Rys@z> (raw)
In-Reply-To: <34BD4F3E.7F86@cerf.net> from "William Ellis" at Jan 14, 98 03:50:22 pm
:
: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?
:Thanks in Advance, Bill
:
Newport == Indy graphics
So I guess the code should be changed so it doesn't assume
there's a newport hardware.
--
Peace, Ariel
next prev parent reply other threads:[~1998-01-14 23:56 UTC|newest]
Thread overview: 32+ 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 [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
2001-05-23 12:03 Boot Problem Patric Mrawek
2001-05-23 20:47 ` David N. Lombard
2001-05-23 21:25 ` Jeff Golds
2001-05-24 2:19 ` Brent D. Norris
[not found] <Pine.LNX.4.21.0201250656230.1598-100000@Consulate.UFP.CX>
2002-04-10 22:33 ` boot problem Dan Olson
2004-04-27 23:17 Carlos Alberto Pereira Gomes
2004-04-28 0:08 ` Ian Pratt
2005-05-02 12:07 Andrew
2005-05-02 13:41 ` chuck gelm
2005-05-02 15:16 ` Ray Olszewski
2005-05-02 15:26 ` Andrew
2005-05-02 16:08 ` Ray Olszewski
2005-05-02 16:10 ` Andrew
[not found] ` <4b0d6e0d05050206107fae523@mail.gmail.com>
2005-05-02 15:21 ` Andrew
2008-08-10 17:25 Boot problem mengualjeanphi
2009-12-04 19:28 malc
2010-07-09 15:06 boot problem Lubos Kolouch
2010-07-09 15:10 ` Daniel Kozlowski
2019-05-23 12:54 Boot problem Michel Macena
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=199801142355.PAA09106@oz.engr.sgi.com \
--to=ariel@oz.engr.sgi.com \
--cc=ariel@cthulhu.engr.sgi.com \
--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 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.