Re: Trouble with Macbook Pro 8,2 (broadcom 4331) and latest b43

[AndrewL733 <AndrewL733@aol.com>]

Hi
> See my other mail on this... it's not really NM, but I believe it's a
> bug in the driver exposed by some behavior that NM has that static
> wpa_supplicant does not.  You should be able to trigger the same
> behavior by periodically executing 'iwlist wlan0 scan' on the command
> line, or by asking wpa_supplicant to scan by using wpa_cli.
>
> Grabbing more debugging info using "-dddt" as arguments to the
> supplicant would help.
Sure, I will do that
>
> Also, are you sure your manually started copy of wpa_supplicant is the
> only copy that's running?
Yes, I'm sure.  I did "ps aux | grep wpa" before  starting wpa_supplicant.
>> wpa on the command line:
>>
>> [root@andynewmac andy]# wpa_supplicant -Dwext -i wlan0 -c
>> /etc/wpa_supplicant.conf
>> CTRL-EVENT-DISCONNECTED bssid=00:00:00:00:00:00 reason=0
>> ioctl[SIOCSIWSCAN]: Device or resource busy
>> Failed to initiate AP scan.
>> ioctl[SIOCSIWSCAN]: Device or resource busy
>> Failed to initiate AP scan.
> These aren't necessarily a good start, though sometimes they are
> expected.
>
>> Trying to associate with 48:5b:39:5b:67:27 (SSID='es-network2' freq=2412
>> MHz)
>> Associated with 48:5b:39:5b:67:27
>> WPA: Key negotiation completed with 48:5b:39:5b:67:27 [PTK=CCMP GTK=TKIP]
>> CTRL-EVENT-CONNECTED - Connection to 48:5b:39:5b:67:27 completed (auth)
>> [id=1 id_str=]
>> CTRL-EVENT-DISCONNECTED bssid=48:5b:39:5b:67:27 reason=0
>> ioctl[SIOCSIWSCAN]: Device or resource busy
>> Failed to initiate AP scan.
>> ioctl[SIOCSIWSCAN]: Device or resource busy
>> Failed to initiate AP scan.
> There's not enough debugging output from the supplicant to figure out
> why the disconnect event occurred though.  That's the real reason there
> are problems here.  WEXT doesn't give us enough information about why
> the disconnect occurred.  Instead of using "-Dwext", can you use
> "-Dnl80211" instead?  WEXT is an old API and is replaced by nl80211,
> which gives us much more usable information.

Will try and report back.
> Dan
>
>
Andy