linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 09 Jul 2013 14:22:04 +0100	[thread overview]
Message-ID: <51DC0E7C.9080306@inov.pt> (raw)
In-Reply-To: <CA+XVXfeB3jpXaaV4vgbHUVRdPeH9tPVRWvRhZsYHmg33HNzmmw@mail.gmail.com>

On 09-07-2013 13:42, Arik Nemtsov wrote:
> On Tue, Jul 9, 2013 at 2:27 PM, José Miguel Gonçalves
> <jose.goncalves@inov.pt> wrote:
>
>> Any more ideas on how to debug this? Is there any specific debug_level mask
>> that can apply to the driver to help it?
> You can try the mask 0x63c20 (it's pretty verbose, so I would put it
> in pastebin).
>
> Perhaps this is a genuine problem with the antenna of the card?

Nope. The AP is 1 meter away form my board (even without antenna in the 
card it should associate).

> Can
> you verify the RSSI of the AP is ok using iw?

The iw output:

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.

José Gonçalves

  reply	other threads:[~2013-07-09 13:22 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 [this message]
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=51DC0E7C.9080306@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).