On Fri, Nov 26, 2010 at 4:07 AM, Giacomo Comes <comes@xxxxxxxx> wrote: > On Thu, Nov 25, 2010 at 07:12:28PM +0000, Dave Kilroy wrote: >> >> > Attached you will find the wpa_supplicant.log created with the >> > following command line: >> > wpa_supplicant -ieth1 -c wpa_supplicant.conf -f wpa_supplicant.log -dd >> >> <paste> >> Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver >> 'default' ctrl_interface 'N/A' bridge 'N/A' >> ... >> WEXT: cfg80211-based driver detected >> ... >> Driver did not support SIOCSIWENCODEEXT >> </paste> >> >> eh? This looks like the problem. The driver should definitely support >> this via the cfg80211 wrappers. >> >> You might try explicitly forcing wpa_supplicant to use the WEXT driver >> with -Dwext, though I think the netlink interface ought to work as >> well. > > Done. wpa_supplicant.log looks exactly the same except the line: > Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A' > is replaced with: > Initializing interface 'eth1' conf 'wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A' > as it should be. > > One thing that I forgot to mention is that when I run wpa_supplicant, > on the standard error are printed the following messages: > ioctl[SIOCSIWENCODEEXT]: Invalid argument > ioctl[SIOCSIWENCODEEXT]: Invalid argument > ioctl[SIOCGIWSCAN]: Resource temporarily unavailable > ioctl[SIOCSIWSCAN]: Device or resource busy > ioctl[SIOCSIWSCAN]: Device or resource busy > ioctl[SIOCSIWSCAN]: Device or resource busy > and so on until I interrupt wpa_supplicant. > >> >> Check whether CONFIG_CFG80211_WEXT is configured in your kernel (it should be). > > It is. > >> >> Also ensure that you're not trying to use CCMP. orinoco only supports >> WPA with TKIP encryption. > > wpa_supplicant.conf contains: > network={ > ssid="Comes" > psk="<password>" > key_mgmt=WPA-PSK > priority=5 > proto=WPA > } Just had a closer look at your log. wpa_supplicant is clearing keys 4 and 5, which is why you're getting invalid arguments reported. This shouldn't affect driver behaviour. After that, something seems to go wrong with scanning. Try a plain scan with wpa_supplicant turned off. Do you get any results? iw dev eth1 scan iwlist eth1 scan Dave. -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html