Description of problem: Broadcom WiFi driver included with kernel (brcmsmac/bcma) is broken. It is unable to accept long WPA/WPA2 key (some 45 characters including spaces etc). Broadcom's driver (wl.ko) works like charm. Version-Release number of selected component (if applicable): 3.2.2-1.fc16.x86_64 How reproducible: Easily Steps to Reproduce: 1. use NetworkManager to connecto to my WLAN 2. enter WPA/WPA2 key 3. NetworkManager keeps asking forkey like it was entered incorrectly. Actual results: No association/connection to WLAN Expected results: Connection Additional info: If I pre-save the configuration and switch to wl.ko driver I get connected(NetworkManager) within few seconds. After switching back to kernel-supplied driver I cannot connect.Same behaviour in GNOME and KDE. It happens only with LOOONG WPA/WPA2 key - I can connect to networks with shorter key, public networks, enterprise networks
Meanwhile I tried "broadcom-wl/kmod-wl" package from rpmfusion and it works as well. So only the kernel supplied driver is broken. MP
Arend, this kernel is using compat-wireless-3.3-rc1...
brcmsmac has no notion of encryption whatsoever as it does not provide encryption offloading to mac80211. wl.ko is not a mac80211 driver.
It sounds legit but doesn't help me at all. How can you help you to help me? wl.ko uses lib80211 and lib80211_crypt_tkip MP
(In reply to comment #4) > It sounds legit but doesn't help me at all. > How can you help you to help me? wl.ko uses lib80211 and lib80211_crypt_tkip I guess you want to help me, right? > > MP Exactly how long is the WPA/WPA2 key you are using?
Sorry, should have been "How can Ihelp you to help me". Freezeing here, both brain and hands are malfunctioning :) It's 44 chars long passphrase, includes UPPER and lower case letters, spaces, numbers and common sentence interpunction such as comma (,) and dot (.) TIA MP
# Mass update to all open bugs. Kernel 3.6.2-1.fc16 has just been pushed to updates. This update is a significant rebase from the previous version. Please retest with this kernel, and let us know if your problem has been fixed. In the event that you have upgraded to a newer release and the bug you reported is still present, please change the version field to the newest release you have encountered the issue with. Before doing so, please ensure you are testing the latest kernel update in that release and attach any new and relevant information you may have gathered. If you are not the original bug reporter and you still experience this bug, please file a new report, as it is possible that you may be seeing a different problem. (Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.