IBM 8832 Deployment Manual page 33

procedures in the following sections to configure Red
acc urate mouse tracking. Type the commands through the remote console or at the keyboard that is
atta ched to the BladeCenter unit.
1. P roviding resolution information to the mouse handler
The mouse handler (mousedev) must have the correct resolution informatio
mouse cursor correctly. If the host (blade server) resolution is not 1024 x
following steps to provide the correct resolution data to the mouse handler:
If you need to switch to
a.
b. To unload the mouse device driver module
c. To notify the mouse device driver of the video resolution, add the
/etc/modules.conf file:
options mousedev xres=x yres=y
(where x and y are the video res
d. To reload the mouse device driver module, type: insmod mousedev
e. To return to GUI mode, if necessary, type: init 5
2. C hanging the pointer speed settings
T o enable the remote mouse to track properly in Red Hat Linux, set the mouse acceleration and
threshold values to 1. To change mouse acceleration and threshold values for the current
session, open a terminal window and type: xset m 1 1
Complete the followi
mouse is not supported in the text console.
* If you are using GNOME:
1. Press Ctrl+Esc.
2. From the menu, click Programs->Settings->Session->Se
3. Click the Startup programs tab.
4. Click Add.
5. In the command line, type: xset m 1 1 and click OK.
6. Click Apply and OK
7. Log out from the session and select
The next time you log in, the remote and local mouse are synchron
* If you are using KDE:
1. Using the keyboard, press Alt+F1.
2. From the menu, click Preferences --> Peripherals --> Mouse.
3. Click the Advanced tab and change the Pointer Acceleration and Thre
4. Click Apply and OK to close the window.
5. Log out from the session and select "Save current setup" in the Log Out window.
The next time you log in, the remote and local mouse are synchronized.
3. S ynchronizing the remote and local mouse for remote control sessions
If the remote and local mouse are not sy
between them on the remote client window
screen in the remote client window. Then, move the local mouse back in the window. This will
correct the alignment between the mice.
4. C orrecting mouse cursor click related issues
NOTE: The blade server might not start in GUI mode if the
server is turned on. This migh
monitor, and mouse. If there is no mou
work, complete the following steps to correct the problem:
1. Open a terminal window.
2. Type setup.
3. Click Mouse Configuration.
4. Scroll down and select the g
5. Click Yes to update X Configuration.
Version 3.0, 3/10/2006
The BladeCenter Deployment Guide is intended as a personal productivity tool. It is not intended to be comprehensive and is provided for
guidance only, on an 'as is basis' without warranty of any kind. Please be aware that its contents have not been certified by IBM.
IBM BladeCenter Deployment Guide
text mode, type: init 3
olution)
ng steps to preserve these changes between sessions. NOTE: A remote
to close the window.
"Save current setup" in the Log Out window.
nchronized correctly, that is, if there is a constant offset
, move the mouse toward the bottom of the monitor
t happen if the blade server is not associated with the keyboard,
se cursor or if single clicks from the remote mouse do not
eneric or two-button USB mouse. Click OK.
http://w3-03.ibm.com/support/techdocs/atsmastr.nsf/WebIndex/WP100564
Hat Linux and the X Window System for
, type: rmmod mousedev
ssion properties->Startup programs.
ized.
mouse is not detected when the blade
n to track the remote
768, complete the
following line to the
shold values to 1.
33