Return-path: Received: from mail-fx0-f46.google.com ([209.85.161.46]:39049 "EHLO mail-fx0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751134Ab0LDMBj (ORCPT ); Sat, 4 Dec 2010 07:01:39 -0500 Received: by fxm20 with SMTP id 20so2982909fxm.19 for ; Sat, 04 Dec 2010 04:01:38 -0800 (PST) MIME-Version: 1.0 In-Reply-To: <20101204033646.GA22662@monopoli.naic.edu> References: <20101130021911.GA18971@monopoli.naic.edu> <20101202002234.GA30670@monopoli.naic.edu> <20101203001052.GA16808@monopoli.naic.edu> <20101203202321.GA21937@monopoli.naic.edu> <20101204033646.GA22662@monopoli.naic.edu> Date: Sat, 4 Dec 2010 12:01:34 +0000 Message-ID: Subject: Re: orinoco_cs module and WPA not working From: Dave Kilroy To: Giacomo Comes Cc: linux-wireless@vger.kernel.org Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-wireless-owner@vger.kernel.org List-ID: >> I'm at a loss. I've looked at the wpa_supplicant code, and had another >> look at the driver. The scan should be a plain wildcard scan - which >> you've identified works. >> >> Does setting scan_ssid=1 in the wpa_supplicant network block change >> the behaviour? That's usually only necessary for hidden SSIDs - but >> I'd like to know if the scan succeeds in this case. > > No It doesn't work. > But I have more informations for you. > > I have been testing different versions of wpa_supplicant > and I have found that if a use wpa_supplicant 0.7.0 or earlier, > it works. With 0.7.1 or newer it fails. > wpa_supplicant 0.7.0 works even without applying your patch. I've set myself up so I can test with orinoco_usb. I can reproduce the issue (or something that looks the same). After much confusion, I suspect the initial scan is being triggered before the hardware is ready. Internally, wpa_supplicant will do an 'ifconfig eth1 up' followed by an 'iwlist eth1 scan', and it seems the driver/hardware wants more time between them. Try the following (either in two command prompts, or with wpa_supplicant in the background): prompt1$ wpa_supplicant -dd -ieth1 .... prompt2$ ifconfig eth1 down prompt2$ ifconfig eth1 up and see what wpa_supplicant is doing. If it has got scan results then you're probably seeing what I am. I need to have a think about how this needs to be fixed in the driver. Dave.