From: Green, Simon (SGreen@KRAFTEUROPE.COM)
Date: Fri Sep 20 2002 - 04:22:27 EDT
I've seem something slightly similar with an S7A. The system had been
booted with a console attached to S2. Subsequently, it wouldn't recognise
anything on S1 as a console. (I believe it would have still worked OK as an
ordinary serial terminal but wasn't in a position to try that.)
To get around it, we booted into maintenance mode. Then when it gets to the
point of saying "Press 1 to have this as your console", (or whatever the
message is), switch the cable over, then press 1. (The display doesn't
refresh, but it should still accept input.) everything was OK after that.
Simon Green
Philip Morris ITSC Europe
AIX-L Archive at http://marc.theaimsgroup.com/?l=aix-l&r=1&w=2
AIX FAQ at http://www.faqs.org/faqs/aix-faq/
N.B. Unsolicited email from vendors will seldom be appreciated.
> -----Original Message-----
> From: Robert Miller [mailto:rmiller@SMUD.ORG]
> Sent: 19 September 2002 22:45
> To: aix-l@Princeton.EDU
> Subject: 7043-150 not displaying on 3151 until OS starts?
>
>
> Folks,
>
> Have an odd problem with a 43p-150. Have an ibm3151 terminal
> connected to
> serial port S1, and when I boot the system it doesn't show the normal
> splashscreen with the "Memory Keyboard SCSI..." text
> displayed that tells
> you when you can hit one of the function keys to boot into
> service mode or
> access SMS. It eventually will come up with some console log
> messages and
> eventually give a login prompt that you can login to and use
> to access the
> box.
>
> When I let the box boot and change the console to the other
> serial port,
> everything works fine. When I change the console back, it
> stops working
> again.
>
> This really sounds odd - I've run diags and they come up
> clean, has anyone
> seen this before or have any idea how to fix it? If it never
> came up with a
> login prompt, I'd assume the port or the cable was bad, but
> it eventually
> comes up with a usable login and the calbe works fine when
> attached to the
> other serial port. So, it's something to do with the port,
> but I can't
> think of what - perhaps something munged in the microcode for
> this box?
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 22:16:13 EDT