From: Hin-Tak Leung <hintak.leung@gmail.com>
To: Celejar <celejar@gmail.com>
Cc: Pavel Roskin <proski@gnu.org>, linux-wireless@vger.kernel.org
Subject: Re: Broadcom 4318 not working with bleeding edge kernels
Date: Wed, 21 Oct 2009 23:37:49 +0100 [thread overview]
Message-ID: <3ace41890910211537q34c0cc93r8a9ae4f8d511b3f0@mail.gmail.com> (raw)
In-Reply-To: <20091021173449.0a3ec80f.celejar@gmail.com>
On Wed, Oct 21, 2009 at 10:34 PM, Celejar <celejar@gmail.com> wrote:
> On Wed, 21 Oct 2009 11:29:17 -0400
> Pavel Roskin <proski@gnu.org> wrote:
>
>> 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.
>
> Version is 0.6.9, from the Debian package version 0.6.9.3. I don't
> know the exact command line, since I've been invoking it through the
> Debian ifupdown scripts. I haven't been specifying a backend, and the
> Debian documentation states that wext is used in that case.
'ps -lax -w -w' should show the full command line of currently running
processes. Read the documentation of ps.
also, have a look inside /var/log/wpa_supplicant.log (or wherever
Debian puts it) for the log.
> I have been playing with it some more, and it sometimes works, and
> sometimes doesn't. The only absolutely consistent pattern that I've
> seen is that (in my limited testing) it seems to always work right
> after unloading / reloading the driver (b43) (or a fresh boot).
>
> As I mentioned, I've been using the Debian ifupdown scripts. I have
> now tried running wpa_supplicant directly, and so far it has worked
> consistently, with a very minimal, mostly default config:
>
> 'wpa_supplicant -iwlan0 -c/wpa.conf'
>
> where wpa.conf contains:
>
> ctrl_interface=/var/run/wpa_supplicant
>
> network={
> ssid="my-ssid"
> psk="my passphrase"
> }
>
>
> So at this point, I guess the problem is something that I need to
> report to Debian, some sort of bugginess with their scripts. Thanks
> for the help ;)
>
> Celejar
> --
> mailmin.sourceforge.net - remote access via secure (OpenPGP) email
> ssuds.sourceforge.net - A Simple Sudoku Solver and Generator
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2009-10-21 22:43 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
2009-10-21 21:34 ` Celejar
2009-10-21 22:37 ` Hin-Tak Leung [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=3ace41890910211537q34c0cc93r8a9ae4f8d511b3f0@mail.gmail.com \
--to=hintak.leung@gmail.com \
--cc=celejar@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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