The keyboard issues are likely a result of the KVM you're using. While the "O" series SGIs have the ubiquitous PS2 keyboard and mouse interface, SGI elected to use the less common keyboard scan code set 3 <scan code set 2 is more common in the PC world>. Most PS2 keyboards work when directly connected to an SGI system, but some KVMs seem to only translate a fairly rigid implementation of scan code 2.
So, some KVMs have the ability to transparently relay scan code set 3, some require a jumper or configuration change, and others apparently pass everything through as the <more common> scan code 2. For instance, I have a KVM that works as long as all of the systems connected are SGI; if one of the connected systems is a PC that uses scan 2, as soon as I select that system the key mapping is incorrect for the SGI systems and cannot be reset without removing the PC and restarting the SGI systems.
A little background: man pckeyboard
The PS/2 Keyboard Interface
The Indy, Indigo2, O2, OCTANE and Onyx2 systems use an industry-standard
PC-compatible keyboard with a PS/2 style (6 pin mini-DIN) connector.
The keyboard connects to the back of the system unit with a shielded
partially coiled cord and is detachable at the system cabinet only. The
system communicates with the keyboard via a clocked serial protocol. SGI
uses keyboard scan code set 3, which sends a scan code on key press and a
"break" code followed by repeating the scan code. Every key has a unique
scan code. All keys function the same way, allowing the system software
to use keys in any manner.
* Scan Code Set 1
- Original XT scan code set; supported by some modern keyboards
* Scan Code Set 2
- Default scan code set for all modern keyboards
* Scan Code Set 3
- Optional PS/2 scan code set--rarely used
And lastly, an indirect mention in a Belkin support document of how to apply the correct scan code to specific ports on one of their enterprise level KVMs <which may or may not work with other Belkin models>: http://www.belkin.com/support/article/? ... 199&scid=0