APPENDIX C: I NFORMATIONAL NOTES 153As a result, the Virtual KVM Client and the Multi-Platform Client (MPC) are unable to processthese keys from a Mac client’s keyboard.Mouse Pointer Synchronization (Fedora)When connected in dual mouse mode to a target server running Fedora, the target and localmouse pointers may lose synchronization after some time.To re-synchronize the mouse cursors:Use the Synchronize Mouse option from the Virtual KVM Client.The following table summarizes the Dominion KX II mouse modes, and whether or not thesemodes remain synchronized when accessing target servers running Fedora:MOUSE MODE FEDORA C ORE 5 FEDORA C ORE 6Absolute Mouse Synchronization™ No NoIntelligent Mouse Mode No YesStandard Mouse Mode Yes NoResolving Fedora Core FocusUsing the Multi-Platform Client (MPC), occasionally there is an inability to log into a DominionKX II device or to access target servers (Windows, SUSE, etc.). In addition, the Ctrl+Alt+M keycombination may not bring up the Keyboard Shortcut menu. This situation occurs with thefollowing client configuration: Fedora Core 6 and Firefox 1.5 or 2.0.Through testing, it has been determined that installation of libXp resolves window focusing issueswith Fedora Core 6. Raritan has tested with libXp-1.0.0.8.i386.rpm; this resolved all of thekeyboard focus and popup-menu problems.Note: libXp is also required for the SeaMonkey™ (formerly Mozilla) browser to work with theJava plugin.SUSE/VESA Video ModesThe SuSE X.org configuration tool SaX2 generates video modes using modeline entries in theX.org configuration file. These video modes do not correspond exactly with VESA video modetiming (even when a VESA monitor is selected). Dominion KX II, on the other hand, relies onexact VESA mode timing for proper synchronization. This disparity can result in black borders,missing sections of the picture, and noise.To configure the SUSE video display:1. The generated configuration file /etc/X11/xorg.conf includes a “Monitor” section with anoption named UseModes. For example:UseModes "Modes[0]"2. Either comment out this line (using #) or delete it completely.3. Restart the X server.With this change, the internal video mode timing from the X server will be used and willcorrespond exactly with the VESA video mode timing, resulting in the proper video display onthe Dominion KX II.
