IBM JS20 Hardware Maintenance Manual - Page 159

Mouse, problems

Get IBM JS20 - BladeCenter - 8842 PDF manuals and user guides
UPC - 000435230263
View all IBM JS20 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 159 highlights

Symptom FRU/action Only the cursor appears. v Verify that the correct blade server controls the console. If the problem remains, see"Undetermined problems" on page 156. The monitor goes blank when v Verify that the monitor cable is connected to the video port on the BladeCenter you direct it to a working blade management module. Some IBM monitors have their own self-tests. If you server, or goes blank when you suspect a problem with the monitor, see the information that comes with the start some application programs monitor for adjusting and testing instructions. in the blade servers. If you still cannot find the problem, try using the monitor with another blade server. If the problem persists, see the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit. The screen is wavy, unreadable, 1. If the monitor self-tests show the monitor is working correctly, consider rolling, distorted, or has screen the location of the monitor. Magnetic fields around other devices (such as jitter. transformers, appliances, fluorescent lights, and other monitors) can cause screen jitter or wavy, unreadable, rolling, or distorted screen images. If this happens, turn off the monitor. (Moving a color monitor while it is turned on might cause screen discoloration.) Then move the device and the monitor at least 305 mm (12 in.) apart. Turn on the monitor. Notes: a. To prevent diskette drive read/write errors, be sure the distance between monitors and diskette drives is at least 76 mm (3 in.). b. Non-IBM monitor cables might cause unpredictable problems. c. An enhanced monitor cable with additional shielding is available for the 9521 and 9527 monitors. For information about the enhanced monitor cable, contact your IBM reseller or IBM marketing representative. 2. Monitor. 3. System board. Wrong characters appear on the 1. If the wrong language is displayed, update the firmware or operating system screen. with the correct language in the blade server that has ownership of the monitor. 2. Monitor. 3. System board. No video. 1. Make sure the correct machine is selected, if applicable. 2. Make sure all cables are locked down. Mouse problems Symptom The mouse does not work. FRU/action 1. Verify that: v The blade server is connected to the shared BladeCenter monitor. v The mouse cable is securely connected to the BladeCenter management module, and the keyboard and mouse cables are not reversed. v The mouse works correctly with other blade servers. v The mouse is recognized as a USB device, not PS2, by the blade server. Although the mouse is a PS2-style device, communication with the mouse is through an internal USB bus in the BladeCenter chassis. Some operating systems permit you to select the type of mouse during installation of the operating system. Select USB. 2. Mouse or pointing device. 3. Management module on the BladeCenter unit; see the Hardware Maintenance Manual and Troubleshooting Guide for your BladeCenter unit. Chapter 10. Symptom-to-FRU index 149

  • 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
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
Symptom
FRU/action
Only
the
cursor
appears.
v
Verify
that
the
correct
blade
server
controls
the
console.
If
the
problem
remains,
see“Undetermined
problems”
on
page
156.
The
monitor
goes
blank
when
you
direct
it
to
a
working
blade
server,
or
goes
blank
when
you
start
some
application
programs
in
the
blade
servers.
v
Verify
that
the
monitor
cable
is
connected
to
the
video
port
on
the
BladeCenter
management
module.
Some
IBM
monitors
have
their
own
self-tests.
If
you
suspect
a
problem
with
the
monitor,
see
the
information
that
comes
with
the
monitor
for
adjusting
and
testing
instructions.
If
you
still
cannot
find
the
problem,
try
using
the
monitor
with
another
blade
server.
If
the
problem
persists,
see
the
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
for
your
BladeCenter
unit.
The
screen
is
wavy,
unreadable,
rolling,
distorted,
or
has
screen
jitter.
1.
If
the
monitor
self-tests
show
the
monitor
is
working
correctly,
consider
the
location
of
the
monitor.
Magnetic
fields
around
other
devices
(such
as
transformers,
appliances,
fluorescent
lights,
and
other
monitors)
can
cause
screen
jitter
or
wavy,
unreadable,
rolling,
or
distorted
screen
images.
If
this
happens,
turn
off
the
monitor.
(Moving
a
color
monitor
while
it
is
turned
on
might
cause
screen
discoloration.)
Then
move
the
device
and
the
monitor
at
least
305
mm
(12
in.)
apart.
Turn
on
the
monitor.
Notes:
a.
To
prevent
diskette
drive
read/write
errors,
be
sure
the
distance
between
monitors
and
diskette
drives
is
at
least
76
mm
(3
in.).
b.
Non-IBM
monitor
cables
might
cause
unpredictable
problems.
c.
An
enhanced
monitor
cable
with
additional
shielding
is
available
for
the
9521
and
9527
monitors.
For
information
about
the
enhanced
monitor
cable,
contact
your
IBM
reseller
or
IBM
marketing
representative.
2.
Monitor.
3.
System
board.
Wrong
characters
appear
on
the
screen.
1.
If
the
wrong
language
is
displayed,
update
the
firmware
or
operating
system
with
the
correct
language
in
the
blade
server
that
has
ownership
of
the
monitor.
2.
Monitor.
3.
System
board.
No
video.
1.
Make
sure
the
correct
machine
is
selected,
if
applicable.
2.
Make
sure
all
cables
are
locked
down.
Mouse
problems
Symptom
FRU/action
The
mouse
does
not
work.
1.
Verify
that:
v
The
blade
server
is
connected
to
the
shared
BladeCenter
monitor.
v
The
mouse
cable
is
securely
connected
to
the
BladeCenter
management
module,
and
the
keyboard
and
mouse
cables
are
not
reversed.
v
The
mouse
works
correctly
with
other
blade
servers.
v
The
mouse
is
recognized
as
a
USB
device,
not
PS2,
by
the
blade
server.
Although
the
mouse
is
a
PS2-style
device,
communication
with
the
mouse
is
through
an
internal
USB
bus
in
the
BladeCenter
chassis.
Some
operating
systems
permit
you
to
select
the
type
of
mouse
during
installation
of
the
operating
system.
Select
USB.
2.
Mouse
or
pointing
device.
3.
Management
module
on
the
BladeCenter
unit;
see
the
Hardware
Maintenance
Manual
and
Troubleshooting
Guide
for
your
BladeCenter
unit.
Chapter
10.
Symptom-to-FRU
index
149