[SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

nawitus · 2010-08-03 16:42:24

EDIT: Solved in 2.6.35.1

Updated kernel to 2.6.34.2-1 with a full system upgrade and wlan stopped working. Wired connection works well. Network manager does not see/sense any available wlan connections. Connecting manually to a known wlan name (essid) does not work either. The wlan light on my laptop (HP Pavilion dv6544eo) is constantly red, even though it should be blue when the wlan card is working properly. Switching the wlan-button off and on again changes the wlan state in Network Manager to be 'device not ready'.

nawi ~ $ ifconfig
eth0      Link encap:Ethernet  HWaddr 00:1B:24:73:A0:17  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:20 Base address:0x8000 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

nawi ~ $ ifconfig wlan0
wlan0     Link encap:Ethernet  HWaddr 00:00:00:00:00:00  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

nawi ~ $ ifconfig wlan0 up
SIOCSIFFLAGS: Permission denied
nawi ~ $ sudo ifconfig wlan0 up
SIOCSIFFLAGS: Cannot assign requested address
nawi ~ $ sudo ifconfig wlan0 up 192.168.0.50
SIOCSIFFLAGS: Cannot assign requested address
SIOCSIFFLAGS: Cannot assign requested address

HP Laptop specs
networkmanager 0.8-1

There's errors in /var/log/errors.log, but the same errors were happening constantly before the system upgrade and are probably not the cause for my problems.

Aug  3 17:06:48 nawi kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
Aug  3 17:06:48 nawi kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
Aug  3 17:38:50 nawi NetworkManager: user_connection_updated_cb: assertion `old_connection != NULL' failed
Aug  3 18:57:06 nawi kernel: pnp 00:03: can't evaluate _CRS: 12298
Aug  3 18:57:11 nawi NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Aug  3 18:57:55 nawi sudo: pam_unix(sudo:auth): conversation failed
Aug  3 19:03:19 nawi kernel: pnp 00:03: can't evaluate _CRS: 12298
Aug  3 19:03:25 nawi NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Aug  3 19:04:04 nawi sudo: pam_unix(sudo:auth): conversation failed
Aug  3 19:04:25 nawi NetworkManager: user_connection_updated_cb: assertion `old_connection != NULL' failed

My wlan stopped working around 18:57 after the reboot of my laptop.

/var/log/daemon.log

Aug  3 18:56:10 nawi init: Switching to runlevel: 6
Aug  3 18:56:10 nawi NetworkManager: <info>  (wlan0): device state change: 8 -> 3 (reason 38)
Aug  3 18:56:10 nawi NetworkManager: <info>  (wlan0): deactivating device (reason: 38).
Aug  3 18:56:10 nawi dhcpcd[21332]: received SIGTERM, stopping
Aug  3 18:56:10 nawi dhcpcd[21332]: wlan0: removing interface
Aug  3 18:56:10 nawi NetworkManager: <info>  (wlan0): canceled DHCP transaction, dhcp client pid 21332
Aug  3 18:56:10 nawi NetworkManager: <WARN>  nm_dhcp_manager_handle_event(): Received DHCP event from unexpected PID 21332 (expected 0)
Aug  3 18:56:13 nawi acpid: exiting
Aug  3 18:56:13 nawi NetworkManager: <info>  disconnected by the system bus.
Aug  3 18:56:13 nawi NetworkManager: no sender
Aug  3 18:56:13 nawi nm-dispatcher.action: Disconnected from the system bus, exiting.
Aug  3 18:56:13 nawi console-kit-daemon[4029]: WARNING: no sender
Aug  3 18:56:13 nawi ntpd[4015]: Terminating
Aug  3 18:57:07 nawi acpid: starting up
Aug  3 18:57:07 nawi acpid: 4 rules loaded
Aug  3 18:57:07 nawi acpid: waiting for events: event logging is off
Aug  3 18:57:05 nawi init: Entering runlevel: 3
Aug  3 18:57:09 nawi acpid: client connected from 3877[82:82]
Aug  3 18:57:09 nawi acpid: 1 client rule loaded
Aug  3 18:57:10 nawi NetworkManager: <info>  starting...
Aug  3 18:57:10 nawi NetworkManager: <info>  Trying to start the modem-manager...
Aug  3 18:57:10 nawi NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing li$
Aug  3 18:57:10 nawi NetworkManager: <info>  Found wlan radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:0c.0/0000:03:00.0/ssb0:0/ieee$
Aug  3 18:57:10 nawi NetworkManager: <info>  Found wlan radio killswitch rfkill1 (at /sys/devices/platform/hp-wmi/rfkill/rfkill1) (driver hp-wmi)
Aug  3 18:57:10 nawi NetworkManager: <info>  WiFi enabled by radio killswitch; enabled by state file
Aug  3 18:57:10 nawi NetworkManager: <info>  WWAN enabled by radio killswitch; enabled by state file
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): carrier is OFF
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): new Ethernet device (driver: 'forcedeth')
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): exported as /org/freedesktop/NetworkManager/Devices/0
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): now managed
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): device state change: 1 -> 2 (reason 2)
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): bringing up device.
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): preparing device.
Aug  3 18:57:11 nawi NetworkManager: <info>  (eth0): deactivating device (reason: 2).
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'b43')
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): exported as /org/freedesktop/NetworkManager/Devices/1
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): now managed
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): device state change: 1 -> 2 (reason 2)
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): bringing up device.
Aug  3 18:57:11 nawi NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Aug  3 18:57:11 nawi NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Aug  3 18:57:11 nawi NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was
not provided by any .service files
Aug  3 18:57:11 nawi NetworkManager: <info>  Trying to start the supplicant...
Aug  3 18:57:12 nawi NetworkManager: <info>  (wlan0): supplicant manager state:  down -> idle
Aug  3 18:57:12 nawi NetworkManager: <info>  (wlan0): device state change: 2 -> 3 (reason 0)
Aug  3 18:57:12 nawi NetworkManager: <info>  (wlan0): supplicant interface state:  starting -> ready

It seems that the device is deactived for "reason: 2".

messages.log:

Aug  3 18:57:06 nawi kernel: b43-phy0: Broadcom 4311 WLAN found (core revision 13)
Aug  3 18:57:11 nawi kernel: b43 ssb0:0: firmware: requesting b43/ucode13.fw
Aug  3 18:57:11 nawi kernel: b43 ssb0:0: firmware: requesting b43/b0g0initvals13.fw
Aug  3 18:57:11 nawi kernel: b43-phy0: Loading firmware version 478.104 (2008-07-01 00:50:23)

wpa-supplicant -u is running too.

nawi /etc/NetworkManager $ iwconfig wlan0
wlan0     IEEE 802.11bg  Mode:Managed  Access Point: Not-Associated   
          Tx-Power=0 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
nawi /etc/NetworkManager $ iwlist wlan0 scan
wlan0     Failed to read scan data : Network is down

nawi /etc/NetworkManager $

dmesg.log <pastebin.com>

[root@nawi b43]# lsmod | grep b43
b43                   157367  0 
ssb                    40054  1 b43
mmc_core               46834  3 b43,ssb,sdhci
pcmcia                 32806  2 b43,ssb
mac80211              161287  1 b43
cfg80211              121416  2 b43,mac80211
led_class               1835  2 b43,sdhci

rc.conf <pastebin.com>

Last edited by nawitus (2010-08-04 16:20:01)

Inxsible · 2010-08-03 17:33:47

others have had this problem as well. They solved it by downgrading their kernel. Not that its an optimal solution, but keeping the network up is more important that having the latest kernel for the time being atleast.

But before you do that, you might wanna try out a different network manager like wicd, to see if that works, although one other thread I noticed that wicd had problems seeing networks as well.

Last edited by Inxsible (2010-08-03 17:35:09)

FamiCube64 · 2010-08-03 17:34:23

I'm having the same issues with a BCM4318 card, using the b43 driver. I'll post again if I manage to fix it, but for now you're going to have to downgrade the kernel. Edit: Downgrading to 2.6.33 fixes the issue.

Thanks for the info, wonder.

Last edited by FamiCube64 (2010-08-03 19:57:59)

cruznick · 2010-08-03 18:22:50

I am having the same problem

wonder · 2010-08-03 18:47:42

report upstream.

2.6.34.2 has ssb changes and seems they busted it. http://www.kernel.org/pub/linux/kernel/ … g-2.6.34.2

commit 4584740e4ec1db166d862112b1b90e35cadaad03
Author: Christoph Fritz <chf.fritz@googlemail.com>
Date:   Sun Jul 11 18:26:15 2010 -0500

    ssb: Handle Netbook devices where the SPROM address is changed
    
    For some Netbook computers with Broadcom BCM4312 wireless interfaces,
    the SPROM has been moved to a new location. When the ssb driver tries to
    read the old location, the systems hangs when trying to read a
    non-existent location. Such freezes are particularly bad as they do not
    log the failure.
    
    This patch is modified from commit
    da1fdb02d9200ff28b6f3a380d21930335fe5429 with some pieces from other
    mainline changes so that it can be applied to stable 2.6.34.Y.
    
    Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>
    Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>

nawitus · 2010-08-03 19:18:36

Downgrading kernel to 34.1 solves this temporarily.

archman-cro · 2010-08-03 20:18:42

Yeah, I can double this. Using bcm4311 with b43 driver here.
'SCIOCSIFFLAGS: Cannot assign requested address' while trying 'ifconfig wlan0 up'.
2.6.34.1-1 was the last one that's known to work. Cheers.

Last edited by archman-cro (2010-08-03 20:19:21)

Leonid.I · 2010-08-03 20:23:01

Aug  3 17:06:48 nawi kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
Aug  3 17:06:48 nawi kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.

This seems like a hardware/BIOS problem. It could well be, that no future kernel will work for you, unless this is fixed.

Last edited by Leonid.I (2010-08-03 20:23:19)

.:B:. · 2010-08-03 20:26:03

Could you mark this as [SOLVED] please, and maybe detail in your title that it was an upgrade from .34.2 to .34.1? That will help people searching the forums.

Thank you

nawitus · 2010-08-03 20:30:58

.:B:. wrote:

Could you mark this as [SOLVED] please, and maybe detail in your title that it was an upgrade from .34.2 to .34.1? That will help people searching the forums.
Thank you

I added the version numbers, but won't add [SOLVED] since downgrade is not a real solution in my opinion..

Leonid.I wrote:

Aug  3 17:06:48 nawi kernel: b43-phy0 ERROR: Fatal DMA error: 0x00000800, 0x00000000, 0x00000000, 0x00000000, 0x00000000, 0x00000000
Aug  3 17:06:48 nawi kernel: b43-phy0 ERROR: This device does not support DMA on your system. Please use PIO instead.
This seems like a hardware/BIOS problem. It could well be, that no future kernel will work for you, unless this is fixed.

No, I did the update and reboot after 17:06, so that doesn't seem to be cause of this problem.

Last edited by nawitus (2010-08-03 20:32:59)

KoS · 2010-08-03 21:22:08

The same happened on my Lenovo S12 (ION) with Broadcom BCM4312 wireless and b43 driver.
Downgrading to kernel26-2.6.34.1 solved the issue.

Some additional notes to the problem. I noticed that the MAC address was changed upon every reboot to random numbers, and I could either connect to the wireless network or not based on whether the MAC address was a valid MAC address or not. It was pretty strange but wonder's comment clears this up a bit. I hope however that they will fix it in the kernel and not all further kernels will be unusable for us.

wonder · 2010-08-03 22:30:44

KoS wrote:

It was pretty strange but wonder's comment clears this up a bit. I hope however that they will fix it in the kernel and not all further kernels will be unusable for us.

that would happen if nobody reports this issue upstream. bugs are not fixed automagically. somebody should do it and paste at least the link here.

also it would be nice to see if 2.6.35 is affected. now that is in testing, it should be easy to test

Last edited by wonder (2010-08-03 22:34:16)

FamiCube64 · 2010-08-03 22:42:08

I'm getting ready to test 6.35 right now, hold tight.

Edit: Compiling now...

Last edited by FamiCube64 (2010-08-03 23:10:19)

wonder · 2010-08-03 23:12:09

FamiCube64 wrote:

I'm getting ready to test 6.35 right now, hold tight.
Edit: Compiling now...

why not enabling testing and do pacman -Syu ?

archman-cro · 2010-08-03 23:57:17

With wonder's recommendation, I've opened an issue upstream. (Since I did a search and haven't found any similar threads there, already)

Bug 16505

Btw, sorry for the typos in the report.

Last edited by archman-cro (2010-08-03 23:59:11)

tomk · 2010-08-03 23:58:01

b43 working as expected here with testing/kernel26-2.6.35-1.

FamiCube64 · 2010-08-04 02:33:10

I can confirm the issue is fixed in 2.6.35-1. In regards to wonder's question, I didn't know it was in the repos.

varg04444 · 2010-08-04 03:36:09

Hello everybody, I confirm the problem in my vostro 1320 too with BCM4312 wi-fi card, and it's work fine with kernel 2.6.35-1 by testiing repository.

KoS · 2010-08-04 07:49:32

I can also confirm that moving to kernel 2.6.35 solved the problem!

archman-cro · 2010-08-04 08:06:13

A reply from bugzilla:

"Fix for BCM43XX problems in 2.6.34.2

This problem is my fault. The offset calculated for the SPROM is wrong as shown
in the attached patch. The commit 4584740e4ec1db166d862112b1b90e35cadaad03 has
been a problem, but I did not think it was in 2.6.34.2 as GregKH reported a
merge problem with it.

v2.6.35 is not affected by this problem. It will cause a problem for some
Netbook computers with BCM4312 cards as they will freeze when loading ssb. That
fix will be in 2.6.35."

There is also a fix for this issue under 2.6.34.2:

2.6.34.2: ssb: Fix error is SPROM offsets

Signed-off-by: Larry Finger <Larry.Finger@lwfinger.net>

Index: linux-2.6.34.y/drivers/ssb/pci.c
===================================================================
--- linux-2.6.34.y.orig/drivers/ssb/pci.c
+++ linux-2.6.34.y/drivers/ssb/pci.c
@@ -169,7 +169,7 @@ err_pci:
 }
 
 /* Get the word-offset for a SSB_SPROM_XXX define. */
-#define SPOFF(offset)    ((offset) / sizeof(u16))
+#define SPOFF(offset)    (((offset) - SSB_SPROM_BASE1) / sizeof(u16))
 /* Helper to extract some _offset, which is one of the SSB_SPROM_XXX defines. */
 #define SPEX16(_outvar, _offset, _mask, _shift)    \
     out->_outvar = ((in[SPOFF(_offset)] & (_mask)) >> (_shift))

Now I dunno how to apply it, but it's cool, since that's fixed in 2.6.35.

Edit: Aaah, I realize now, https://bugzilla.kernel.org/attachment. … ction=diff.

Last edited by archman-cro (2010-08-04 08:18:44)

FamiCube64 · 2010-08-11 21:01:04

Sorry to drag this thread back up but kernel 2.6.34.3-1 in the core repo fixes the issue, for those who don't like using testing.

WMP · 2011-08-30 22:42:38

I have this same problem on 3.0.2, 3.0.3, 3.0.4

Arch Linux

#1 2010-08-03 16:42:24

[SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#2 2010-08-03 17:33:47

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#3 2010-08-03 17:34:23

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#4 2010-08-03 18:22:50

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#5 2010-08-03 18:47:42

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#6 2010-08-03 19:18:36

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#7 2010-08-03 20:18:42

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#8 2010-08-03 20:23:01

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#9 2010-08-03 20:26:03

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#10 2010-08-03 20:30:58

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#11 2010-08-03 21:22:08

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#12 2010-08-03 22:30:44

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#13 2010-08-03 22:42:08

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#14 2010-08-03 23:12:09

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#15 2010-08-03 23:57:17

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#16 2010-08-03 23:58:01

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#17 2010-08-04 02:33:10

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#18 2010-08-04 03:36:09

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#19 2010-08-04 07:49:32

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#20 2010-08-04 08:06:13

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#21 2010-08-11 21:01:04

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

#22 2011-08-30 22:42:38

Re: [SOLVED] WLAN (b43) not working after kernel update 34.1->34.2

Board footer