Subject: Re: Problems with the wm driver
To: Manuel Bouyer <email@example.com>
From: Bill Studenmund <firstname.lastname@example.org>
Date: 04/22/2005 16:53:47
Content-Type: text/plain; charset=us-ascii
On Fri, Apr 22, 2005 at 09:37:57PM +0200, Manuel Bouyer wrote:
> On Fri, Apr 22, 2005 at 01:28:50PM +0300, Martti Kuparinen wrote:
> > On Fri, 22 Apr 2005, Martti Kuparinen wrote:
> > >I'm having big problems with the wm(4) driver. I have two integrated p=
> > >on the motherboard (wm0 and wm1) and two ports (wm2 and wm3) on a
> > >dual-port PCI card.
> > >
> > >No matter what I do I can't get the media detected on wm1 and wm3.
> > >wm0 and wm2 work just fine. Linux 2.6.11 on an identical Dell PowerEdg=
> > >is able to use all ports just fine.
> > I don't know what's going on here but I was able to get address
> > for wm0, wm1 and wm3 with dhclient. This was shown on the console:
> > wm2: unable to allocate or map rx buffer 104, error =3D 55
> > wm2: interface not running
> You could try increasing NMBCLUSTERS. if_wm will allocate 256 RX buffers
> per interface. With 4 interfaces you're at 1024, which is the
> default NMBCLUSTERS value.
Oh, yeah, that problem. Yes, increase NMBCLUSTERS. We have machines with=20
six wm's in them, and we had to do that to get them to boot.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (NetBSD)
-----END PGP SIGNATURE-----