I tried several cards around last May,
and never did get one working quite right with 1.4.1 or 1.4.2.
I enclose an e-mail that I think was a nice summation of the
situation last May.

If you look in the archives for "10/100 ethernet cards - followup",
there's a fairly long thread.

I never tried 1.5.  I don't think it was available at the time.
Is there any guess about when this will release?  Would this be
a "reckless" thing for me to do on a production system?

-dgl-

At 3:25 PM -0500 9/28/00, Henry B. Hotz wrote:
>That was fast.  I've got 2, maybe 3, cards that should work and 
>confirmation that I can't just assume anything from port-i386 will 
>work without effort.
>
>Cliff:  do any of your not-working cards overlap with the reported 
>working ones?  It would be interesting to see if we can confirm your 
>suspicion that the problem was in the PCI support code.  I'm looking 
>at [78]500 machines myself.
>
>The last time I remember a report on the list someone had something 
>*almost* working, but not quite.  I assume anything that works on 
>port-i386 should be fixable with a minimum of effort, but it's nice 
>to see I shouldn't have to resort to that.
>
>Thanks guys.  Also TIA to anyone who is yet to answer.
>
>Now for the comparison shopping part. . .
>
>Signature held pending an ISO 9000 compliant
>signature design and approval process.
>h.b.hotz@jpl.nasa.gov, or hbhotz@oxy.edu


enclosed:

>X-Sender: mw34@postoffice2.mail.cornell.edu
>Mime-Version: 1.0
>Date: Wed, 3 May 2000 23:51:11 -0400
>To: port-macppc@netbsd.org
>From: Michael Wolfson <mw34@cornell.edu>
>Subject: Re: 10/100 ethernet cards - followup
>Sender: port-macppc-owner@netbsd.org
>Precedence: list
>Delivered-To: port-macppc@netbsd.org
>
>Hi,
>
>Before I add to the FAQ, let me just make sure I've got it all straight:
>
>Donald Lee <donlee@icompute.com> reports that:
>Asante Rev B does not work
>Bay Networks Netgear FA310TX (has Lite-On chip) does not work
>SMC EZnet 10/100 PCI card not configured (rtk)
>3Com 3c905[b]-TX works, but not under stress (ex)
>
>Rod Morehead <rmore@rmore.net> reports that:
>Asante Mac DEC based 10/100 PCI Rev A. part number is 09-00169-01 works in
>-current (de)
>
>Izumi Tsutsui <tsutsui@ceres.dti.ne.jp> reports that:
>Macronix MX98715A works in -current (tlp)
>3Com 3C905B-TX works, not heavily tested, in -current (ex)
>
>Havard.Eidnes@runit.sintef.no reports that:
>SMC 83C170 (EPIC/100) should be supported by (epic) in -current
>
>"sanjayl" <sanjayl@iqmail.net> reports that:
>the fxp devices work
>
>Thilo Manske <Thilo.Manske@HEH.Uni-Oldenburg.DE> reports that:
>3Com 3c905B works (ex)
>SMC 9432TX, Etherpower II doesn't work (epic)
>RealTek 8139 does not work (rtl)
>D-Link DFE-530TX works, but see PR kern/7948(vr)
>
>Monroe Williams <monroe@pobox.com> reports that:
>Farallon Fast EtherTX 10/100 card (part # PN996L-TX) (de) works
>
>General categories are:
>built-in
>NE2000-compatable PCI cards (ne)
>	ne*     at pci? dev ? function ?        # NE2000-compatible Ethernet
>DEC Tulip-compatable (de)
>	de*     at pci? dev ? function ?        # DEC 21x4x-based Ethernet
>3Com compatable (ep)
>	ep*     at pci? dev ? function ?        # 3Com 3c59x
>3Com 3C905B (ex)
>	ex*     at pci? dev ? function ?        # 3Com 90x[B]
>	exphy*  at mii? phy ?                   # 3Com internal PHYs
>Lite-On PNIC (tlp)
>Intel i82557/8/9 chipsets (fxp)
>SMC Etherpower II
>	epic*   at pci? dev ? function ?        # SMC EPIC/100 Ethernet
>RealTek 8139 (rtk)
>D-Link DFE-530TX (vr)
>
>Some notes to be aware of:
>Often a vendor will start shipping with the Tulip chipset and will later
>(without any packaging change) switch to some cheaper ethernet chipset that
>may not be supported under NetBSD.  Thus even though a board is listed here
>as supported, the vendor may change the chipset without notice.
>
>Also, even though a MI PCI board may be listed as supported, it may not
>have ever been tested on a big-endian system and may have endianness issues
>(that can be fixed relatively easily once someone is aware of the problem).
>
>Also, remember that the GENERIC kernel does not include device drivers that
>have not been fully tested.  You may need to build a kernel with your
>ethernet card device added in.  NetBSD 1.4.2 does not contain many of these
>drivers, as they have only been added recently.  You should update your
>system to a recent -current snapshot.
>
>Also, be sure to add the physical interface (mii) for your card when
>building a kernel with your ethernet device added.
>
>Also, sometimes some cards do not handle auto-negotiation properly.  Try
>turning it off and manually set the speeds on both your machine and the
>remote machine/switch.  This would make an otherwise working card appear to
>not work.
>
>  -- MW