Type 1 Complex

rf90951a Type 1 Refdisk
rd9095a Diagnostics (common to all T1-4)

84F9154 SOD Type 1 with socket -OR- solder pads for Weitek 4167
84F9155 Type 1 "J" and "K" with Weitek socket
91F9812 Non-SOD Type 1 with nothing but SMDs or resist to right of CPU
52G9509 8590/95 Dual Booting Capability EPROM

SCSIFIX.ZIP Finally! A utility to alter the number of sectors for a SCSI drive and convert them to a 3.94GB drive! Bob Eager, you have answered a prayer!

Specifications
   Memory
   Features

"G" 486SX 20 MHz
"J" 486DX 25 MHz
   "J" Variants
"K" 486DX 33 MHz
   "K" Variants
Upgrade 486DX2 66 MHz
   Upgrade 486DX2 66 MHz Back
   Supports Non-IML Configurations
Upgrade 486DX 50 MHz
   Identify Upgrade 486/50
   How is this different to the other T1 boards and the T3 Enhanced complex?

Info on Weitek 4167
What is the Square Of Death?
   Square of Death Limits
   ECA #0530 90-0K9/95-0KD with Complex P/N 84F9356
256 KB Cache Memory Option Kit 17 ns and 15 ns
   256K 17 ns Cache Daughtercard
   L2 Cache Performance
ODP vs. ODPR
Complex BIOS
   Support for >1 GB Disks as IML Drive
   Enhanced BIOS Effects
   Upgrade EPROM Additional Capabilities
   Complex EPROM Speeds
   Am27C010 versus Am28F010
   Type 1 Complex Upgrade to "8590/95 Dual Booting Capability EPROM"
CR1 What?

Japanese 486DX 25 MHz Complex
Japanese 486DX 33 MHz Complex


Specifications

Memory

RAM:
   Min/Max on system board: 8 / 64 MB
   PS/2 parity FPM 72-pin SIMMs, interleaved (install SIMMs in pairs)
   80 and 85 ns memory SIMMs are supported, 70 ns for optimum memory performance.

ROM:
   All expect DX2-66: 128 KB EPROM, AM27C010-155DC (32-pin DIP)
   DX2-66: 256 KB Flash ROM, AM28F010-150JC (32-pin PLCC, 12 V Vpp)

Cache:
   L1: 8 KB
   L2: optional 256 KB write-through (except "G", standard with DX-50)

Features

  • Socket for 17 ns 256 KB write-through L2 cache on J, K, and Upgrade DX2-66
  • Socket for 15 ns 256 KB write-through L2 cache on Upgrade 486DX-50
  • No Weitek 4167 coprocessor socket on later J, K, and Upgrade complexes
  • 24 bit DMA; 10-12 MHz (or 20 MHz?) *
  • Dual path memory design (Dual Bus Interleave).
  • 20 MB per second data transfer support (for MCA bus)

* DMA controller originally limited to 16MB. Fixed by the last BIOS update (unknown how).


"G" 486SX 20 MHz (FCC ID ANOIBM486A20) *

CR1 Solder pads for LED
J1 Solder pads for L2 cache connector
J2 SX/DX jumper
OS1 20.0000 MHz Osc (CPU, Local Bus)
OS2 Osc solder pads
U1 169-pin LIF Socket for 486SX-20
U7 57F2194 Memory Controller
U16, 20 78F1659 Data Iface/Buffer (RAM)
U30 78F1659 Data Iface/Buffer (MCA)
U36 Am27C010 BIOS ROM
U38 90X8134 DMA Controller

   On the 20 MHz board, jumper 2 must be on 1 and 2 if a 487SX processor is installed in position U1. If there isn't a 487SX in U1, the jumper must be on 2 and 3.

Note: When installing a CPU, align beveled corner with the beveled outline on the board.

Note: The "G" is the only Type 1 complex to lack a 160 pin L2 Cache option connector.


"J" 486DX 25 MHz (64F0201, old 84F8036, FCC ID ANOIBM486A25)

191-052 IBM PS/2 486/25 AND 486/33 PROCESSOR UPGRADE OPTIONS


CR1 Solder pads for LED
J1 Socket for 17 ns L2 cache option
OS1 25.0000 MHz Osc (CPU)
OS2 20.0000 MHz Osc (Local Bus)
U1 169-pin LIF Socket for 486DX-25
U7 57F2194 Memory Controller
U8 142 pin PGA Weitek 4167
U16, 20 78F1659 or 54F2958 (old)
   Data Iface/Buffer (RAM)
U30 78F1659 or 54F2958 (old)
   Data Iface/Buffer (MCA)
U36 Am27C010 BIOS ROM
U38 90X8134 DMA Controller

J1 The 160 position connector is AMP 650756-1, dtd 9145.

J8 The "J" complex has been seen in three guises:

  • J8 present: 142 pin socket for Weitek 4167
  • J8 absent: Solder pads, no socket SOD - likely will NOT support 5x86
  • J8 absent: No solder pads, non-SOD - likely supports 5x86

"J" Variants

Looking into the functionality of a Weitek 4167 "Abacus" in the U8 position. From this VERY limited sample, it seems you need 54F2958 Data Iface/Buffer (RAM) (old) in U16, 20, and 30 to support the Weitek 4167.

Special J (J with 4167 socket)
PCB 84F8036 026
Small sticker on Weitek socket "Kit 34"
Complex BIOS "IBM Confidential" U2IT16 84F9155 18 June 90
54F2958 Data Iface/Buffer (old)

Not So Special J (4167 socket) Lorenzo Mollicone sent some pix,
84F8208 (handwritten on sticker)
BIOS 64F6032, 1990
54F2958 Data Iface/Buffer (old)


Info on Weitek 4167

Weitek Abacus FPU by Axel Muhr
WeitekDisk.zip Test suite from Weitek (local link)

Applications that took advantage of the Weitek Abacus were scarce. AutoShade, Autodesk Renderman, 3-D Studio were the most prominent to use a Weitek coprocessor. If you happen to own one, you might actually use or at least test it... so here's the official test-suite from Weitek. It contains these tools:

  • DOS TSR to update the BIOS for Abacus support (if missing)
  • Test tool - checks for Abacus presence using INT 11h BIOS calls.
  • Diagnostic tool
  • 2 demos: Side-by-side Mandelbrot benchmark and rendering Phong shaded beach ball
  • Abacus macros for using it natively in your cool assembly code

copro16a.txt The best source of technical information about the 4167 is the highly recommended copro16a.txt by Norbert Juffa in 1994.

4167 Floating-Point Coprocessor advanced data


"K" 486DX 33 MHz (64F0198, FCC ID ANOIBM486A33) * *

190-186 IBM PERSONAL SYSTEM/2 486/33 PROCESSOR UPGRADE OPTION

CR1 Solder pads for LED
J1 Socket for 17 ns L2 cache option
OS1 33.0000 MHz Osc (CPU)
OS2 20.0000 MHz Osc (Local Bus)
U1 169-pin LIF Socket for 486DX-33
U7 57F2194 Memory Controller
U8 142 pin socket, SOD or bare
U16, 20 78F1659 or 54F2958 (old)
   Data Iface/Buffer (RAM)
U30 78F1659 or 54F2958 (old)
   Data Iface/Buffer (MCA)
U36 Am27C010 BIOS ROM
U38 90X8134 DMA Controller

J8 The "K" complex has been seen in three guises:

  • J8 present: 142 pin socket for Weitek 4167
  • J8 absent: Solder pads, no socket SOD - likely will NOT support 5x86
  • J8 absent: No solder pads, non-SOD - likely supports 5x86

"K" Variants

"Special K" (American breakfast cereal)
BIOS 84F9155 "IBM Confidential"
PCB is marked 64F5785 01 (right above U7)
54F2958 Data Iface/Buffer (old)

Not So Special K
BIOS 84F9154 (unknown if 4167 flavored)
PCB is marked 64F5785 01
78F1659 Data Iface/Buffer

It appears they share the same PCB, one has "IBM Confidential" / 54F2958, the other 84F9154 / 78F1659 (84F9154 likely a straight 486 BIOS)

Non-SOD Ks (Nothing where U8 was, just green resist)
FRU 64F0198
PCB is 92F1186 01
BIOS is 91F9812 (NOT Dual Booting Capability EPROM)
78F1659 Data Iface/Buffer


What is the SOD?

What exactly is this "Square Of Death" (SOD)?

It is the mark of the beast. This square of solder pads is actually the binary equivalent of 666.

David Beem responds:
   The missing A1 & A2 pins make this a dead giveaway for the Weitek 4167 coprocessor. Steven Wachtel reports "memory management" problems (ECA #0530) with the SOD complex, which might make sense since the Weitek processors use high memory areas to transfer op codes. So, can a socket go in place to see if a 4167 would be functional there, or was it a dropped option? I suppose that with a couple SOD T1s (one of each of the patches talked about in this thread) & a Weitek 4167 I am one of those that could answer the question.

>Regarding the sensitivity of this complex, has anyone ever tried to swap the BIOS with another Type 1 complex that is known to work with the faster CPUs?

   Despite the complexes being very similar & using the same reference disk, fundamental changes for things like the Weitek coprocessor could really mess things up. IBM would issue a whole complex if there were problems, not just a BIOS change. Other than the T4 'N' I have seen no evidence of other complex types checking things like CPUID.

Peter adds:
   The only reflection from the past is the comment of an IBM employee confronted with that exact question. He said "Forget about it". He then added that the complex had been designed at a time when IBM was yet "Big Blue" and tended not to give too much control over their products to one OEM and they therefore integrated provisions for a "non-Intel" MCU (the Weitek), but the full integration never came.

   Practically the SOD can be judged as an analog to the "spare" dual-in-line artifact solder spots that can be found on many cards, where the developers planned to build "something" but weren't sure what it could be and how it should look. Reserve spots in a way suitable for add-ons or patches, barely attached to the whole board - apart from power, GND and some basic address / data / signal lines. The outline matches the Weitek math-co, but it is (after my knowledge) not supported from neither the glue logic nor the platform BIOS.

SOD Limitations (from Tim Clarke)

   The limitation of the 'poor DMA controller' for the Type 1 SOD board appears to be that you can't run a Cyrix/IBM 5x86 at greater that 'x2 clocking' (i.e. 50Mhz in a Type 2, 66Mhz in a Type 1) or an AMD 586 at greater than 'x3 clocking' (i.e. 75Mhz in a Type 2, 100Mhz in a Type 1). Ed. You CAN run a 486DX4-100 ODPR on a SOD. It's only a 3x multiplier.

   Not having a SOD Type 2 I can't test this, but I would expect the same limits to apply. So, you should be able to run a DX2-50, DX2-ODPR (@ 50Mhz), Cyrix/IBM 5x86 (@50Mhz) or AMD 586 (@ 75Mhz) in a SOD Type 2. The 'performance' of a Cyrix/IBM 5x86 @ 'x2 clocking' and the AMD 586 @ 'x3 clocking' are *roughly* equal, although I have a preference for the Cyrix/IBM chip.

ECA #0530 90-0K9/95-0KD with Complex P/N 84F9356

Steven Wachtel wrote:

   These systems appear to have a memory management problem. In my environment it was seen on a Model 90 with 16 MB of RAM. The system would hang during OS2 boot or during invocation of simple processes after a basic install (such as the system editor ). Symptoms at other OS2 sites would include excessive "random" trap errors. Not using DOS on these systems, I would expect the problem to surface as some indeterminate memory related failure in the E/XMS region.

   During initial setup of this machine, the problem appeared as an inability to create a usable backup reference disk ( if said disk was used there were always errors ). On restart after the failure the machine will request to exec its own auto-reconfiguration and mark out the "bad" regions. For my situation I had the IBM CE on-site for ~6 days for two separate events. The CE changed each memory chip and riser (for the M90) multiple times and recombined them in every combination representation.

   Today (11/5/91) after following his instincts and direction of the higher level support reps, he contacted them again. They asked for the part number of the CPU board, upon which rests a Gate Array based custom memory controller. He was advised that there are *known* problems with the down-rev boards in my new machines. This problem exists(ed?) on the 0KD models of the M90 and M95, and possibly (as I do not have any to verify this ) the 0JD models. IBM's second level support is apparently aware of this potential problem, but has not disseminated this to the CE level or the purchasing customer.

Problem part identification and rectification:
   If the Processor Complex ( nee-CPU board ) part number is 84F9356 ( or 84F anything ? ) on the "barcode/label" of the board you should get a replacement.
   The replacement part bears the part number 92F... I do not know if this is free. Note, I have a M95 with this later board version that has never shown any of these problems.


Upgrade 486DX2 66 MHz (92F0145 / 52G9480, FCC ID ANOIBMB33)

192-178 IBM PS/2 486DX2-66 PROCESSOR UPGRADE OPTION

CR1 Solder pads for LED
J1 Socket for 17 ns L2 cache option
J4 EEPROM Jumper (leave on "R")
OS1 33.3333 MHz Osc (CPU)
OS2 20.0000 MHz Osc (Local Bus)
U1 169-pin LIF Socket for 486DX2-66
U8 57F2194 Memory Controller
U22, 28 78F1659 Data Iface/Buffer (RAM)
U39 78F1659 Data Iface/Buffer (MCA)
U43 Am28F010 41G9374 BIOS ROM "L"
U47 Am28F010 41G4978 BIOS ROM "R"
U45 90X8134 DMA Controller

J4 Once you toggle this jumper you will end up in a 0129 3000 error - "EEPROM Jumper is in the wrong position" and no boot or such. I'd reported that some time ago while testing around with the 92F0145.

   Most likely it was originally intended to select which one of the two Flash ROM banks is active (by default?). But for what reason they changed things and the alternative setting branches into a BIOS error-code instead. (BIOS layout changes, line in case of the T4 BIOS?)

Note: Leave J4 jumper on the center and bottom pin - "R".

Upgrade 486DX2 66 MHz Back

CR2 Schottky Diode B54 (Flash Vpp)
L1 Inductor 47 uH (Flash Vpp)
U77 LT1109-12 DC/DC Conv. (Flash Vpp)

U77, CR2, L1 (plus some other passives) are part of a local 12 V voltage generator. This additional "programming voltage" (Vpp) is required by the Flash memory to perform erase/write operations. Its general topology closely replicates the "Flash Memory VPP Generator" circuit from the LT1109 datasheet (page 1).

Peter sez:
   As a follow up notice: Yes, it *has* a Flash ROM BIOS. And, yes, it comes up with the Type 1 reference disk. Even installs a reference partition as usual with these disks.

   But the system permanently fails to boot into this Type 1 reference partition. Once you reboot it and press [ctrl]+[alt]+[ins] at CP 66 (cursor top / right) the machine loads the operating system instead jumping into reference.

   The platform nicely takes the Kingston Turbochip *without* restoration of the system partition. Runs fine with it - right from the start.

Supports Non-IML Configurations

   Dennis Smith found out that this complex can successfully boot without an IML device at ID6. He booted a SCSI drive at ID0 WITH NO IML track. I did it here with my upgrade DX2-66.

   His guess was this complex was designed to support RAID Arrays, and the early RAID controller, "Passplay" had no ability to boot from an array.


Upgrade 486DX 50 MHz (92F0048, FCC ID ANOIBM486A50)

191-096 Personal System/2 486/50 Processor Upgrade Option [Type 1 486/50]
52G9509 "8590/95 Dual Booting Capability EPROM" HERE

CR1 Solder pads for LED
J1 Socket for 15 ns L2 cache option
OS1 50.0000 MHz Osc (CPU)
OS2 20.0000 MHz Osc (Local Bus)
U1 169-pin LIF Socket for 486DX-50
U8 57F2194 Memory Controller
U22, 28 78F1659 Data Iface/Buffer (RAM)
U40 78F1659 Data Iface/Buffer (MCA)
U44 Am27C010 91F9812 BIOS ROM
U47 90X8134 DMA Controller

U44 Complex BIOS Stock version is 91F9812. This version does not fully support the F/W SCSI [Corvette] and IML from up to 3.94GB drives.

To get the most out of this complex, you need the 52G9509 "8590/95 Dual Booting Capability EPROM" -AND- the SCSI adapter needs the 92F2244 and 92F2245 SCSI BIOS Firmware. All three can Spocks, short Tribbles, and all Fast/Wide SCSI adapters come stock with the 44/45 SCSI BIOS pair.

Note: This complex needs the 15 ns cache. The other Type 1 complexes use 17ns memory.

Some observations:
The chipset appears the same as other Type 1s with the addition of decoding circuitry.

The Upgrade 486DX-50 is a Type 1 with true 50MHz CPU on the complex! All Type 1 complexes [except "G"] use a 160 position 4x40 receptacle for the L2 Cache option. Having the 486DX-50 on the complex PCB instead of a daughtercard means that any upgrade CPU will NOT be getting close to a Model 90 memory riser!

Note: On the Upgrade 486DX-50, the CPU clock, OSC1, has been moved from being under the left side of U16. It is visible even with an L2 Cache option installed. OSC1 is a black SMD, so if you don't see a shiny oscillator like you are used to, look again.

Note: The Type 3 "M" complex is the only other true 486DX-50, but the "M"'s DX-50 is on the daughtercard! [M is also called the "double-decker"]

Note: The Type 3 "M" complex is the "Enhanced 486/50" while the Type 1 486/50 is the "486/50 Processor Upgrade"

Identify Upgrade 486/50

I have noticed that sometimes, an older complex that was replaced is put into the box from the upgrade.

To positively identify the Upgrade 486/50, look at the back for the FCC ID sticker. It should say "FCC ID ANOIBM486A50".



What happens: A 486/33 "K" is replaced by a 486/50, the "K" is put into the box, and through no fault [it is almost 30 years old!] the complex is called a 486/50 because that's what is on the box... This happens with other adapters as well.

The 486/50 is easy to identify, the location of OS1 is to the left of other Type 1 complexes, OS1 is 50.0000 MHz, and OS1 is an SMD [black plastic]. All other Type 1 complex use metal canned oscillators.

Note: The yellow component just below OS1 is "A5C 334K".

So if you want the fastest Type 1 complex, remember that Black is Beautiful!

DX4-100 Upgrade

100 MHz Type 1 Upgrade (mod by Peter, article by Tam Pham)

How is this different to the other T1 boards and the T3 Enhanced complex?

From Peter:
   As far as I can tell (from the pictures of that complex) it varies through some different wiring and modified ASICs. The part of the hardware that deals with the CPU clock generation looks a bit different. The rest of the card is the "later" Non-SOD Type 1 platform as I have it here in my trusty old AKD.

   It seems as if IBM wanted to offer an upgrade path to DX-50 *without* the ECC option - for those customers that have a -xKx machine already and for the Mod. 90 maybe, which does not cope with the "2 layers" DX-50 Type 3 platform very well. This board was not offered with any particular Mod. 90 / 95 right from the start. It has been an option only.

We, the god-Emperor:
   As surmised before, the T1-50 "Big 50" was released to allow 486DX-50 power without ECC support without the need for the double-deck M. I'm not so sure that is the case:

191-198 IBM PS/2 486SX/25,33,50 PROCESSOR UPGRADE OPTIONS Oct 17, 1991
192-101 IBM PS/2 ENHANCED 486/50 PROCESSOR UPGRADE OPTION Apr 28, 1992

To be klar about the improvement in the M complex:
   Enhanced dual path memory design (Dual Bus Interleave). Although Base 1 allows both the processor and busmasters to access memory concurrently through two paths, the Base 3 and 4 has buffers at both paths to provide better performance. Also the buffer on the adapter side (I/O buffer) uses packet data transfers for writes. This means 16 bytes are collected and this packet is written in one cycle to memory as opposed to writing for every 4 bytes received (as with unbuffered systems).

Tom sums things up:
   The T1 Upgrade 50 board is (obviously) just an incremental improvement of the existing T1 design. It provides higher CPU performance, and comes standard with L2 cache. But that's about it... Other than that, it's just the same "old" T1. The R&D time and costs would be relatively low with this one, so IBM would be able to push it out to the market quicker and for more accessible price (in IBM terms...).

   The Enhanced T3 50 complex, on the other hand, is a drastically different beast. It brings not only a higher CPU performance, but also better system throughput, thanks to its improved design and streaming capabilities. It also comes with a 32-bit DMA controller, ECC memory support, and more. All these enhancements were of course reflected by its development time and price tag.

   So, clearly what we have here are two very different designs, with different capabilities, release dates, and price points. If your server needed some more CPU headroom and it needed it now (late 91/early 92), the T1 Upgrade 50 would have been the right choice for you. If you sought after higher overall performance, or some of the new features, the Enhanced T3 platform would give you that. For extra $$$...

Lorenzo Mollicone
   The Announcement Letter says "... an external 256KB level two cache is provided as standard on the processor complex" All of my boxed Upgrade 486DX-50 Processor Upgrade Options have the L2 Cache.


256 KB Cache Memory Option Kit 17 ns and 15 ns [Work in Progress!]

Note: In a advertising/ tech nugget booklet, IBM ran tests with a number of [then] current applications, and the best they could do was 6%; that is, six percent. I bet they wanted much better.

17 ns for "J" [25], "K" [33] and Upgrade 486DX2-66 [33] complexes
15 ns for Upgrade 486DX-50 [50] MHz complex

   The 256 KB cache is a 5.5 x 3.0 inch card that connects to either the 25, 33 or 50 MHz complex. The connector is 160 pins arranged in four columns and 40 rows. The complex provides all the power required to drive the 256 KB cache.

256 KB cache memory option three basic logic elements:

  • 256 KB of SRAM
  • 4 KB of TAG SRAM
  • A cache controller.

   256 KB of Static Random Access Memory ["Data SRAM"]. This is two-way set associative, which allows each index location in the cache to store two pieces of information. This improves the hit ratio, and decreases the number of times that cache items must be removed to make room for new items.

   4 KB of "TAG SRAM" stores some of the cache item's address bits, used to store and locate the item, and some bits used for validity checking.

   "Cache Controller" coordinates access to the SRAM. On a cache-hit, the controller organizes the access of the data from the data SRAM using the TAG SRAM address. On a cache-miss, the controller places the new data into the cache, updating the TAG SRAM and data SRAM at the correct index location.

   The controller is also responsible for ensuring that the address being searched for is actually a cacheable address. If not, no cache search will be done.

Optional Cache Card Installation
   Plug the 256 KB cache onto the receptacle on the complex. One pin, called the "key", has been removed to provide a guide for inserting the card correctly.

256K Cache Not Visible under System programs?
   After installing the 256 KB cache, the processor will simply begin to use the cache. It will not appear in the configuration of the system. The only time you will see the L2 Cache in a message is when it is malfunctioning.


256K 17 ns Cache Daughtercard (6451095 or 64F0199)

64F0199, Front Side *

U1-U4 Toshiba TC55329J-17
U5,6,8 TI SN74ACT2160-17FM
U10 AMD 64F6043
U11 AMD 84F8257
U12 AMD 64F6065
U13 AMD 84F8261
U14 AMD 64F6046
U15 AMD 64F6048
U16 AMD 84F7970
U17 AMD 64F6066

Huh, I noticed that U11 on the -15 ns version is close to the OPT [?] than all the other PLCCs. And here we have U11 with a 84F8257... I wonder if this chip has the presence ID bits akin to multi-card units...

U5,6,8 TI SN74ACT2160-17FM - 8K x 4 2-Way Cache Address Comparator/Data RAM; Datasheet (Bitsaver pages 170-194)

Ed. The chips change from module to module. Yours may be different. I see no specific memory or cache controller chips [yet], the AMD chips are GAL/PALs, and they probably aren't the highest performance option...

64F0199, Back Side *

J1 159-pin connector AMP 650754-1
TD1 Fil-Mag 77Z14A030
TD2, TD4 Fil-Mag 77Z14A025
TD5, TD6 Fil-Mag 77Z14A045
U18-U21 IDT 74FCT646ASO
U22, U23 TI T031XS AS573A
U24-U27 Toshiba TC55329J-17

U18-U21 IDT 74FCT646ASO - Fast CMOS Octal Transceiver/Register; Datasheet (Bitsavers pages 417-422)

TD? Fil-Mag or Sprague 77Z14Annn Active TTL Delay Module
   Equivalent to bel S423-00nn Active TTL Delay Module


92F0050 / 10G3527 Front Side Thx to Lorenzo Mollicone

Huh, U11 is 10G3532. P/N is 10G3527. All the other PLCCs are 91F97nn.

92F0050 / 10G3527 Back Side Thx to Lorenzo Mollicone

Significant change from 17 ns version. The 64F0199 uses five Fil-Mag Delay Modules and the 15 ns uses ONE bel S423-0025-02.

bel S423-0025-02 5 Tap Leading Edge Control Standard Delay Module; Datasheet (archive)

Motorola MC88915FN55 Low Skew CMOS PLL Clock Driver 55 MHz; Datasheet

How Does System Know That Cache Installed if it Doesn't show Up?

On -17, U11 is 84F8257, different from most of the PLCCs. If I could see a sticker on the 64F0199, I bet it would be 84F82nn...

US5530887A Methods and apparatus for providing automatic hardware device identification in computer systems that include multi-card adapters and/or multi-card planar complexes

Example Multi-Card Adapter is the Image Adapter/A:
@8DF0.ADF - IBM Image Adapter/A
@8DF1.ADF - IBM Image/A and Printer/Scanner Option
@8DF2.ADF - DSS and sub card 2
@8DF3.ADF - DSS and sub card 3
@8DF4.ADF - IBM Image Adapter/A 3MB
@8DF5.ADF - IBM Image/A with Printer/Scanner Option

WBST and Major Tom, my SWAG is U11 stores a POSID for the L2 Cache option, and upon power on, the POSID for the complex is combined with that of the L2 cache, and that way, the system knows what is attached. It makes sense.

WBST responds:
   I'm not so sure that the L2 cache module has a "POSID" as such, but as you speculated, some of the ID pins on the interconnect are tested to "modify" the complex's configuration table during POST.


L2 Cache Performance

From Us, the god-Emperor of Microchannel:
   Praytell, what use can one make of the 256K cache for the T1 complexes? I hate to admit it, but I never noticed a large (or significant) boost when I added one.

From Tony Ingenoso:
   The effects of modern bloatware on a write-through can be disheartening... IMO IBM's matched cycle scheme goes a long way towards helping keep the L1 lines filled at a brisk pace even when no L2 is present. The T2's abnormally good performance (considering its other genetic limitations) shows this well. For all practical purposes, 90/95's have a 64 bit memory subsystem working to fill the L1 lines.

From Charles Lasitter:
   What do you see with one speed processors (DX50) that are coupled with a faster cache 64F0050, or the T3 and integrated cache? Since they don't have a 'fall back' processing speed in the event of an L1 miss, but rather use a 15ns L2 vs 17ns, is there any difference for them?
   I believe we've seen LARGE increases in speed when doing something like kernel rebuilds compared to no cache. I think it may depend on what you're doing and the operating system.

From Tony:
   I don't see this as a core multiplier issue -- even the low end DX25 T2 runs better than one might expect it to. The kernel rebuild improvements aren't surprising - compilation algorithms and the bits of data they work tend to be well localized if modules aren't too massive. Initial parsing would be very read intensive as well and should make good use of an L2. Cache performance is indeed a very task specific kind of thing. Scattered code/data can effectively neutralize it totally.

   DX50's are strange -- they often outrun DX2-66 when main memory bandwidth or I/O is the constraint. When staying in L1, then the DX2-66 wins due to the multiplier. With a fast L2 and fairly scattered code/data a DX50 is going to do very well.

From Peter
   Uhmmm ... I had the occasion to test a T1 DX2-33/66 board under Linux. And compare it with the same T1 DX-50 (!) board - both with the L2 cache.

   The 486DX2-33/66 showed 33 BogoMips, the DX50 25 only ... same as the T3 DX50 while a DX2-50/100 (Intel DX4-100 in 2x mode) on a T3-platform runs at -supposed- 50 Bogomips almost.

   In the practical use the T1 DX50 wasn't much slower than the T1 DX2 - the XF86 stuff paced at the same rate on both. None of the machines "felt" faster or slower. The DX4 T3 was a bit faster - but not significantly. All 3 machines had the same XGA-2 card, the same TR 16/4 network adapter, the same 32MB Parity RAM and the same IBM 400MB HD with the Linux on it.

   The T1 platforms had the "plug on" 256K L2 cache (17ns on DX2, 15ns on DX50) and the T3 had its own integrated cache. I did not write down all the values ... maybe I should repeat that session again to get some definite, comparable data.


ODP vs. ODPR

   169 pin ODP - 487SX installed with 486SX still in place, needs the "SX-disable" pin. Important on boards with soldered CPU.
   168 pin ODPR - (R - "Replace") replaces 486SX / 486DX does not need "SX-disable" pin.


Complex BIOS

BIOS stored in EPROM. (except for the Upg-66 complex that uses Flash memory).
BIOS ROM dumps HERE.

Support for >1 GB Disks as IML Drive

   Type 1 complexes require the combination of BIOS 52G9509 and SCSI BIOS 92F2244/45 in order to handle IML drives >1GB (new limit is 3.94GB). The upgrade BIOS incorporates the "Enhanced IML" which supports IML from a drive >1GB and "Search IML" which allows IML from a drive other than ID6. The SCSI BIOS 44/45 pair supports drives well over 8GB. (Ed. You OS may have other ideas...)

More information HERE.

Some Other Thoughts

From Charles Lasitter:
   I've had some VERY entertaining results in my installations, depending on what other drives were present, and which version of the processor BIOS was used.

   With the 52G9509 in place, ID6 in bottom bay (Mod 95) at end of cable, ID5 in bay above on next spot on cable, I couldn't get the IML to go to ID6 to save my ass. It made a beeline for ID5 every time. Put in the old BIOS, and it goes straight for ID6.

Enhanced BIOS Effects

From Charles Lasitter:
   As a result of a programming project with Mr. Clarke, I am now fairly certain that the odd behavior of an IBM SCSI controller "ignoring" ID6 to lay an IML track on a drive that was ID5 was really a function of the enhanced BIOS, which sniffs out the signature of any current or previous IML partition on a series of drives, and insists upon installing or recovering a system partition to that same location.

   This same feature is related to the IBM controller's inability to do an actual format of the drive if there has been an IML partition on the drive before. The space at the end of the drive is never released, because the IBM controller refuses for format that area of the drive.

   That's why I typically use the RAID adapter when I REALLY want to nuke some drives.

Upgrade EPROM Additional Capabilities

  1. More efficient use of Adapter ROM memory minimizes adapter configuration conflicts.
  2. BIOS support for IML drives up to 3.94 gigabytes per device.
  3. Supports "Search IML" from any PUN or SCSI ID. System partition is no longer restricted to SCSI ID=6. Each HD ID is searched for valid system partition.
  4. Allows redundant system partitions (IML).
  5. Sharing of SCSI devices. An external SCSI device, (ex. 3511), may be shared between two system units.

   Type 1 complexes (except DX2-66 Upgrade, 92F0145) need BIOS 52G9509 to handle IML drives of >1,023MB. (U36 in drawing)

Complex EPROM Speeds

   The normal EPROM speed is 120 ns (or so). Other than the fact that the second stage of POST is contained on a mechanical device, how fast is stage 1 completed?

Peter replies:
   Original chips got 120 or 150 ns where the total read cycle time does not even reach that. Depending on the wait states during BIOS access I would dare the guess that it is closer to 250 ns for each word read. And while the ROM read speed is dependent on the total processor board cycle times it cannot be sped up somehow.

It is like using ZR-spec tires on an old '67 Mustang that would not even come close to the 300 km/h allowed for these tires ...

As you noted: the next part of the boot up runs off the HD but also at very carefully selected transfer speeds to allow even the slowest HD to cope with it. I don't think that using a faster HD (or FDD as well) would speed up the process significantly. The boot process has been designed to be carried out under worst case conditions to allow debugging or running a diagnostic tool afterwards (like CTRL-A). All of that includes a lot wait loops. If I were a better programmer I would flea out the BIOS for these and run it under the assumption that the HD could keep pace and get in the data as fast as possible ... and if *that* fails retry in a slower mode. As far as I know they don't even use DMA to access the media but PIO.

Am27C010 versus Am28F010

I was diddling about, looking to turn out some 52G5909 T1 Upgrade BIOS for Lorenzo. In my desire to be lazy, I thought getting some EEPROMs would make my life easier, no UV eraser needed, just "Blank Device"...

So I then pumped out five 28F010, and it is great! Blank 'em and program, no UV eraser needed... and then I ran into "Stuck bit Hell". I struggled through 20 28F010 in order to get ten good EEPROMs. I then sent my love children to Lorenzo, thinking, "Hey, they verified and have the same Czechsum, must be good" and I... was... wrong...

Lorenzo said:
"swapped BIOS chip, video never goes live. Tried two chips, both don't seem to initialize."

So, experience suggests that you stay with the same device family or hilarity may ensue... I can't explain in detail why, but I sure as heck can say it didn't work for me. YMMD

Type 1 Complex Upgrade to "8590/95 Dual Booting Capability EPROM"

Complexes with the following EPROM part numbers may be upgraded:

PROCESSOR FRU P/N MODEL EPROM P/N LOC.
20 MHz SX 92F0049 0GX 91F9812 U36
25 MHz DX 64F0201 0JX 84F9154 OR 91F9812 U36
33 MHz DX 64F0198 0KX 84F9154 OR 91F9812 U36
50 MHz DX 92F0048 P3 (UPGD) 91F9812 U44

It was called the "8590/95 Dual Booting Capability EPROM Package".

PART NUMBER 52G9509 (was 52G9750 - try this if other PN is not known)

Note: Use the latest refdisk and diags. See above...


CR1 What?

You can see this on a number of Type 1 complexes, including the Upgrade 486DX2-66 and the Upgrade 486DX-50. What is CR1 for?

Tom says:
   CR1 would be a diode. Judging by its convenient location right in the corner, it's probably supposed to be a diagnostic LED.

Apparently Lorenzo already tried this:
   No blinks, no on-off. Solid glow.


9595 Main Page