In message <20060207034233.D97D823CFB@thoreau.thistledown.com.au>, Simon Burge 
writes:
>Matthias Scheler wrote:
>
>> In article <20060204141545.GD5671@sanctum.terrorpin.net>,
>> 	Ben Collver <collver@peak.org> writes:
>> > However, I have seen NetBSD fail to recognize Intel gigE chipsets that
>> > are listed in the man page as supported.
>> 
>> Could you please let us know which ones? At least the manual page
>> should be corrected.
>
>I too have seen issues with wm.  I have a board here with:
>
>wm0 at pci3 dev 3 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
>wm0: interrupting at irq 11
>wm0: 64-bit 133MHz PCIX bus
>wm0: 256 word (8 address bits) MicroWire EEPROM
>wm0: Ethernet address 00:30:48:70:41:98
>wm1 at pci4 dev 2 function 0: Intel i82545EM 1000BASE-T Ethernet, rev. 1
>wm1: interrupting at irq 11
>wm1: 64-bit 100MHz PCIX bus
>wm1: 256 word (8 address bits) MicroWire EEPROM
>wm1: Ethernet address 00:07:e9:1f:c4:71
>
>wm0 is on the motherboard, wm1 is a PCIX card.  wm0 will only work if I
>hard wire it to 10mbit/sec (with "media 10baseT" in the ifconfig line).
>The "external" wm works perfectly however.
>

For wm0, are you using it on a 10BaseT network?  I've noticed similar 
problems on my laptop:

wm0 at pci2 dev 1 function 0: Intel i82540EP 1000BASE-T Ethernet, rev. 3
wm0: interrupting at irq 11
wm0: 32-bit 33MHz PCI bus
wm0: 64 word (6 address bits) MicroWire EEPROM
wm0: Ethernet address 00:11:25:43:e8:a4
makphy0 at wm0 phy 1: Marvell 88E1011 Gigabit PHY, rev. 4

It works fine on 100BaseT networks; on 10BaseT nets, I have to set the 
speed explicitly, even though it detects the network speed correctly.
The problem was introduced somewhere between 2.0 and 3.0; it's still 
there on -current.  See PR kern/30078.

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb