Forcing PCXAL keyboard detection in Tru64?

From: Bütow, Michael (michael.buetow@comsoft.de)
Date: Mon Jul 31 2006 - 08:00:09 EDT


Dear managers,

I have a small keyboard mapping problem on a system of Alpha DS10 machines connected via a KVM switch. All are running Tru64 5.1B+PK3.

On the SRM console of all machines, the kbd_hardware_type is set to PCXAL, matching the physical keyboard.
However, when booted (using mwm, no CDE), the keyboard mapping is incorrect, as experienced by many keys not working, issuing different symbols etc.

Running "xkbdfltmap -noexec" returned a string containing "-m lk411", which would suggest that the OS thinks it's dealing with a type LK411 keyboard, instead of PCXAL. The OS has support for both installed (subsets OSFKBDLK411540 and OSFKBDPCXAL540).

I found I could fix the keyboard mapping temporarily using the command

  /usr/bin/X11/xkbcomp -R/usr/lib/X11/xkb -m pcxal keymap/digital_us -o :0.0

After unsuccessfully searching manuals, forums etc., I look to the collective wisdom of this list for answers to these questions:
1. what might be causing the incorrect mapping?
2. what is best place to configure this setting under Tru64 to make it persistent?

Hoping for advice,
Michael



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:31 EDT