Bug#420820: no console set IBM p5 server

2007-05-25 Thread Frans Pop
On Wednesday 16 May 2007 19:41, Rolf Brudeseth wrote: I tested the script with the console attached to serial port 1 and 2 (hvsi0 and hvsi1). I had to make some minor changes to the script to get it to work. Thanks. Sorry for the delay, but here is a new version of the script. It now uses

Bug#420820: no console set IBM p5 server

2007-05-25 Thread Rolf Brudeseth
Here is another thought. Could you test if creating a getty line using /dev/console just magically works? Given the fact that the installer does not need any special setup and uses /dev/console, that might just do it. It would remove the need to figure out exactly what type of virtual console

Bug#420820: no console set IBM p5 server

2007-05-17 Thread Sven Luther
On Wed, May 16, 2007 at 12:41:18PM -0500, Rolf Brudeseth wrote: I tested the script with the console attached to serial port 1 and 2 (hvsi0 and hvsi1). I had to make some minor changes to the script to get it to work. I don't know, but you may want to implement the changes differently.

Bug#420820: no console set IBM p5 server

2007-05-17 Thread Rolf Brudeseth
On Wed, May 16, 2007 at 12:41:18PM -0500, Rolf Brudeseth wrote: I tested the script with the console attached to serial port 1 and 2 (hvsi0 and hvsi1). I had to make some minor changes to the script to get it to work. I don't know, but you may want to implement the changes

Bug#420820: no console set IBM p5 server

2007-05-17 Thread Sven Luther
On Thu, May 17, 2007 at 10:44:41AM -0500, Rolf Brudeseth wrote: On Wed, May 16, 2007 at 12:41:18PM -0500, Rolf Brudeseth wrote: I tested the script with the console attached to serial port 1 and 2 (hvsi0 and hvsi1). I had to make some minor changes to the script to get it to

Bug#420820: no console set IBM p5 server

2007-05-16 Thread Rolf Brudeseth
I tested the script with the console attached to serial port 1 and 2 (hvsi0 and hvsi1). I had to make some minor changes to the script to get it to work. I don't know, but you may want to implement the changes differently. Regardless, before you submit the final 90console script, I assume I

Bug#420820: no console set IBM p5 server

2007-05-15 Thread Frans Pop
On Monday 14 May 2007 23:55, Rolf Brudeseth wrote: On Monday 14 May 2007 22:29, Rolf Brudeseth wrote: - Step 1: $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] == hvsi0 or hvc0 $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED]

Bug#420820: no console set IBM p5 server

2007-05-15 Thread Frans Pop
On Tuesday 15 May 2007 08:03, Frans Pop wrote: My question is: if hvsi1 is being used, what is the output of cat /proc/device-tree/options/output-device/vdevice/[EMAIL PROTECTED] or does that file just not exist in that case? Sorry, forget about this one. I see I misread your mail. I

Bug#420820: no console set IBM p5 server

2007-05-15 Thread Sven Luther
On Mon, May 14, 2007 at 09:38:25PM +0200, Frans Pop wrote: (No need to CC me. I see your replies on the debian-boot mailing list.) On Monday 14 May 2007 21:09, Rolf Brudeseth wrote: ~ # /usr/lib/finish-install.d/90console [...] + readlink /proc/1560/fd/0 + rawconsole=/dev/console

Bug#420820: no console set IBM p5 server

2007-05-15 Thread Sven Luther
On Tue, May 15, 2007 at 08:03:13AM +0200, Frans Pop wrote: On Monday 14 May 2007 23:55, Rolf Brudeseth wrote: On Monday 14 May 2007 22:29, Rolf Brudeseth wrote: - Step 1: $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] == hvsi0 or hvc0 $ cat

Bug#420820: no console set IBM p5 server

2007-05-15 Thread Frans Pop
On Monday 14 May 2007 22:58, Frans Pop wrote: All in all, this looks easy enough to implement. I'll give it a shot over the next few days and send you something to test. Please try the attached script. It is a drop-in replacement for /usr/lib/finish-install.d/90console. Just copy it over the

Bug#420820: no console set IBM p5 server

2007-05-15 Thread James A Lindeman
As long as Linux kernel creates the Linux,stdout-package property in the /chosen that indicates the console-path, then this script doesn't need to look at the output-device property in the /options node (the /options node represents the various NVRAM varaibles, which is how Open Firmware

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Frans Pop
On Monday 14 May 2007 17:33, Rolf Brudeseth wrote: I got the login prompt after I modified /etc/inittab (via a linux install I had on another disk). OK, your report did not really make that clear. It was probably not really necessary to include the login prompt then. I understood that that is

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Rolf Brudeseth
I got the login prompt after I modified /etc/inittab (via a linux install I had on another disk). OK, your report did not really make that clear. It was probably not really necessary to include the login prompt then. I understood that that is what you saw when it appeared to be hanging.

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Rolf Brudeseth
So, the next step is to find out why the installer does not recognize that you are on serial console. Can you please boot the installer again and activate a debug shell (there is an option in the installer's main menu, or alternatively you can use that network-console component). Please

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Frans Pop
On Monday 14 May 2007 20:23, Rolf Brudeseth wrote: ~ # ls -l /usr/lib/finish-install.d/90console ls: /usr/lib/finish-install.d/90console: No such file or directory Sorry, the file only appears after you have passed the step load additional installer components, so you will have to walk through

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Rolf Brudeseth
~ # cat /usr/lib/finish-install.d/90console #!/bin/sh set -e set -x log() { logger -t finish-install $@ } # Since this script is running with debconf, 'tty' does # not give reliable answers about what sort of terminal # we have. The stdin of /sbin/debian-installer seems # to tell the

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Frans Pop
(No need to CC me. I see your replies on the debian-boot mailing list.) On Monday 14 May 2007 21:09, Rolf Brudeseth wrote: ~ # /usr/lib/finish-install.d/90console [...] + readlink /proc/1560/fd/0 + rawconsole=/dev/console Thanks. So the debian-installer process thinks a regular console is

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Rolf Brudeseth
On Monday 14 May 2007 21:09, Rolf Brudeseth wrote: ~ # /usr/lib/finish-install.d/90console [...] + readlink /proc/1560/fd/0 + rawconsole=/dev/console Thanks. So the debian-installer process thinks a regular console is being used. That means that we do indeed need that redirection

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Frans Pop
On Monday 14 May 2007 22:29, Rolf Brudeseth wrote: - Step 1: $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] == hvsi0 or hvc0 $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] == hvsi1 Do these pseudo files always exist, or just if a serial

Bug#420820: no console set IBM p5 server

2007-05-14 Thread Rolf Brudeseth
On Monday 14 May 2007 22:29, Rolf Brudeseth wrote: - Step 1: $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] == hvsi0 or hvc0 $ cat /proc/device-tree/options/output-device /vdevice/[EMAIL PROTECTED] == hvsi1 Do these pseudo files always exist, or just

Bug#420820: no console set IBM p5 server

2007-05-11 Thread Geert Stappers
retitle 420820 no console set IBM p5 server reassign 420820 finish-install thanks 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: [EMAIL PROTECTED]:~$ diff /etc/inittab

Bug#420820: no console set IBM p5 server

2007-05-11 Thread Geert Stappers
Op 11-05-2007 om 22:25 schreef Geert Stappers: Op 11-05-2007 om 14:26 schreef Rolf Brudeseth: 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