Well I tried blacklisting ssb as that was the recommendation I dug up on broadcom's site but I'm led to believe that only applies if you're using the broadcom-sta driver which doesn't cover the ancient broadcom chipset I have. I'm forced to use b43legacy so still back to square 1. I think I've tried everything shy of saying f these drivers and seeing if ndiswrapper gives me better results.
Much googling has turned up many people with the same issue with a plethora of different cards in kernel 2.6.30 and on... with slack 13.1 I have kernel 220.127.116.11.
One thing I did find that might be a solution is: http://www.opennet.ru/tips/info/2214.shtml
which is translated here
although I'm not quite sure I understand it and it may need to be altered since it was done by someone running Ubuntu?
I've made an unlock-wlan file with that bash script in it per the instructions but beyond that I'm not quite sure what to do with it.
If I run it nothing happens as far as changing my rfkill state. An rfkill list still shows phy0 as hard blocked.
Hopefully someone with more knowledge that I can figure out what those crazy Russians are recommending?
Edit: Just found this too: http://forums.gentoo.org/viewtopic-t...5-start-0.html
... not sure what's going on in the guy's resolution though and how I can make that possibly happen.Edited by tier - 1/19/11 at 7:55pm