Conference turris::digital_unix

8598.0. "disable keyboard check on 3.2X?" by GIZARD::WETZEL () Mon Jan 27 1997 13:20

OK, I've spent a couple of hours searching for the answer I'm looking
for.  Lot's of info that is very close, but none on the money.  My
apologies if I missed the answer.  

ANYWAY....

A slightly different version of this note was placed in the Sable
notesfile.  Originally, I thought the issue was caused by firmware.
Now I believe the issue is with DIGITAL UNIX 3.2X.  (Notice I said
"issue" and not "bug" or "feature").  We know that all bugs are
actually features and therefore there are no bugs.


I have a customer with a rather unique situation.  We sell a 3rd party
device called Master Console.  What the Master Console does is connect 
two or more computers to one monitor, mouse, and keyboard.  It has
enough intelligence to cause each system to believe that it has it's
own monitor, mouse, and keyboard.   Therefore whenever the computer
expects something from the keyboard the Master Console returns it.
The Master Console supports both the PCXAL (LK471) and LK411.

The customer is using a PCXAL.

Here's the problem.  I see that during UNIX boot (3.2G in my case) the Alpha
queries to find out what type of keyboard it has.  It first checks if
it is a LK411.  The Master Console recognizes it and returns the appropriate
sequence causing the Alpha to believe that the keyboard is a LK411.

So, the customer boots and gets LK411 mapping on a LK471.

Now, of course one solution is for Master Console to change their firmware.
I've made them aware of that.  However, I've been told that there is a way 
to stop this check from happening.  At first glance I thought that the
>>>set kbd_hardware_type PCXAL would fix it, but it seems to have no effect.

Is this keyboard check disable function fact or fiction?

--------------------------------------------------------------------------------

Possible Options are:

	1.  Upgrade UNIX
	2.  re-map keyboard after boot.
	3.  Disable keyboard check. 

1 is probably out for the near future.  2 is a kloodge.  I really want
to go with 3, but haven't figured out how yet.  

I don't think there's a ready automatic solution to 
your problem.  The device driver for the keyboard
will send a sequence of commands to the keybaord to
see what it is.  If the Master Console says its LK411
we believe it and there is no existing overide.  If
the kbd_hardware_type console firmware variable does
exist, its only at the firmware level and is not exported
to the O/S.  The driver wasn't designed to support such
a device.

We are doing some work in the input space in the next
major release (read, not available this year).  I will
forward the request for a configuration variable
(/etc/sysconfigtab) that would allow the ability to
force the default keyboard or do something to handle
this case.

Sounds like your fasted bet is a Master Console
option to set the keybaord type.

If you'd like to keep in touch, feel free to send
me mail directly,

Paul
[Posted by WWW Notes gateway]