Re: Enabling CONFIG_DEBUG_SLAB breakes b43 module
On Monday 11 February 2008 13:22:14 Jörg Sommer wrote: Hi, I'm using the b43 driver to connect to a WPA2 encrypted WLAN. When I enable the kernel option CONFIG_DEBUG_SLAB my connection breaks. wpa_supplicant can establish the connection and I can make pings or DNS queries, but downloading a file kills the connection. So ehm. Disable DEBUG_SLAB? -- Greetings Michael. ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems b43 driver and bcm4318
Please disregard my previous message. I just now saw the thread [bcm4318 problem on HP nx6110] where I foud the cause to my problem: I downloaded the wrong firmware version. Thanks for making this drivers available. jorges ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
b43legacy: fix firmware load message level
The firmware version information should always get printed. Not only on a debug build. The patch by Michael Buesch has been ported to b43legacy. Signed-off-by: Stefano Brivio [EMAIL PROTECTED] --- Index: wireless-2.6/drivers/net/wireless/b43legacy/main.c === --- wireless-2.6.orig/drivers/net/wireless/b43legacy/main.c +++ wireless-2.6/drivers/net/wireless/b43legacy/main.c @@ -1670,10 +1670,11 @@ static int b43legacy_upload_microcode(st err = -EOPNOTSUPP; goto error; } - b43legacydbg(dev-wl, Loading firmware version 0x%X, patch level %u - (20%.2i-%.2i-%.2i %.2i:%.2i:%.2i)\n, fwrev, fwpatch, - (fwdate 12) 0xF, (fwdate 8) 0xF, fwdate 0xFF, - (fwtime 11) 0x1F, (fwtime 5) 0x3F, fwtime 0x1F); + b43legacyinfo(dev-wl, Loading firmware version 0x%X, patch level %u + (20%.2i-%.2i-%.2i %.2i:%.2i:%.2i)\n, fwrev, fwpatch, + (fwdate 12) 0xF, (fwdate 8) 0xF, fwdate 0xFF, + (fwtime 11) 0x1F, (fwtime 5) 0x3F, + fwtime 0x1F); dev-fw.rev = fwrev; dev-fw.patch = fwpatch; -- Ciao Stefano ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Possible problem on b43 driver's init
On Feb 11, 2008 10:18 AM, Michael Buesch [EMAIL PROTECTED] wrote:
On Monday 11 February 2008 03:14:57 David Cohen wrote:
On Feb 10, 2008 9:40 PM, Pavel Roskin [EMAIL PROTECTED] wrote:
On Sun, 2008-02-10 at 17:28 -0400, David Cohen wrote:
Hi all,
I'm here again reporting another possible problem with my wireless
card and b43 driver. Please don't bite me this time, I promise I'm
sending all useful inputs :D
Well, the problem is:
- After boot my laptop, the wireless card is not connected to my wifi
network. But if I just type sudo iwlist scan, then it connects.
- The same problem does not occur if I use ndiswrapper or another
laptops.
I believe it's a feature of mac80211. It only scans for APs under some
circumstances. Setting ESSID triggers scanning. I suggest that you do
it in this order:
bring the interface up
set the WEP key
set the ESSID
Hi,
I tried this, but it didn't work also.
By the way, your AP is set for shared key authentication. It delays
authentication because mac80211 tries open system first and fails.
I can wait for 5 minutes and it still doesn't authenticate.
The weird point is it does not occur with ndiswrapper or with other
linux laptop.
Even without that step, shared key authentication needs 4 packets to be
sent, rather than 2 for open system authentication. It's believed that
shared key is even less secure than open system. See e.g.
http://www.networkworld.com/research/2002/0909wepprimer.html
It's just a home network :) . But thanks anyway, it's useful to know.
Regards,
David Cohen
Can you try this patch?
Same problem... didn't fix it yet. Same output logs also.
Regards,
David Cohen
Index: wireless-2.6/net/mac80211/ieee80211.c
===
--- wireless-2.6.orig/net/mac80211/ieee80211.c 2008-02-08 22:54:22.0
+0100
+++ wireless-2.6/net/mac80211/ieee80211.c 2008-02-10 14:07:23.0
+0100
@@ -172,12 +172,13 @@ static inline int identical_mac_addr_all
static int ieee80211_open(struct net_device *dev)
{
struct ieee80211_sub_if_data *sdata, *nsdata;
struct ieee80211_local *local = wdev_priv(dev-ieee80211_ptr);
struct ieee80211_if_init_conf conf;
int res;
+ bool need_hw_reconfig = 0;
sdata = IEEE80211_DEV_TO_SUB_IF(dev);
/* we hold the RTNL here so can safely walk the list */
list_for_each_entry(nsdata, local-interfaces, list) {
struct net_device *ndev = nsdata-dev;
@@ -225,13 +226,13 @@ static int ieee80211_open(struct net_dev
if (local-open_count == 0) {
res = 0;
if (local-ops-start)
res = local-ops-start(local_to_hw(local));
if (res)
return res;
- ieee80211_hw_config(local);
+ need_hw_reconfig = 1;
ieee80211_led_radio(local, local-hw.conf.radio_enabled);
}
switch (sdata-vif.type) {
case IEEE80211_IF_TYPE_VLAN:
list_add(sdata-u.vlan.list, sdata-u.vlan.ap-u.ap.vlans);
@@ -302,12 +303,14 @@ static int ieee80211_open(struct net_dev
atomic_inc(local-iff_allmultis);
if (sdata-flags IEEE80211_SDATA_PROMISC)
atomic_inc(local-iff_promiscs);
local-open_count++;
+ if (need_hw_reconfig)
+ ieee80211_hw_config(local);
netif_start_queue(dev);
return 0;
}
--
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Re: Problems b43 driver and bcm4318
Quoting [EMAIL PROTECTED]: Hi, I tried the new b43 driver from kernel 2.6.24 hoping I could get rid of ndiswrapper, but something is wrong. Can you please give me advice as how to troubleshoot this? Below follows the output from dmesg after I modprobe'd the b43 driver. I can't connect to the access point (WEP), but iwlist wlan0 scan actually works. I'm quite sure your case is described in the mail archives: https://lists.berlios.de/pipermail/bcm43xx-dev/2008-February/006779.html It looks like you are using firmware for the git version of the driver, not for Linux 2.6.24.x and older. And by the way, Linux 2.6.24.1 would give you are better message about firmware compatibility. And you probably want to go to the latest 2.6.24.x anyway to avoid a major security issue with the kernel. -- Regards, Pavel Roskin ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Problems b43 driver and bcm4318
Hi, I tried the new b43 driver from kernel 2.6.24 hoping I could get rid of ndiswrapper, but something is wrong. Can you please give me advice as how to troubleshoot this? Below follows the output from dmesg after I modprobe'd the b43 driver. I can't connect to the access point (WEP), but iwlist wlan0 scan actually works. Thanks in advace, jorges dmesg output after modprobing b43: -- ssb: Sonics Silicon Backplane found on PCI device :00:09.0 b43-phy0: Broadcom 4318 WLAN found b43-phy0 debug: Found PHY: Analog 3, Type 2, Revision 7 b43-phy0 debug: Found Radio: Manuf 0x17F, Version 0x2050, Revision 8 b43-phy0 debug: DebugFS (CONFIG_DEBUG_FS) not enabled in kernel config phy0: Selected rate control algorithm 'simple' b43-phy0 debug: Loading firmware version 410.2160 (2007-05-26 15:32:10) b43-phy0 debug: Chip initialized b43-phy0 debug: 32-bit DMA initialized Registered led device: b43-phy0:tx Registered led device: b43-phy0:rx Registered led device: b43-phy0:assoc b43-phy0 debug: Wireless interface started HW CONFIG: channel=1 freq=2412 phymode=2 b43-phy0 debug: Adding Interface type 2 ADDRCONF(NETDEV_UP): wlan0: link is not ready HW CONFIG: channel=1 freq=2412 phymode=2 phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x A1=ff:ff:ff:ff:ff:ff A2=00:15:f2:db:ac:72 A3=ff:ff:ff:ff:ff:ff b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie() Pid: 6389, comm: syslog-ng Tainted: P2.6.24-gentoo #4 Call Trace: IRQ [882080c9] :b43:b43_dma_handle_txstatus+0xa8/0x36a [881f7ebc] :b43:b43_interrupt_tasklet+0x636/0x6bf [8022facf] tasklet_action+0x36/0x5e [8022fdba] __do_softirq+0x46/0x90 [8020c0dc] call_softirq+0x1c/0x28 [8020cf80] do_softirq+0x2c/0x7d [8022fd35] irq_exit+0x3f/0x7e [8020d2ef] do_IRQ+0x96/0xa7 [8020b931] ret_from_intr+0x0/0xa EOI WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie() Pid: 6389, comm: syslog-ng Tainted: P2.6.24-gentoo #4 Call Trace: IRQ [88208101] :b43:b43_dma_handle_txstatus+0xe0/0x36a [881f7ebc] :b43:b43_interrupt_tasklet+0x636/0x6bf [8022facf] tasklet_action+0x36/0x5e [8022fdba] __do_softirq+0x46/0x90 [8020c0dc] call_softirq+0x1c/0x28 [8020cf80] do_softirq+0x2c/0x7d [8022fd35] irq_exit+0x3f/0x7e [8020d2ef] do_IRQ+0x96/0xa7 [8020b931] ret_from_intr+0x0/0xa EOI HW CONFIG: channel=2 freq=2417 phymode=2 phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x A1=ff:ff:ff:ff:ff:ff A2=00:15:f2:db:ac:72 A3=ff:ff:ff:ff:ff:ff b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error b43-phy0 ERROR: PHY transmission error WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie() Pid: 6389, comm: syslog-ng Tainted: P2.6.24-gentoo #4 Call Trace: IRQ [882080c9] :b43:b43_dma_handle_txstatus+0xa8/0x36a [881f7ebc] :b43:b43_interrupt_tasklet+0x636/0x6bf [8022facf] tasklet_action+0x36/0x5e [8022fdba] __do_softirq+0x46/0x90 [8020c0dc] call_softirq+0x1c/0x28 [8020cf80] do_softirq+0x2c/0x7d [8022fd35] irq_exit+0x3f/0x7e [8020d2ef] do_IRQ+0x96/0xa7 [8020b931] ret_from_intr+0x0/0xa EOI WARNING: at drivers/net/wireless/b43/dma.c:1098 parse_cookie() Pid: 6389, comm: syslog-ng Tainted: P2.6.24-gentoo #4 Call Trace: IRQ [88208101] :b43:b43_dma_handle_txstatus+0xe0/0x36a [881f7ebc] :b43:b43_interrupt_tasklet+0x636/0x6bf [8022facf] tasklet_action+0x36/0x5e [8022fdba] __do_softirq+0x46/0x90 [8020c0dc] call_softirq+0x1c/0x28 [8020cf80] do_softirq+0x2c/0x7d [8022fd35] irq_exit+0x3f/0x7e [8020d2ef] do_IRQ+0x96/0xa7 [8020b931] ret_from_intr+0x0/0xa EOI HW CONFIG: channel=3 freq=2422 phymode=2 phy0: TX to low-level driver (len=42) FC=0x0040 DUR=0x A1=ff:ff:ff:ff:ff:ff A2=00:15:f2:db:ac:72 A3=ff:ff:ff:ff:ff:ff WARNING: at drivers/net/wireless/b43/dma.c:1095 parse_cookie() Pid: 6389, comm: syslog-ng Tainted: P2.6.24-gentoo #4 Call Trace: IRQ [882080c9] :b43:b43_dma_handle_txstatus+0xa8/0x36a [881f7ebc] :b43:b43_interrupt_tasklet+0x636/0x6bf [8022facf] tasklet_action+0x36/0x5e [8022fdba] __do_softirq+0x46/0x90 [8020c0dc] call_softirq+0x1c/0x28 [8020cf80] do_softirq+0x2c/0x7d [8022fd35] irq_exit+0x3f/0x7e [8020d2ef] do_IRQ+0x96/0xa7 [8020b931] ret_from_intr+0x0/0xa EOI [80491fed] acpi_pm_read+0x7/0xe [8023f0a3] do_gettimeofday+0x2b/0x95
Re: Possible problem on b43 driver's init
On Monday 11 February 2008 03:14:57 David Cohen wrote:
On Feb 10, 2008 9:40 PM, Pavel Roskin [EMAIL PROTECTED] wrote:
On Sun, 2008-02-10 at 17:28 -0400, David Cohen wrote:
Hi all,
I'm here again reporting another possible problem with my wireless
card and b43 driver. Please don't bite me this time, I promise I'm
sending all useful inputs :D
Well, the problem is:
- After boot my laptop, the wireless card is not connected to my wifi
network. But if I just type sudo iwlist scan, then it connects.
- The same problem does not occur if I use ndiswrapper or another
laptops.
I believe it's a feature of mac80211. It only scans for APs under some
circumstances. Setting ESSID triggers scanning. I suggest that you do
it in this order:
bring the interface up
set the WEP key
set the ESSID
Hi,
I tried this, but it didn't work also.
By the way, your AP is set for shared key authentication. It delays
authentication because mac80211 tries open system first and fails.
I can wait for 5 minutes and it still doesn't authenticate.
The weird point is it does not occur with ndiswrapper or with other
linux laptop.
Even without that step, shared key authentication needs 4 packets to be
sent, rather than 2 for open system authentication. It's believed that
shared key is even less secure than open system. See e.g.
http://www.networkworld.com/research/2002/0909wepprimer.html
It's just a home network :) . But thanks anyway, it's useful to know.
Regards,
David Cohen
Can you try this patch?
Index: wireless-2.6/net/mac80211/ieee80211.c
===
--- wireless-2.6.orig/net/mac80211/ieee80211.c 2008-02-08 22:54:22.0
+0100
+++ wireless-2.6/net/mac80211/ieee80211.c 2008-02-10 14:07:23.0
+0100
@@ -172,12 +172,13 @@ static inline int identical_mac_addr_all
static int ieee80211_open(struct net_device *dev)
{
struct ieee80211_sub_if_data *sdata, *nsdata;
struct ieee80211_local *local = wdev_priv(dev-ieee80211_ptr);
struct ieee80211_if_init_conf conf;
int res;
+ bool need_hw_reconfig = 0;
sdata = IEEE80211_DEV_TO_SUB_IF(dev);
/* we hold the RTNL here so can safely walk the list */
list_for_each_entry(nsdata, local-interfaces, list) {
struct net_device *ndev = nsdata-dev;
@@ -225,13 +226,13 @@ static int ieee80211_open(struct net_dev
if (local-open_count == 0) {
res = 0;
if (local-ops-start)
res = local-ops-start(local_to_hw(local));
if (res)
return res;
- ieee80211_hw_config(local);
+ need_hw_reconfig = 1;
ieee80211_led_radio(local, local-hw.conf.radio_enabled);
}
switch (sdata-vif.type) {
case IEEE80211_IF_TYPE_VLAN:
list_add(sdata-u.vlan.list, sdata-u.vlan.ap-u.ap.vlans);
@@ -302,12 +303,14 @@ static int ieee80211_open(struct net_dev
atomic_inc(local-iff_allmultis);
if (sdata-flags IEEE80211_SDATA_PROMISC)
atomic_inc(local-iff_promiscs);
local-open_count++;
+ if (need_hw_reconfig)
+ ieee80211_hw_config(local);
netif_start_queue(dev);
return 0;
}
--
Greetings Michael.
___
Bcm43xx-dev mailing list
Bcm43xx-dev@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
Enabling CONFIG_DEBUG_SLAB breakes b43 module
Hi, I'm using the b43 driver to connect to a WPA2 encrypted WLAN. When I enable the kernel option CONFIG_DEBUG_SLAB my connection breaks. wpa_supplicant can establish the connection and I can make pings or DNS queries, but downloading a file kills the connection. The kernel log includes these lines: [ 593.513610] eth1: RX protected frame, but have no key [ 593.574095] b43-phy0 debug: Removing Interface type 2 [ 593.598874] b43-phy0 debug: Wireless interface stopped [ 593.599135] b43-phy0 debug: DMA-32 0x0200 (RX) max used slots: 4/64 [ 593.601390] b43-phy0 debug: DMA-32 0x02A0 (TX) max used slots: 0/128 [ 593.618607] b43-phy0 debug: DMA-32 0x0280 (TX) max used slots: 0/128 [ 593.626237] b43-phy0 debug: DMA-32 0x0260 (TX) max used slots: 0/128 [ 593.634301] b43-phy0 debug: DMA-32 0x0240 (TX) max used slots: 0/128 [ 593.642281] b43-phy0 debug: DMA-32 0x0220 (TX) max used slots: 2/128 [ 593.651068] b43-phy0 debug: DMA-32 0x0200 (TX) max used slots: 0/128 [ 601.021777] b43-phy0 debug: Loading firmware version 351.126 (2006-07-29 05:54:02) [ 602.751023] b43-phy0 debug: Chip initialized [ 602.760835] b43-phy0 debug: 30-bit DMA initialized [ 602.777127] b43-phy0 debug: Wireless interface started [ 602.823829] b43-phy0 debug: Adding Interface type 2 [ 602.828855] ADDRCONF(NETDEV_UP): eth1: link is not ready [ 604.273055] eth1: Initial auth_alg=0 [ 604.273082] eth1: authenticate with AP 00:14:1b:60:5d:00 [ 604.276600] eth1: RX authentication from 00:14:1b:60:5d:00 (alg=0 transaction=2 status=0) [ 604.276620] eth1: authenticated [ 604.276629] eth1: associate with AP 00:14:1b:60:5d:00 [ 604.280697] eth1: RX AssocResp from 00:14:1b:60:5d:00 (capab=0x431 status=0 aid=161) [ 604.280720] eth1: associated [ 604.280742] eth1: CTS protection enabled (BSSID=00:14:1b:60:5d:00) [ 604.280752] eth1: switched to short barker preamble (BSSID=00:14:1b:60:5d:00) [ 604.281061] eth1: WMM queue=2 aci=0 acm=0 aifs=3 cWmin=15 cWmax=1023 burst=0 [ 604.281072] eth1: WMM queue=3 aci=1 acm=0 aifs=7 cWmin=15 cWmax=1023 burst=0 [ 604.281081] eth1: WMM queue=1 aci=2 acm=0 aifs=2 cWmin=7 cWmax=15 burst=30 [ 604.281091] eth1: WMM queue=0 aci=3 acm=0 aifs=2 cWmin=3 cWmax=7 burst=15 [ 604.283358] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 604.395160] eth1: RX protected frame, but have no key [ 604.396598] eth1: RX protected frame, but have no key [ 604.397609] eth1: RX protected frame, but have no key [ 607.038550] eth1: RX deauthentication from 00:14:1b:60:5d:00 (reason=14) [ 607.038567] eth1: deauthenticated [ 607.083301] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready [ 607.148534] eth1: Initial auth_alg=0 [ 607.148560] eth1: authenticate with AP 00:14:1b:60:5d:00 [ 607.151549] eth1: RX authentication from 00:14:1b:60:5d:00 (alg=0 transaction=2 status=0) [ 607.151569] eth1: authenticated [ 607.151578] eth1: associate with AP 00:14:1b:60:5d:00 [ 607.166211] eth1: RX ReassocResp from 00:14:1b:60:5d:00 (capab=0x0 status=13 aid=0) [ 607.166229] eth1: AP denied association (code=13) [ 607.353166] eth1: associate with AP 00:14:1b:60:5d:00 [ 607.355885] eth1: RX deauthentication from 00:14:1b:60:5d:00 (reason=2) [ 607.355904] eth1: deauthenticated [ 608.355322] eth1: authenticate with AP 00:14:1b:60:5d:00 [ 608.357688] eth1: RX authentication from 00:14:1b:60:5d:00 (alg=0 transaction=2 status=0) [ 608.357707] eth1: authenticated [ 608.357716] eth1: associate with AP 00:14:1b:60:5d:00 [ 608.361568] eth1: RX AssocResp from 00:14:1b:60:5d:00 (capab=0x0 status=13 aid=0) [ 608.361586] eth1: AP denied association (code=13) [ 608.561470] eth1: associate with AP 00:14:1b:60:5d:00 [ 608.569470] eth1: RX deauthentication from 00:14:1b:60:5d:00 (reason=2) [ 608.569489] eth1: deauthenticated [ 609.568954] eth1: authenticate with AP 00:14:1b:60:5d:00 [ 609.570574] eth1: RX authentication from 00:14:1b:60:5d:00 (alg=0 transaction=2 status=0) [ 609.570589] eth1: authenticated [ 609.570598] eth1: associate with AP 00:14:1b:60:5d:00 [ 609.572686] eth1: RX AssocResp from 00:14:1b:60:5d:00 (capab=0x0 status=13 aid=0) [ 609.572698] eth1: AP denied association (code=13) % uname -a Linux ibook 2.6.24 #1 Thu Feb 7 10:22:52 CET 2008 ppc GNU/Linux I've an Airport Extreme Card. # lspci -s 10:12 -v 0001:10:12.0 Network controller: Broadcom Corporation BCM4306 802.11b/g Wireless LAN Controller (rev 03) Subsystem: Apple Computer Inc. AirPort Extreme Flags: bus master, fast devsel, latency 16, IRQ 52 Memory at 80084000 (32-bit, non-prefetchable) [size=8K] Capabilities: [40] Power Management version 2 Kernel driver in use: b43-pci-bridge Kernel modules: ssb Bye, Jörg. -- But in the case of git revert, it should be an ancestor (or the user is just insane, in which case it doesn't matter - insane people can do insane things) Linus Torvalds [EMAIL PROTECTED] ___ Bcm43xx-dev mailing list
b43legacy: add firmware information to modinfo
This adds the firmware ID to modinfo. The patch by Michael Buesch has been ported to b43legacy. Signed-off-by: Stefano Brivio [EMAIL PROTECTED] --- Index: wireless-2.6/drivers/net/wireless/b43legacy/main.c === --- wireless-2.6.orig/drivers/net/wireless/b43legacy/main.c +++ wireless-2.6/drivers/net/wireless/b43legacy/main.c @@ -60,6 +60,8 @@ MODULE_AUTHOR(Stefano Brivio); MODULE_AUTHOR(Michael Buesch); MODULE_LICENSE(GPL); +MODULE_FIRMWARE(B43legacy_SUPPORTED_FIRMWARE_ID); + #if defined(CONFIG_B43LEGACY_DMA) defined(CONFIG_B43LEGACY_PIO) static int modparam_pio; module_param_named(pio, modparam_pio, int, 0444); -- Ciao Stefano ___ Bcm43xx-dev mailing list Bcm43xx-dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/bcm43xx-dev
