Re: yongari nfe problems

On Thu, Mar 08, 2007 at 04:33:36PM -0800, Mr. Darren wrote:
 > I tried the following overhauled nfe drivers after no
 > success in getting nfe to work with my hardware.  
 > > http://people.freebsd.org/~yongari/nfe/if_nfe.c
 > >  > >  > > >
 > > http://people.freebsd.org/~yongari/nfe/if_nfereg.h
 > >  > >  > > >
 > > http://people.freebsd.org/~yongari/nfe/if_nfevar.h
 > 
 > It still doesn't work, but I have a new set of errors.
 > 
 > nfe0: <NVIDIA nForce MCP55 Networking Adapter> port
 > 0xb000-0xb007 mem
 > 0xfe02a000-0xfe02afff,0xfe029000-0xfe0290ff,0xfe028000-0xfe02800f
 > irq 10 at device 16.0 on pci0
 > nfe0: Ethernet address: 00:15:f2:f4:af:5e
 > miibus1: <MII bus> on nfe0
 > nfe0: [ITHREAD]
 > nfe1: <NVIDIA nForce MCP55 Networking Adapter> port
 > 0xac00-0xac07 mem
 > 0xfe027000-0xfe027fff,0xfe026000-0xfe0260ff,0xfe025000-0xfe02500f
 > irq 11 at device 17.0 on pci0
 > nfe1: Ethernet address: 00:15:f2:f4:af:5f
 > miibus2: <MII bus> on nfe1
 > nfe1: [ITHREAD]
 > nfe0: link state changed to DOWN
 > nfe0: link state changed to UP
 > nfe0: watchdog timeout (missed Tx interrupts) --
 > recovering
 > nfe0: watchdog timeout (missed Tx interrupts) --
 > recovering
 > 

According to Shigeaki Tagashira'page nForce 590 is supported by
nfe(4). ATM I have no idea why it shows watchdog timeout errors.
Btw, I don't see what PHY driver was attached in your message.
(You can check it with dmesg(8) and normally it would pick up
e1000phy(4).)

 > 
 > the missing tx interrupts were made while trying
 > /sbin/dhclient nfe0
 > 
 > My motherboard is the ASUS crosshair NVIDIA nForce 590
 > FreeBSD DARREN 7.0-CURRENT FreeBSD 7.0-CURRENT #12:
 > Thu Mar  8 16:57:38 UTC 2007    
 > root_at_DARREN:/usr/obj/usr/src/sys/DARREN  amd64
 > the cvsup this kernel was compiled with is less than 1
 > week old.
 > 
 > -Darren
-- 
Regards,
Pyun YongHyeon