Karmic BCM4311 doesn't work with Broadcom B43 wireless driver and Driver Broadcom STA

Bug #421095 reported by Tyrael
52
This bug affects 8 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
Nominated for Karmic by evp55555

Bug Description

Broadcom B43 worked the first time but stops working after reboot / halt.
I tried 2 different AP with both WEP. One result connected but only ping and few connection worked (other PCs connected to the same AP worked perfectly) the other gives authentication time out.

STA driver freeze sometimes the notebook and gives similar error.

With Ubuntu 9.04 the wireless card works.

$ hwinfo --netcard
22: PCI 600.0: 0280 Network controller
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_14e4_4311
  Unique ID: vTuk.cqdzXVTrWLB
  Parent ID: hoOk.6RaQ2iO1oj0
  SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:06:00.0
  SysFS BusID: 0000:06:00.0
  Hardware Class: network
  Model: "Hewlett-Packard Company BCM4311 802.11b/g Wireless LAN Controller"
  Vendor: pci 0x14e4 "Broadcom"
  Device: pci 0x4311 "BCM4311 802.11b/g WLAN"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x1364 "BCM4311 802.11b/g Wireless LAN Controller"
  Revision: 0x01
  Driver: "b43-pci-bridge"
  Driver Modules: "ssb"
  Memory Range: 0x40000000-0x40003fff (rw,non-prefetchable)
  IRQ: 18 (847 events)
  Module Alias: "pci:v000014E4d00004311sv0000103Csd00001364bc02sc80i00"
  Driver Info #0:
    Driver Status: ssb is active
    Driver Activation Cmd: "modprobe ssb"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #12 (PCI bridge)

23: PCI 808.0: 0200 Ethernet controller
  [Created at pci.318]
  UDI: /org/freedesktop/Hal/devices/pci_10ec_8139
  Unique ID: rBUF.LI924rkRv88
  Parent ID: 6NW+.WGY8iKV5q78
  SysFS ID: /devices/pci0000:00/0000:00:1e.0/0000:08:08.0
  SysFS BusID: 0000:08:08.0
  Hardware Class: network
  Model: "Realtek RTL-8139/8139C/8139C+"
  Vendor: pci 0x10ec "Realtek Semiconductor Co., Ltd."
  Device: pci 0x8139 "RTL-8139/8139C/8139C+"
  SubVendor: pci 0x103c "Hewlett-Packard Company"
  SubDevice: pci 0x30a5
  Revision: 0x10
  Driver: "8139too"
  Driver Modules: "8139too"
  Device File: eth0
  I/O Ports: 0x2000-0x2fff (rw)
  Memory Range: 0xd0100000-0xd01000ff (rw,non-prefetchable)
  IRQ: 16 (31472 events)
  HW Address: 00:16:d4:b7:46:e8
  Link detected: yes
  Module Alias: "pci:v000010ECd00008139sv0000103Csd000030A5bc02sc00i00"
  Driver Info #0:
    Driver Status: 8139too is active
    Driver Activation Cmd: "modprobe 8139too"
  Driver Info #1:
    Driver Status: 8139cp is active
    Driver Activation Cmd: "modprobe 8139cp"
  Driver Info #2:
    Driver Status: epl is not active
    Driver Activation Cmd: "modprobe epl"
  Config Status: cfg=new, avail=yes, need=no, active=unknown
  Attached to: #17 (PCI bridge)

$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

$ sudo lshw -C network
  *-network
       description: Network controller
       product: BCM4311 802.11b/g WLAN
       vendor: Broadcom Corporation
       physical id: 0
       bus info: pci@0000:06:00.0
       version: 01
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list
       configuration: driver=b43-pci-bridge latency=0
       resources: irq:18 memory:40000000-40003fff
  *-network
       description: Ethernet interface
       product: RTL-8139/8139C/8139C+
       vendor: Realtek Semiconductor Co., Ltd.
       physical id: 8
       bus info: pci@0000:08:08.0
       logical name: eth0
       version: 10
       serial: 00:16:d4:b7:46:e8
       size: 100MB/s
       capacity: 100MB/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=8139too driverversion=0.9.28 duplex=full ip=192.168.123.130 latency=32 link=yes maxlatency=64 mingnt=32 multicast=yes port=MII speed=100MB/s
       resources: irq:16 ioport:2000(size=256) memory:d0100000-d01000ff

$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03)
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03)
00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03)
00:1b.0 Audio device [0403]: Intel Corporation 82801G (ICH7 Family) High Definition Audio Controller [8086:27d8] (rev 01)
00:1c.0 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 1 [8086:27d0] (rev 01)
00:1c.2 PCI bridge [0604]: Intel Corporation 82801G (ICH7 Family) PCI Express Port 3 [8086:27d4] (rev 01)
00:1d.0 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #1 [8086:27c8] (rev 01)
00:1d.1 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #2 [8086:27c9] (rev 01)
00:1d.2 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB UHCI Controller #3 [8086:27ca] (rev 01)
00:1d.7 USB Controller [0c03]: Intel Corporation 82801G (ICH7 Family) USB2 EHCI Controller [8086:27cc] (rev 01)
00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev e1)
00:1f.0 ISA bridge [0601]: Intel Corporation 82801GBM (ICH7-M) LPC Interface Bridge [8086:27b9] (rev 01)
00:1f.1 IDE interface [0101]: Intel Corporation 82801G (ICH7 Family) IDE Controller [8086:27df] (rev 01)
00:1f.2 SATA controller [0106]: Intel Corporation 82801GBM/GHM (ICH7 Family) SATA AHCI Controller [8086:27c5] (rev 01)
00:1f.3 SMBus [0c05]: Intel Corporation 82801G (ICH7 Family) SMBus Controller [8086:27da] (rev 01)
06:00.0 Network controller [0280]: Broadcom Corporation BCM4311 802.11b/g WLAN [14e4:4311] (rev 01)
08:08.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ [10ec:8139] (rev 10)

$ uname -a
Linux marce-laptop 2.6.31-8-generic #28-Ubuntu SMP Thu Aug 27 14:43:30 UTC 2009 i686 GNU/Linux

$ dmesg | grep ound
[ 0.000000] ACPI: BIOS bug: multiple APIC/MADT found, using 0
[ 0.000000] found SMP MP-table at [c00f65c0] f65c0
[ 0.280712] ACPI: No dock devices found.
[ 0.300202] pci 0000:06:00.0: BAR 0: no parent found for of device [0xd0000000-0xd0003fff]
[ 0.369960] pnp: PnP ACPI: found 10 devices
[ 2.943265] isapnp: No Plug & Play device found
[ 2.993432] hub 1-0:1.0: USB hub found
[ 2.994523] hub 2-0:1.0: USB hub found
[ 2.995316] hub 3-0:1.0: USB hub found
[ 2.996127] hub 4-0:1.0: USB hub found
[ 3.021630] device-mapper: multipath round-robin: version 1.0.0 loaded
[ 3.031705] BIOS EDD facility v0.16 2004-Jun-25, 0 devices found
[ 5.288155] ssb: Sonics Silicon Backplane found on PCI device 0000:06:00.0
[ 11.049496] lp: driver loaded but no devices found
[ 1893.272552] ssb: Sonics Silicon Backplane found on PCI device 0000:06:00.0

$ dmesg | grep witch
[ 0.204424] ACPI: EC: non-query interrupt received, switching to interrupt mode
[ 0.501055] Switched to high resolution mode on CPU 1
[ 0.503988] Switched to high resolution mode on CPU 0
[ 2.534933] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2
[ 2.535016] ACPI: Lid Switch [LID]
[ 4.967836] Console: switching to colour frame buffer device 160x50

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

after installing B43 wireless driver

dmesg:

[ 359.040422] cfg80211: Calling CRDA to update world regulatory domain
[ 359.092393] cfg80211: World regulatory domain updated:
[ 359.092402] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 359.092411] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 359.092418] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 359.092426] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 359.092433] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 359.092441] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 359.145184] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
[ 359.274357] phy0: Selected rate control algorithm 'minstrel'
[ 359.276197] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]
[ 359.368318] b43-phy1: Broadcom 4311 WLAN found (core revision 10)
[ 359.433627] phy1: Selected rate control algorithm 'minstrel'
[ 359.532254] b43 ssb0:0: firmware: requesting b43/ucode5.fw
[ 359.548075] b43 ssb0:0: firmware: requesting b43/pcm5.fw
[ 359.556250] b43 ssb0:0: firmware: requesting b43/b0g0initvals5.fw
[ 359.564283] b43 ssb0:0: firmware: requesting b43/b0g0bsinitvals5.fw
[ 359.688184] b43-phy1: Loading firmware version 410.2160 (2007-05-26 15:32:10)
[ 359.774204] Registered led device: b43-phy1::tx
[ 359.774589] Registered led device: b43-phy1::rx
[ 359.774974] Registered led device: b43-phy1::radio
[ 359.801678] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 367.710335] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 367.908198] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 368.108156] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 368.308162] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 374.146026] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 374.344187] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 374.544064] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 374.744168] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 380.564950] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 380.764131] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 380.964150] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 381.164174] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 386.981022] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 387.180126] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 387.380147] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 387.580112] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 393.405573] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 393.604187] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 393.804172] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 394.004142] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 399.822094] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 400.021158] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 400.220156] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 400.420152] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 406.228991] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 406.428169] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 406.628181] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 406.828177] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 411.964949] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 412.164160] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 412.364084] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 412.564141] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 418.381087] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 418.580210] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 418.780057] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 418.980115] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out
[ 424.805037] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 425.004146] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 425.204106] wlan0: authenticate with AP 00:c0:49:cc:8f:4e
[ 425.404114] wlan0: authentication with AP 00:c0:49:cc:8f:4e timed out

$ sudo iwlist scanning
lo Interface doesn't support scanning.

eth0 Interface doesn't support scanning.

wmaster0 Interface doesn't support scanning.

wlan0 Scan completed :
          Cell 01 - Address: 00:C0:49:CC:8F:4E
                    Channel:7
                    Frequency:2.442 GHz (Channel 7)
                    Quality=39/70 Signal level=-71 dBm
                    Encryption key:on
                    ESSID:"realm"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 22 Mb/s
                    Bit Rates:6 Mb/s; 9 Mb/s; 12 Mb/s; 18 Mb/s; 24 Mb/s
                              36 Mb/s; 48 Mb/s; 54 Mb/s
                    Mode:Master
                    Extra:tsf=0000000162b7d121
                    Extra: Last beacon: 456ms ago
                    IE: Unknown: 00057265616C6D
                    IE: Unknown: 010582848B962C
                    IE: Unknown: 030107
                    IE: Unknown: 0706455520010D14
                    IE: Unknown: 2A0100
                    IE: Unknown: 32080C1218243048606C
                    IE: Unknown: DD0600032F010001

$ iwconfig
lo no wireless extensions.

eth0 no wireless extensions.

wmaster0 no wireless extensions.

wlan0 IEEE 802.11bg ESSID:"realm"
          Mode:Managed Frequency:2.442 GHz Access Point: Not-Associated
          Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:off
          Link Quality:0 Signal level:0 Noise level:0
          Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
          Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Revision history for this message
evp55555 (evp55555) wrote :

I have the same issue. Please fix it before the final release.

Revision history for this message
Steven Harms (sharms) wrote :

I can confirm this also.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
LSL (spesialstyrker) wrote :

Same problem on my dell e1705 laptop. BCM4311 wireless.

Revision history for this message
evp55555 (evp55555) wrote :

I don't know why, but I installed karmic again on the same machine (dell Inspiron 1520) , while it is connected to Ethernet, and now the Ethernet and wireless are working (after installing the non-STA driver. I will try the STA again and post here the results.

Revision history for this message
LSL (spesialstyrker) wrote :

I had the same experience on a fresh install and installing the fwcutter with the hard link up to fetch the firmware, but after the first reboot the wireless ceased to function. It would detect the networks available, but would not connect to either unencrypted or encrypted wireless network. Was a short lived victory :(

Revision history for this message
swoody (swoody) wrote :

I do not have this issue. I did a fresh install of Karmic Beta on my laptop which has a BCM4311, and the STA, b43, and openFWWF drivers all work fine without any issues that I've come across. I have connected to WPA and unencrypted networks without issue.

Revision history for this message
hejkki (heikki-kniivila) wrote :

it worked for me after a fresh install, but
after trying to share the connection from network manager -> create new wireless network...
all stopped working.

Even after i tried to remove the new connection that i made, nothing started working again.

Revision history for this message
bernie eiben (b-eiben) wrote :

Worked on ASUS 1000HE in pre-release of 9.10 [ although needed fiddling and only worked after about 5 trials ]

This netbook has a 'changed' wireless interface [BCM4311] to support Windoze, hacked OSX and linux - only Ubuntu Remix currently doesn't work..

Revision history for this message
bernie eiben (b-eiben) wrote :

 There's more wrong - I just rebooted and got the 'driver is authenticated' from the widget - but no sign that
wireless is supported, Then via 'right-click' on the ethernet-connection' I saw the 'connect to hidden networks' ,
which was the first clue, that things might work.. so I entered the 'hidden network' stuff' (SSID and pwd) and got
a connection. Only after disconnecting Ethernet, I finally see the Wireless picture on the top bar..

So in Summary - it's a 'step back' from the pre-release and is getting further away in comparison to Windoze and
MAC-OSX which directly connect [ no need for "sudo apt-get update" , "authentication" , entering a wireless network in the network widget and reboots ] .. and netbooks are currently high volume sales items ..

Revision history for this message
semacore (surerank) wrote :

I am using a n wireless card on a dell xps m1710.

It seems to happen when the computer is idle and then the driver becomes corrupt and won't reload.

I've done the following about 7 times... it's a temporary fix at best but does get you working ... until at least the computer goes idle.

1 - Add the Install CD to the software sources
2 - In Synaptic, locate the broadcomm sta package and mark for reinstall
3 - Reboot, go to Administration/Hardware drivers and hopefully now the wirelles driver is working.
4 - rinse and repeat

Could the issue be connected to the screen going dim when idle and not re-brightening bug?

Revision history for this message
semacore (surerank) wrote :

I should note that this was not an issue when I first "upgraded" from the stable 9.04 to the buggy 9.10

This problem was caused by one of the updates since the release which I took because I was trying to fix other issues.

The hardware I have worked fine under:
 - Ubuntu 8.04.3 LTS (Hardy Heron)
 - Ubuntu 8.10 (Intrepid Ibex)
 - Ubuntu 9.04 (Jaunty Jackalope)
 - Windows Vista

Is there a guide for downgrading to 9.04?

Revision history for this message
semacore (surerank) wrote :

seems to be fixed.

Revision history for this message
semacore (surerank) wrote :

Not fixed afterall.
Problem came back when laptop was left on and allowed to hibernate/sleep.
Not sure what one has to do with the other.

Could it be connected to the problem where the screen can't recover from being dimmed 50%?

Revision history for this message
Night Eagle (nighteagle) wrote :

Problem seems to be that since a recent update (approx 12/4/2009, guessing 2.6.31-16 kernel or modules), b43 driver initialized in "disabled" state rather than state at shutdown. I found a workaround: I'm able to "enable wifi" on my Dell Inspiron 1501 laptop via <Fn-F2> key once booted and then I get wifi as normal. Main problem here seems to be that the b42s always initializing in "disabled" state rather than "active" or prior state at shutdown. This previously worked fine in Jaunty and Karmic until applying a small batch of recent updates that included kernel 2.6.31-16.

Interesting was that falling back to an older kernel did not fix, at least not immediately, so maybe the problem is that "active" state is not being saved (so regardless of kerel booted, starts as inactive)? Need to try boot in older kernel, activate, shutdown, reboot in same old kernel to see if this theory is holds true.

Revision history for this message
Night Eagle (nighteagle) wrote :

This does look to be a change in behavior in the b43 driver.

With 2.6.31-16, I have to manually "turn on" wifi via <Fn-F2> keypress on my laptop. Upon keypress, kernel drivers are loaded and the interface is brought up.

With 2.6.28-16 and earlier, the kernel module is loaded the interface brought up automatically.

When I initially updated to Karmic w/ kernel 2.6.31-15, i'm pretty sure wifi via b43 worked fine, just as it did in 2.6.28. Problems started with recent update that included 2.6.31-16 kernel. However, when I test now, 2.6.31-15 behaves like 2.6.31-16 -- I have to manually "turn on" wifi.

This is a pretty brutal regression for anyone afflicted, but at least there is a easy workaround.

Revision history for this message
Night Eagle (nighteagle) wrote :
Download full text (15.7 KiB)

Here are some relevant log lines from bootup (when b43 fails to activate), then I press Fn-F2 and that activates the radio properly. Looks like maybe nw-manager is trying to bring up the interface before b43 has loaded firmware.

reboot:

Dec 22 18:05:05 mecca NetworkManager: Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list.
Dec 22 18:05:05 mecca NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list.
Dec 22 18:05:05 mecca NetworkManager: <info> Found radio killswitch rfkill1 (at /sys/devices/pci0000:00/0000:00:06.0/0000:05:00.0/ssb0:0/ieee80211/phy0/rfkill1) (driver <unknown>)
Dec 22 18:05:05 mecca NetworkManager: <info> Found radio killswitch rfkill0 (at /sys/devices/virtual/rfkill/rfkill0) (driver <unknown>)
Dec 22 18:05:05 mecca NetworkManager: <info> Wireless now disabled by radio killswitch
Dec 22 18:05:05 mecca NetworkManager: SCPlugin-Ifupdown: (27727968) ... get_connections.
Dec 22 18:05:05 mecca NetworkManager: SCPlugin-Ifupdown: (27727968) ... get_connections (managed=false): return empty list.
Dec 22 18:05:05 mecca NetworkManager: Ifupdown: get unmanaged devices count: 0
Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): driver supports SSID scans (scan_capa 0x01).
Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): new 802.11 WiFi device (driver: 'b43')
Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): now managed
Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): device state change: 1 -> 2 (reason 2)

Dec 22 18:05:05 mecca kernel: [ 24.598586] b43-phy0: Broadcom 4311 WLAN found (core revision 10)
Dec 22 18:05:05 mecca kernel: [ 24.647622] cfg80211: World regulatory domain updated:
Dec 22 18:05:05 mecca kernel: [ 24.647628] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
Dec 22 18:05:05 mecca kernel: [ 24.647633] (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 22 18:05:05 mecca kernel: [ 24.647637] (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 22 18:05:05 mecca kernel: [ 24.647640] (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
Dec 22 18:05:05 mecca kernel: [ 24.647643] (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 22 18:05:05 mecca kernel: [ 24.647647] (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
Dec 22 18:05:05 mecca kernel: [ 24.781605] phy0: Selected rate control algorithm 'minstrel'
Dec 22 18:05:05 mecca kernel: [ 24.782536] Broadcom 43xx driver loaded [ Features: PL, Firmware-ID: FW13 ]

Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): bringing up device.
Dec 22 18:05:05 mecca NetworkManager: <info> (wlan0): deactivating device (reason: 2).

fn-F2 activates b43:

Dec 22 18:06:47 mecca kernel: [ 127.440167] BUG: scheduling while atomic: swapper/0/0x10010000
Dec 22 18:06:47 mecca NetworkManager: <info> Wireless now enabled by radio killswitch
Dec 22 18:06:47 mecca kernel: [ 127.440178] Modules linked in: binfm...

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.