All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christopher Williamson <home@chrisaw.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Dan Williams <dcbw@redhat.com>
Subject: Re: Problem connecting to wifi on libertas_cpio (sd8686)
Date: Wed, 20 Jul 2016 02:53:32 -0700	[thread overview]
Message-ID: <CANXHH3k3wSYYc2xS1rk9JqeWmekC+79YCYshMcXA-yz4rX_+Hw@mail.gmail.com> (raw)
In-Reply-To: <CANXHH3k4x1QWY9H4n=hDeLmVMxdi4HOuVxHTv1ztX0AhZF7B-Q@mail.gmail.com>

Just following up from my previous email:

I am actually setting the reg domain using: iw reg set GB (copy/pasted
the IN from elsewhere - oops!)

As for progress, however, I have tried the following:

- setting the debug level to 0xfffffff. This still produces no
additional output even with 8 set in printk.

- removing the v9 firmware - same result as before - system fully locks up.

- disabling ipv6 - gets rid of IPv6 interface not up warning but
that’s not causing any problems and this didn’t make any difference.

It doesn’t seem to matter what I try at the moment - all attempts to
connect result in the system crashing which I guess is better than it
just asking me for a password over and over - it looks like it is
attempting association at this point which is good but I don’t know
why the box is crashing out and dmesg -w doesn’t show any additional
output before the freeze.

If anyone has any more ideas I would be more than happy to try them!
Thanks for the help so far Dan!

Christopher Williamson

On 19 July 2016 at 18:41:34, Christopher Williamson
(home@chrisaw.com(mailto:home@chrisaw.com)) wrote:

> So I’ve now disabled IPv6 and have set the GB (Great Britain) regulation code using:
>
> iw reg set IN
>
> Now when I try to connect to the network using wicd the system seems to crash - I guess at least it’s doing something more than just asking for the password again like it did with NetworkManager but so far no further progress on getting this working properly.
>
> Christopher Williamson
>
>
>
> On 19 July 2016 at 18:03:16, Christopher Williamson (home@chrisaw.com(mailto:home@chrisaw.com)) wrote:
>
> > Absolutely!
> >
> > With the debug logging enabled I got the following:
> >
> > Connecting the device initially with debug enabled:
> >
> > [ 205.302685] libertas_sdio: Libertas SDIO driver
> > [ 205.302698] libertas_sdio: Copyright Pierre Ossman
> > [ 205.503465] cfg80211: World regulatory domain updated:
> > [ 205.503478] cfg80211: DFS Master region: unset
> > [ 205.503483] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time)
> > [ 205.503492] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
> > [ 205.503499] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A, 2000 mBm), (N/A)
> > [ 205.503505] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A, 2000 mBm), (N/A)
> > [ 205.503513] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (N/A)
> > [ 205.503522] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000 KHz AUTO), (N/A, 2000 mBm), (0 s)
> > [ 205.503529] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A, 2000 mBm), (0 s)
> > [ 205.503535] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A, 2000 mBm), (N/A)
> > [ 205.503542] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 0 mBm), (N/A)
> > [ 212.249171] gma500 0000:00:02.0: Backlight lvds set brightness 7a127a12
> > [ 212.324898] mmc1: new SDIO card at address 0001
> > [ 212.921672] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): 00:02:78:69:49:94, fw 9.70.20p0, cap 0x00000303
> > [ 212.925774] libertas_sdio mmc1:0001:1 (unnamed net_device) (uninitialized): PREP_CMD: command 0x00a3 failed: 2
> > [ 212.936190] libertas_sdio mmc1:0001:1 wlan0: Marvell WLAN 802.11 adapter
> > [ 213.053612] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> >
> >
> > Strangely when I attempt to connect to the WiFi network I’m using the only error I get is:
> >
> > [ 338.076632] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
> >
> > I was expecting more output and am guessing I’ve missed something here.
> >
> > Christopher Williamson
> >
> > On 19 July 2016 at 17:38:35, Dan Williams (dcbw@redhat.com(mailto:dcbw@redhat.com)) wrote:
> >
> > > On Tue, 2016-07-19 at 12:06 -0400, Christopher Williamson wrote:
> > > > Hi everyone!
> > > >
> > > > I’ve just got myself a Viliv N5 and am trying to get the integrated
> > > > Wifi chipset working on it.
> > > >
> > > > I am able to see networks around me but any attempts to connect them
> > > > appear to time out and fail.
> > > >
> > > > I have filed a linux kernel bug related to this issue:
> > > > https://bugzilla.kernel.org/show_bug.cgi?id=135421goo
> > > >
> > > > I figured here may be a good place to ask about it and hopefully to
> > > > get to the bottom of why it happens and how I can help to fix it.
> > > >
> > > > Happy to provide any information which may be helpful! :)
> > >
> > > Can you reload the driver stack:
> > >
> > > rmmod libertas_sdio
> > > rmmod libertas
> > > modprobe libertas libertas_debug=0x251e7ff
> > > modprobe libertas_sdio
> > >
> > > and then reproduce the issue? The debug info should dump to 'dmesg'
> > > and may tell us what's going on.
> > >
> > > Dan

  reply	other threads:[~2016-07-20  9:53 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 [this message]
2016-07-20 16:57         ` Dan Williams
2016-07-20 20:06           ` Christopher Williamson
2016-07-20 21:50             ` Dan Williams
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=CANXHH3k3wSYYc2xS1rk9JqeWmekC+79YCYshMcXA-yz4rX_+Hw@mail.gmail.com \
    --to=home@chrisaw.com \
    --cc=dcbw@redhat.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.