IBM 8835 - Eserver 325 - 1 GB RAM Maintenance And Troubleshooting Manual page 90

Note: See "System" on page 94 to determine which components should be replaced by a field service technician.
Symptom
A problem occurs only
occasionally and is difficult to
detect.
Note: See "System" on page 94 to determine which components should be replaced by a field service technician.
Symptom
All or some keys on the
keyboard do not work.
The mouse or pointing device
does not work.
Note: See "System" on page 94 to determine which components should be replaced by a field service technician.
Symptom
The amount of system memory
displayed is less than the
amount of physical memory
installed.
80 Eserver 325 Type 8835: Hardware Maintenance Manual and Troubleshooting Guide
Intermittent problems
FRU/action
1. Verify that:
v All cables and cords are connected securely to the rear of the server and
attached options.
v When the server is turned on, air is flowing from the rear of the server at the
fan grill. If there is no airflow, the fan is not working. This causes the server
to overheat and shut down.
v Ensure that the SCSI bus and devices are configured correctly and that the
last external device in each SCSI chain is terminated correctly.
2. Check the system error log.
Keyboard, mouse, or pointing-device problems
FRU/action
1. Verify that:
v The keyboard cable is securely connected to the system, and the keyboard
and mouse cables are not reversed.
v The server and the monitor are turned on.
2. Keyboard.
3. System board.
1. Verify that:
v The mouse or pointing-device cable is securely connected, and that the
keyboard and mouse cables are not reversed.
v The mouse device drivers are installed correctly.
2. Mouse or pointing device.
3. System board.
Memory problems
FRU/action
1. Verify that:
v The memory modules are seated properly.
v You have installed the correct type of memory.
v If you changed the memory, you updated the memory configuration with the
Configuration/Setup Utility program.
v All banks of memory on the DIMMs are enabled. The server might have
automatically disabled a DIMM bank when it detected a problem or a DIMM
bank could have been manually disabled.
2. Check POST error log for error message 289:
v If the DIMM was disabled by a system-management interrupt (SMI), replace
the DIMM.
v If the DIMM was disabled by the user or by POST:
a. Start the Configuration/Setup Utility program.
b. Enable the DIMM.
c. Save the configuration and restart the server.
3. DIMM.
4. System board.