Hello John et al,
(previous email had a typo in ML addr, sorry for the extra noise)
Both b43 and b43legacy fail to load on bcm4318 for a while now, while it used
to work (with known issues) more or less
fine. The issue started happening not long before ssb united the support of b44
as well. Ther
On Saturday 13 October 2007 10:17:30 Vitaly Bordug wrote:
> phy1: Failed to select rate control algorithm
> phy1: Failed to initialize rate control algorithm
That's nothing b43 or ssb related.
Compile and load the rc80211_simple module.
--
Greetings Michael.
_
Hello John et al,
Both b43 and b43legacy fail to load on bcm4318 for a while now, while it used
to work (with known issues) more or less
fine. The issue started happening not long before ssb united the support of b44
as well. Therefor, I noticed the difference
soon, because I am not able to use
Hello Michael,
On Sat, 13 Oct 2007 10:24:47 +0200
Michael Buesch wrote:
> On Saturday 13 October 2007 10:17:30 Vitaly Bordug wrote:
> > phy1: Failed to select rate control algorithm
> > phy1: Failed to initialize rate control algorithm
>
> That's nothing b43 or ssb related.
> Compile and load th
Hi all,
I tried (I think) latest b43 driver on a bcm4318. It works quite well, but on
a series of connect/reconnect I had attached stack in dmesg.
Any idea?
Chris
FYI (normal dmesg output)
b43-phy0: Broadcom 4318 WLAN found
b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7
b43-phy0 debug
On Saturday 13 October 2007 16:14:31 Vitaly Bordug wrote:
> Hello Michael,
>
> On Sat, 13 Oct 2007 10:24:47 +0200
> Michael Buesch wrote:
>
> > On Saturday 13 October 2007 10:17:30 Vitaly Bordug wrote:
> > > phy1: Failed to select rate control algorithm
> > > phy1: Failed to initialize rate contr
On Saturday 13 October 2007 18:23:33 Christian Hoffmann wrote:
> Hi all,
>
> I tried (I think) latest b43 driver on a bcm4318. It works quite well, but on
> a series of connect/reconnect I had attached stack in dmesg.
>
> Any idea?
>
> Chris
>
> FYI (normal dmesg output)
> b43-phy0: Broadcom 4
In commit 7eff2e7a8b65c25920207324e56611150eb1cd9a, the calling sequence
for add_uevent_var was changed, but the ssb driver was not modified, which
leads to a "Unable to handle kernel paging request" oops. This patch fixes
the problem.
Signed-off-by: Larry Finger <[EMAIL PROTECTED]>
---
drivers/
