Am 04.07.2013 22:57, schrieb Michael Biebl:
> Hi Roland,
> 
>> Jul  4 16:02:25 elastomir wpa_supplicant[1700]: nl80211: 'nl80211' generic 
>> netlink not found
>> Jul  4 16:02:25 elastomir wpa_supplicant[1700]: Failed to initialize driver 
>> 'nl80211'
>> Jul  4 16:02:25 elastomir wpa_supplicant[1700]: ioctl[SIOCSIWENCODEEXT]: 
>> Invalid argument
>> Jul  4 16:02:25 elastomir wpa_supplicant[1700]: ioctl[SIOCSIWENCODEEXT]: 
>> Invalid argument
>> Jul  4 16:02:31 elastomir wpa_supplicant[1700]: eth1: Trying to associate 
>> with 14:0c:76:f9:23:bd (SSID='FreeWifi' freq=2472 MHz)
>> Jul  4 16:02:31 elastomir wpa_supplicant[1700]: ioctl[SIOCSIWGENIE]: 
>> Operation not supported
>> Jul  4 16:02:31 elastomir wpa_supplicant[1700]: eth1: Association request to 
>> the driver failed
> 
> 
> That looks suspcious. Do you get a reliable network connection if you
> use ifupdown+wpa_supplicant directly?

It would be useful to test both wext *and* nl80211.

> The difference between squeeze and wheezy might be, that NM now uses
> nl80211 instead of wext and the old card/driver is possibly not
> supporting the new interface properly.
>

The problem is, that if a driver supports both interfaces, nl80211 is
preferred over wext. I'm a bit puzzled about

> Jul  4 16:02:24 elastomir NetworkManager[12446]: <info> (eth1): using WEXT 
> for WiFi device control

So NM says it is using WEXT, but wpasupplicant is complaining about
nl80211 related errors. My guess is, that the problem is buried
somewhere there.

Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to