BCM4306 cannot associate with any version of b43 driver
I feel I have to escalate this regression to the mailing lists because I've had no response on the kernel bugzilla from quite some time now.
With the release of the b43 driver, my card can no longer associate with its AP. I've been testing with 2.6.24 and the wireless-git tree hoping that someone would fix it, but I've had no requests for testing and no response.
http://bugzilla.kernel.org/show_bug.cgi?id=9987
What else do I need to do to get someone to help me? More debugging information? Please ask me to do something, I'm trying to be an active participant in the process...
Signature · 2 lines
Gabriel A. Devenyi B.Eng. [email protected]
Quoted 8 lines · Gabriel A. Devenyi
I feel I have to escalate this regression to the mailing lists because I've had no response on the kernel bugzilla from quite some time now.
With the release of the b43 driver, my card can no longer associate with its AP. I've been testing with 2.6.24 and the wireless-git tree hoping that someone would fix it, but I've had no requests for testing and no response.
http://bugzilla.kernel.org/show_bug.cgi?id=9987
What else do I need to do to get someone to help me? More debugging information? Please ask me to do something, I'm trying to be an active participant in the process...
Which channel is your AP on?
Signature · 1 line
Brian
Quoted 8 lines · Gabriel A. Devenyi
I feel I have to escalate this regression to the mailing lists because I've had no response on the kernel bugzilla from quite some time now.
With the release of the b43 driver, my card can no longer associate with its AP. I've been testing with 2.6.24 and the wireless-git tree hoping that someone would fix it, but I've had no requests for testing and no response.
http://bugzilla.kernel.org/show_bug.cgi?id=9987
What else do I need to do to get someone to help me? More debugging information? Please ask me to do something, I'm trying to be an active participant in the process...
Did you notice the old firmware message in the dmesg output you provided?
Have you tried the version 4 firmware?
Signature · 1 line
Brian
Quoted 9 lines · Gabriel A. Devenyi
I feel I have to escalate this regression to the mailing lists because I've had no response on the kernel bugzilla from quite some time now.
With the release of the b43 driver, my card can no longer associate with its AP. I've been testing with 2.6.24 and the wireless-git tree hoping that someone would fix it, but I've had no requests for testing and no response.
Is your AP using channel 13 or something like that by any chance? Then you'll need to load mac80211 with the option ieee80211_regdom=64 to make this work. Add
options mac80211 ieee80211_regdom=64
to modprobe.conf and reload the mac80211 module.
Signature · 1 line
Frederik Himpe
Quoted 12 lines · On Thu, 3 Apr 2008 17:47:02 +0000 (UTC) Frederik Himpe <[email protected]>…
Quoted 9 lines · Gabriel A. Devenyi
I feel I have to escalate this regression to the mailing lists because I've had no response on the kernel bugzilla from quite some time now.
With the release of the b43 driver, my card can no longer associate with its AP. I've been testing with 2.6.24 and the wireless-git tree hoping that someone would fix it, but I've had no requests for testing and no response.
Quoted 8 lines
Is your AP using channel 13 or something like that by any chance? Then you'll need to load mac80211 with the option ieee80211_regdom=64 to make this work. Add
options mac80211 ieee80211_regdom=64
to modprobe.conf and reload the mac80211 module.
If it is a recent kernel (2.6.24) then this needs to be:
options cfg80211 ieee80211_regdom="JP"
instead.
I had a problem with the iwlwifi driver in this regard, my AP is on channel 12. Scanning found it, but it wouldn't associate. The option string above fixed it for me.
Signature · 4 lines
Brian Morrison
"Arguing with an engineer is like wrestling with a pig in the mud;
after a while you realize you are muddy and the pig is enjoying it."Quoted 4 lines
I had a problem with the iwlwifi driver in this regard, my AP is on channel 12. Scanning found it, but it wouldn't associate. The option string above fixed it for me.
FWIW, that was recently "fixed", scanning will no longer find it.
johannes
Quoted 1 line · Brian Morrison
Which channel is your AP on?
My AP is on channel 11.
Quoted 2 lines
Did you notice the old firmware message in the dmesg output you provided? Have you tried the version 4 firmware?
Comment #3 on the bug points this out, and in comment #4 I updated the firmware.
Please add me to CC as I am not subscribed to the list
Signature · 2 lines
Gabriel A. Devenyi B.Eng. [email protected]