LAN Adapter/A for Ethernet
"LEGENDS" card
@FFE0.ADF - IBM LAN Adapter/A for Ethernet
@8F9C.DGS  IBM LAN Adapter/A for Ethernet Diagnostics (IBM)

Linux Driver for the IBM LAN Adapter/A for Ethernet 
EMTLAN.ZIP  IBM LAN Adapter/A  Option Disk v2.2 (9-15-95) (Thanks to Dan Hamilton)
EMTLAN.rar IBM LAN Adapter/A  Option Disk v2.2 (9-15-95) in .rar
ETHER32a.ZIP IBM LAN Adapter/A  Option Disk v1.0 (2-25-93)
laninst.pdf  Installation and Testing instructions for the LAN Adapter /A. (IBM PCBBS)

LAN Adapter/A for Ethernet-Installation and Testing
Technical Reference Ethernet Adapter Interface
Alfred Arnolds LAN Adapter Shootout results.   LAN /A is pretty good...
DP83934 Datasheet
DP8329CN Datasheet

LAN Adapter/A(Old)
LAN Adapter/A (New)
AAUI Drop Cable (P/N 59G9004)
Soft Error 265
ADF Sections

LAN Adapter/A (Old) FRU 48G7172 (same as newer card!)

D2 - Link LED solderpads
D3 - Receive (RXD) LED solderpads
D4 - Transmit (TXD) LED solderpads
P2 - Apple Attachment Unit Interface (AAUI)
P3 - Thinnet Coaxial
P4 - RJ45 Category 5 Cable Connector
RN1-5 Bourns Resistor Networks
U6-9 - IDT 7164 (?)
U10 - Natl Semi DP83934AVQB "SONIC-T"
U15 - National Semiconductor 60G1582
U22 - 59G2495
U23 - 59G2496
U28 - 59G2499
U37, 38 - Bel S553-1006-AE
U40 - Halo 5V to 9V
U50 - Pulse Electronics PE-65424
U51 - Pulse Electronics PE-65428 
X1 - Adapter BIOS/RPL 60G3315
Y2 - Kyocera 20.0000MHz

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
   This adapter is an excellent (if a bit large) Microchannel network adapter. Performance has been reported to be quite good without the tendency to consume excessive amounts of CPU power. It also works under quite a few different operating systems, including my choice of Windows NT 3.1. I have noticed that it doesn't seem to "get along well" with a VIA Rhine II 10/100 network card as included on an Asus motherboard. If I had to guess, I'd blame the VIA Rhine II for being "naughty".

   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 this to keep the LAN/A from complaining: (see Soft Error 265)
> Is there anything can be done about the LAN/A's insistence on having a cable attached to it?
   I suspect that sticking a wrap plug into it will keep it from complaining, but I haven't tested that.

(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.)

   Images and text in this section are from from William R. Walsh, unless stated otherwise. Original page is HERE

LAN Adapter /A (new) 48G7172 (also FRU 10H4633)
J1 RJ45
J2 Apple AUI
U1,2,7,8 Cypress CYC185-35VC
U3 NS DP83934AVQB Sonic-T
U9 Boot ROM
U13 NS SCX6B64AOK Gate Array
U19 NS DP8392CN
Y2 40.0000 MHz osc 

Mini AUI to AUI Cable P/N 59G9004

Sorry, William, that's what IBM calls it. Not AAUI....

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.

AdapterId FFE0 IBM LAN Adapter/A for Ethernet 

Adapter Base I/O Address
     <"I/O address 1000" (1000-109f)>, 2000 (2000-209f), 3000 (3000-309f), 4000 (4000-409f), 5000 (5000-509f), 6000 (6000-609f), 7000 (7000-709f)

Adapter Interrupt Request Level
       <"Interrupt 5">, 15, 10, 11

Network Media Connection
   To configure this adapter, you must set the Network Media type that is connected to the adapter (Ed. Duh-huh! Just waiting to try it...)
       < "Twisted Pair">, Thin Ethernet, Thick Ethernet (AAUI)

Adapter BIOS-ROM / RAM Location
   This adapter requires a memory location to be allocated for it's BIOS-ROM and Shared RAM.  There are 5 locations that can be selected with 2 RAM sizes for some addresses.  If possible, a 32K memory size address should be selected for best throughput.
   <"C8000-CFFFF" (C800-CFFF)>, D000-D7FF, D800-DFFF, C400-C7FF, C8000-CBFFF, D0000-D3FFF, D4000-D7FFF, D8000-DBFFF

9595 Main Page