brcmsmac driver only works when sitting next to the AP

Roland Vossen rvossen at broadcom.com
Thu Aug 18 08:07:54 UTC 2011


Hello Dan,

can you reply ?

Thanks, Roland.

On 08/17/2011 12:39 PM, Roland Vossen wrote:
>>> 'Aug 14 13:39:02 stt300 NetworkManager[1181]:
>>> supplicant_interface_acquire: assertion `mgr_state ==
>>> NM_SUPPLICANT_MANAGER_STATE_IDLE' failed'
>>>
>>> I also see many 'wpa_supplicant[1204]: 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 ?
>
> Thanks, Roland.





More information about the devel mailing list