> > The system appeared to hang because a getty process was not started for
> > the console.
>
>> Debian GNU/Linux 4.0 hv2pos hvsi0
> >
> > hv2pos login: rolfb
>
> > Password:
>
>
>
> As you did get a login prompt, it seems that /etc/inittab was set up
>
> correctly to use the serial console (an active T0: line pointing to the
>
> correct serial device). Normally this should be sufficient.
I got the login prompt after I modified /etc/inittab (via a linux install I had on another disk).
>
>
>
> How exactly did you boot the installer (with what parameters)?
>
I tried both 'install64' and 'expert64'.
> What exactly do you mean by "the system appeared to hang"?
>
Nothing else was echo'ed to the screen. At the time, I did not realize that with Etch the sshd server is not enabled by default.
I later understood that the system was up an running just fine, except for this serial port console issue.
> Was there indeed a correct T0: line in /etc/inittab (please send us the
>
> inittab as created by the installer)?
Yes there was and it was commented out.
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
But I do not believe that is of significance.
>
> If there was, why would your system need an additional co: line where
>
> other systems with serial console setup do not?
By other systems you mean Apple computers or prior generation IBM workstations? What has changed on IBM System p5 servers is that the serial ports or console on the HMC is virtualized via the onboard service processor.
IBM System p5 servers do not have any ttySx ports available by default, and those ports would not allow access to ASM and SMS menues. Only hvsi0/1 and hvc0 allow access to those menues. The ASM menus are used for tasks such as powering up the system at standby power. The SMS menues allows you to interact with a menu based front end to Open Firmware, where you can choose install/boot devices, initiate network install, etc.
If you do a search on google with 'hvsi0' and 'hvc0' you will find lots of documentation.
>
>
>
> Cheers,
>
> FJP
Rolf
Original /etc/inittab file:
$ cat /etc/inittab.orig
# /etc/inittab: init(8) configuration.
# $Id: inittab,v 1.91 2002/01/25 13:35:21 miquels Exp $
# The default runlevel.
id:2:initdefault:
# Boot-time system configuration/initialization script.
# This is run first except when booting in emergency (-b) mode.
si::sysinit:/etc/init.d/rcS
# What to do in single-user mode.
~~:S:wait:/sbin/sulogin
# /etc/init.d executes the S and K scripts upon change
# of runlevel.
#
# Runlevel 0 is halt.
# Runlevel 1 is single-user.
# Runlevels 2-5 are multi-user.
# Runlevel 6 is reboot.
l0:0:wait:/etc/init.d/rc 0
l1:1:wait:/etc/init.d/rc 1
l2:2:wait:/etc/init.d/rc 2
l3:3:wait:/etc/init.d/rc 3
l4:4:wait:/etc/init.d/rc 4
l5:5:wait:/etc/init.d/rc 5
l6:6:wait:/etc/init.d/rc 6
# Normally not reached, but fallthrough in case of emergency.
z6:6:respawn:/sbin/sulogin
# What to do when CTRL-ALT-DEL is pressed.
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now
# Action on special keypress (ALT-UpArrow).
#kb::kbrequest:/bin/echo "Keyboard Request--edit /etc/inittab to let this work."
# What to do when the power fails/returns.
pf::powerwait:/etc/init.d/powerfail start
pn::powerfailnow:/etc/init.d/powerfail now
po::powerokwait:/etc/init.d/powerfail stop
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
# <id>:<runlevels>:<action>:<process>
#
# Note that on most Debian systems tty7 is used by the X Window System,
# so if you want to add more getty's go ahead but skip tty7 if you run X.
#
1:2345:respawn:/sbin/getty 38400 tty1
2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3
4:23:respawn:/sbin/getty 38400 tty4
5:23:respawn:/sbin/getty 38400 tty5
6:23:respawn:/sbin/getty 38400 tty6
# Example how to put a getty on a serial line (for a terminal)
#
#T0:23:respawn:/sbin/getty -L ttyS0 9600 vt100
#T1:23:respawn:/sbin/getty -L ttyS1 9600 vt100
# Example how to put a getty on a modem line.
#
#T3:23:respawn:/sbin/mgetty -x0 -s 57600 ttyS3