Re: Adding PHY driver to 5.1 release

["Michael T. Davis" <DAVISM%ecr6.ohio-state.edu@localhost>]

At 00:05:56.64 on 27-JUL-2011 in message
<01O44ASMIB429F1A96%ecr6.ohio-state.edu@localhost>, I wrote:

>       I just installed 5.1 release (i386) on a system, but I'm having trouble
>talking to my Intel NICs.  This is what dmesg has to say about one of them:
>
>wm0 at pci1 dev 4 function 0: Intel i82541PI 1000BASE-T Ethernet, rev. 5
>wm0: interrupting at ioapic0 pin 16
>wm0: 32-bit 33MHz PCI bus
>wm0: 64 word (6 address bits) MicroWire EEPROM
>wm0: Ethernet address 00:0e:0c:82:96:0a
>igphy0 at wm0 phy 1: Intel IGP01E1000 Gigabit PHY, rev. 0
>igphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> 1000baseT-FDX, auto
>
>I have the interface configured with an IP address (via /etc/ifconfig.wm0),
> but
>attaching a live cable doesn't do anything.  (`ifconfig wm0' reports "status:
>no carrier."  FWIW, it also reports "enabled=0.")  I note that the kernel is
>configured with igphy device support (per the sources), but there's no man
>page, whereas there is an igphy man page at www.netbsd.org.  Is the 5.1
>release missing something which is preventing me from using this NIC?  If so,
>what's the most straightforward mechanism for acquiring it?  Or do I just need
>to tweak a setting somewhere?
>[...]

        I would consider tracking -current, except that this installation
will be for an enterprise firewall.  Using -current for such a mission-
critical role would not seem to be a good choice.  I'm going to try a
different (older) NIC to see if that resolves the issue.  I have a candidate
in mind, but I would appreciate any positive recommendations for a (32-bit)
PCI copper NIC that supports 1GbE that's supported (i.e. known to work) under
the 5.1 release.  (I'm not necessarily tied to Intel.)

        Since the mii(4) man page lacks a cross-reference for igphy under
-current (though -current does include an igphy(4) page), and with this
experience, I think it's safe to conclude that the card I tried isn't
properly supported yet.  Perhaps under a future release...?

Regards,
Mike