PS/2 Error Index
The first PS/2 was born in early 1987... As of today [25 May 2019] the first PS/2s are around 32 years old. This is possibly older than some new users. These young'uns have not had 20 years to immerse themelves in PS/2 arcania, nor is there the [formerly] unlimited supplies of frugally priced parts and systems. Sadly, the folks that were present and had a part in the creation and development of these systems are starting to fade away... I have to collect and unify troubleshooting so as to assist folks that are arriving late to the party...



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
   If multiple errors occur during POST, resolve them in the order that they are presented.
 
   Always cold boot and run Advanced Diagnostics (go into System Programs and at the main menu do a Ctrl-A) before replacing components when trying to resolve software problems. If diags don't fail, replacing components will probably not solve the problem. Refer to the software vendor for possible patches. The software may not be supported on the system. 

Multiple POST Error Procedure
   If more than one error code is displayed, diagnose the first error code first. The cause of the first error code could cause other devices to fail. This is especially important with configuration errors.

   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
A o (small o) indicates a short beep
A - (underscore) means a long beep

o            Normal Operation
o o           A problem exists, check config. Run diags, if no error code displayed
_ o           Display or display adapter problem.
_ o o         Display or display adapter problem.
_ o o o       Display or display adapter problem.
o o o o o o   Continuous short beeps. Check keyboard.
________      Continuous solid beep. System board.
 

Dead System (no POST, screen blank, no beep) 
   The most likely cause is a device that is shorting out the power supply. An improperly inserted memory module, a defective adapter or device can cause a short circuit. To prevent damage to a power supply, the system board must present a "POWER GOOD" signal to the power supply in 150mS or less. If this does not occur, then the power supply shuts down internally. 

   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
1.   Verify power is on (IS cord plugged in?). If the system has power, then go to #2


        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.

When troubleshooting intermittent post errors, or any unusual, system problems, (for example; system performs power-on reset unexpectedly during operation) check the line cord for proper seating.  Slight forming of the male contacts in the system unit power supply connector may correct the problem -OR- you can sometimes adjust the female contacts in the line cord plug.

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. 
       Remove all external connections, KB, mouse, display, 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.
         If OK, replace system board memory and retry # 3. 
         If still no beep, verify PSU voltages. If voltages are OK, replace system board. 
         If voltages are incorrect, replace the power supply. 85/95 PS 90 PS 500 PS


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 
       something is added and the beep is no longer heard, the last item plugged in is 
       probably defective. At this point, it is not necessary to reconfigure the system 
       each time an adapter or device is added because we expect any beep. 

Batteries
   Defective or weak batteries can cause loss of all setup information. If only part of the setup is lost, the battery is probably NOT the cause. Inaccurate time is usually caused by software, but some of the older models with the 6v batteries are more prone to time slowing down.


Clearing 96 8N1
From Peter Wendt- 
Do the following: 
- push a piece of card under the CMOS-buffer battery clip to have it isolated 
- toggle the Password Override Jumper 
- wait 20 minutes 
- remove the card from under the battery clip 
- start the system with a known good board & appropriate ref.disk 

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. 
 (Ed. I just pull the battery and wait 5 minutes, then it autoconfigures with a 161/163, Date Time not set) 

 

9595 Main Page