From: "José Miguel Gonçalves" <jose.goncalves@inov.pt>
To: Arik Nemtsov <arik@wizery.com>
Cc: Luciano Coelho <coelho@ti.com>, linux-wireless@vger.kernel.org
Subject: Re: wl127x: Unable to associate with a WPA2-PSK AP
Date: Wed, 10 Jul 2013 00:59:43 +0100 [thread overview]
Message-ID: <51DCA3EF.8090900@inov.pt> (raw)
In-Reply-To: <CA+XVXfd8WouC7UWwD5z=OAMT2AUaU25d13thinjRDe-JpTQCEw@mail.gmail.com>
Hi Arik,
On 09-07-2013 20:10, Arik Nemtsov wrote:
> On Tue, Jul 9, 2013 at 4:22 PM, José Miguel Gonçalves
> <jose.goncalves@inov.pt> wrote:
>> http://pastebin.com/XmEzqjHs
>>
>> The dmesg output with debug mask set to 0x63c20:
>>
>> http://pastebin.com/zGE0Gfp8
>>
>> Note that with debug activated I did not see the driver's "Beacon loss
>> detected" messages.
> You have this line in the log:
> [ 72.435000] wlan0: deauthenticated from 88:43:e1:57:79:c0 (Reason: 23)
>
> This means:
> Association request rejected because the information in the Power
> Capability element is
> unacceptable
>
> In other words the AP is disconnecting you since your Tx power is
> inadequate (probably too high?). I'd try to limit it using iw, or just
> set a different regdomain where its limited.
> Also I'd try with a different AP.
I think that return code is a bogus caused by the driver debug code,
because when I remove all the debug I see a different behaviour, i.e.,
after brief associating with the AP, I see 3 driver messages;
wlcore: Beacon loss detected. roles:0xff
and then receive from wpa_supplicant;
wlan0: CTRL-EVENT-DISCONNECTED bssid=88:43:e1:57:79:c0 reason=4
locally_generated=1
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="A. Guidance"
auth_failures=1 duration=10
and I've not make any mistake on the pre-shared key.
Also I've used this AP for tests of different wireless adapters with
success. Inclusive have use it with the same hardware platform and same
kernel and sysapps (ifconfig, iw, wpa_supplicant, etc...) and a TP-Link
TL-WN722N Wi-Fi adapter (ath9k_htc driver) and had no problems in
associating that adapter.
Can my problems be related with an inadequate NVS file? I've generated
it with the calibrate tool from ti-utils and the INI file TQS_D_1.7.ini
with the command "calibrator plt calibrate". Is this the correct INI for
my module (Jorjin's WG7350 - wl1273 based)?
Any ideas also why I can not get a complete APs list with the command
"iw wlan0 scan"? No one as seen this behaviour before?
José Gonçalves
next prev parent reply other threads:[~2013-07-10 0:00 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 18:54 wl127x: Unable to associate with a WPA2-PSK AP José Miguel Gonçalves
2013-07-08 19:08 ` Arik Nemtsov
2013-07-08 22:47 ` José Miguel Gonçalves
2013-07-09 7:21 ` Arik Nemtsov
2013-07-09 9:09 ` Luciano Coelho
2013-07-09 9:33 ` José Miguel Gonçalves
2013-07-09 9:40 ` Luciano Coelho
2013-07-09 11:27 ` José Miguel Gonçalves
2013-07-09 12:42 ` Arik Nemtsov
2013-07-09 13:22 ` José Miguel Gonçalves
2013-07-09 19:10 ` Arik Nemtsov
2013-07-09 23:59 ` José Miguel Gonçalves [this message]
2013-07-10 9:22 ` Luciano Coelho
2013-07-10 12:34 ` José Miguel Gonçalves
2013-07-10 16:30 ` José Miguel Gonçalves
2013-07-10 17:17 ` Luciano Coelho
2013-07-10 17:48 ` José Miguel Gonçalves
2013-07-10 18:16 ` Larry Finger
2013-07-10 20:29 ` Luciano Coelho
2013-07-10 20:27 ` Luciano Coelho
2013-07-11 12:08 ` José Miguel Gonçalves
2013-07-11 13:29 ` Luciano Coelho
2013-07-11 13:33 ` José Miguel Gonçalves
2013-07-11 13:59 ` Luciano Coelho
2013-07-11 17:34 ` José Miguel Gonçalves
2013-07-11 18:26 ` José Miguel Gonçalves
2013-07-10 8:48 ` Luciano Coelho
2013-07-10 14:12 ` José Miguel Gonçalves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=51DCA3EF.8090900@inov.pt \
--to=jose.goncalves@inov.pt \
--cc=arik@wizery.com \
--cc=coelho@ti.com \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).