Indigo2 Kernel Boots!!!

Indigo2 Kernel Boots!!!

[Jesse Dyson]

Hi,
I have an Indigo2.  I have tftp/dhcp(bootp)/nfs configured correctly (I
think).  I am using the hardhat-5.1-sgi.tar.gz distribution and the kernel
vmlinux-2.2.14-r4x00-cvs.ecoff.

I am using the monitor commands:
unsetenv netaddr (dur to DHCP bug)
boot bootp():/vmlinux nfsroot=208.128.132.35:/home/jdyson/sgi-linux/mipseb

/vmlinux is a symbolic link to vmlinux-2.2...

I have the distribution in the mipseb folder (RedHat is a subdirectory of
mipseb).  I think this is right.

When I run this the kernel seems to start up (finds hardware, etc).
Connects to the root filesystem...The last message I get is "Warning:
unable to open an initial console"

I have removed the graphics card from the machine (evidently the vx
frame-buffer card is a problem).  I am connected to the serial port to get
access to command monitor, etc.

Anybody have any suggestions on what to do next or what I am doing wrong.
Thank you in advance for your time; and thanks guys for helping me get to
this point.

Thanks,
Jesse Dyson

Re: Indigo2 Kernel Boots!!!

[Klaus Naumann]

On Thu, 30 Nov 2000, Jesse Dyson wrote:

> Hi,
> I have an Indigo2.  I have tftp/dhcp(bootp)/nfs configured correctly (I
> think).  I am using the hardhat-5.1-sgi.tar.gz distribution and the kernel
> vmlinux-2.2.14-r4x00-cvs.ecoff.
> 
> I am using the monitor commands:
> unsetenv netaddr (dur to DHCP bug)
> boot bootp():/vmlinux nfsroot=208.128.132.35:/home/jdyson/sgi-linux/mipseb
> 
> /vmlinux is a symbolic link to vmlinux-2.2...
> 
> I have the distribution in the mipseb folder (RedHat is a subdirectory of
> mipseb).  I think this is right.
> 
> When I run this the kernel seems to start up (finds hardware, etc).
> Connects to the root filesystem...The last message I get is "Warning:
> unable to open an initial console"

If you're booting the kernel with serial console you have to
link /dev/console to /dev/ttyS0 - see also Pitfalls section in the
Linux on Indigo2 HOWTO (http://oss.sgi.com/mips/i2-howto.html)

		CU, Klaus

-- 
Full Name   : Klaus Naumann     | (http://www.mgnet.de/) (Germany)
Nickname    : Spock             | Org.: Mad Guys Network
Phone / FAX : ++49/177/7862964  | E-Mail: (spock@mgnet.de)
PGP Key     : www.mgnet.de/keys/key_spock.txt

Re: Indigo2 Kernel Boots!!!

[Jesse Dyson]

Hi,
I'm not exactly sure what this means to "link" /dev/console.  Based on the
FAQ (http://foobazco.org/~weslows/Install-HOWTO.html), I shouldn't have to
do the inittab stuff since I am in ser port 1.  I noticed I do not have an
/etc/inittab file in my root fs, but there is a inittabold.  Is there
something with these files I have to fix or do I do an 'ln -s' or
something on the /dev/console and point it to /dev/ttyS0?

Sorry for my ignorance.

Thanks for your help.

Thanks,
Jesse Dyson 

On Thu, 30 Nov 2000, Klaus Naumann wrote:

> On Thu, 30 Nov 2000, Jesse Dyson wrote:
> 
> > Hi,
> > I have an Indigo2.  I have tftp/dhcp(bootp)/nfs configured correctly (I
> > think).  I am using the hardhat-5.1-sgi.tar.gz distribution and the kernel
> > vmlinux-2.2.14-r4x00-cvs.ecoff.
> > 
> > I am using the monitor commands:
> > unsetenv netaddr (dur to DHCP bug)
> > boot bootp():/vmlinux nfsroot=208.128.132.35:/home/jdyson/sgi-linux/mipseb
> > 
> > /vmlinux is a symbolic link to vmlinux-2.2...
> > 
> > I have the distribution in the mipseb folder (RedHat is a subdirectory of
> > mipseb).  I think this is right.
> > 
> > When I run this the kernel seems to start up (finds hardware, etc).
> > Connects to the root filesystem...The last message I get is "Warning:
> > unable to open an initial console"
> 
> If you're booting the kernel with serial console you have to
> link /dev/console to /dev/ttyS0 - see also Pitfalls section in the
> Linux on Indigo2 HOWTO (http://oss.sgi.com/mips/i2-howto.html)
> 
> 		CU, Klaus
> 
> -- 
> Full Name   : Klaus Naumann     | (http://www.mgnet.de/) (Germany)
> Nickname    : Spock             | Org.: Mad Guys Network
> Phone / FAX : ++49/177/7862964  | E-Mail: (spock@mgnet.de)
> PGP Key     : www.mgnet.de/keys/key_spock.txt
> 

Re: Indigo2 Kernel Boots!!!

[Keith M Wesolowski]

On Thu, Nov 30, 2000 at 09:41:26AM -0500, Jesse Dyson wrote:

> > > think).  I am using the hardhat-5.1-sgi.tar.gz distribution and the kernel
...
> I'm not exactly sure what this means to "link" /dev/console.  Based on the
> FAQ (http://foobazco.org/~weslows/Install-HOWTO.html), I shouldn't have to
> do the inittab stuff since I am in ser port 1.  I noticed I do not have an

The FAQ on my site has nothing whatever to do with the Hard Hat
distribution.  I have no idea how relevant it is if you're using that.

-- 
Keith M Wesolowski			wesolows@chem.unr.edu
University of Nevada			http://www.chem.unr.edu
Chemistry Department Systems and Network Administrator

Re: Indigo2 Kernel Boots!!!

[Kevin D. Kissell]

> I'm not exactly sure what this means to "link" /dev/console.  Based on the
> FAQ (http://foobazco.org/~weslows/Install-HOWTO.html), I shouldn't have to
> do the inittab stuff since I am in ser port 1.  I noticed I do not have an
> /etc/inittab file in my root fs, but there is a inittabold.  Is there
> something with these files I have to fix or do I do an 'ln -s' or
> something on the /dev/console and point it to /dev/ttyS0?

When the init process fires up, it opens /dev/console as the
console output device.  A default SGI workstation installation
file system will have /dev/console bound to the major/minor device
node of the graphics display console.  If you want to run with a serial
console, you must therefore change this to bind /dev/console
to the serial port.  You can do this by doing an explicit mknod,
or by linking to the appropriate serial port device node,
which is usually /dev/ttyS0.

            Kevin K.

Re: Indigo2 Kernel Boots!!!

[Kevin D. Kissell]

> I'm not exactly sure what this means to "link" /dev/console.  Based on the
> FAQ (http://foobazco.org/~weslows/Install-HOWTO.html), I shouldn't have to
> do the inittab stuff since I am in ser port 1.  I noticed I do not have an
> /etc/inittab file in my root fs, but there is a inittabold.  Is there
> something with these files I have to fix or do I do an 'ln -s' or
> something on the /dev/console and point it to /dev/ttyS0?

When the init process fires up, it opens /dev/console as the
console output device.  A default SGI workstation installation
file system will have /dev/console bound to the major/minor device
node of the graphics display console.  If you want to run with a serial
console, you must therefore change this to bind /dev/console
to the serial port.  You can do this by doing an explicit mknod,
or by linking to the appropriate serial port device node,
which is usually /dev/ttyS0.

            Kevin K.

Re: Indigo2 Kernel Boots!!!

[Ralf Baechle]

On Thu, Nov 30, 2000 at 05:10:32PM +0100, Kevin D. Kissell wrote:

> When the init process fires up, it opens /dev/console as the
> console output device.  A default SGI workstation installation
> file system will have /dev/console bound to the major/minor device
> node of the graphics display console.  If you want to run with a serial
> console, you must therefore change this to bind /dev/console
> to the serial port.  You can do this by doing an explicit mknod,
> or by linking to the appropriate serial port device node,
> which is usually /dev/ttyS0.

Which both are wrong.  /dev/console should be a char device major 5, minor 1.
There is no need to change this ever except for very old kernels.  With 2.2
or 2.4 whenever people change /dev/console's major/minor it's usually painting
over some bug.

  Ralf

Re: Indigo2 Kernel Boots!!!

[Kevin D. Kissell]

> > When the init process fires up, it opens /dev/console as the
> > console output device.  A default SGI workstation installation
> > file system will have /dev/console bound to the major/minor device
> > node of the graphics display console.  If you want to run with a serial
> > console, you must therefore change this to bind /dev/console
> > to the serial port.  You can do this by doing an explicit mknod,
> > or by linking to the appropriate serial port device node,
> > which is usually /dev/ttyS0.
>
> Which both are wrong.  /dev/console should be a char device major 5, minor
1.
> There is no need to change this ever except for very old kernels.  With
2.2
> or 2.4 whenever people change /dev/console's major/minor it's usually
painting
> over some bug.

Having been through the exercise a dozen or more times with
the SGI 2.2 kernel distributions for the Indy, I would be fascinated
to know what bug I was painting over, and where the correct
procedure was documented.

            Kevin K.

Re: Indigo2 Kernel Boots!!!

[Kevin D. Kissell]

> > When the init process fires up, it opens /dev/console as the
> > console output device.  A default SGI workstation installation
> > file system will have /dev/console bound to the major/minor device
> > node of the graphics display console.  If you want to run with a serial
> > console, you must therefore change this to bind /dev/console
> > to the serial port.  You can do this by doing an explicit mknod,
> > or by linking to the appropriate serial port device node,
> > which is usually /dev/ttyS0.
>
> Which both are wrong.  /dev/console should be a char device major 5, minor
1.
> There is no need to change this ever except for very old kernels.  With
2.2
> or 2.4 whenever people change /dev/console's major/minor it's usually
painting
> over some bug.

Having been through the exercise a dozen or more times with
the SGI 2.2 kernel distributions for the Indy, I would be fascinated
to know what bug I was painting over, and where the correct
procedure was documented.

            Kevin K.

Re: Indigo2 Kernel Boots!!!

[Harald Koerfgen]

On 01-Dec-00 Kevin D. Kissell wrote:
> 
>> > When the init process fires up, it opens /dev/console as the
>> > console output device.  A default SGI workstation installation
>> > file system will have /dev/console bound to the major/minor device
>> > node of the graphics display console.  If you want to run with a serial
>> > console, you must therefore change this to bind /dev/console
>> > to the serial port.  You can do this by doing an explicit mknod,
>> > or by linking to the appropriate serial port device node,
>> > which is usually /dev/ttyS0.
>>
>> Which both are wrong.  /dev/console should be a char device major 5, minor
> 1.
>> There is no need to change this ever except for very old kernels.  With
> 2.2
>> or 2.4 whenever people change /dev/console's major/minor it's usually
> painting
>> over some bug.
> 
> Having been through the exercise a dozen or more times with
> the SGI 2.2 kernel distributions for the Indy, I would be fascinated
> to know what bug I was painting over, and where the correct
> procedure was documented.

linux/Documentation/serial-console.txt

-- 
Regards,
Harald

Re: Indigo2 Kernel Boots!!!

[Ralf Baechle]

On Fri, Dec 01, 2000 at 04:33:48PM +0100, Harald Koerfgen wrote:

> > Having been through the exercise a dozen or more times with
> > the SGI 2.2 kernel distributions for the Indy, I would be fascinated
> > to know what bug I was painting over, and where the correct
> > procedure was documented.
> 
> linux/Documentation/serial-console.txt

In addition let me add some word about what the term console actually is,
this commonly seems to cause confusition because the word is used with two
different meanings:

 1) The device on which you login in single user mode, that's usually some
    kind of serial device at ttyS0 or a virtual console, that is with keyboard
    and some kind of text terminal.
 2) The second is the device which the kernel prints all the printk messages
    and data sent to /dev/console to.  The two often often but not always
    refer to the same actual device.

/dev/console (as chardev 5/1) differs from another device in some important
ways:

 - When opened by a process without controlling tty it will not become a
   CTTY even if the NOCTTY flag is not set.
 - It will never block but rather loose data.  This may sound like a
   disadvantage but it's actually very important for proper operation.  For
   example, if /dev/console'd block due to a serial console with hardware
   handshaking enabled (DON'T) syslogd writing to it may also block for an
   unbounded time and thus as soon as /dev/log is full all services trying to
   log via syslog(3) will also freeze.

   Syslogd actually tries to be clever about avoiding this from happening
   but fails to handle one case correctly, so this is a real world scenario.

 - It uses different routines to access the console device than normal
   write access to i.e. ttyS0.

The most common problem is that CONFIG_SERIAL_CONSOLE wasn't configured;
some drivers are simply buggy and don't properly register the console
on startup.  Dunno what the problem was in your case, Kevin.

  Ralf

console knowledge

[Gordon McNutt]

This is a little off-topic, so if people complain I can take it offline. But
since this doesn't seem to be (very) common knowledge maybe others would like to
see it, as well.

Ralf Baechle wrote:

> /dev/console (as chardev 5/1) differs from another device in some important
> ways:
>
>  - When opened by a process without controlling tty it will not become a
>    CTTY even if the NOCTTY flag is not set.

What do you mean by "controlling tty"? And why is the distinction noted above
important? I assume it has something to do with keyboard input/screen output, but
perhaps you can clarify.

Thanks,

--Gordon

Re: console knowledge

[Ralf Baechle]

On Fri, Dec 01, 2000 at 11:15:50AM -0700, Gordon McNutt wrote:

> > /dev/console (as chardev 5/1) differs from another device in some important
> > ways:
> >
> >  - When opened by a process without controlling tty it will not become a
> >    CTTY even if the NOCTTY flag is not set.
> 
> What do you mean by "controlling tty"?
> output, but perhaps you can clarify.

Controlling terminal is a fundamental UNIX term; you should check a good
UNIX book about it.  The glibc info pages also have some words about it.

> And why is the distinction noted above important? I assume it has something
> to do with keyboard input/screen

Reread my posting, it describes some of the differences in the behaviour
of for example /dev/console and /dev/ttyS0 even though both refer to the
same device.

That could be different.  The classic UNIX setup is sending /dev/console to
the printer on one serial and having the system's console terminal on
another.  Any arbitrary device combination would be possible.

  Ralf