IBM 4910-33D Installation Guide - Page 47

Problem determination, Symptom, Actions - 33s

Get IBM 4910-33D PDF manuals and user guides View all IBM 4910-33D manuals
Add to My Manuals
Save this manual to your list of manuals

Page 47 highlights

March 2009 Problem determination Table 10. 4810/4910 Problem symptoms table (continued) Symptom Actions System Getting Blue Screens Often, blue screens are caused by OS, driver, or application software issues. Diagnosing blue screens should be handled through a software diagnostic path. Slow System Behavior Ethernet Connection slow No Audio No Video Serial IO Device Not Working USB IO Device Not Working To determine if the hardware has contributed to a blue screen situation, run the system unit diagnostics, including running the extended diagnostics for the hard drive. Run the RSS system unit diagnostics test to determine if the system unit hardware is having any problems detected by the diagnostics; if not, invoke a software diagnostic path. Run the RSS system unit diagnostics test, including the Ethernet test, while the system is connected to the Ethernet; if not, invoke a software diagnostic path. Confirm that speaker cables are securely plugged into the system unit. Run the RSS system unit diagnostics test, including the audio test. Confirm that the proper audio driver is installed. 1. Confirm that the monitor power cord is attached. 2. Confirm that there is a solid connection of the video cable to the system unit in the correct monitor port. 3. Ensure that the monitor is powered ON. 4. Perform monitor diagnostics. 1. Examine the device cable and replace if indicated. 2. Run self tests on the device and replace if indicated. 3. Use the RSS diagnostic program and the appropriate wrap plug tool. If this test is successful, then the problem relates to the IO device or to a non-hardware system software problem. 4. Replace a SurePort card if the port is part of the SurePort card. 1. Confirm operation of the IO port USB connection using the memory key to boot diagnostics through that port. Chapter 4. Problem determination 33

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
Table 10. 4810/4910 Problem symptoms table (continued)
Symptom
Actions
System Getting Blue Screens
Often, blue screens are caused by OS, driver, or
application software issues. Diagnosing blue screens
should be handled through a software diagnostic path.
To determine if the hardware has contributed to a blue
screen situation, run the system unit diagnostics,
including running the extended diagnostics for the
hard drive.
Slow System Behavior
Run the RSS system unit diagnostics test to
determine if the system unit hardware is having any
problems detected by the diagnostics; if not, invoke a
software diagnostic path.
Ethernet Connection slow
Run the RSS system unit diagnostics test, including
the Ethernet test, while the system is connected to the
Ethernet; if not, invoke a software diagnostic path.
No Audio
Confirm that speaker cables are securely plugged into
the system unit. Run the RSS system unit diagnostics
test, including the audio test. Confirm that the proper
audio driver is installed.
No Video
1.
Confirm that the monitor power cord is attached.
2.
Confirm that there is a solid connection of the
video cable to the system unit in the correct
monitor port.
3.
Ensure that the monitor is powered
ON
.
4.
Perform monitor diagnostics.
Serial IO Device Not Working
1.
Examine the device cable and replace if indicated.
2.
Run self tests on the device and replace if
indicated.
3.
Use the RSS diagnostic program and the
appropriate wrap plug tool. If this test is
successful, then the problem relates to the IO
device or to a non-hardware system software
problem.
4.
Replace a SurePort card if the port is part of the
SurePort card.
USB IO Device Not Working
1.
Confirm operation of the IO port USB connection
using the memory key to boot diagnostics through
that port.
Problem determination
March 2009
Chapter 4. Problem determination
33