
Fault Isolation 4-35
The following algorithm is used to determine the output device:
1. If there is a remote card, choose the one with the lowest select code.
2. If there is an internal bit mapped display controller, choose it as console.
3. If there is a bit mapped display controller in DIO-II space, choose the one with
the lowest select code. If not go the next step.
4. Use dummy display drivers.
Only one output device at a time is used as the console output device; however, the
Boot ROM initializes and clears any bit mapped video/graphics board that it finds,
even if that board is not chosen as the console device. Note that if a device fails self-
test then, the device is considered not present. The Boot ROM always tests a device
before choosing it as the console output device.
Input Devices
Common input devices include the HP 46021A Keyboard or a terminal connected to
the RS-232 interface. Keyboards may be directly connected to the HP-HIL interface
port, or to one or two graphics display controllers connected to a local graphics bus
interface board. HP-HIL interfaces in graphics display controllers are considered an
external interface.
Note that if an internal HP-HIL interface and a remote terminal are both present in a
system, they are both enabled. Similarly, if an external HP-HIL interface and a remote
console are both present in a system, they are both enabled, provided no internal key-
board is present. An external interface is never enabled when an internal interface is
present.
When more than one external keyboard is present, the one with the lowest select code
is enabled. If several HP 98735 Graphics Display Controllers exist on a system, then
you must ensure that the external keyboard associated with the display controller at the
address 560000
16
has the lowest select code of all the external keyboards in the system.
This must be done to ensure that the keyboard associated with the first display control-
ler is not input console while the second display controller is output console. The Boot
ROM does not attempt to verify the display/keyboard relationship.
If a keyboard controller or a remote RS-232 card fails, then it is considered by the al-
gorithm to be not present. For example, if an internal keyboard fails self-test, a
Keyboard Failed
message is displayed; however, the input device search algorithm
goes ahead and looks for an external keyboard. The Boot ROM always tests a device
before choosing it as the console input device.
Summary of Contents for Apollo 9000 400dl
Page 4: ...iv VCCI Class 1 ITE Equipment VCCI Class 2 ITE Equipment ...
Page 6: ...vi ...
Page 22: ......
Page 26: ...1 4 Product Overview Figure 1 1 HP Apollo Model 400t or Model 400dl Workstation ...
Page 40: ......
Page 42: ...2 2 System Controls Figure 2 1 Model 400t and 400dl System ...
Page 54: ...3 4 Theory of Operation Figure 3 1 Model 400t System Block Diagram ...
Page 55: ...Theory of Operation 3 5 Figure 3 2 Model 400dl System Block Diagram ...
Page 57: ...Theory of Operation 3 7 Figure 3 4 Model 400s DIO II System Unit Functional Block Diagram ...
Page 58: ...3 8 Theory of Operation Figure 3 5 Model 400s ISA System Unit Functional Block Diagram ...
Page 70: ...3 20 Theory of Operation Figure 3 6 Model 400s System Unit Power Distribution Diagram ...
Page 74: ...4 4 Fault Isolation Figure 4 1 Main Flowchart ...
Page 75: ...Fault Isolation 4 5 Figure 4 1 Main Flowchart Cont ...
Page 76: ...4 6 Fault Isolation Figure 4 2 Model 400t and 400dl System Power LED Not On ...
Page 77: ...Fault Isolation 4 7 Figure 4 3 Model 400s System Power LED Not On ...
Page 78: ...4 8 Fault Isolation Figure 4 4 Domain Keyboard Problems ...
Page 79: ...Fault Isolation 4 9 Figure 4 5 Problems with Display ...
Page 80: ...4 10 Fault Isolation Figure 4 6 Diskless Node Partnering Problems ...
Page 81: ...Fault Isolation 4 11 Figure 4 7 Problems with Winchester Disk ...
Page 82: ...4 12 Fault Isolation Figure 4 8 Problems While Booting ...
Page 83: ...Fault Isolation 4 13 Figure 4 9 Node Causes Network Problems ...
Page 86: ...4 16 Fault Isolation Figure 4 10 Diagnostic Relationships for Domain OS Compatible Mode ...
Page 99: ...Fault Isolation 4 29 Figure 4 13 HP UX Compatible Mode Main Troubleshooting Flowchart ...
Page 100: ...4 30 Fault Isolation Figure 4 14 HP UX Compatible Mode Boot Flowchart ...
Page 101: ...Fault Isolation 4 31 Figure 4 14 HP UX Compatible Mode Boot Flowchart Cont ...
Page 131: ...Fault Isolation 4 61 Figure 4 17 System Unit Cover Removal Model 400t and Model 400dl ...
Page 132: ...4 62 Fault Isolation Figure 4 18 Power Connections Model 400t and Model 400dl ...
Page 148: ......
Page 151: ...FRU Removal and Replacement 5 3 Figure 5 1 System Unit Cover Removal Model 400t and 400dl ...
Page 152: ...5 4 FRU Removal and Replacement Figure 5 2 System Components Model 400t and 400dl ...
Page 181: ...FRU Removal and Replacement 5 33 Figure 5 26 Model 400s Front Door Removal ...
Page 183: ...FRU Removal and Replacement 5 35 Figure 5 27 Model 400s Bezel Removal ...
Page 193: ...FRU Removal and Replacement 5 45 Figure 5 34 Model 400s ISA Backplane Removal ...
Page 195: ...FRU Removal and Replacement 5 47 Figure 5 35 Model 400s ISA Card Cage Removal ...
Page 205: ...FRU Removal and Replacement 5 57 Figure 5 40 Model 400s Memory Board Removal ...
Page 209: ...FRU Removal and Replacement 5 61 Figure 5 43 Model 400s ISA Center Wall Removal ...
Page 211: ...FRU Removal and Replacement 5 63 Figure 5 44 Model 400s Standard ISA Motherboard Removal ...
Page 213: ...FRU Removal and Replacement 5 65 Figure 5 45 Model 400s 3 Slot DIO II Card Cage Removal ...
Page 215: ...FRU Removal and Replacement 5 67 Figure 5 46 Model 400s DIO II Center Wall Removal ...
Page 217: ...FRU Removal and Replacement 5 69 Figure 5 47 Model 400s DIO II Motherboard Removal ...
Page 221: ...FRU Removal and Replacement 5 73 Figure 5 49 Model 400s LED Board Removal ...
Page 234: ......
Page 236: ...A 2 FRU Configurations Figure A 1 CPU Board Configurations ...
Page 240: ...A 6 FRU Configurations Figure A 5 Alternate 802 5 Network Controller AT Jumper Configuration ...
Page 282: ......