2013-06-19 21:43:51

by Martin Zobel-Helas

[permalink] [raw]
Subject: strange b43 problem // 3.9 regression?

Hi,

i run Debian unstable on my MacBookPro8,2. Since the update to Debian's
3.9 kernel i run into strange problems with my b43 wireless. Still works
perfect with Debian's latest 3.8 kernel from snapshot.debian.org.

Scenario:
Fresh reboot into Linux 3.9 kernel, without loading any wireless driver.

# cat /proc/version
Linux version 3.9-1-amd64 ([email protected]) (gcc version 4.7.2 (Debian 4.7.2-5) ) #1 SMP Debian 3.9.5-1

Kernel 3.8.13 that stills works perfectly:
# dpkg -l linux-image-3.8-2-amd64 | grep ^ii
ii linux-image-3.8-2-amd64 3.8.13-1 amd64 Linux 3.8 for 64-bit PCs


# lspci -nn | grep 802
03:00.0 Network controller [0280]: Broadcom Corporation BCM4331 802.11a/b/g/n [14e4:4331] (rev 02)

firmware install as per http://homepage.uibk.ac.at/~c705283/archives/2011/09/04/linux_support_for_broadcom_4331_wireless_chip_macbook_pro_81/index.html

# modprobe b43
# iwlist scan
...
wlan0 No scan results

# iwlist wlan0 scan
...
wlan0 No scan results
#

also NetworkManager does not detect any SSID at this point. I wait for
several minutes, still no results.

Now i plug in my wireless USB wlan token from TP-Link
# lsusb | grep TP-Link
Bus 001 Device 028: ID 0cf3:7015 Atheros Communications, Inc. TP-Link TL-WN821N v3 802.11n [Atheros AR7010+AR9287]
# iwlist wlan1 scan | grep Cell
Cell 01 - Address: C4:0A:CB:DE:8C:B0
Cell 02 - Address: C4:0A:CB:DE:8C:B1
Cell 03 - Address: C4:0A:CB:DE:8C:B2

# iwlist wlan0 scan | grep Cell
#

So still no results here. But the interesting part starts now:
If i now do the following:
# iwlist scan | grep Cell
Cell 01 - Address: C4:0A:CB:DE:8C:B0
Cell 02 - Address: C4:0A:CB:DE:8C:B2
Cell 03 - Address: C4:0A:CB:DE:8C:B1
Cell 01 - Address: C4:0A:CB:DE:8C:B0
Cell 02 - Address: C4:0A:CB:DE:8C:B2
Cell 03 - Address: C4:0A:CB:DE:8C:B1
# iwlist wlan0 scan | grep Cell
Cell 01 - Address: C4:0A:CB:DE:8C:B0
Cell 02 - Address: C4:0A:CB:DE:8C:B1
Cell 03 - Address: C4:0A:CB:DE:8C:B2

and NetworkManager immediately sees SSIDs on my wireless wlan0
interface. Running "iwlist wlan0 scan" from now on shows me my SSIDs on
the b43 interface.

Doing the above procedure, works reliable reproducable for me.

"iwlist scan" first scans my wlan1 interface (TP-Link) and then wlan0
(Broadcom). I therefor wonder if this is somewhat a timing problem in
the wireless stack.

I attached detailed information about my hardware of my system to this
mail. If you need any more information, i will provide the needed
information. I need to admit that i am not that deeply involved into
linux kernel.

Cheers,
Martin
--
Martin Zobel-Helas <[email protected]>
GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B


Attachments:
(No filename) (2.76 kB)
lshw (26.20 kB)
lsmod (8.67 kB)
lspci (2.59 kB)
lsusb (882.00 B)
kernlog.gz (36.47 kB)
dmidecode (28.15 kB)
Download all attachments