This should be an easy one for you guys. ;) Here's the scoop: I found this bug in the kernel's own Bugzilla, so I followed that and tried out patches and whatnot. The final patches they came up with fixes this issue. I'm wondering if you guys can get those patches into the next kernel revision. (I've patched my own system. This is just for convenience for users that hit this later on.) The kernel's bug entry is: http://bugzilla.kernel.org/show_bug.cgi?id=9987 Reproducible: Always Steps to Reproduce: 1. Install any 2.6.24 kernel 2. Load b43 and use any configuration you desire 3. Try to associate with or without WEP and watch it cry Actual Results: The card fails to associate as if I had a bad WEP key or I was too far away. The router just doesn't seem to want to talk. Expected Results: I can digg stuff. ;)
We'll keep an eye on this and attempt the backport once it makes the development upstream kernel tree.
Created attachment 150892 [details, diff] upstream patch workaround invalid bluetooth settings Patch from upstream linux development tree
Created attachment 150893 [details, diff] btcoexist workarounds patch btcoexist patch from upstream linux development tree
Can you apply the two patches I attached against gentoo-sources-2.6.25-r1 (or the latest gentoo-sources-2.6.25-rX) test and post the results here.
please reopen when you have tested these Actually, they are included in Linux 2.6.25.2. I'll be doing a new release soon, so hopefully that will fix it.
Sorry, today was the day I planned on replying. I've been extremely busy lately. I'm wary about installing extremely new, unstable software on my system. I want to be sure it isn't going to "hurt" anything else first before I try this. Is the kernel going to be fairly self-contained, or will it require extra libraries or do something funky with some other folder, for instance?
