So I'm helping these folks get their problem resolved and what I'm
seeing, I don't understand.  On the working card, we get:, with a little
debugging output:

Jun 18 12:27:52 www2 /netbsd: ex0 at pci0 dev 9 function 0: 3Com 3c905B-TX 10/100 Ethernet
Jun 18 12:27:52 www2 /netbsd: ex0: interrupting at irq 11
Jun 18 12:27:52 www2 /netbsd: ex0: MAC address 00:50:04:71:f0:8c
Jun 18 12:27:52 www2 /netbsd: 
Jun 18 12:27:52 www2 /netbsd: elinxl:elink_w3_reset_options = 0xa
Jun 18 12:27:52 www2 /netbsd: elinkxl: sc->ex_conf = 0x7
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 0
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 1
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 2
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 3
[..., cycles through the configured phys, 0-24]
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 23
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 24
Jun 18 12:27:52 www2 /netbsd: ex_mii_readreg: err = 0, val = 30793
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 24
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: err = 0, val = 0
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 24
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: err = 0, val = 0
Jun 18 12:27:53 www2 /netbsd: 
Jun 18 12:27:53 www2 /netbsd: mii_oui(0x0, 0x0) returns 0x0
Jun 18 12:27:53 www2 /netbsd: mii_model(0x0) returns 0x0
Jun 18 12:27:53 www2 /netbsd: exphy0 at ex0 phy 24: 3Com internal media interface
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 24
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: err = 0, val = 12288
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: sc->ex_conf = 0x7, phy = 24
Jun 18 12:27:53 www2 /netbsd: ex_mii_readreg: err = 0, val = 30793
Jun 18 12:27:53 www2 /netbsd: exphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

And on another 905b we get the same probe, but  the mii_readreg never
returns anyting other than 0, even when the phy value is 24, which appears
to be a magic constant in /usr/src/sys/dev/ic/elinkxlvar.h

	My questions are:

1.  What's magic about the phy value of 24 on an Elinkxl card with an
internal phy?

2.  Is it possible this card, which is brand new, is one of the new
3c905b-M cards which is being mis-identified with a 3c905b-TX?

3.  Are there online technical documents talking about this card and the
phy?

4.  The 2 cards seem to have different chips on them, but I don't remember
what they are, given that the cards aren't in my posession.

5.  Do the DOS/Windows configuration settings for performance versus CPU
load in the card's diagnostic program affect the NetBSD's driver behavior
toward this card?
-thanks for any ideas.
-Brian