Changed the long dell/oneiric package version back to short version, and fixed lintian warnings about incorrect file ownership with recent dpkg versions.
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms_6.20.55.19_amd64.deb -- N.B.: I tried to contact the original package maintainer, "Hsin-Yi Chen (hychen)" <hyc...@canonical.com>, but the email bounced Delivery to the following recipient failed permanently: hyc...@canonical.com Technical details of permanent failure: Google tried to deliver your message, but it was rejected by the recipient domain. We recommend contacting the other email provider for further information about the cause of this error. The error that the other server returned was: 550 550 5.1.1 <hyc...@canonical.com>: Recipient address rejected: User unknown in virtual alias table (state 13). On Fri, Oct 19, 2012 at 6:22 PM, Jasmine Hassan <jasmine.a...@gmail.com>wrote: > Reposting updated link, as I'm getting emails about it. it's also > mentioned at the bottom of the homepage jas.gemnetworks.com :) > > http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms/wireless-bcm43142-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb > > Sorry about the long file name. forgot to rename dell's stupid > mile-long package name, and when re-importing in new repo, it got > renamed back to original name. > > Apparently broadcom's linux driver page is still stuck at 5.100.82.112 :p > http://www.broadcom.com/support/802.11/linux_sta.php > > Arend, > Anything you can do about the latter, at least? > > Thanks, > Jas > > On Mon, Oct 1, 2012 at 2:49 PM, Jasmine Hassan <jasmine.a...@gmail.com> > wrote: > > And because, the log you're referencing, begins with: > > > > # wpa_supplicant -d -Dnl80211,wext -ieth2 -u -s -O > /var/run/wpa_supplicant > > > > I obviously ran it with the same -D option used in functions.sh: > > nl80211,wext (in the same order). Pointless, of course, as I know that > > the wl.ko module loaded at the time was built with wext only. I guess > > I could've just as well ran with - > > > > On Mon, Oct 1, 2012 at 2:26 PM, Jasmine Hassan <jasmine.a...@gmail.com> > wrote: > >> Resend. Sorry, forgot to "reply all" on the last 2 emails > >> > >> because wpa_supplicant 1.0 (at least on LMDE/Debian testing) always > >> tries nl80211 first > >> # grep -i wext /etc/wpa_supplicant/* > >> /etc/wpa_supplicant/functions.sh:# -D driver backend ('wext' if none > given) > >> /etc/wpa_supplicant/functions.sh: > >> WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS > >> -D nl80211,wext" > >> /etc/wpa_supplicant/functions.sh: > >> wpa_msg stderr "using > >> \"nl80211,wext\" wpa-driver instead ..." > >> /etc/wpa_supplicant/functions.sh: > >> WPA_SUP_OPTIONS="$WPA_SUP_OPTIONS > >> -D nl80211,wext" > >> /etc/wpa_supplicant/functions.sh: wpa_msg verbose > "wpa-driver > >> nl80211,wext (default)" > >> > >> -- > >> > >> And to answer your other question, attached the complete snipped part > >> > >> -- > >> Jasmine > >> > >> On Mon, Oct 1, 2012 at 2:06 PM, Arend van Spriel <ar...@broadcom.com> > wrote: > >>> 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 > >>> > >>> >
