On Fri, Jul 27, 2001 at 05:29:13PM -0400, Greg A. Woods wrote:
> First the tlp problem.  I've got an el-cheapo 10/100 card (IIRC it's the
> one Rogers@Home shipped with my cable modem) installed in my IBM PC 325
> server running 1.5W 2001/06/24.  It's recognized by tlp as:
> 
> 	tlp0 at pci1 dev 7 function 0: Macronix MX98715AEC-x Ethernet, pass 2.5
> 	tlp0: broken MicroWire interface detected; setting SROM size to 1Kb
> 	tlp0: interrupting at irq 15
> 	tlp0: Ethernet address 00:80:c6:f1:46:80
> 	tlp0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX

  I have a similar card (Sohoware Fast SFA110A):

    tlp0 at pci0 dev 12 function 0: Macronix MX98715AEC-x Ethernet, pass 2.5
    tlp0: interrupting at irq 10
    tlp0: Ethernet address 00:80:c6:f9:c9:54
    tlp0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX

(but note the absence of the "broken MicroWire interface...")

> I now have it plugged into one of the 100baseTX ports on digital
> VNswitch 900EX and it seems to work OK at 100baseTX/FDX:
> 
> tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>         address: 00:80:c6:f1:46:80
>         media: Ethernet 100baseTX full-duplex
>         status: active
>         inet 204.92.254.15 netmask 0xffffff00 broadcast 204.92.254.255
>         inet6 fe80::280:c6ff:fef1:4680%tlp0 prefixlen 64 scopeid 0x2

  Mine is similar:

tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:80:c6:f9:c9:54
        media: Ethernet 100baseTX full-duplex
        status: active
        inet 192.168.0.1 netmask 0xffffff00 broadcast 192.168.0.255

but no inet6 here.  For a long time it wouldn't do full duplex, but I was
pleasantly surprised recently to find it working in 1.5W (July 12, 2001).
I still need to set full duplex by hand, though.

> I get thousands of these messages when almost any traffic hits the card
> (I'm using it as the main interface for now):
> 
> 	Jul 27 17:17:24 proven /netbsd: tlp0: receive error: MII error
> 	Jul 27 17:17:24 proven /netbsd: tlp0: receive error: CRC error
> 
> It's still very fast and there don't seem to be any extra errors from
> netstat's point of view.  Everything works fine -- some stuff works
> better and faster of course now that the system talks to my core network
> at 100baseTX/FDX.

  I get no such errors.  The network load here is generally quite light,
but it has been stressed a bit doing duty serving a diskless macppc.  The
card seems to be working well, though I haven't checked its performance.
Maybe that "broken MicroWire interface..." message indicates the source of
your problems?  But you might try a newer kernel, just in case that makes
a difference.

--Jim