Latest kernel makes wireless connection to WPA2 router fail

[paul s]

i work with a mbp4,1
http://www.smolts.org/client/show/pub_734339f1-74c4-4607-a763-2ef2378ab19e

which has a BCM4328 adapter...

>> b43                   127352  0
>> ssb                    39572  1 b43
>> mac80211              199632  1 b43
>> cfg80211               37088  2 b43,mac80211
>> input_polldev           3952  2 b43,applesmc

what i don't see is the wl module loaded in your output... perhaps you
are using another driver or something... but it doesn't look like the
driver is there...

i'm pretty sure you need to blacklist the b43 driver... these are the
modules that are blacklist on my mbp:

blacklist bcm43xx
blacklist ssb
blacklist b43
blacklist ndiswrapper

also check to see if these are loaded as they are needed as well for the
wpa encryption:
lib80211                6356  2 lib80211_crypt_tkip,wl
lib80211_crypt_tkip     9296  0

>>     some error messages from NetworkManager, or wpa_supplicant, that

if your ssid is hidden, network manager will not be able to connect for
some unearthly reason... you might want to use wicd instead, but there
isn't an rpm for it, however it works lovely...

> The best thing for you to do is to open a Bugzilla bug for the kernel component

no need, broadcom's wireless driver is working with the latest kernel...

cheers
paul








On 08/30/2009 04:41 PM, Henrik Frisk wrote:
> 
> 
> On Sun, Aug 30, 2009 at 9:22 PM, Sam Varshavchik <mrsam at courier-mta.com 
> <mailto:mrsam at courier-mta.com>> wrote:
> 
>     Henrik Frisk writes:
> 
>         Hi,
> 
>         I'm running FC11 on a MacBook Pro. After the latest kernel
>         updates (to 2.6.29.6-217.2.16.fc11.x86_64) I cannot connect to
>         my wireless router anymore. If I boot up in the previous kernel
>         it works fine. Any ideas on how I can fix this? The wireless
>         interface on this laptop is a Broadcom Corporation BCM4322.
> 
> 
>     No problems on this laptop with BCM4311 and the latest kernel.
> 
>     Generally, a blanket statement that something doesn't work offers
>     very little usable information to work with. At the very least, you
>     should gather some preliminary information yourself, such as:
> 
> 
> Right, sorry about that.
>  
> 
> 
>     1) the output of lsmod, to determine whether the b43 kernel module
>     is loaded.'
> 
>  
> It wasn't but it didn't change anything to add it. Here's the output of 
> 'lsmod | grep b43'
> b43                   127352  0
> ssb                    39572  1 b43
> mac80211              199632  1 b43
> cfg80211               37088  2 b43,mac80211
> input_polldev           3952  2 b43,applesmc
> 
> 
>     2) various bits of information from /var/log/messages. kernel
>     messages from early in the boot process would report whether or not
>     the kernel module was loaded, and if not why not. Or may be you have
>     some error messages from NetworkManager, or wpa_supplicant, that
>     point towards a clue.
> 
> 
> Here's the output of 'cat messages | grep Network':
> 
> Aug 30 22:34:34 localhost NetworkManager: <info>  Activation 
> (eth1/wireless) Stage 2 of 5 (Device Configure) successful.  Connected 
> to wireless network 'dinergy'.
> Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) 
> Stage 3 of 5 (IP Configure Start) scheduled.
> Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) 
> Stage 3 of 5 (IP Configure Start) started...
> Aug 30 22:34:34 localhost NetworkManager: <info>  (eth1): device state 
> change: 5 -> 7 (reason 0)
> Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) 
> Beginning DHCP transaction.
> Aug 30 22:34:34 localhost NetworkManager: <info>  dhclient started with 
> pid 9060
> Aug 30 22:34:34 localhost NetworkManager: <info>  Activation (eth1) 
> Stage 3 of 5 (IP Configure Start) complete.
> Aug 30 22:34:34 localhost NetworkManager: <info>  DHCP: device eth1 
> state changed normal exit -> preinit
> Aug 30 22:35:20 localhost NetworkManager: <info>  Device 'eth1' DHCP 
> transaction took too long (>45s), stopping it.
> Aug 30 22:35:20 localhost NetworkManager: <info>  eth1: canceled DHCP 
> transaction, dhcp client pid 9060
> Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) 
> Stage 4 of 5 (IP Configure Timeout) scheduled...
> Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) 
> Stage 4 of 5 (IP Configure Timeout) started...
> Aug 30 22:35:20 localhost NetworkManager: <info>  (eth1): device state 
> change: 7 -> 9 (reason 5)
> Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) 
> failed for access point (dinergy)
> Aug 30 22:35:20 localhost NetworkManager: <info>  Marking connection 
> 'Auto dinergy' invalid.
> Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) failed.
> Aug 30 22:35:20 localhost NetworkManager: <info>  Activation (eth1) 
> Stage 4 of 5 (IP Configure Timeout) complete.
> Aug 30 22:35:20 localhost NetworkManager: <info>  (eth1): device state 
> change: 9 -> 3 (reason 0)
> Aug 30 22:35:20 localhost NetworkManager: <info>  (eth1): deactivating 
> device (reason: 0).
> 
> It finds the access point but fails at connecting..
> 
> thanks for any help,
> 
> /h
>