From: "Arend van Spriel" <arend@broadcom.com>
To: "Dan Williams" <dcbw@redhat.com>
Cc: "Arend van Spriel" <aspriel@gmail.com>, linux-wireless@vger.kernel.org
Subject: Re: NetworkManager not connecting anymore
Date: Mon, 30 Sep 2013 16:20:55 +0200 [thread overview]
Message-ID: <524988C7.1080903@broadcom.com> (raw)
In-Reply-To: <1380549653.6136.4.camel@dcbw.foobar.com>
On 09/30/13 16:00, Dan Williams wrote:
> 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
Hi Dan,
Thanks for explaining. 1) seems to be the issue. 'ps -ae | grep wpa' did
not return anything. I decided to remove and install wpa_supplicant.
Sometimes the helpdesk approach works ;-)
Regards,
Arend
prev parent reply other threads:[~2013-09-30 14:21 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
2013-09-30 14:20 ` Arend van Spriel [this message]
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=524988C7.1080903@broadcom.com \
--to=arend@broadcom.com \
--cc=aspriel@gmail.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 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).