IBM 8685 Hardware Maintenance Manual - Page 49

Ethernet controller messages, Recovering the BIOS code

Page 49 highlights

Table 5. Ethernet troubleshooting chart (continued) Ethernet controller problem FRU/actions The Ethernet controller Check the following: stopped working without v Run diagnostics for the Ethernet controller. apparent cause. v Try a different connector on the hub. v Reinstall the device drivers. See your operating-system documentation and the ServerGuide information. v Reseat or replace the adapter. Ethernet controller messages The integrated Ethernet controller might display messages from certain device drivers. The latest information available concerning these messages will be made available at the IBM Support Web site at http://www.ibm.com/pc/support. Note: See the documentation on the Broadcom NetXtreme Gigabit Ethernet Software CD that came with the server for information about configuring the Ethernet controller. Recovering the BIOS code If your BIOS code has become damaged, such as from a power failure during a flash update, you can recover your BIOS code using the flash ROM page-swap jumper (J50) and a BIOS flash diskette. Note: Use one of the following methods to obtain a BIOS flash diskette: v Use the ServerGuide program to make a BIOS flash diskette. v Download a BIOS flash diskette from the World Wide Web. Go to http://www.ibm.com/pc/support/, click IBM Server Support, and make the selections for your server. v Contact your IBM service representative. The flash memory of your server consists of a primary page and a backup page. The J50 jumper controls which page is used to start the server. If the BIOS code in the primary page is damaged, you can use the backup page to start the server; then, start the BIOS flash diskette to restore the BIOS code to the primary page. To recover the BIOS code, complete the following steps: 1. Turn off the server and peripheral devices and disconnect all power cords and external cables; then, remove the cover. 2. Locate jumper J50 (flash ROM page-swap) on the system board. Chapter 3. Diagnostics 39

  • 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
  • 219
  • 220

Table 5. Ethernet troubleshooting chart (continued)
Ethernet controller
problem
FRU/actions
The Ethernet controller
stopped working without
apparent cause.
Check the following:
v
Run diagnostics for the Ethernet controller.
v
Try a different connector on the hub.
v
Reinstall the device drivers. See your operating-system documentation and the
ServerGuide information.
v
Reseat or replace the adapter.
Ethernet controller messages
The integrated Ethernet controller might display messages from certain device
drivers. The latest information available concerning these messages will be made
available at the IBM Support Web site at http://www.ibm.com/pc/support.
Note:
See the documentation on the Broadcom NetXtreme Gigabit Ethernet
Software CD that came with the server for information about configuring the
Ethernet controller.
Recovering the BIOS code
If your BIOS code has become damaged, such as from a power failure during a
flash update, you can recover your BIOS code using the flash ROM page-swap
jumper (J50) and a BIOS flash diskette.
Note:
Use one of the following methods to obtain a BIOS flash diskette:
v
Use the ServerGuide program to make a BIOS flash diskette.
v
Download a BIOS flash diskette from the World Wide Web. Go to
IBM Server Support
, and make the
selections for your server.
v
Contact your IBM service representative.
The flash memory of your server consists of a primary page and a backup page.
The J50 jumper controls which page is used to start the server. If the BIOS code in
the primary page is damaged, you can use the backup page to start the server;
then, start the BIOS flash diskette to restore the BIOS code to the primary page.
To recover the BIOS code, complete the following steps:
1.
Turn off the server and peripheral devices and disconnect all power cords and
external cables; then, remove the cover.
2.
Locate jumper J50 (flash ROM page-swap) on the system board.
Chapter 3. Diagnostics
39