linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Christopher Williamson <home@chrisaw.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Problem connecting to wifi on libertas_cpio (sd8686)
Date: Wed, 20 Jul 2016 16:50:32 -0500	[thread overview]
Message-ID: <1469051432.3286.4.camel@redhat.com> (raw)
In-Reply-To: <CANXHH3minohF3z9bWc2NAghiU=w4DbsH1jU8iE8=v7H1pGdFcg@mail.gmail.com>

On Wed, 2016-07-20 at 13:06 -0700, Christopher Williamson wrote:
> Hi Dan,
> 
> Ah - yeah I hadn’t thought it may be a kernel build option. I’ve now
> built that and dmesg is a much more lively place!
> 
> I’ve provided output logs for both when the device is connected and
> when a connection attempt is made - hopefully this is useful.

<snip>

The card is scanning and only finds 'shaunthesheep' 20 seconds after
you "connect for the first time".  The logs stop 3 seconds later.  Are
you connecting with wicd or something else?

Can you run wpa_supplicant with the "-dddtu" option so we can get debug
log output from it?

Dan

  reply	other threads:[~2016-07-20 21:50 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-19 16:06 Problem connecting to wifi on libertas_cpio (sd8686) Christopher Williamson
2016-07-19 16:38 ` Dan Williams
2016-07-19 17:03   ` Christopher Williamson
2016-07-19 17:41     ` Christopher Williamson
2016-07-20  9:53       ` Christopher Williamson
2016-07-20 16:57         ` Dan Williams
2016-07-20 20:06           ` Christopher Williamson
2016-07-20 21:50             ` Dan Williams [this message]
2016-07-20 22:16               ` Christopher Williamson
2016-07-21 13:02                 ` Christopher Williamson
2016-07-21 15:37                 ` Dan Williams
2016-07-21 18:10                   ` Christopher Williamson
2016-07-21 18:55                     ` Christopher Williamson
2016-07-21 20:38                       ` Dan Williams
2016-07-21 21:00                         ` Christopher Williamson
2016-07-21 22:00                           ` Christopher Williamson
2016-07-22  8:09                             ` Arend Van Spriel
2016-07-22  8:21                               ` Christopher Williamson
2016-07-22  8:48                                 ` Christopher Williamson
2016-07-22 16:16                                   ` Dan Williams
2016-07-22 16:24                                     ` Christopher Williamson
2016-07-22 16:39                                       ` Christopher Williamson
2016-07-22 16:54                                         ` Christopher Williamson
2016-07-22 17:17                                           ` Christopher Williamson
     [not found]                                             ` <CANXHH3m2XEjkOfXGhtBUqCfu4Vix365fiRHzHL3DanoVzOsT3w@mail.gmail.com>
2016-07-22 21:47                                               ` Christopher Williamson
2016-07-23 12:29                                                 ` Christopher Williamson
2016-07-23 13:26                                                   ` Christopher Williamson
2016-07-25 16:17                                                     ` Dan Williams

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=1469051432.3286.4.camel@redhat.com \
    --to=dcbw@redhat.com \
    --cc=home@chrisaw.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).