From: "William J. Earl" <wje@fir.engr.sgi.com>
To: ralf@uni-koblenz.de
Cc: "William J. Earl" <wje@fir.engr.sgi.com>,
William Ellis <bellis@cerf.net>,
Linux porting team <linux@cthulhu.engr.sgi.com>
Subject: Re: boot problem
Date: Wed, 14 Jan 1998 22:10:45 -0800 [thread overview]
Message-ID: <199801150610.WAA18877@fir.engr.sgi.com> (raw)
In-Reply-To: <19980115061519.46558@uni-koblenz.de>
ralf@uni-koblenz.de writes:
> On Wed, Jan 14, 1998 at 04:56:38PM -0800, William J. Earl wrote:
>
> > > 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.
> >
> > IRIX probes for the graphics card. If the probe fails, it
> > assumes this is not one. If there is no graphics, or if console != g,
> > it sets the system console to the serial port. Note, however, that
> > IRIX normally puts up an X login on the graphics head even if
> > console=d and thus the console is on the serial port. This seems
> > like a reasonable approach for linux as well.
>
> Indeed, this is how Linux will behave after the probe / console env
> thing is fixed. I assume your more than minimal necessary probe has the
> purpose to make shut that the machine does not only have gfx but also
> that the gfx found in the address space is not something else like the
> XZ for example?
...
Yes, that is correct. Also, it means that the system will
come up with a serial console if the graphics board is completely dead.
next prev parent reply other threads:[~1998-01-15 6:15 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
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 [this message]
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=199801150610.WAA18877@fir.engr.sgi.com \
--to=wje@fir.engr.sgi.com \
--cc=bellis@cerf.net \
--cc=linux@cthulhu.engr.sgi.com \
--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.