From: "Arend van Spriel" <arend@broadcom.com>
To: "Jasmine Hassan" <jasmine.aura@gmail.com>
Cc: 688823@bugs.debian.org, linux-wireless@vger.kernel.org
Subject: Re: broadcom-sta-dkms: to version >= 6.20.55.19 (r300276)
Date: Mon, 1 Oct 2012 14:06:05 +0200 [thread overview]
Message-ID: <5069872D.4050607@broadcom.com> (raw)
In-Reply-To: <CAHbMyCYW3qW8R4VV4jGimaqYQHMRd8aeV8GU6Uu5CYNcWVch5Q@mail.gmail.com>
On 09/27/2012 04:24 PM, Jasmine Hassan wrote:
> Update on 3.6-rc7 problems with wpasupplicant-1.0-2 and broadcom-sta
> 6.20.55.19 (r300276)
> 1. Fails to associate to AP (WPA encryption used) when wl.ko built with wext
> 2. Kernel bug when wl.ko built with nl/cfg80211
Commenting on issue 1 only, here.
>> Updated deb: http://jas.gemnetworks.com/debian/wireless-bcm43142-dkms-6.20.55.19_amd64.deb
>>
>> Also tested on linux 3.5.0-4.dmz.1-liquorix-amd64, and it works for me
>>
>> Now, given a power regression in kernel 3.5, I was eager to test drive
>> 3.6-rc6, and found rc7 out already!
>> So yesterday I installed linux 3.6-rc7.towo.1-siduction-amd64, the
>> "wl" module compiles and installs, and loads okay upon boot to
>> 3.6-rc7. However, I'm unable to associate to my AP:
>>
>> Pointers in syslog
>> Sep 25 21:34:10 terra wpa_supplicant[2787]: nl80211: 'nl80211' generic
>> netlink not found
>> Sep 25 21:34:10 terra wpa_supplicant[2787]: Failed to initialize
>> driver 'nl80211'
>> [..snip]
Not sure what is snipped here. Your wpa_supplicant seems to try nl80211.
Maybe it goes and try WEXT instead, but that is missing from the log. Do
you recall or still have the entire syslog?
>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate
>> with 00:xx:xx:xx:xx:xx (SSID='xxxxxxx' freq=2452 MHz)
>> Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Association request
>> to the driver failed
>>
>> As bcm43142 is fairly new, this proprietary driver is all that's there
>> to support it. Sad face.
>>
>> Cheers,
>> Jasmine
Gr. AvS
next prev parent reply other threads:[~2012-10-01 12:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHbMyCZ0YU5Jim9kBaBNxmp946ZJfJyNf6f4HNEm8Eti9gO9QA@mail.gmail.com>
2012-09-27 14:24 ` broadcom-sta-dkms: to version >= 6.20.55.19 (r300276) Jasmine Hassan
2012-10-01 12:06 ` Arend van Spriel [this message]
2012-10-01 12:26 ` Jasmine Hassan
2012-10-01 12:49 ` Jasmine Hassan
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=5069872D.4050607@broadcom.com \
--to=arend@broadcom.com \
--cc=688823@bugs.debian.org \
--cc=jasmine.aura@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.