On Thu, 09 Dec 1999 12:56:02 -0800 
 Jonathan Stone <jonathan@DSG.Stanford.EDU> wrote:

 > Thanks for the suggestion.  I had already turned on all the PCI-BIOS
 > entries which (as of a couple of weeks ago) were needed to get the
 > card probed. I guess it changed.  That's enough to get the netgear
 > card recognized. NOw it says unknown phy, attaches ukphy, and cannot
 > see a link parter. The same cable and card works under Windows...

tlp0 at cardbus0 dev 0 function 0: DECchip 21143 Ethernet, pass 4.1
tlp0: interrupting at 11
tlp0: Ethernet address 00:10:7a:15:27:e4
ukphy0 at tlp0 phy 1: Generic IEEE 802.3u media interface
ukphy0: OUI 0x0010dd, model 0x0002, rev. 1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
tlp0: supplying EUI64: 00:10:7a:ff:fe:15:27:e4
tlp0: starting DAD for fe80:0009::0210:7aff:fe15:27e4
tlp0: DAD complete for fe80:0009::0210:7aff:fe15:27e4 - no duplicates found

That's a NetGear FA-510.  Works Great.  Typing over it now.

dr-evil:thorpej 192$ ifconfig -m tlp0
tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        media: Ethernet autoselect (10baseT)
        status: active
        supported Ethernet media:
                media none
                media 10baseT
                media 10baseT mediaopt full-duplex
                media 100baseTX
                media 100baseTX mediaopt full-duplex
                media autoselect
        inet 208.176.2.166 netmask 0xfffffff0 broadcast 208.176.2.175
        inet6 fe80:9::210:7aff:fe15:27e4 prefixlen 64
dr-evil:thorpej 193$ 

The PHY is made by Enable Semiconductor.  I have been unable to reach
them (their publised URL of http://www.enablesemi.com/ doesn't even
resolve!), which is why I don't have the datasheet to write the PHY
driver with.  But ukphy is working fine for me.  The thing is plugged
into a no-name, cheap-ass 10baseT hub.  It also works fine when plugged
into a NetGear 10baseT hub when I'm in my office.

You should, however, read the message I recently sent to tech-net
regarding NWAY, PHYs, and all that.

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>