b43: missing firmware causes kernel panic

Single user (S appended to kernel boot args)

* starting configure network device security
* starting mount network filesystems
* starting failsafe boot delay
* starting network connection manager
* stopping mount network filesystems
* starting bridge socket events into upstart
* starting bluetooth daemon
* starting configure network device
* starting configure network device security
* starting mount network filesystems
* stopping mount network filesystems
* stopping failsafe boot delay
* starting system V initialisation compatibility
* starting set sysctls from /etc/sysctl.conf
* stopping set sysctls from /etc/sysctl.conf
* starting configure network device
* starting configure network device security
* starting configure network device
[ xx.xxxx] b43-phy0 ERROR: firmware file "b43/ucode5.fw" not found
[ xx.xxxx] b43-phy0 ERROR: firmware file "b43-open/ucode5.fw" not found
[ xx.xxxx] b43-phy0 ERROR: You must go to http://wireless.kernel.org [snip] read all the instructions on this website.

throughout the boot process, i was toggling the numlock key
this responded right up to this point; it is now non-responsive.

suggest Bug #945257 bears a striking resemblence.

issue reproduces booting off usb

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

have successfully booted system by adding 'b43.blacklist=yes ' to kernel arguments

(https://help.ubuntu.com/8.04/installation-guide/sparc/boot-parms.html)

Rather than failing to find firmware, I get:

"b43: Unknown parameter 'blacklist'"

Are you trying to perform a fresh Precise install with the non-pae kernel?

12.04 is the last release that will support non-PAE. The default (and boot) kernel for 12.04 32 bit is now the PAE kernel, so there is no easy way to install a non-PAE kernel. We are only providing an upgrade path from prior releases.

Have not got as far as installation. Planned to use this machine to test 12.04.
System hangs booting off 32bit live desktop ISO; it has to be power cycled.

System only has 2gb RAM, indifferent about PAE kernel

I'd tried a couple of the alpha builds; none of those would boot this machine either.

Downloading daily precise build on the assumption that it contains the requested 3.2.0-18.28 kernel. Issue occurs booting the live ISO, so not in a position to upgrade the kernel using apt

20120308 build contains 3.2.0-18-generic-pae
Doesn't resolve issue. System hangs without the workaround in place - b43 kernel param

Now I've got a way to boot it; will do fresh precise install; defaults. Assuming issue will apply to installed kernel as well; will be able to upgrade that.

installation performed.
system hangs when rebooting; modified boot arguments to see messages; got it up with b43.blacklist=yes workaround
ran update
configured the ethernet connection
ran update
no kernel in updates; kernel wasn't in 'held back' list either. Installed everything else.

rebooted
hung: b43 firmware.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

ran apport-collect to get current 12.04 data rather than the 11.10 stuff

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc6-precise/

It hangs with the same b43 errors.
system boots with the same workaround.

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.3.0-030300rc6-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro b43.blacklist=yes

Trying some others to see when the regression occurred.

No bug.

v3.1.5-precise/ 09-Dec-2011 18:34
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.5-030105-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro

Bug

v3.2-precise/ 05-Jan-2012 02:00
3.2.0-030200-generic-pae

No bug.

v3.1.8-precise/ 06-Jan-2012 23:23
$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.8-030108-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro

Bug

v3.2-rc4-precise/ 08-Dec-2011 20:05
3.2.0-030200rc4-generic-pae

To be fair, I get no ethernet on v3.1.8 and v3.1.5 so while it boots, it's not very useful !

Some guidance would be appreciated if this is a helpful line of inquiry.

My take on it ..

I don't see the bug downstream in the 3.1 branch; so if it was in 3.1, it has been fixed in 3.1.x prior to 3.1.5. This is the earliest precise tagged 3.1.x

I've tested the earliest release of 3.2 that is tagged precise.

If this is helpful .. are any of the oneiric tagged kernels likely to work with my precise build? Or would I need to rebuild to oneiric to check further back?

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

not being presented with a new kernel, as per instructions.
maybe I'm on a slow mirror; will keep trying.

$ cat /proc/version_signature
Ubuntu 3.2.0-18.28-generic-pae 3.2.9
$ sudo apt-get update >/dev/null
$ sudo apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages have been kept back:
  empathy empathy-common nautilus-sendto-empathy
The following packages will be upgraded:
  libvisual-0.4-plugins update-notifier update-notifier-common usb-creator-common usb-creator-gtk
5 upgraded, 0 newly installed, 0 to remove and 3 not upgraded.
Need to get 271 kB of archives.
After this operation, 0 B of additional disk space will be used.
Do you want to continue [Y/n]?

The kernel package can be installed specifically with:

sudo apt-get update
sudo apt-get install linux

or

sudo apt-get update
sudo apt-get dist-upgrade

it turned up this evening.
however, it still hangs with the same firmware issue.

$ cat /proc/version_signature /proc/cmdline
Ubuntu 3.2.0-18.29-generic-pae 3.2.9
BOOT_IMAGE=/vmlinuz-3.2.0-18-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro b43.blacklist=yes

any comments / thoughts on #32, #33, #34 ?

upgraded kernel.
still hangs.

$ cat /proc/version_signature /proc/cmdline
Ubuntu 3.2.0-19.30-generic-pae 3.2.11
BOOT_IMAGE=/vmlinuz-3.2.0-19-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro b43.blacklist=yes

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

Hi Ben,

The final version of upstream v3.3 is available. Would it be possible for you to test this kernel before we bisect to find the bad commit? The kernel can be downloaded from:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

still hangs.

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.3.0-030300-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro b43.blacklist=yes

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

didn't find 3.2.0-19.31 in repos; Found 20.32
doesn't work

$ cat /proc/version_signature /proc/cmdline
Ubuntu 3.2.0-20.32-generic-pae 3.2.12
BOOT_IMAGE=/vmlinuz-3.2.0-20-generic-pae root=UUID=a0ffacd5-d56c-4c11-88ac-255c7ddbd346 ro b43.blacklist=yes

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

rebuilt with oneiric to try older kernels

$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=11.10
DISTRIB_CODENAME=oneiric
DISTRIB_DESCRIPTION="Ubuntu 11.10"

$ cat /proc/version_signature /proc/cmdline
Ubuntu 3.0.0-16.29-generic 3.0.20
BOOT_IMAGE=/vmlinuz-3.0.0-16-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.4-030104-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.0-030100-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.0.0-0300-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.5-030105-generic-pae root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.5-030105-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.3.0-030300-generic-pae root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro b43.blacklist=yes

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.3.0-030300-generic-pae root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro b43.blacklist=yes

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-030200-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro b43.blacklist=yes

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-030200rc4-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro b43.blacklist=yes

$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-030200rc2-generic root=UUID=ee8d8fac-4004-4e28-a442-b0c4357c9631 ro b43.blacklist=yes

So, to summarise ..

bug not present:
vmlinuz-3.1.0-030100-generic

bug present:
vmlinuz-3.2.0-030200rc2-generic

bug is also still present in the final release 3.3.0

I am assuming that the development tree runs 3.1-rc10 -> 3.1.0 -> 3.2-rc1 ...

I couldn't test
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.2-rc1-oneiric/

because there's no 32bit build

will need to rebuild system to test precise kernels.

We can perform a bisect to narrow down when the regression was introduced.

Also, this issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

I've searched for a kernel bug and didn't find a single hit for b43.

Further digging suggests a better way to get support.
http://linuxwireless.org/en/users/Drivers/b43#Bug_reporting

Now have an account at the kernel bugzilla ready to roll if needed.

posted to their mailing list
http://lists.infradead.org/pipermail/b43-dev/2012-March/002458.html

Whoops, accidentally changed the status of the bug. Can it be changed back?

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get dist-upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

There were some duplicates of this bug, e.g. #956677. I've marked that one as duplicate.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/950295

Hi Ben,

I noticed the following message on the upstream mailing list:
http://lists.infradead.org/pipermail/b43-dev/2012-March/002462.html

In that message you said you installed Ubuntu's b43 firmware package and rebooted into the 3.2.0-rc2 kernel, which resolved the issue. So did you install the v43 firmware from Oneiric and using that with Precise solves the problem?

It would appear that if the firmware is present, the kernel doesn't hang. The 'invalid argument' path through the code also doesn't trigger the hang. Only the 'no firmware' path is a problem.

I have downgraded to oneiric so I could try the older mainline kernels that hadn't been tagged for precise. I've been away, so haven't had time to rebuild to precise.

3.2.0-rc2 is the oldest kernel I've found with the bug (the stock oneiric being older and so not buggy)
I used that one to test the effect of having firmware in place.

A generic workaround would appear to be

* bootstrap off the iso
* add 'b43.blacklist=yes' to the kernel args
* install
* reboot off the hard disk, adding the kernel argument to stop it hanging
* install the firmware

Or chroot etc., but this is less challenging.

I'll download the latest ISO, rebuild to precise, and will confirm.

I have a suspicion about this. If I'm right this will be a regression introduced in 3.2, so an easy first test is to install the 3.1 mainline build from the link below and see if the problem is present there. Please give that a try and report back the results. Thanks!

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.1-oneiric/

Already tested.

See #47. Kernels with 'b43.blacklist=yes' in the command line are broken, kernels without it booted fine.

I can only narrow it down this far:

bug not present:
vmlinuz-3.1.0-030100-generic

bug present:
vmlinuz-3.2.0-030200rc2-generic

There's no mainline 32bit rc1 mainline kernel built for me to test.

I've rebuilt the machine with precise this evening; I can pop on the 3.1.0 kernel tomorrow or thursday.

strike that; i've already got it downloaded.
here's precise with the 3.1.0 kernel; booting fine with the b43 module loading.

ben@tecumseh:~$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu 12.04 LTS"
ben@tecumseh:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.1.0-030100-generic root=UUID=ec1fde3e-cf25-49df-a729-b4e2b01281eb ro
ben@tecumseh:~$ lsmod | grep b43
b43 322846 0
mac80211 405552 1 b43
cfg80211 167429 2 b43,mac80211
bcma 20232 1 b43
ssb 46176 2 b43,b44
ben@tecumseh:~$ dmesg | grep b43
[ 2.344843] b43-pci-bridge 0000:06:02.0: enabling device (0000 -> 0002)
[ 2.344877] b43-pci-bridge 0000:06:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 2.344897] b43-pci-bridge 0000:06:02.0: setting latency timer to 64
[ 17.124612] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[ 17.300035] Registered led device: b43-phy0::tx
[ 17.300122] Registered led device: b43-phy0::rx
[ 17.300188] Registered led device: b43-phy0::radio
[ 19.839269] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
[ 19.839345] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
[ 19.839415] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

Great, so far so good.

I've posted a build now with a proposed fix for what I suspect causes the problem. Please give it a try.

http://people.canonical.com/~sforshee/lp950295/linux-3.2.0-23.36~lp950295v201204241909/

That works for me!

ben@tecumseh:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-23-generic-pae root=UUID=ec1fde3e-cf25-49df-a729-b4e2b01281eb ro
ben@tecumseh:~$ lsmod | grep b43
b43 342643 0
mac80211 436455 1 b43
cfg80211 178679 2 b43,mac80211
bcma 25651 1 b43
ssb 50691 2 b43,b44
ben@tecumseh:~$ dmesg | grep b43
[ 15.190301] b43-pci-bridge 0000:06:02.0: enabling device (0000 -> 0002)
[ 15.190332] b43-pci-bridge 0000:06:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 15.190348] b43-pci-bridge 0000:06:02.0: setting latency timer to 64
[ 16.153841] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[ 16.366988] Registered led device: b43-phy0::tx
[ 16.367133] Registered led device: b43-phy0::rx
[ 16.370857] Registered led device: b43-phy0::radio
[ 17.293844] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
[ 17.293923] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
[ 17.293995] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.

And to confirm it is your fix, as a control, I then upgraded and found the live -23.36 kernel which is in the repositories ..

root@tecumseh:~# apt-get upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be upgraded:
  linux-headers-3.2.0-23 linux-headers-3.2.0-23-generic-pae
  linux-image-3.2.0-23-generic-pae sessioninstaller
4 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 50.2 MB of archives.
After this operation, 181 kB of additional disk space will be used.
Do you want to continue [Y/n]?

[snip]

Preparing to replace linux-image-3.2.0-23-generic-pae 3.2.0-23.36~lp950295v201204241909 (using .../linux-image-3.2.0-23-generic-pae_3.2.0-23.36_i386.deb) ...
Done.
Unpacking replacement linux-image-3.2.0-23-generic-pae ...
Examining /etc/kernel/postrm.d .
run-parts: executing /etc/kernel/postrm.d/initramfs-tools 3.2.0-23-generic-pae /boot/vmlinuz-3.2.0-23-generic-pae
run-parts: executing /etc/kernel/postrm.d/zz-update-grub 3.2.0-23-generic-pae /boot/vmlinuz-3.2.0-23-generic-pae
Preparing to replace linux-headers-3.2.0-23 3.2.0-23.36~lp950295v201204241909 (using .../linux-headers-3.2.0-23_3.2.0-23.36_all.deb) ...
Unpacking replacement linux-headers-3.2.0-23 ...
Preparing to replace linux-headers-3.2.0-23-generic-pae 3.2.0-23.36~lp950295v201204241909 (using .../linux-headers-3.2.0-23-generic-pae_3.2.0-23.36_i386.deb) ...
Unpacking replacement linux-headers-3.2.0-23-generic-pae ...
Preparing to replace sessioninstaller 0.20+bzr123-0ubuntu2 (using .../sessioninstaller_0.20+bzr128-0ubuntu1_all.deb) ...
Unpacking replacement sessioninstaller ...

[snip]

.. rebooted, and it hung.

I'm running here with the workaround.

ben@tecumseh:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-23-generic-pae root=UUID=ec1fde3e-cf25-49df-a729-b4e2b01281eb ro b43.blacklist=yes
ben@tecumseh:~$ lsmod | grep b43
ben@tecumseh:~$

Awesome. Let me know when the fix is all integrated; I'll download the daily ISO and test it :D

Great, thanks for testing!

I've sent the fix to the maintainers of the driver to make sure they agree with my solution. I'll work on getting the fix into precise once I hear back.

Patch added to wireless-testing

This bug was fixed in the package linux - 3.4.0-1.3

---------------
linux (3.4.0-1.3) quantal; urgency=low

  [ Andy Whitcroft ]

  * [Config] control.stub is an intermediate product not a dependancy
    - LP: #992414

  [ Leann Ogasawara ]

  * remove i386 generic from getabis

  [ Upstream Kernel Changes ]

  * (pre-stable) b43: only reload config after successful initialization
    - LP: #950295
 -- Leann Ogasawara <email address hidden> Wed, 02 May 2012 09:48:14 -0700

What Linux kernel package was the LTS rolled out with?

Precise released with 3.2.0-23.36 and is currently at 3.2.0-24.37. The kernel that's been fixed is for quantal. The fix is queued for precise, but it takes longer to get the fix into a stable release.

I am testing Quantal (as long as it does not break overly much)
I have linux-image-3.4.0-1-generic 3.4.0-1.3 and still need to add b43.blacklist=yes to the kernel command line.
With kernel 3.2.0-24 it worked perfectly without that.
My system is Acer 1830T with Broadcom BCM43225 802.11b/g/n
Working module is brcmsmac, non-working is b43.
Why add this breakage ?
Is there any migration from brcmsmac to b43 in the plans ?

@ Wladimir: no. That b43 gets loaded instead of brcmsmac is probably a bug in your 3.4 kernel.

Wladimir: What you're reporting is off-topic for this bug. It is a problem, and I'll see that it gets fixed, but next time I'd suggest you open a new bug as off-topic comments on bugs are likely to be ignored.

Same bug in Linux Mint 13 RC.

This bug is awaiting verification that the kernel for precise in -proposed solves the problem (3.2.0-25.40). Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-precise' to 'verification-done-precise'.

If verification is not done by one week from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

Ben Prescott (or someone else affected by this bug), could you please verify that this bug is solved with the kernel referred in comment #74?

I could do a test, but I don't know how to verify it. In the meantime I have the b43 firmware installed, so this is not a problem now. Can you give instructions how to reproduce this bug without breaking anything else, and how to verify if the new kernel has fixed it?

Probably the easiest way to test is to temporarily move the /lib/firmware/b43 directory to another location, then run 'sudo modprobe -r b43; sudo modprobe b43'. When your done you can move the directory back to its original location.

Another way would be to remove linux-firmware-nonfree before running the modprobe commands. The disadvantage of this is that you may need to use a wired connection to reinstall the package.

I'm sorry but I cannot reproduce this issue on my PPC iMac with kernel 3.2.0-24-powerpc64-smp.
I had this problem only on first install from install cd.

ack. just upgrading, it seems, every other package on the affected machine. firmware hasn't been installed, so easy to test.

grumble: this bug doesn't appear in my lists of subscribed, affecting, commented, or reported bugs ...

gottit. 'fixed released' isn't included by default.

kernel tested. looks good.

ben@tecumseh:~$ dmesg | egrep 'b43|3.2.0-25.40'
[ 0.000000] Linux version 3.2.0-25-generic-pae (buildd@palmer) (gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5) ) #40-Ubuntu SMP Wed May 23 22:11:24 UTC 2012 (Ubuntu 3.2.0-25.40-generic-pae 3.2.18)
[ 13.215120] b43-pci-bridge 0000:06:02.0: enabling device (0000 -> 0002)
[ 13.215153] b43-pci-bridge 0000:06:02.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22
[ 13.215168] b43-pci-bridge 0000:06:02.0: setting latency timer to 64
[ 13.999034] b43-phy0: Broadcom 4318 WLAN found (core revision 9)
[ 14.207510] Registered led device: b43-phy0::tx
[ 14.207585] Registered led device: b43-phy0::rx
[ 14.207656] Registered led device: b43-phy0::radio
[ 18.918132] b43-phy0 ERROR: Firmware file "b43/ucode5.fw" not found
[ 18.918212] b43-phy0 ERROR: Firmware file "b43-open/ucode5.fw" not found
[ 18.918285] b43-phy0 ERROR: You must go to http://wireless.kernel.org/en/users/Drivers/b43#devicefirmware and download the correct firmware for this driver version. Please carefully read all instructions on this website.
ben@tecumseh:~$ cat /proc/cmdline
BOOT_IMAGE=/vmlinuz-3.2.0-25-generic-pae root=UUID=ec1fde3e-cf25-49df-a729-b4e2b01281eb ro

I stll have this problem in Ubuntu 12.10 alpha1 amd64

@Alessandro

Can you open a new bug for 12.10(Quantal)?

@Josph

Here my new bug for 12.10(Quantal), as you asked. I hope it is OK.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1012281

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.