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/09/2005 03:33:01
On Sat, Oct 08, 2005 at 11:54:58PM +0200, Manuel Bouyer wrote:

> On Fri, Oct 07, 2005 at 05:00:29PM +0000, Dheeraj S wrote:
> > I have managed to own this machine for a few days and it would be nice to
> > get this card working.
> > As Manuel suggested, I tried to change/force the media type to 1000baseSX-FDX
> > and 1000baseSX but to no avail.
> > 
> > I was looking through the code and the code paths in wm_tbi_mediachange()
> > indicates that there is signal but the link is not up.
> > 
> > I am a bit lost here as to what might be the missing piece.
> > 
> > Since there are two Copper and three Fiber cards on this machine, if I enable
> > WM_DEBUG, the logs get swamped by the working wm0/wm1 logs.
> > 
> > Any hints on how to go about fixing it ?
> 
> 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.)

truly
dheeraj