On Thu, Mar 13, 2003 at 01:02:40PM -0500, D'Arcy J.M. Cain wrote:
> On Thursday 13 March 2003 12:09, Manuel Bouyer wrote:
> > On Thu, Mar 13, 2003 at 11:54:57AM -0500, D'Arcy J.M. Cain wrote:
> > > I have this card installed and it is probed as follows.
> > >
> > > wm0 at pci2 dev 10 function 0: Intel i82544EI 1000BASE-T Ethernet, rev. 2
> > > wm0: interrupting at irq 11
> > > wm0: Ethernet address 00:02:b3:c8:1d:42
> > > ukphy0 at wm0 phy 1: Generic IEEE 802.3u media interface
> >
> > The one I have here:
> > wm0 at pci0 dev 16 function 0: Intel i82544EI 1000BASE-T Ethernet, rev. 2
> > wm0: interrupting at irq 11
> > wm0: Ethernet address 00:02:b3:b2:f2:ac
> > makphy0 at wm0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 0
> > makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
> > 1000baseT-FDX, auto
> 
> Hmmph!  I turned on most of the PHYs but missed that one.  Now I have this.
> 
> wm0 at pci2 dev 10 function 0: Intel i82544EI 1000BASE-T Ethernet, rev. 2
> wm0: interrupting at irq 11
> wm0: Ethernet address 00:02:b3:c8:1d:42
> makphy0 at wm0 phy 1: Marvell 88E1000 Gigabit PHY, rev. 0
> makphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 
> 1000baseT-FDX, auto
> 
> Looks more like yours now but I still get the same problem.  However, I do 
> note that when I reboot the switch that the status does go active for 5 
> seconds if that means anything.

All my network adapters are in autoselect more, and detect the media fine.
They're connected to cisco, allied telesyn or to another wm though a cross-over
cable. Maybe your switch has a problem ? So you have a way to force the
switch to 1000baseT-FDX ?

--
Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
     NetBSD: 24 ans d'experience feront toujours la difference
--