Dead System Troubleshooting Dead System Beep Codes CheckPoint Codes (CP codes on Model 95 LED) System Will Not POST - [Breadboarding] POST Errors [errors displayed on screen] Multiple POST Errors General Error Codes 118 Error Code [Memory error logging process 8590 and 8595] 2xx error - Failing memory location, size, speed and type [Mod. 56/57, 76/77, 85 and 90/95] SCSI Error Codes SCSI Fixed Disk Diagnostic Error Return Codes IML Error Codes (I99xxxx) Initial Microcode Load on the 76/77, 85, 90, 95, 500 - and the TP700/720! Clearing the 96 8N1 code [console mode selected!] POST
Errors Multiple POST Error Procedure
If no error codes appear, see if the error symptoms are listed in the Error list. If an adapter consists of multiple FRUs (memory for example) remove the optional FRUs one at a time to see if symptoms change before replacing the adapter. External surge suppressors may be the source for hard to diagnose problems. PS/2
Beep Codes o
Normal
Operation Dead
System (no POST, screen blank, no
beep) Known dufus tricks- SIMM inserted backwards (with enough force ANYTHING is possible). adapter not fully seated in expansion slot, power cord not plugged in, unsupported/defective adapter (Non-IBM adapter, like ALR..), or with a heavily loaded system, too many drives starting at once (overcurrent as the drives attempt to spin up- leave motor start jumper open to start drives after the controller interrogates them) Troubleshooting a Dead System
NOTE:
Intermittent and very difficult to diagnose system
problems, may be caused by line cords which are not
fully seated, or are too loose to make a tight
connection. WARNING! Remove
line cord from outlet before working on line cord
contacts! Replacing the line cord may be necessary in some cases.
Both ends of the line cord should be checked. 2. Remove all adapters, options,
extra memory, etc. 3. Plug in, power on, listen for a
beep. The beep indicates POST has run. Multiple
beeps may occur. 4A. If no beep is heard, verify continuity through
speaker. NOTE: On systems with LogicLock, the switches used to detect unauthorized access might be put in the wrong position during case re-installation. Unit does not run with cover removed (9556/57 9576/77) 4B. If a beep occurs, reinstall adapters one at a
time and return to step 3. When Batteries |
Clearing 96 8N1 From Peter Wendt- IBM wrote in the HMM "Remove the battery, then wait 5 minutes ..." (HMM, September 1993, P/N 71G9316, page 300, "96 8N1 Error Message") but empirical research showed that this doesn't work fairly often. Shortening the battery connectors (with the battery removed of course) *and* toggling the startup password jumper seems to be the only fast cure. There seems to be a board logic, that ANDs the two conditions after a power-on and deletes the entire setup from the CMOS. At least during the "hot phase" when the Mod. 90s and 95s can be found in larger amounts at the customers this procedure was the only one that worked in a sufficiently fast way. And I had quite a lot 95s under service ... (Some are mine now) That worked any time I'd landed on the "ASCII-console
mode" during fiddling with SOD- / bad-DMA platforms and
Kingston Turbochips :-) Moving only the jumper or only
isolating the battery often did *not* cure it. Which is
slightly strange. Password Jumper:
The Stage 2 POST code on the reference diskette is identical to the code loaded onto the system partition, Moving this jumper sets all default values, except ASCII terminal mode. It should be further noted, that moving the Power-On password jumper is effective for only 1 Power-On cycle because stage 1 POST tracks (records) the position of the jumper each time it is run.
|
9595 Main Page |