brcmsmac driver only works when sitting next to the AP
rvossen at broadcom.com
Wed Aug 17 03:39:01 PDT 2011
>> 'Aug 14 13:39:02 stt300 NetworkManager:
>> supplicant_interface_acquire: assertion `mgr_state ==
>> NM_SUPPLICANT_MANAGER_STATE_IDLE' failed'
>> I also see many 'wpa_supplicant: Failed to initiate AP scan' messages.
>> There are no 'Failed to initiate AP scan' messages before the 'assertion
>> failed' message. I do not know if the 2nd message is a byproduct of the
>> 1st result. Regardless, a failed assertion is serious. I cc'ed the
>> network manager mailing list.
> Yeah, the scanning issues are almost certainly what's causing stuff to
> fail; which obviously seems like a driver issue at this point.
Well, the 1st sign that something goes wrong is the assert message in
NetworkManager. After that, the scans are the next things that go wrong.
So I don't understand why you think that this is a driver problem, I
would rather say this is a Network manager problem. Could you explain ?
More information about the devel