All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Arend van Spriel <aspriel@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: NetworkManager not connecting anymore
Date: Mon, 30 Sep 2013 09:00:53 -0500	[thread overview]
Message-ID: <1380549653.6136.4.camel@dcbw.foobar.com> (raw)
In-Reply-To: <CAJ65rDzRUZcZG5+iz2TeQLW7YS+T5xD+M-BxpJp23N=W4dn1+g@mail.gmail.com>

On Sun, 2013-09-29 at 11:11 +0200, Arend van Spriel wrote:
> With a recent update on my Ubuntu 12.10 laptop, wireless connection is no
> longer working with NetworkManager. It is working when using wpa_supplicant
> directly. The nm-applet indicates 'device not ready' for the Wireless
> Networks. Attached is the syslog upon inserting the wireless driver module,
> which is brcmsmac. Not sure if the state change below correlates to the
> nm-applet status.
> 
> NetworkManager[1121]: <info> (wlan0): device state change: unmanaged ->
> unavailable (reason 'managed') [10 20 2]

'unavailable' could mean a couple things:

1) supplicant isn't running or can't be contacted via D-Bus
2) rfkill is blocking wifi
3) the driver returned ENOENT in response to the dev_open() call,
indicating that it does not have any firmware available

The logs you've posted don't look complete; do you get *anything* else
shown?  You can also:

killall -TERM NetworkManager
NetworkManager --no-daemon --log-level=debug

to get more information.

Let me know,
Dan


  parent reply	other threads:[~2013-09-30 13:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJ65rDzRUZcZG5+iz2TeQLW7YS+T5xD+M-BxpJp23N=W4dn1+g@mail.gmail.com>
2013-09-30  8:31 ` Fwd: NetworkManager not connecting anymore Arend van Spriel
2013-09-30 14:00 ` Dan Williams [this message]
2013-09-30 14:20   ` Arend van Spriel

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=1380549653.6136.4.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=aspriel@gmail.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.