For my own enjoyment I decided I was going to fill up an old machine with 
ethernet cards to make sure that the drivers were happy with them. 
Unfortunately, they aren't.

ex0 - 3c905a in pci slot
tlp0 - Linksys LNE-100TX version 4.1
tlp1 - Netgear FA310TX rev D2
tlp2 - Asante Fast 10/100 Ethernet Mac/PC DECchip 21140-AF, should be
	attaching a DAVICOM DM9101F phy, but isn't.
ex1 - 3c905a onboard

- tlp0 tlp0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:04:5a:55:16:9a
        media: Ethernet autoselect (100baseTX full-duplex)
        status: active
        inet 192.168.1.104 netmask 0xffffff00 broadcast 192.168.1.255

	reports this every time dhclient runs:

	DHCPREQUEST on tlp2 to 255.255.255.255 port 67
	DHCPREQUEST on tlp0 to 255.255.255.255 port 67
	DHCPDISCOVER on tlp1 to 255.255.255.255 port 67 interval 6
	ip length 576 disagrees with bytes received 580.
	accepting packet with data after udp payload.

	Come to think of it, I've seen this with le(pmax), bm(macppc), and 
	tlp(i386,macppc), ex interfaces never report this.

-tlp1 tlp1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:02:e3:07:ac:14
        media: Ethernet autoselect (none)
        status: no carrier
        inet 0.0.0.0 netmask 0xff000000 broadcast 255.255.255.255
        inet6 fe80::202:e3ff:fe07:ac14%tlp1 prefixlen 64 scopeid 0x3

	Doesn't work at all, no link light, I suspect hardware failure,
	but it seems odd that it would attach a phy to it and then not
	work.

-tlp2 tlp2: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
        address: 00:00:94:a9:61:cd
        media: Ethernet 10baseT
        status: active
        inet 192.168.1.102 netmask 0xffffff00 broadcast 192.168.1.255
        inet6 fe80::200:94ff:fea9:61cd%tlp2 prefixlen 64 scopeid 0x4

	OK this is even stranger. dmesg doesn't report an actual phy
	attachment at all, my switch indicates 100BaseTD-FDX but
	ifconfig reports 10baseT half duplex. And, it works, as long as
	you have the cable plugged in at boot time. Also reports strange
	warning about packet size mismatch with dhclient

	tlp2 at pci1 dev 11 function 0: DECchip 21140A Ethernet, pass 2.2
	tlp2: interrupting at irq 3
	tlp2: Ethernet address 00:00:94:a9:61:cd
	tlp2: 10baseT, 100baseTX, 10baseT-FDX, 100baseTX-FDX


NetBSD 1.6ZC (GENERIC_DIAGNOSTIC) #0: Tue Sep 23 16:47:48 UTC 2003
        
autobuild@tgm.netbsd.org:/autobuild/HEAD/i386/OBJ/autobuild/HEAD/src/sys
/arch/i386/compile/GENERIC_DIAGNOSTIC
total memory = 127 MB
avail memory = 111 MB
using 1659 buffers containing 6636 KB of memory
BIOS32 rev. 0 found at 0xffe90
mainbus0 (root)
cpu0 at mainbus0: (uniprocessor)
cpu0: Intel Pentium/MMX (586-class), 232.12 MHz, id 0x543
cpu0: features 8001bf<FPU,VME,DE,PSE,TSC,MSR,MCE,CX8>
cpu0: features 8001bf<MMX>
pci0 at mainbus0 bus 0: configuration mode 1
pci0: i/o space, memory space enabled, rd/line, rd/mult, wr/inv ok
pchb0 at pci0 dev 0 function 0
pchb0: Intel 82439HX System Controller (TXC) (rev. 0x03)
pcib0 at pci0 dev 7 function 0
pcib0: Intel 82371SB PCI-to-ISA Bridge (PIIX3) (rev. 0x01)
pciide0 at pci0 dev 7 function 1
pciide0: Intel 82371SB IDE Interface (PIIX3) (rev. 0x00)
pciide0: bus-master DMA support present
pciide0: primary channel wired to compatibility mode
pciide0: primary channel interrupting at irq 14
pciide0: secondary channel wired to compatibility mode
pciide0: secondary channel interrupting at irq 15
uhci0 at pci0 dev 7 function 2: Intel 82371SB USB Host Controller (PIIX3) 
(rev.
0x01)
uhci0: interrupting at irq 11
usb0 at uhci0: USB revision 1.0
uhub0 at usb0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
Texas Instruments TSB12LV26 OHCI IEEE 1394 Host Controller (Firewire 
serial bus,
 interface 0x10) at pci0 dev 13 function 0 not configured
ex0 at pci0 dev 14 function 0: 3Com 3c905-TX 10/100 Ethernet (rev. 0x0)
ex0: interrupting at irq 9
ex0: MAC address 00:a0:24:e9:d2:d0
nsphy0 at ex0 phy 24: DP83840 10/100 media interface, rev. 0
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
ppb0 at pci0 dev 15 function 0: Digital Equipment DECchip 21152 PCI-PCI 
Bridge (
rev. 0x02)
pci1 at ppb0 bus 1
pci1: i/o space, memory space enabled, rd/line, wr/inv ok
tlp0 at pci1 dev 9 function 0: ADMtek AN985 Ethernet, pass 1.1
tlp0: interrupting at irq 3
tlp0: Ethernet address 00:04:5a:55:16:9a
acphy0 at tlp0 phy 1: ACXXX 10/100 media interface, rev. 0
acphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
tlp1 at pci1 dev 10 function 0: Lite-On 82C169 Ethernet, pass 2.0
tlp1: interrupting at irq 11
tlp1: Ethernet address 00:02:e3:07:ac:14
bmtphy0 at tlp1 phy 1: BCM5201 10/100 media interface, rev. 2
bmtphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
tlp2 at pci1 dev 11 function 0: DECchip 21140A Ethernet, pass 2.2
tlp2: interrupting at irq 3
tlp2: Ethernet address 00:00:94:a9:61:cd
tlp2: 10baseT, 100baseTX, 10baseT-FDX, 100baseTX-FDX
vga1 at pci0 dev 16 function 0: S3 Trio32/64 (rev. 0x54)
wsdisplay0 at vga1 kbdmux 1: console (80x25, vt100 emulation)
wsmux1: connecting to wsdisplay0
ex1 at pci0 dev 17 function 0: 3Com 3c905-TX 10/100 Ethernet (rev. 0x0)
ex1: interrupting at irq 11
ex1: MAC address 00:c0:4f:b5:fd:b0
nsphy1 at ex1 phy 24: DP83840 10/100 media interface, rev. 1
nsphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto


-- 

The nice thing about Windows is - It does not just crash, it displays a
dialog box and lets you press 'OK' first.
						-- Arno Schaefer