init=/bin/sh and serial devices

init=/bin/sh and serial devices

[Mike Shaver]

Wierd stuff here.
We've got it mountinng the NFS partition and running /bin/sh, but we
can't type anything to it at that point.
It's kinda weird, because we see the `#' prompt, but stuff I type to
it isn't registering.

stdin in /dev/cua1, FWIW.

I'm going to try to get some better diags, I guess.

Mike

-- 
#> Mike Shaver (shaver@ingenia.com) Ingenia Communications Corporation 
#>              Commando Developer - Whatever It Takes
#>                                                                     
#> "See, you not only have to be a good coder to create a system like
#>    Linux, you have to be a sneaky bastard too." - Linus Torvalds

Re: init=/bin/sh and serial devices

[Alistair Lambie]

On Apr 9,  2:12pm, Mike Shaver wrote:
> Subject: init=/bin/sh and serial devices
> Wierd stuff here.
> We've got it mountinng the NFS partition and running /bin/sh, but we
> can't type anything to it at that point.
> It's kinda weird, because we see the `#' prompt, but stuff I type to
> it isn't registering.
>
> stdin in /dev/cua1, FWIW.
>

Try 'init=/bin/sh </dev/cua1 >/dev/cua1'.  I seem to remember you need that.
Sorry all this seems to be coming piece meal, but it's been a long time since I
have run it up, and you kind of forget some of the details till you are
reminded!

Cheers, Alistair

-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

Re: init=/bin/sh and serial devices

[Alistair Lambie]

BTW, if you use the init package it will take care of all this stuff...you
should be able to just lay it over the top of the root package on your nfs
disk.

Cheers, Alistair

On Apr 9,  2:23pm, Alistair Lambie wrote:
> Subject: Re: init=/bin/sh and serial devices
> On Apr 9,  2:12pm, Mike Shaver wrote:
> > Subject: init=/bin/sh and serial devices
> > Wierd stuff here.
> > We've got it mountinng the NFS partition and running /bin/sh, but we
> > can't type anything to it at that point.
> > It's kinda weird, because we see the `#' prompt, but stuff I type to
> > it isn't registering.
> >
> > stdin in /dev/cua1, FWIW.
> >
>
> Try 'init=/bin/sh </dev/cua1 >/dev/cua1'.  I seem to remember you need that.
> Sorry all this seems to be coming piece meal, but it's been a long time since
I
> have run it up, and you kind of forget some of the details till you are
> reminded!
>
> Cheers, Alistair
>
> --
> Alistair Lambie
				    alambie@wellington.sgi.com
> Silicon Graphics New Zealand				  SGI Voicemail: 56791
> Level 5, Walsh Wrightson Tower,				    Ph:
+64-4-802 1455
> 94-96 Dixon St, Wellington, NZ			  	   Fax:
+64-4-802 1459
>-- End of excerpt from Alistair Lambie



-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

Re: init=/bin/sh and serial devices

[Alistair Lambie]

On Apr 9,  2:30pm, Alistair Lambie wrote:
> Subject: Re: init=/bin/sh and serial devices
> BTW, if you use the init package it will take care of all this stuff...you
> should be able to just lay it over the top of the root package on your nfs
> disk.
>

You will need to edit inittab for the serial devices...it's set up for the vc's
on a 'headed' Indy.


> Cheers, Alistair
>
> On Apr 9,  2:23pm, Alistair Lambie wrote:
> > Subject: Re: init=/bin/sh and serial devices
> > On Apr 9,  2:12pm, Mike Shaver wrote:
> > > Subject: init=/bin/sh and serial devices
> > > Wierd stuff here.
> > > We've got it mountinng the NFS partition and running /bin/sh, but we
> > > can't type anything to it at that point.
> > > It's kinda weird, because we see the `#' prompt, but stuff I type to
> > > it isn't registering.
> > >
> > > stdin in /dev/cua1, FWIW.
> > >
> >
> > Try 'init=/bin/sh </dev/cua1 >/dev/cua1'.  I seem to remember you need
that.
> > Sorry all this seems to be coming piece meal, but it's been a long time
since
> I
> > have run it up, and you kind of forget some of the details till you are
> > reminded!
> >
> > Cheers, Alistair
> >
> > --
> > Alistair Lambie
> 				    alambie@wellington.sgi.com
> > Silicon Graphics New Zealand				  SGI
Voicemail: 56791
> > Level 5, Walsh Wrightson Tower,				    Ph:
> +64-4-802 1455
> > 94-96 Dixon St, Wellington, NZ			  	   Fax:
> +64-4-802 1459
> >-- End of excerpt from Alistair Lambie
>
>
>
> --
> Alistair Lambie
				    alambie@wellington.sgi.com
> Silicon Graphics New Zealand				  SGI Voicemail: 56791
> Level 5, Walsh Wrightson Tower,				    Ph:
+64-4-802 1455
> 94-96 Dixon St, Wellington, NZ			  	   Fax:
+64-4-802 1459
>-- End of excerpt from Alistair Lambie



-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

Re: init=/bin/sh and serial devices

[Alistair Lambie]

On Apr 9,  2:12pm, Mike Shaver wrote:
> Subject: init=/bin/sh and serial devices
> Wierd stuff here.
> We've got it mountinng the NFS partition and running /bin/sh, but we
> can't type anything to it at that point.
> It's kinda weird, because we see the `#' prompt, but stuff I type to
> it isn't registering.
>
> stdin in /dev/cua1, FWIW.
>

Does your Indy not have a 'head' on it....why are you using the serial ports..

Cheers, Alistair

-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

Re: init=/bin/sh and serial devices

[Alex deVries]

-----BEGIN PGP SIGNED MESSAGE-----


On Wed, 9 Apr 1997, Alistair Lambie wrote:
> On Apr 9,  2:12pm, Mike Shaver wrote:
> > stdin in /dev/cua1, FWIW.
> >
> 
> Does your Indy not have a 'head' on it....why are you using the serial ports..

The machine we're working on, bogomips, is in Ottawa, Canada.  Mike's on
business in Mountainview, California.  Joshua "boot boy" Lamorie handles
the hardboots, and I offer petty advice from Boston, watching Mike use
minicom in a ytalk session through a serial connection.  Odd, but it
works.

Does anyone know the the status of gcc for sgi-linux?  I understand the
cross compiler between Irix and sgi-linux is operational.  How about a
native compiler?  I'm keen on porting a ton of RPM's...

- - Alex

<()       Alex deVries
 |_\_ System Administrator
  ^^   The EngSoc Project


-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQB1AwUBM0sbNO5CP+X51y2VAQE7WQMAlU19MKDQO/n7WrLZR28aRU53IuFyzc0x
bKVxD5Nya82B/gfH27cJkxjKjeCSRvboE9qdiVLkgThdavkqUTxrjJDg2kcndGam
EPpOneWEk6wptA7WNmpowXK8ykU1a6pJ
=sbL6
-----END PGP SIGNATURE-----

Re: init=/bin/sh and serial devices

[Ariel Faigon]

:
:-----BEGIN PGP SIGNED MESSAGE-----
:
:
:On Wed, 9 Apr 1997, Alistair Lambie wrote:
:> On Apr 9,  2:12pm, Mike Shaver wrote:
:> > stdin in /dev/cua1, FWIW.
:> >
:> 
:> Does your Indy not have a 'head' on it....why are you using the serial ports..
:
:The machine we're working on, bogomips, is in Ottawa, Canada.  Mike's on
:business in Mountainview, California.  Joshua "boot boy" Lamorie handles
:the hardboots, and I offer petty advice from Boston, watching Mike use
:minicom in a ytalk session through a serial connection.  Odd, but it
:works.
:
:Does anyone know the the status of gcc for sgi-linux?  I understand the
:cross compiler between Irix and sgi-linux is operational.  How about a
:native compiler?  I'm keen on porting a ton of RPM's...
:
:- - Alex
:
:<()       Alex deVries
: |_\_ System Administrator
:  ^^   The EngSoc Project
:
:

This is one of the things that weren't done and we want to get done
by the Linux/SGI developers.  I believe that Miguel is one of the
best people to make this happen.  If we can just get his Indy R5000
out of the bureaucratic mess.  Miguel's Indy was shipped three weeks
ago to Mexico and requires a "special permit for used equipment" by
the Mexican customs to be provided by the SGI Mexico City office)

I hope Miguel will send us some good news soon.
-- 
Peace, Ariel

Re: init=/bin/sh and serial devices

[Ariel Faigon]

:
:-----BEGIN PGP SIGNED MESSAGE-----
:
:
:On Wed, 9 Apr 1997, Alistair Lambie wrote:
:> On Apr 9,  2:12pm, Mike Shaver wrote:
:> > stdin in /dev/cua1, FWIW.
:> >
:> 
:> Does your Indy not have a 'head' on it....why are you using the serial ports..
:
:The machine we're working on, bogomips, is in Ottawa, Canada.  Mike's on
:business in Mountainview, California.  Joshua "boot boy" Lamorie handles
:the hardboots, and I offer petty advice from Boston, watching Mike use
:minicom in a ytalk session through a serial connection.  Odd, but it
:works.
:
:Does anyone know the the status of gcc for sgi-linux?  I understand the
:cross compiler between Irix and sgi-linux is operational.  How about a
:native compiler?  I'm keen on porting a ton of RPM's...
:
:- - Alex
:
:<()       Alex deVries
: |_\_ System Administrator
:  ^^   The EngSoc Project
:
:

This is one of the things that weren't done and we want to get done
by the Linux/SGI developers.  I believe that Miguel is one of the
best people to make this happen.  If we can just get his Indy R5000
out of the bureaucratic mess.  Miguel's Indy was shipped three weeks
ago to Mexico and requires a "special permit for used equipment" by
the Mexican customs to be provided by the SGI Mexico City office)

I hope Miguel will send us some good news soon.
-- 
Peace, Ariel

Re: init=/bin/sh and serial devices

[Martin Knoblauch]

Alistair Lambie wrote:
> 
> On Apr 9,  2:12pm, Mike Shaver wrote:
> > Subject: init=/bin/sh and serial devices
> > Wierd stuff here.
> > We've got it mountinng the NFS partition and running /bin/sh, but we
> > can't type anything to it at that point.
> > It's kinda weird, because we see the `#' prompt, but stuff I type to
> > it isn't registering.
> >
> > stdin in /dev/cua1, FWIW.
> >
> 
> Does your Indy not have a 'head' on it....why are you using
> the serial ports..
>

 this brings up the question: do we already have drivers for
the textport? Not to speak of an X-Server? How are we (SGI)
going to handle this? As far as I know we never published
the hardware dependent parts on the X11 distribution, did we?

Martin 
-- 
+---------------------------------+-----------------------------------+
|Martin Knoblauch                 | Silicon Graphics GmbH             |
|Manager Technical Marketing      | Am Hochacker 3 - Technopark       |
|Silicon Graphics Computer Systems| D-85630 Grasbrunn-Neukeferloh, FRG|
|---------------------------------| Phone: (+int) 89 46108-179 or -0  |
|http://reality.sgi.com/knobi     | Fax:   (+int) 89 46107-179        |
+---------------------------------+-----------------------------------+
|e-mail: <knobi@munich.sgi.com>   | VM: 6-333-8197 | M/S: IDE-3150    |
+---------------------------------------------------------------------+

Re: init=/bin/sh and serial devices

[William J. Earl]

Martin Knoblauch writes:
...
 >  this brings up the question: do we already have drivers for
 > the textport? Not to speak of an X-Server? How are we (SGI)
 > going to handle this? As far as I know we never published
 > the hardware dependent parts on the X11 distribution, did we?
...

    With management authorization, I provided the technical details
for the graphics hardware (and all the other Indy hardware) to David
Miller, who I believe got a textport driver working.

Re: init=/bin/sh and serial devices

[Ariel Faigon]

:
:Martin Knoblauch writes:
:...
: >  this brings up the question: do we already have drivers for
: > the textport? Not to speak of an X-Server? How are we (SGI)
: > going to handle this? As far as I know we never published
: > the hardware dependent parts on the X11 distribution, did we?
:...
:
:    With management authorization, I provided the technical details
:for the graphics hardware (and all the other Indy hardware) to David
:Miller, who I believe got a textport driver working.
:

Also, the agreement we signed with David was that all the Linux work
including those low level drivers will be released under the GPL
i.e. anyone who cares would be able to look at these driver sources.

-- 
Peace, Ariel

Re: init=/bin/sh and serial devices

[Ariel Faigon]

:
:Martin Knoblauch writes:
:...
: >  this brings up the question: do we already have drivers for
: > the textport? Not to speak of an X-Server? How are we (SGI)
: > going to handle this? As far as I know we never published
: > the hardware dependent parts on the X11 distribution, did we?
:...
:
:    With management authorization, I provided the technical details
:for the graphics hardware (and all the other Indy hardware) to David
:Miller, who I believe got a textport driver working.
:

Also, the agreement we signed with David was that all the Linux work
including those low level drivers will be released under the GPL
i.e. anyone who cares would be able to look at these driver sources.

-- 
Peace, Ariel

Re: init=/bin/sh and serial devices

[Alistair Lambie]

On Apr 9,  7:07pm, Martin Knoblauch wrote:
> Subject: Re: init=/bin/sh and serial devices
> Alistair Lambie wrote:
> >
> > On Apr 9,  2:12pm, Mike Shaver wrote:
> > > Subject: init=/bin/sh and serial devices
> > > Wierd stuff here.
> > > We've got it mountinng the NFS partition and running /bin/sh, but we
> > > can't type anything to it at that point.
> > > It's kinda weird, because we see the `#' prompt, but stuff I type to
> > > it isn't registering.
> > >
> > > stdin in /dev/cua1, FWIW.
> > >
> >
> > Does your Indy not have a 'head' on it....why are you using
> > the serial ports..
> >
>
>  this brings up the question: do we already have drivers for
> the textport? Not to speak of an X-Server? How are we (SGI)
> going to handle this? As far as I know we never published
> the hardware dependent parts on the X11 distribution, did we?
>

We already have drivers for 'textport'....well actually it takes over the whole
screen with a font that allows something like 132x80 from what I remeber.  This
has VC support so you can do the usual Alt-F1 etc like on a PC based linux box.
 No work has been done on the X-Server yet.

Cheers, Alistair

-- 
Alistair Lambie					    alambie@wellington.sgi.com
Silicon Graphics New Zealand				  SGI Voicemail: 56791
Level 5, Walsh Wrightson Tower,				    Ph: +64-4-802 1455
94-96 Dixon St, Wellington, NZ			  	   Fax: +64-4-802 1459

Re: init=/bin/sh and serial devices

[David S. Miller]

   Date: Wed, 09 Apr 1997 09:06:29 +0200
   From: Martin Knoblauch <knobi@munich.sgi.com>

   do we already have drivers for the textport?

I wrote the text console driver for 24-bit Newport INDY frame buffers,
and it is in the SGI/Linux code.  I was never able to get around to
doing the 8-bit frame buffer card driver though, so if you've got one
of those in the INDY you are a out of luck for now.  (hinv -v from the
firmware prompt will tell you if you have the 24-bit or 8-bit card)

---------------------------------------------////
Yow! 11.26 MB/s remote host TCP bandwidth & ////
199 usec remote TCP latency over 100Mb/s   ////
ethernet.  Beat that!                     ////
-----------------------------------------////__________  o
David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><

Re: init=/bin/sh and serial devices

[William J. Earl]

David S. Miller writes:
 >    Date: Wed, 09 Apr 1997 09:06:29 +0200
 >    From: Martin Knoblauch <knobi@munich.sgi.com>
 > 
 >    do we already have drivers for the textport?
 > 
 > I wrote the text console driver for 24-bit Newport INDY frame buffers,
 > and it is in the SGI/Linux code.  I was never able to get around to
 > doing the 8-bit frame buffer card driver though, so if you've got one
 > of those in the INDY you are a out of luck for now.  (hinv -v from the
 > firmware prompt will tell you if you have the 24-bit or 8-bit card)
...

     Does the textport driver run in color-index mode?  If so, it will
probably work on the 8-bit card.  The cards are largely identical, except
for the depth of the frame buffer.

Re: init=/bin/sh and serial devices

[David S. Miller]

   Date: Mon, 14 Apr 1997 11:05:52 -0700
   From: "William J. Earl" <wje@fir.engr.sgi.com>

	Does the textport driver run in color-index mode?  If so, it
   will probably work on the 8-bit card.  The cards are largely
   identical, except for the depth of the frame buffer.

If memory serves, I left the chip in the exact mode the firmware has
set it to.  So if the firmware sets up the card to use color-index
mode, then I do as well in the driver.  (I think I did this so I did
not have to deal with monitor frequencies, and resolutions, and that
sort of thing)

But my text rendering code may make assumptions about frame buffer
depth, I draw them using the various simpler raster operation commands
the Newport has, so someone who knows would have to look at my code.

---------------------------------------------////
Yow! 11.26 MB/s remote host TCP bandwidth & ////
199 usec remote TCP latency over 100Mb/s   ////
ethernet.  Beat that!                     ////
-----------------------------------------////__________  o
David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><

Re: init=/bin/sh and serial devices

[Alistair Lambie]

> 
>    Date: Mon, 14 Apr 1997 11:05:52 -0700
>    From: "William J. Earl" <wje@fir.engr.sgi.com>
> 
> 	Does the textport driver run in color-index mode?  If so, it
>    will probably work on the 8-bit card.  The cards are largely
>    identical, except for the depth of the frame buffer.
> 
> If memory serves, I left the chip in the exact mode the firmware has
> set it to.  So if the firmware sets up the card to use color-index
> mode, then I do as well in the driver.  (I think I did this so I did
> not have to deal with monitor frequencies, and resolutions, and that
> sort of thing)
> 
> But my text rendering code may make assumptions about frame buffer
> depth, I draw them using the various simpler raster operation commands
> the Newport has, so someone who knows would have to look at my code.
> 
I've been away for a few days, so sorry about the late reply :-)

It definitely works on an 8 bit machine.  That is what I have used in the past.

Cheers, Alistair

Re: init=/bin/sh and serial devices

[Alistair Lambie]

> 
>    Date: Mon, 14 Apr 1997 11:05:52 -0700
>    From: "William J. Earl" <wje@fir.engr.sgi.com>
> 
> 	Does the textport driver run in color-index mode?  If so, it
>    will probably work on the 8-bit card.  The cards are largely
>    identical, except for the depth of the frame buffer.
> 
> If memory serves, I left the chip in the exact mode the firmware has
> set it to.  So if the firmware sets up the card to use color-index
> mode, then I do as well in the driver.  (I think I did this so I did
> not have to deal with monitor frequencies, and resolutions, and that
> sort of thing)
> 
> But my text rendering code may make assumptions about frame buffer
> depth, I draw them using the various simpler raster operation commands
> the Newport has, so someone who knows would have to look at my code.
> 
I've been away for a few days, so sorry about the late reply :-)

It definitely works on an 8 bit machine.  That is what I have used in the past.

Cheers, Alistair