Marvell Yukon 88E8062 - media selection problem

[Pyun YongHyeon]

On Mon, Jun 30, 2008 at 01:54:23PM +0200, Krzysztof Jedruczyk wrote:
 > Hi,
 > 
 > I am trying to bring up gigabit interface in couple of Nexcom blade servers running FreeBSD/amd64. The interfaces (two Marvell Yukon 88E8062 controllers) are recognized properly, but no media is ever detected:
 > 
 > > ifconfig
 > msk0: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
 >         options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4>
 >         ether 00:10:f3:0d:d6:45
 >         media: Ethernet autoselect (none)
 >         status: no carrier
 > msk1: flags=8802<BROADCAST,SIMPLEX,MULTICAST> metric 0 mtu 1500
 >         options=11a<TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4>
 >         ether 00:10:f3:0d:d6:46
 >         media: Ethernet autoselect (none)
 >         status: no carrier
 > 
 > I tried manual setting of media - but the driver won't allow me to set 1000baseSX link (this is what other blades in the same chasis with working em driver are reporting).
 > 
 > # ifconfig msk0 media 1000baseSX
 > ifconfig: SIOCSIFMEDIA (media): Device not configured
 > 
 > I'm puzzled here: are there known limitations in the driver wrt support of certain media types?
 > 
 > Here is pciconf -lv information if it helps...
 > 
 > mskc0 at pci0:3:0:0:       class=0x020000 card=0x628211ab chip=0x434711ab rev=0x14 hdr=0x00
 >     vendor     = 'Marvell Semiconductor (Was: Galileo Technology Ltd)'
 >     device     = 'Yukon 88E8062 PCI-E IPMI Gigabit Ethernet Controller'
 >     class      = network
 >     subclass   = ethernet
 > 
 > This is on 7.0-RELEASE on amd64. I also tried kernel from 7-STABLE from few days ago, but the problem was still present.
 > 

The 88E8062 support wasn't tested due to lack of hardware and I just
copied the device id from myk driver. Would you show me the output
of "devinfo -rv| grep oui" ? Also it would be better if I can see
verbosed boot message.

-- 
Regards,
Pyun YongHyeon