OH... the keyboard gets locked up if my TERM is ansi or scoansi.
If anyone needs more info, please ask.
Thanks,
DonF


foz_67@hotmail.com (foz_67) wrote in message news:<8a247e46.0309281500.46c51224@posting.google. com>...
> Hi there,
>
> Our keyboard gets locked up when running an oash menu script.
> We get total loss of keyboard function, no CapsLock, no NumLock,
> nothing.
> The same script doesn't lock up telnet or serial connections, only the
> console's keyboard.
>
> Running OSR5.0.6 Enterprise with the following patches...
> rs506a/oss629a/oss635a/oss636a/oss639a/oss640a/oss642a/oss643a/oss645a/oss648a
>
> We've been using the same menu script for a few years now without
> problems. This problem has started happening in the last 2 or 3
> months on a fresh installations on new Dell PowerEdge servers. We've
> had prior (exact installs) on identical PowerEdge servers without
> issue.
>
> I've tried different keyboards but I'm still getting the same result.
>
> Someone on this news group had suggested the following...
>
> >This sounds like the keyboard controller is locking up. Next time it
> >happens, dial in and log in as root. Enter the commands:
> >
> > # kbmode at < /dev/tty01
> > # kbmode xt < /dev/tty01
> >
> >Check whether the keyboard starts working again. If it does, we're
> on
> >the right track. (Note that in some cases, it will start to work
> again
> >but will fail again almost immediately. This is OK; we're really
> just
> >making sure of our problem diagnosis. If the kbmode sequence lets
> you
> >get any further response out of the keyboard, the problem is
> solvable).
> >
> >Ok. Supposing that the kbmode sequence got a response out of the
> >keyboard: try the following patch:
> >
> > # _fst -w /unix -
> >* i8042disints/W -1 <--- make sure that's a capital W
> >* $q
>
>
> Although the kbmode commands did get the keyboard back, the patch made
> no difference.
>
> Any more ideas?
>
> Thanks,
> DonF