Subject: Re: kern/31303: wm(4) driver doesn't detect/attach to a fiber phy
To: Manuel Bouyer <bouyer@antioche.eu.org>
From: Dheeraj S <dheeraj@ece.gatech.edu>
List: netbsd-bugs
Date: 10/10/2005 10:22:46
On Mon, Oct 10, 2005 at 09:58:05AM +0200, Manuel Bouyer wrote:

> On Sun, Oct 09, 2005 at 03:33:01AM +0000, Dheeraj S wrote:
> > > You'll probably need to change DPRINTF to take a per-interface argument,
> > > and enable this per-interface bit only for the appropiate one in
> > > wm_attach (based on device ID/revision for example, or
> > > pa->pa_(bus,device,function) values (the later will allow you to really
> > > select the one you want).
> > > 
> > In the meantime, I tried to loopback the card using a single strand of fiber
> > and the card springs to life, I can see the link status led glow. (Of course,
> > it is of little use.)
> 
> Does ifconfig shows link up too ?
> 
Yes. if config shows link up too. (status : active) and I get the following
messages

Oct  5 15:56:51 saras /netbsd: wm0: DAD detected duplicate IPv6 address fe80:0002::02d0:b7ff:fe45:7c2a: NS in/out=1/1, NA in=0
Oct  5 15:56:51 saras /netbsd: wm0: DAD complete for fe80:0002::02d0:b7ff:fe45:7c2a - duplicate found

truly
dheeraj