- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Right way to force PCXAL keyboard in Tru64 ?
Operating System - Tru64 Unix
1755122
Members
3431
Online
108830
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-30-2006 11:50 PM
07-30-2006 11:50 PM
Right way to force PCXAL keyboard in Tru64 ?
Hello all,
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
Though I searched quite a few places, I still have these questions:
1. what is causing the incorrect mapping (we have many similar systems which do not exhibit this problem)
2. what is right place to configure this setting to make it persistent?
Hoping for advice,
Michael
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
Though I searched quite a few places, I still have these questions:
1. what is causing the incorrect mapping (we have many similar systems which do not exhibit this problem)
2. what is right place to configure this setting to make it persistent?
Hoping for advice,
Michael
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP