From: "José Miguel Gonçalves" <jose.goncalves@inov.pt>
To: Luciano Coelho <coelho@ti.com>
Cc: Arik Nemtsov <arik@wizery.com>, linux-wireless@vger.kernel.org
Subject: Re: wl127x: Unable to associate with a WPA2-PSK AP
Date: Tue, 09 Jul 2013 12:27:05 +0100 [thread overview]
Message-ID: <51DBF389.5060209@inov.pt> (raw)
In-Reply-To: <1373362817.21065.191.camel@cumari.coelho.fi>
Hi,
I've upgraded the firmware and also backported all patches in Luca's
tree which do not break API compatibility in kernel 3.9 and still have
no success. Here goes the log:
[root ~]$ wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
[ 38.295000] wlcore: firmware booted (Rev 6.3.10.0.136)
[ 38.655000] cfg80211: Calling CRDA for country: PT
[ 38.655000] cfg80211: Regulatory domain changed to country: PT
[ 38.665000] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 38.665000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[ 38.675000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[ 38.675000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[ 38.685000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[ 38.685000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz),
(N/A, 4000 mBm)
wlan0: SME: Trying to authenticate with 88:43:e1:57:79:c0 (SSID='[
38.945000] wlan0: authenticate with 88:43:e1:57:79:c0
A. Guidance' freq=2452 MHz)
[ 38.985000] wlan0: send auth to 88:43:e1:57:79:c0 (try 1/3)
[ 38.990000] wlan0: authenticated
wlan0: Trying to associate with 88:43:e1:57:79:c0 (SSID='A. Guidance'
freq=2452 MHz)
[ 39.065000] wlan0: associate with 88:43:e1:57:79:c0 (try 1/3)
[ 39.070000] wlan0: RX AssocResp from 88:43:e1:57:79:c0 (capab=0x431
status=0 aid=1)
[ 39.095000] wlan0: associated
[ 39.095000] cfg80211: Calling CRDA for country: PT
[ 39.105000] cfg80211: Regulatory domain changed to country: PT
[ 39.105000] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp)
[ 39.110000] cfg80211: (2402000 KHz - 2482000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[ 39.125000] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[ 39.125000] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz),
(N/A, 2000 mBm)
[ 39.140000] cfg80211: (5490000 KHz - 5710000 KHz @ 40000 KHz),
(N/A, 2700 mBm)
[ 39.140000] cfg80211: (57240000 KHz - 65880000 KHz @ 2160000 KHz),
(N/A, 4000 mBm)
wlan0: Associated with 88:43:e1:57:79:c0
[ 40.925000] wlcore: Beacon loss detected. roles:0xff
[ 42.610000] wlcore: Beacon loss detected. roles:0xff
[ 44.275000] wlcore: Beacon loss detected. roles:0xff
[ 45.740000] wlcore: Connection loss work (role_id: 0).
[ 45.740000] wlan0: Connection to AP 88:43:e1:57:79:c0 lost
And I still have the issue of not being able to scan all APs in the
vicinity. I can only (briefly) associate with my AP because I restrict
the scanning frequencies in wpa_supplicant.conf file;
country=PT
ap_scan=1
ctrl_interface=/var/run/wpa_supplicant
network={
ssid="A. Guidance"
scan_freq=2452
key_mgmt=WPA-PSK
proto=WPA2
pairwise=CCMP TKIP
group=TKIP
psk="<some_password_in_ascii>"
}
Any more ideas on how to debug this? Is there any specific debug_level
mask that can apply to the driver to help it?
José Gonçalves
next prev parent reply other threads:[~2013-07-09 11:27 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 [this message]
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
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=51DBF389.5060209@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.