From: Dan Williams <dcbw@redhat.com>
To: Roland Vossen <rvossen@broadcom.com>
Cc: Camaleón <noelamac@gmail.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
"Brett Rudley" <brudley@broadcom.com>,
"Henry Ptasinski" <henryp@broadcom.com>,
"Arend Van Spriel" <arend@broadcom.com>,
networkmanager-list@gnome.org
Subject: Re: brcmsmac driver only works when sitting next to the AP
Date: Tue, 16 Aug 2011 10:40:10 -0500 [thread overview]
Message-ID: <1313509211.2065.36.camel@dcbw.foobar.com> (raw)
In-Reply-To: <4E4A5641.4020604@broadcom.com>
On Tue, 2011-08-16 at 13:36 +0200, Roland Vossen wrote:
> Hello Camaleón,
>
> So the first problem that you encounter is that scan does not work. Lets
> dive into that first.
>
> I see in the log that you sent:
>
> 'Aug 14 13:39:02 stt300 NetworkManager[1181]:
> supplicant_interface_acquire: assertion `mgr_state ==
> NM_SUPPLICANT_MANAGER_STATE_IDLE' failed'
>
> I also see many 'wpa_supplicant[1204]: Failed to initiate AP scan' messages.
>
> There are no 'Failed to initiate AP scan' messages before the 'assertion
> failed' message. I do not know if the 2nd message is a byproduct of the
> 1st result. Regardless, a failed assertion is serious. I cc'ed the
> network manager mailing list.
Yeah, the scanning issues are almost certainly what's causing stuff to
fail; which obviously seems like a driver issue at this point.
Dan
next prev parent reply other threads:[~2011-08-16 15:37 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-14 12:16 brcmsmac driver only works when sitting next to the AP Camaleón
2011-08-16 11:36 ` Roland Vossen
2011-08-16 15:40 ` Dan Williams [this message]
2011-08-17 10:39 ` Roland Vossen
2011-08-18 8:07 ` Roland Vossen
2011-08-19 14:32 ` Roland Vossen
2011-08-19 15:21 ` Camaleón
2011-08-21 21:43 ` Camaleón
2011-08-22 10:03 ` Roland Vossen
2011-08-22 11:27 ` Camaleón
2011-08-22 12:57 ` Roland Vossen
2011-08-22 13:28 ` Camaleón
2011-08-22 13:55 ` Roland Vossen
2011-08-22 14:27 ` Camaleón
2011-08-23 8:41 ` Roland Vossen
2011-08-23 8:59 ` Camaleón
2011-08-23 9:27 ` Roland Vossen
2011-08-23 9:53 ` Camaleón
2011-08-23 10:38 ` Roland Vossen
2011-08-23 10:53 ` Camaleón
2011-08-23 11:23 ` Roland Vossen
2011-08-23 14:06 ` Camaleón
2011-08-23 14:18 ` Roland Vossen
2011-08-23 14:48 ` Camaleón
2011-08-23 14:58 ` Roland Vossen
2011-08-23 15:27 ` Camaleón
2011-08-23 17:37 ` Roland Vossen
2011-08-23 18:01 ` Camaleón
2011-08-22 14:15 ` Roland Vossen
2011-08-22 14:28 ` Camaleón
2011-08-22 16:37 ` Dan Williams
2011-08-19 20:47 ` Dan Williams
2011-08-22 6:52 ` Roland Vossen
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=1313509211.2065.36.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=devel@driverdev.osuosl.org \
--cc=henryp@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=networkmanager-list@gnome.org \
--cc=noelamac@gmail.com \
--cc=rvossen@broadcom.com \
/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.