Troubleshooting
Problem
This tip attempts to document problems that may occur when using Linux in combination with the BladeCenter management module's remote control features.
Resolving The Problem
| Source |
|---|
RETAIN tip: H09845
| Symptom |
|---|
This tip attempts to document problems that may occur when using Linux in combination with the BladeCenter management module's remote control features.
Please also refer to the Linux installation instructions for the BladeCenter for additional information related to installing Linux. The installation instructions contain details on how to configure XFree86 for use with the BladeCenter management module remote control. Some of the problems that may be seen include:
- Remote mouse cursor does not track correctly.
- Remote mouse alignment issues under the graphical login screen (KDM or XDM)
- Remote and local mouse not synchronized during remote control session.
- No mouse cursor.
- Single clicks from the remote mouse do not work.
| Affected configuration |
|---|
The system may be any of the following IBM eServer systems:
- IBM eServer BladeCenter, Type 8677 (any model).
The following network operating systems NOS(es) are affected:
- SUSE LINUX, any supported version.
- Red Hat Enterprise LINUX, any supported version
Note: This does not imply that the network operating system will work under all combinations of hardware and software. Please see the compatibility page for more information: http://www.ibm.com/servers/eserver/serverproven/compat/us/
| Solution |
|---|
| Remote mouse cursor does not track correctly: |
|---|
It is necessary that the mouse handler (mousedev) in Linux get the correct resolution information in order to track the remote mouse cursor properly. If the host (Blade) resolution is not 1024x768:
- Enter the following commands to provide the correct resolution data to mouse handler:
init 3 (Switch to text mode if necessary) rmmod mousedev (Unload the mouse driver module)
- Add the following statement to /etc/modules.conf (for SUSE LINUX Enterprise 8 or RHEL 2.1 and 3) or to /etc/modprobe.conf (for SUSE LINUX Enterprise 9 and RHEL 4 or later):
options mousedev xres=X yres=Y
(Notify the mouse driver of the video resolution where X and Y specify the video resolution)
- Enter the following commands:
insmod mousedev (Reload the mouse driver module) init 5 (Return to GUI mode if necessary)
Note: It is also necessary to set the mouse acceleration and threshold values to 1. The default settings in Linux will not allow the remote mouse to track properly. To change mouse acceleration and threshold values for the current session open a terminal window and type xset m 1 1 and press Enter.
| To preserve these changes between sessions do the following: |
|---|
| GNOME |
|---|
- Using the keyboard press CTRL+ESC keys to bring a menu on the desktop.
- From this menu select: Programs -> Settings -> Session -> Session properties and startup programs.
- Select the Startup Programs tab.
- Select Add option to open another window.
- In the command line type xset m 1 1 and click OK to save this command.
- Click Apply and then OK to exit this window.
- Log out from this session and be sure to check the save current setup check box on the Log out window.
The next time you log in, the remote and local mouse will be synchronized.
| KDE |
|---|
- Using the keyboard press ALT+F1 to bring a menu on the desktop.
- From this menu, press Preferences -> Peripherals -> Mouse.
- Select the Advanced Tab and change the Pointer Acceleration and Threshold values to 1.
- Click Apply and then OK to exit this window.
- Log out from this session and be sure to check the save current setup check box on the Log out window.
The next time you log in, the remote and local mouse will be synchronized.
| WindowMaker |
|---|
- Using the keyboard press F12 to bring a menu on the desktop.
- Select WindowMaker and then WPrefs to launch WindowMaker Preferences Utility.
- Select the Mouse Preferences Icon and change the acceleration and threshold values to 1.
- Save changes and Close the window.
- Log out from this session and be sure to check the Save workspace State check box on the Log out window.
The next time you log in, the remote and local mouse will be synchronized.
| MWM |
|---|
- Open a terminal window and type xset m 1 1 and press Enter.
- See the instructions under section labeled "Remote and local mouse not synchronized during remote control session" for additional help if needed.
The change is not saved between sessions so you will have to repeat this every time you login.
| TWM |
|---|
- Open a terminal window and type xset m 1 1 and press Enter.
See the instructions under section labeled "Remote and local mouse not synchronized during remote control session" for additional help if needed.
The change is not saved between sessions so you will have to repeat this every time you login.
| 2.0 Remote mouse alignment issues under the graphical login screen (KDM or XDM) |
|---|
- At the login screen, switch to a console by pressing Ctrl + Alt + F2
- Log into the system as the root user.
- Switch out of the graphical run level (5) by running the command:
init 3
- Press Enter to get the command prompt back.
- For SUSE, edit the '/etc/X11/xdm/Xsetup' file. Insert the following line at the end of the file, but before the line that says 'exit 0':
$xset m 1 1
- For Red Hat, add the following entry to the /etc/X11/xdm/Xsetup_0 file:
xset m 1 1
- Switch back to GUI mode by running the command:
init 5
| 3.0 Remote and local mouse not synchronized during remote control session. |
|---|
If the remote and local mouse are not synchronized properly, there is a constant off set between them on the remote client window then move the mouse towards the bottom of the video screen in the remote client window. Then move the local mouse back in the window. This will fix the alignment between the two mice.
| 4.0 No mouse cursor. |
|---|
- Open a terminal window.
- Type sax2 -F mouse and press Enter.
- The utility will start and display auto-detected values and the mouse should work. Select Apply.
- Select Finish option.
- On the next screen select Start to test the settings. The utility should display a test screen with current settings.
- Select Save Configuration option
- Exit the utility.
To fix this for RHEL do the following:
- Open a terminal window.
- Type setup
- Select Mouse Configuration.
- Scroll down and select the generic or two-button USB mouse.
- Select OK.
- Select Yes to update the X Window System Configuration.
- Exit the utility.
- Press Ctrl+Alt+Backspace.
| 5.0 Single clicks from the remote mouse do not work. |
|---|
- Type sax2 -F mouse and press Enter.
- Delete the mouse settings by selecting Remove.
- Select Finish and Save Configuration option
- Exit the utility.
- Reboot the server
- Login (text mode since no pointer is defined yet)
- Type sax2 and press Enter.
- The SaX2 utility will display a screen with auto-detected values and the mouse should work now.
- To change settings (e.g. resolution) select Alter and then Change Configurations. Do NOT use any previous configuration files detected by the system.
- Select Next to change settings (do not change settings that are working or okay - e.g. Mouse).
- After making changes select Finish and then Start to test the new settings. The utility should display a test screen with the new settings.
- Select Save Configuration option
- Exit the utility.
- Type startx at the prompt for the changes to take effect.
To fix this for RHEL do the following:
- Open a terminal window.
- Type setup
- Select Mouse Configuration.
- Scroll down and select the generic or two-button USB mouse.
- Select OK.
- Select Yes to update the X Window System Configuration.
- Exit the utility.
- Press Ctrl+Alt+Backspace.
The next time you log in to the X Window System, the remote mouse will work correctly.
Document Location
Worldwide
Was this topic helpful?
Document Information
Modified date:
28 January 2019
UID
ibm1MIGR-45201