Re: bcm43xx regression in 2.6.24 (with patch)

From: Michael Buesch
Date: Mon Feb 25 2008 - 04:55:56 EST


On Monday 25 February 2008 07:49:35 Greg KH wrote:
> On Mon, Feb 25, 2008 at 08:16:17AM +0200, Pekka J Enberg wrote:
> > Hi Michael,
> >
> > On Sun, 24 Feb 2008, Michael Buesch wrote:
> > > > The ony way I see this was possible, you manually changed the
> > > > module loading order, so that the b43xx module was loaded prior
> > > > to the ssb and b44 modules. Right?
> > >
> > > Right. So "so I'm left with either no wifi or no ethenet" being wrong.
> >
> > Lets make this simple: it used to work before and now it doesn't.
> > Therefore it's a regression that must be addressed. Period.
>
> Isn't the resolution Michael is suggesting is, "use the different driver"?

I have two resolutions. One being:
rmmod b44
rmmod ssb
modprobe bcm43xx
modprobe b44

The other being: Wait for 2.6.25 and use the maintained b43 driver.

--
Greetings Michael.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/