This one time, at band camp, Frans Pop said: > reassign 541831 finish-install 2.22 > thanks > > On Sunday 16 August 2009, Stephen Gran wrote: > > Comments/Problems: > > The only complaint from the install is that after the install was > > completed and the machine rebooted, there was no getty listening on > > ttyS0. > > Was the installation itself done over ttyS0? If it was, it surprises me a > lot that there was no inittab entry for it. > > It sounds like the "rsc console" is something different, which could > explain what you saw. Maybe we need special handling for this case. The rsc is much like an iLo or alom. It's just another management interface that offers a 'console' interface to manage the OS. I did the install using this interface, obtained by running 'break -c'. > Questions: > - What were the contents of /etc/inittab after the installation? Were > the entries for tty[1-6] commented out or not? # 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 I had to uncomment T0 to get a console with 'console -f' from the rsc. > - Can you reboot the installer, activate a debug shell and give the output > of: > - console-type ~ # console-type serial > - readlink /proc/self/fd/0 ~ # readlink /proc/self/fd/0 /dev/console > - # 'pidof debian-installer' does not work in lenny, so we need: > ps | grep "[/]sbin/debian-installer" > readlink /proc/<pid from command above>/fd/0 ~ # pidof debian-installer ~ # ps | grep "[/]sbin/debian-installer" 912 root 1600 S /bin/sh /sbin/debian-installer ~ # readlink /proc/912/fd/0 /dev/console > - If the first is not "serial" and/or the last is not /dev/ttyS0, then > how could the need to set up serial console be detected? That's a very good question. Interestingly, I see this in dmesg: [ 32.032662] console handover: boot [earlyprom0] -> real [tty0] So at least at that point, the kernel thinks it _is_ tty0. Unfortunately, I don't know enough about whether there is a difference between what you attach to with 'console -f' in the rsc and what you attach to with 'break -c'. I naively think that they should be the same thing, but it is possible that they are not. > - Does the installer work correctly and does a listener for serial console > get set up for the installed system if you boot D-I with console=ttyS0? No: steal-ctty: No such file or directory steal-ctty: No such file or directory steal-ctty: No such file or directory Over and over. So, this doesn't look like a problem the installer can fix. It's just odd that the OS doesn't see the serial console on the same device as the installer does: sgran@zee:~$ readlink /proc/self/fd/0 /dev/ttyS0 Well, I'm a bit mystified about how this could be fixed, so I don't mind if you want to close it as unresolvable or punt it over to the sparc porters to see if they can shed any light on it. > If changes are needed, that would probably be in the script > /usr/lib/finish-install.d/90console (from finish-install). Looks like it's unlikely to need any patching. Cheers, -- ----------------------------------------------------------------- | ,''`. Stephen Gran | | : :' : sgran@debian.org | | `. `' Debian user, admin, and developer | | `- http://www.debian.org | -----------------------------------------------------------------
Attachment:
signature.asc
Description: Digital signature