Re: yongari nfe problems

From: Pyun YongHyeon <pyunyh_at_gmail.com>
Date: Tue, 13 Mar 2007 09:58:45 +0900
On Tue, Mar 13, 2007 at 09:46:01AM +0900, To Rainer Hurling wrote:
 > On Mon, Mar 12, 2007 at 10:41:40PM +0100, Rainer Hurling wrote:
 >  > Pyun YongHyeon, thank you for reply.
 >  > 
 >  > Sorry for the late answer, but I have been on business trip.
 >  > 
 >  > Pyun YongHyeon schrieb:
 >  > >On Sun, Mar 11, 2007 at 09:09:47AM +0100, Rainer Hurling wrote:
 >  > > > Pyun YongHyeon schrieb:
 >  > > > >[... SNIP ...] 
 >  > > > >
 >  > > > >Did stock nfe(4) work on MCP55?
 >  > > > >(I'm not interested in how nve(4) works on MCP55.)
 >  > > > >I'm afraid MCP55 requires different programming. Searching archives
 >  > > > >for Linux forcedeth driver also reveals issues on MCP55 which is
 >  > > > >exactly the same issue I think.
 >  > > > >I'll let you know if I find a clue but it's hard to fix due to lack
 >  > > > >of MCP55 hardware and documentation.
 >  > > > 
 >  > > > 
 >  > > > Yes, nfe(4) works on MCP55, but with some strange behaviour, see below.
 >  > > > 
 >  > > > I am working with FreeBSD 7.0-CURRENT from 03/07/2007 on MSI K9N Neo. 
 >  > > > 'dmesg | grep nfe' gives me:
 >  > > > 
 >  > > > nfe0: <NVIDIA nForce MCP55 Networking Adapter> port 0xb000-0xb007 mem
 >  > > > 0xfbef7000-0xfbef7fff,0xfbefa800-0xfbefa8ff,0xfbefa400-0xfbefa40f irq 21
 >  > > > at device 8.0 on pci0
 >  > > > miibus0: <MII bus> on nfe0
 >  > > > ukphy0: <Generic IEEE 802.3u media interface> PHY 1 on miibus0
 >  > > > ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
 >  > > > 1000baseT-FDX, auto
 >  > > > nfe0: using obsoleted if_watchdog interface
 >  > > > nfe0: Ethernet address: xx:xx:xx:xx:xx:xx
 >  > > > nfe0: [ITHREAD]
 >  > > > 
 >  > > > It seems that there is a problem with watchdog. Perhaps the choosen 
 >  > > > media interface ukphy0 is not correct?
 >  > > > 
 >  > >
 >  > >Normally nVidia GigEs use Marvell PHY which is served by e1000phy(4)
 >  > >so I guess power saving mode had ukphy attach the PHY.
 >  > >Booting/loading module with bootverbose mode will show up OUI/model/rev
 >  > >of the PHY. Please let me know the OUI/model/rev output of ukphy(4).
 >  > 
 >  > for ukphy0 bootverbose gives me :
 >  > 
 >  > OUI 0x0001c1  model 0x0002  rev. 0
 >  > 
 > 
 > Hmm, it's gigabit PHY from Vitesse semiconductor.
 > AFAIK there is no driver for the PHY but I guess ciphy(4) would be a
 > possible driver for the PHY. I've checked Vitesse site for the PHY
 > documentation but it seems they require a kind of NDA and it's not
 > available option to me.
 > 
 > Please try attached patch and rebuild miibus(4) and give it a spin.
 > 

Oops, please use this patch.

-- 
Regards,
Pyun YongHyeon

Received on Mon Mar 12 2007 - 23:56:32 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:39:06 UTC