[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#420820: no console set IBM p5 server

retitle 420820 no console set IBM p5 server
reassign 420820 finish-install

Op 11-05-2007 om 14:26 schreef Rolf Brudeseth:
> Here is the fix I implemented, since the system is non-HMC managed and the
> serial cable is attached to port1:
> rolfb@hv2pos:~$ diff /etc/inittab /etc/inittab.orig
> 63d62
> < co:2345:respawn:/sbin/getty hvsi0 9600 vt100

Because you had to add that line, was it not added by d-i

IIRC adds d-i a "serial line getty",
when the installer is booted with 'console=ttyS0'
(where "ttyS0" is an example of a valid serial port )

I also remember bugreports about that behaviour,
but I don't remember their status.

> Note that there are three possible consoles on an IBM p5 Server:
> co:2345:respawn:/sbin/getty hvsi0 9600 vt100   <== Console via serial port 1 (Non-HMC managed)
> co:2345:respawn:/sbin/getty hvsi1 9600 vt100   <== Console via serial port 2 (Non-HMC managed)
> co:2345:respawn:/sbin/getty hvc0 9600 vt100    <== Console via HMC

Would it OK to activate all three?
Assuming that detecting a p5 server can be done.

> The baud rate is ignored.
> The serial port baud rates are managed through the Service Processor ASM menues.

No worries Mate!
This is in the /etc/inittab on my iBook

2:23:respawn:/sbin/getty 38400 tty2
3:23:respawn:/sbin/getty 38400 tty3

where tty2 and tty3 are virtual consoles, where baudrate neither matters.

Geert Stappers

preferred diff syntax is "diff -u   oldfile  newfile"
e.g.: diff -u /etc/inittab.orig /etc/inittab

Reply to: