"LEGENDS" card @FFE0.DGS IBM LAN Adapter/A for Ethernet Diagnostics (IBM) 25H3518.bin Image for POST/BIOS 2.20 (28 pin 16kx8, M27C128-12) 192-210 IBM LAN Adapter/A for Ethernet Linux
Driver for the IBM LAN Adapter/A for
Ethernet LAN
Adapter/A
for Ethernet-Installation and Testing e2ra2000.boo LAN Adapter/A(Old) LAN Adapter/A (New) LAN/A Block Diagram AAUI Drop Cable (P/N 59G9004) Running without BIOS/RPL Chip 25H3518 BIOS/RPL Error Messages Soft Error 265 Causes of a 265 Error (Found it!) ADF Sections LAN Adapter/A (Old) FRU 48G7172 (same as newer card!) ![]()
D2-4 I read the SONIC-T datasheet and traced the leads to find out the diode functions. It was easy since the traces are straightforward - they stay on the top layer of the board and go right to the matching pins on the IC. P2 - Apple Attachment Unit Interface (AAUI) Connector (no, it's not a "dorky mini-AUI" or "IBM bizarro C14") You can see some AAUI "breakouts" here. A pinout is available here. Since this adapter already has RJ45 and coaxial connectors, my guess is that the AAUI connector is provided for attachment to "thicknet" coaxial networks. You could also use it to bypass a failed component on the adapter. Thoughts & Experiences
I found this card (and continue to use it) in a 9585-0X6. This card and the host computer were both filthy and kept somewhere very damp.As a testament to IBM's ability to build quality hardware, the card has (sometimes heavy) rust in places but it continues to work excellently. If there was one major "strike" against this adapter, it would be the "requirement" to have a network cable connected to it at startup. The LAN/A performs a self test and checks for the presence of a network cable. If it doesn't find one, then it will complain and may even cause the elusive "265" POST error to surface on some machines and circumstances. Rick Ekblaw suggested that sticking a wrap plug into it will keep it from complaining. (WRW. You'd probably have to build one. I saw nobody selling Ethernet wrap plugs other than the IBM AUI wrap plug, which I already have.) NOTICE: LAN Adapter /A (new) 48G7172 (also FRU 10H4633) ![]()
LAN/A Block Diagram ![]() Mini AUI to AUI Cable P/N 59G9004 ![]() Sorry, William, that's what IBM calls it. Not AAUI.... Running without BIOS/RPL Chip e2ra2000.boo LAN Technical Reference SC30-3661-00 If BIOS or RPL function is not desired, the boot ROM may be physically removed. BUT... Boot ROM removal will prevent adapter from performing either the Boot or RPL function.
25H3518 BIOS/RPL Error Messages PR001 - POST/RPL ROM integrity error. ROM incorrectly inserted in socket or defective. Verify ROM is correctly inserted in socket U9 / X1. Verify ROM is not damaged (no pins are bent or missing). PR002 - I/O configuration error. Adapter mis-configured. Possible I/O address conflict. Check adapter configuration and workstation configuration. If adapter and workstation configurations are correct and problems persist, have adapter serviced. PR003 - Memory configuration error. Adapter mis-configured. Possible memory conflict. Verify adapter configuration and workstation configuration are correct. If adapter and workstation configurations are correct and problems persist, have adapter serviced. PR004 - ID PROM integrity error. The Ethernet Controller's ID PROM is defective. Have adapter serviced. PR005 - Buffer memory integrity error. On-card RAM is defective. Have adapter serviced. PR006 - Register integrity error. Ethernet adapter is defective. Have adapter serviced. PR007 - Watchdog timer error. Ethernet adapter is defective. Have adapter serviced. PR008 - No interrupt received. Adapter mis-configured or system interrupt signal is defective. Possible interrupt conflict. Verify adapter configuration and workstation configuration are correct. Run system diagnostics. If adapter and workstation configurations are correct and system diagnostics run without error and problems persist, have adapter serviced. PR009 - CAM integrity error. Ethernet adapter is defective. Have the adapter serviced. PR010 - Cable connection error. Cable not connected, wrong connect, or wrong cable type. Check all cable connections, verify cable type is correct, verify cable is working correctly. PR011 - Transmission loopback error. Defective cable or Defective adapter. Verify cable is working correctly. If cable is working correctly and problems persist, have adapter serviced. PR012- Insufficient memory for RPL. Not enough RAM available on workstation. Reallocate workstation RAM or add workstation RAM. PR013 - Adapters not responding or failures detected. Unknown. Verify installation is correct. If it is is correct and problems persist, have adapter serviced. 256 - Exists in an un-commented line in POST/RPL image, most likely due to LAN/A not being connected to LAN NOTE: When you are asked to review the adapter and workstation configuration, that is to compare the adapter's system programs settings versus that of the Operating System. Snippet from 25H3518 > Notice the lonely "265" entry, but no associated text.... > > IBM LAN Adapter/A for Ethernet POST/RPL v2.20 > (C) IBM, NSC, 1994. All rights reserved. > Testing adapter in slot ... OK > *** PR001 POST/RPL ROM integrity error. *** > *** PR002 I/O configuration error. *** > *** PR003 Memory configuration error. *** > *** PR004 ID ROM integrity error. *** > *** PR005 Buffer memory integrity error. *** > *** PR006 Register integrity error. *** > *** PR007 Watchdog Timer error. *** > *** PR008 No interrupt received. *** > *** PR009 CAM integrity error. *** > *** PR010 Cable connection error. *** > *** PR011 Transmission loopback error. *** > *** PR012 Insufficient memory for RPL. *** > *** PR013 Adapter not responding. *** > 265 > 0 00 POST Driver Init Table could not be found Press F1 to continue... > > v2.20 (941103) > RPL: Mini-AUI > RPL: 10BASE2 > RPL: 10BASE-T Soft Error 265 Rick Ekblaw rears up from the mists at IBM and utters: The PS/2 error code 265 (or 00026500) has been a bit of "myth" to me -- I'd heard of people getting it, but had never seen one myself until yesterday. I was working on reviving a PC Server 500 with the P/390 card set (a worthy endeavor, I assure you). This PC Server 500 has a 2-channel SCSI Fast/Wide RAID adapter (Passplay), a P/390 processor card with daughter card (additional S/390 RAM), a "Huron" S/370 Channel Adapter, an SVGA Adapter/A, an Etherstreamer MC32, and a LAN/A for Ethernet. The nine 4.3GB DASD are configured as an 8-disk array with 1 hot spare, and the array has two logical drives - the OS/2 boot drive is about 1GB in size, the rest is the data drive for the emulated 3390-3 DASD volumes. The LAN/A was configured for twisted pair (RJ45 connector), but I didn't have it plugged into the network, and the LAN/A POST was throwing up a PR011 error on the screen (Transmission loopback failure). No other error codes were being posted, and the information panel was not showing an error code, either. But just when you expected the machine to boot, it prompted for the Reference Diskette. OK, put in the Reference Diskette, press F1, and it said that the system posted error 265, run Diagnostics to isolate the error. Thinking that the 265 was some sort of
"soft" error related to the PR011, I plugged the LAN/A
into a hub so that the LAN/A POST ran clean. Sure
enough, the machine would now boot into OS/2 Warp 3
without complaint, and I could IPL OS/390 (*that* took a
while, the 390 processor on the P/390 card is functional
but not very fast). So, the 265 error code is "real",
but it's a rare beast. Causes
of a 265 Error AdapterId FFE0 IBM LAN Adapter/A for Ethernet Adapter Base I/O Address
Adapter Interrupt Request
Level Network Media Connection
Adapter BIOS-ROM / RAM
Location |