Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
Hi Cyril, Thanks for replying On Fri, Oct 26, 2012 at 7:38 AM, Cyril Lacoux clac...@easter-eggs.com 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 wl_id_table declaration). Yes, I sure have noticed, because I wanted to update the readme file of original broadcom-wl when repacking a tarball. It's funny how even PCI_VENDOR_ID_BROADCOM was replaced with PCI_ANY_ID. I'll be pleased to upload the new version of the broadcom-sta driver when it's released (including i386 binary). Unfortunately, I doubt that will happen anytime soon, if at all. After failing to get any reply from broadcom linux-sta driver support, I contacted brcm80211 developers to ask if the linux-sta driver page could be updated with a tarball release of this driver, and an attempt to answer my request was simply: This driver version was a Dell-specific release, which they can redistribute. However, 5.100.82.112 on our internet page is our latest generic release. Anyway this can't be done before Wheezy release. Nods. I keep forgetting about the freeze period. Thanks a bunch. Cheers, -- Cyril Lacoux Cheers, Jasmine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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 broadcom-sta package (which has an i386 binary). So, I must separately maintain this amd64 driver for bcm43142, on private repo, at least temporarily. Should I open an ITP? 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 wl_id_table declaration). I'll be pleased to upload the new version of the broadcom-sta driver when it's released (including i386 binary). Anyway this can't be done before Wheezy release. Cheers, -- Cyril Lacoux --- amd64.orig/src/wl/sys/wl_linux.c 2012-05-24 10:48:28.0 +0400 +++ amd64/src/wl/sys/wl_linux.c 2012-10-23 05:24:43.0 +0400 @@ -2,15 +2,21 @@ * Linux-specific portion of * Broadcom 802.11abg Networking Device Driver * - * Copyright (C) 2010, Broadcom Corporation - * All Rights Reserved. + * Copyright (C) 2011, Broadcom Corporation. All Rights Reserved. * - * THIS SOFTWARE IS OFFERED AS IS, AND BROADCOM GRANTS NO WARRANTIES OF ANY - * KIND, EXPRESS OR IMPLIED, BY STATUTE, COMMUNICATION OR OTHERWISE. BROADCOM - * SPECIFICALLY DISCLAIMS ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS - * FOR A SPECIFIC PURPOSE OR NONINFRINGEMENT CONCERNING THIS SOFTWARE. + * Permission to use, copy, modify, and/or distribute this software for any + * purpose with or without fee is hereby granted, provided that the above + * copyright notice and this permission notice appear in all copies. + * + * THE SOFTWARE IS PROVIDED AS IS AND THE AUTHOR DISCLAIMS ALL WARRANTIES + * WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF + * MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY + * SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES + * WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION + * OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN + * CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. * - * $Id: wl_linux.c,v 1.524.2.40.2.15 2011-02-09 02:28:28 Exp $ + * $Id: wl_linux.c 280943 2011-08-31 21:37:04Z $ */ #define LINUX_PORT @@ -37,6 +43,7 @@ #include linux/string.h #include linux/ethtool.h #include linux/completion.h +#include linux/usb.h #include linux/pci_ids.h #define WLC_MAXBSSCFG 1 @@ -57,7 +64,7 @@ #include wlioctl.h #include wlc_key.h -typedef const struct si_pub si_t; +typedef const struct si_pub si_t; #if LINUX_VERSION_CODE = KERNEL_VERSION(2, 4, 5) #error No support for Kernel Rev = 2.4.5, As the older kernel revs doesn't support Tasklets @@ -77,10 +84,6 @@ #include wl_linux.h -#ifdef WL_THREAD -#include linux/kthread.h -#endif - #if defined(USE_CFG80211) #include wl_cfg80211.h #endif @@ -90,20 +93,6 @@ static int wl_monitor_start(struct sk_buff *skb, struct net_device *dev); -#ifdef WL_ALL_PASSIVE -static void wl_start_txqwork(struct wl_task *task); -static void wl_txq_free(wl_info_t *wl); -#define TXQ_LOCK(_wl) spin_lock_bh((_wl)-txq_lock) -#define TXQ_UNLOCK(_wl) spin_unlock_bh((_wl)-txq_lock) - -static void wl_set_multicast_list_workitem(struct work_struct *work); - -static void wl_timer_task(wl_task_t *task); -static void wl_dpc_rxwork(struct wl_task *task); -#else - -#endif - static int wl_reg_proc_entry(wl_info_t *wl); static int wl_linux_watchdog(void *ctx); @@ -139,15 +128,11 @@ u8 rx_hdr[16], tx_hdr[16]; }; -#define WL_INFO(dev) ((wl_info_t*)(WL_DEV_IF(dev)-wl)) +#define WL_INFO(dev) ((wl_info_t*)(WL_DEV_IF(dev)-wl)) static int wl_open(struct net_device *dev); static int wl_close(struct net_device *dev); -#ifdef WL_THREAD -static int wl_start_wlthread(struct sk_buff *skb, struct net_device *dev); -#else static int BCMFASTPATH wl_start(struct sk_buff *skb, struct net_device *dev); -#endif static int wl_start_int(wl_info_t *wl, wl_if_t *wlif, struct sk_buff *skb); static struct net_device_stats *wl_get_stats(struct net_device *dev); @@ -155,24 +140,13 @@ static void wl_set_multicast_list(struct net_device *dev); static void _wl_set_multicast_list(struct net_device *dev); static int wl_ethtool(wl_info_t *wl, void *uaddr, wl_if_t *wlif); -#ifdef NAPI_POLL -#if LINUX_VERSION_CODE = KERNEL_VERSION(2, 6, 30) -static int wl_poll(struct napi_struct *napi, int budget); -#else -static int wl_poll(struct net_device *dev, int *budget); -#endif -#else static void wl_dpc(ulong data); -#endif static void wl_link_up(wl_info_t *wl, char * ifname); static void wl_link_down(wl_info_t *wl, char *ifname); static int wl_schedule_task(wl_info_t *wl, void (*fn)(struct wl_task *), void *context); -#ifdef WL_THREAD -static int
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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 separately maintain this amd64 driver for bcm43142, on private repo, at least temporarily. Should I open an ITP? First release (6.20.55.19-1) supporting all kernels 2.6.x up to and including 3.6.x - known issue: limited scan results on 3.6 compared to results on any previous kernel. personally tested on 3.2, 3.4, 3.5, and 3.6 - debian packaging based on that of broadcom-sta's, maintaining copyright file - all changes are logged in changelog, building on changelog of the dkms oneiric package found on dells. from changelog, for debian/patches: - Make all patches compliant with dep3 format. - Add 01-Makefile: Use cfg80211 on 3.x kernels, require amd64, cleanup - Sync 02-license: Attribute Dan Baumann, update patch for 6.20.55.19 - Sync 03-rename-to-wlan0: Attribute Cyril Lacoux, refresh patch - Add 04-linux-semaphore-include: patch all three headers that declare semaphore structure and use semaphore functions (wl_iw.h, wl_linux.h, and wl_cfg80211.h). See patch header for more details - Rename 06-3.2.0 to 05-kernel_3.1_onwards.patch: Refresh, and update the check to = 3.1.0, because this is when ndo_set_multicast_list was actually dropped, and not in 3.2.0 - Import 06-user_ioctl_reqs.patch with relevant code from #672677, attribute Cyril Lacoux, and simplify rssi error handling return - Add 07-kernel_3.4_onwards: include asm/system.h iff kernel 3.4 - Add 08-kernel_3.6_onwards: nl80211: move scan API to wdev Through apt = 1. add key: wget http://jas.gemnetworks.com/jasmineaura.gpg.key -O- | sudo apt-key add - 2. add to apt sources: # /etc/apt/sources.list.d/wireless-bcm43142.list deb http://jas.gemnetworks.com/debian debian main deb-src http://jas.gemnetworks.com/debian debian main 3. install # apt-get install wireless-bcm43142-dkms or get source: # apt-get source wireless-bcm43142-dkms Directly == browse to http://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142/ for dkms package: wireless-bcm43142-dkms_6.20.55.19-1_amd64.deb 23-Oct-2012 01:44 1.3M Imitation of a clean upstream source: wireless-bcm43142_6.20.55.19.orig.tar.bz2 23-Oct-2012 01:45 1.1M debian packaging (including patches) wireless-bcm43142_6.20.55.19-1.debian.tar.gz 23-Oct-2012 01:44 12K Best, Jasmine -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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='xxx' 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
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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.comwrote:
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='xxx' 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
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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 Getting 404 HTTP error on this link. Gr. AvS -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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 ar...@broadcom.comwrote: 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.debhttp://jas.gemnetworks.com/debian/pool/main/w/wireless-bcm43142-dkms_6.20.55.19_amd64.deb Getting 404 HTTP error on this link. Gr. AvS
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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='xxx' 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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='xxx' 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
Sep 25 21:34:10 terra kernel: [ 18.223028] NET: Registered protocol family 17
Sep 25 21:34:10 terra NetworkManager[2750]: info (eth2): supplicant interface
state: starting - ready
Sep 25 21:34:10 terra NetworkManager[2750]: info (eth2): device state change:
unavailable - disconnected (reason 'supplicant-available') [20 30 42]
Sep 25 21:34:10 terra NetworkManager[2750]: info (eth2): supplicant interface
state: ready - inactive
Sep 25 21:34:10 terra NetworkManager[2750]: warn Trying to remove a
non-existant call id.
Sep 25 21:34:10 terra acpid: client connected from 2811[0:0]
Sep 25 21:34:10 terra acpid: 1 client rule loaded
Sep 25 21:34:11 terra laptop-mode: enabled, not active
Sep 25 21:34:12 terra kernel: [ 20.272321] radeon: switched off
Sep 25 21:34:12 terra kernel: [ 20.716266] elevator: type bfq not found
Sep 25 21:34:12 terra kernel: [ 20.716270] elevator: switch to bfq
Sep 25 21:34:12 terra kernel: [ 20.716270] failed
Sep 25 21:34:23 terra dbus[2635]: [system] Activating service
name='org.freedesktop.ConsoleKit' (using servicehelper)
Sep 25 21:34:23 terra dbus[2635]: [system] Successfully activated service
'org.freedesktop.ConsoleKit'
Sep 25 21:34:28 terra dbus[2635]: [system] Activating service
name='org.freedesktop.UDisks' (using servicehelper)
Sep 25 21:34:28 terra dbus[2635]: [system] Successfully activated service
'org.freedesktop.UDisks'
Sep 25 21:34:29 terra pulseaudio[3688]: [pulseaudio] pid.c: Daemon already
running.
Sep 25 21:34:30 terra dbus[2635]: [system] Activating service
name='org.freedesktop.UPower' (using servicehelper)
Sep 25 21:34:30 terra dbus[2635]: [system] Successfully activated service
'org.freedesktop.UPower'
Sep 25 21:34:30 terra NetworkManager[2750]: info Auto-activating connection
'xxx'.
Sep 25 21:34:30 terra NetworkManager[2750]: info Activation (eth2) starting
connection 'xxx'
Sep 25 21:34:30 terra NetworkManager[2750]: info (eth2): device state change:
disconnected - prepare (reason 'none') [30 40 0]
Sep 25 21:34:30 terra NetworkManager[2750]: info Activation (eth2) Stage 1 of
5 (Device Prepare) scheduled...
Sep 25 21:34:30 terra NetworkManager[2750]: info Activation (eth2) Stage 1 of
5 (Device Prepare) started...
Sep 25 21:34:30 terra NetworkManager[2750]: info Activation (eth2) Stage 2 of
5 (Device Configure) scheduled...
Sep 25 21:34:30 terra NetworkManager[2750]: info Activation (eth2) Stage 1 of
5 (Device Prepare) complete.
Sep 25 21:34:30 terra NetworkManager[2750]: info Activation (eth2) Stage 2 of
5 (Device Configure) starting...
Sep 25 21:34:30 terra NetworkManager[2750]: info (eth2): device state change:
prepare - config (reason 'none') [40 50 0]
Sep 25 21:34:30
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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='xxx' 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
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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 $(SUBLEVEL) in /lib/modules/3.6-rc7.towo.1-siduction-amd64/build/Makefile --- # make KERNELRELEASE=3.6-rc7.towo.1-siduction-amd64 -C /lib/modules/3.6-rc7.towo.1-siduction-amd64/build M=`pwd` make: Entering directory `/usr/src/linux-headers-3.6-rc7.towo.1-siduction-amd64' /bin/sh: 1: [: Illegal number: /bin/sh: 1: [: Illegal number: Wireless Extension is the only possible API for this kernel version Using Wireless Extension API ... --- So it was building the wl module with WEXT rather than nl/CFG80211, which is undesirable of course for such a recent (and 3.x) kernel. It is actually now deprecated. See: http://git.kernel.org/linus/10bab00afed042c1a38ed5ffb135e2aea5ce1277 And as the Makefile checks for API variable, this could be mitigated by adding API=CFG80211 to the make command, and though the Makefile still tries to check for SUBLEVEL and trips, it still builds with CFG80211, as desired: --- # make API=CFG80211 KERNELRELEASE=3.6-rc7.towo.1-siduction-amd64 -C /lib/modules/3.6-rc7.towo.1-siduction-amd64/build M=`pwd` make: Entering directory `/usr/src/linux-headers-3.6-rc7.towo.1-siduction-amd64' /bin/sh: 1: [: Illegal number: /bin/sh: 1: [: Illegal number: CFG80211 API specified in command line Using CFG80211 API ... --- But this defeats the whole point of using a DKMS package in the first place, and Dell/Broadcom hasn't provided a source-only package for this version. The submitted dkms package is obviously missing readme and license files, at least. So I was able to get around this mess by creating a secondary patch for the Makefile (there's a preexisting 0001-Makefile.patch) and placing it in: /usr/src/wireless-bcm43142-dkms-6.20.55.19~bdcom0602.0400.1000.0400/patches/0002-Makefile.patch Patch Attached. Edit the dkms.conf file, and add my new patch under the PATCH[0] line: PATCH[1]=0002-Makefile.patch Then dkms remove and dkms install the module for the 3.6-rc7 kernel. Now wl.ko is built with nl/cfg80211 However, now I hit a kernel BUG at include/net/cfg80211.h:2473 caused by wpa_supplicant # apt policy wpasupplicant wpasupplicant: Installed: 1.0-2 Candidate: 1.0-2 Version table: *** 1.0-2 0 500 http://mirror.rts-informatique.fr/linuxmint/debian/incoming/ testing/main amd64 Packages 100 /var/lib/dpkg/status Details of running wpa_supplicant (1.0-2) in debugging mode when wl.ko was built with WEXT, and the kernel BUG details re wpa_supplicant. As this is a dev kernel release, adding linux-wireless to the loop. And apologies if I shouldn't because this is regarding a proprietary, unpublished broadcom driver. Please let me know if you need any further information. Best, Jasmine On Wed, Sep 26, 2012 at 12:42 AM, Jasmine Hassan jasmine.a...@gmail.com wrote: 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 controller [0280]: Broadcom Corporation Device [14e4:4365] (rev 01) # dmesg | grep BCM eth0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.20.55.19 (r300276) Someone (owner of Vostro 3460 laptop with the same card) kindly uploaded the original debs, at http://wielki.tk/vostro/ The driver in question: http://wielki.tk/vostro/debs/wireless-bcm43142-oneiric-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb But it had at least two main issues that needed fixing: 1. Failed to compile on kernel 3.2.x. Solution: One-line change of the call 'ndo_set_multicast_list' to 'ndo_set_rx_mode', in wl_linux.c 2. Failed to compile on Kernel 3.4.x. Like broadcom-sta/5.100.82.112-7 , this version also suffered issue with missing asm/system.h on 3.4.x (see bug #677193). Fixed in the same manner as that proposed in said bug. (Updated md5sum of wl_linux.c, per changes 1 2 above) 3. Removed oneiric (reference to Ubuntu 11.10) from package name, and all directory path-names everywhere in the package contents, as it is no longer ubuntu/oneiric-specific. 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
Bug#688823: broadcom-sta-dkms: to version = 6.20.55.19 (r300276)
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 controller [0280]: Broadcom Corporation Device [14e4:4365] (rev 01) # dmesg | grep BCM eth0: Broadcom BCM4365 802.11 Hybrid Wireless Controller 6.20.55.19 (r300276) Someone (owner of Vostro 3460 laptop with the same card) kindly uploaded the original debs, at http://wielki.tk/vostro/ The driver in question: http://wielki.tk/vostro/debs/wireless-bcm43142-oneiric-dkms_6.20.55.19~bdcom0602.0400.1000.0400-0somerville1_amd64.deb But it had at least two main issues that needed fixing: 1. Failed to compile on kernel 3.2.x. Solution: One-line change of the call 'ndo_set_multicast_list' to 'ndo_set_rx_mode', in wl_linux.c 2. Failed to compile on Kernel 3.4.x. Like broadcom-sta/5.100.82.112-7 , this version also suffered issue with missing asm/system.h on 3.4.x (see bug #677193). Fixed in the same manner as that proposed in said bug. (Updated md5sum of wl_linux.c, per changes 1 2 above) 3. Removed oneiric (reference to Ubuntu 11.10) from package name, and all directory path-names everywhere in the package contents, as it is no longer ubuntu/oneiric-specific. 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] Sep 25 21:34:31 terra wpa_supplicant[2787]: eth2: Trying to associate with 00:xx:xx:xx:xx:xx (SSID='xxx' 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 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
