Hi Cyril,
Thanks for replying
On Fri, Oct 26, 2012 at 7:38 AM, Cyril Lacoux wrote:
> I think you should not do that because this driver doesn't seem to be only for
> this chipset but an enhanced version of the broadcom-sta driver which support
> recent chipsets (see attached diff, in particular
Le mardi 23 octobre 2012 06:34:06, Jasmine Hassan a écrit :
Hi,
> When attempting to make an upstream tarball out of the dkms package,
> similar to the upstream tarball of broadcom-sta-5.100.82.112, I
> noticed the dkms pacakge only includes an x86_64 binary, so that
> cannot replace the current
Hi,
When attempting to make an upstream tarball out of the dkms package,
similar to the upstream tarball of broadcom-sta-5.100.82.112, I
noticed the dkms pacakge only includes an x86_64 binary, so that
cannot replace the current broadcom-sta package (which has an i386
binary). So, I must separatel
Sorry about that, and thanks for replying.
http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms/wireless-bcm43142-dkms_6.20.55.19_amd64.deb
On Fri, Oct 19, 2012 at 9:00 PM, Arend van Spriel wrote:
> On 10/19/2012 08:53 PM, Jasmine Hassan wrote:
>
>> Changed the long dell/oneiric
On 10/19/2012 08:53 PM, Jasmine Hassan wrote:
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
Gett
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 ma
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 lo
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 t
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
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.
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
Apparently the wireless-bcm43142-dkms/Makefile was tripping due to
missing $(SUBLEV
Package: broadcom-sta-dkms
Version: 6.20.55.19
Hello,
My newish Dell Inspiron 15R 5520 shipped with ubuntu installed, and
had this (apparently unreleased?) version of broadcom-sta-dkms, for
the bcm43142 (Dell hybrid wifi/bluetooth adapter / 14e4:4365)
# lspci -nn | tail -1
08:00.0 Network contro
12 matches
Mail list logo
