From: Pavel Roskin <proski@gnu.org>
To: Celejar <celejar@gmail.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Broadcom 4318 not working with bleeding edge kernels
Date: Wed, 21 Oct 2009 11:29:17 -0400 [thread overview]
Message-ID: <1256138957.26054.4.camel@mj> (raw)
In-Reply-To: <20091020214702.a76fa4aa.celejar@gmail.com>
On Tue, 2009-10-20 at 21:47 -0400, Celejar wrote:
> Oct 17 19:44:19 localhost wpa_supplicant[3477]: Trying to associate with 00:14:d1:3e:ff:30 (SSID='cranford' freq=2437 MHz)
> Oct 17 19:44:19 localhost wpa_supplicant[3477]: Association request to the driver failed
Since the message is from wpa_supplicant, it must be something between
wpa_supplicant and mac80211. I don't think any code in b43 is involved.
Perhaps you should include some information about wpa_supplicant, i.e.
its version and the command line. Please try the latest wpa_supplicant.
Please try both wext and nl80211 drivers. That would help understand
the extent of the problem.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-10-21 15:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 1:47 Broadcom 4318 not working with bleeding edge kernels Celejar
2009-10-21 15:29 ` Pavel Roskin [this message]
2009-10-21 21:34 ` Celejar
2009-10-21 22:37 ` Hin-Tak Leung
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=1256138957.26054.4.camel@mj \
--to=proski@gnu.org \
--cc=celejar@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.