bcm43xx: firmware needs to be cut again if user upgrades kernel

Bug #138400 reported by Matteo Z
52
Affects Status Importance Assigned to Milestone
Restricted Manager
Won't Fix
Wishlist
Unassigned
jockey (Ubuntu)
Fix Released
Undecided
Unassigned
linux-restricted-modules-2.6.22 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

When a user upgrades to a new kernel version, the system will not move or rebuild the bcm43xx firmware, which is installed using the Restricted Manager interface. The user should not lose his network connection this way when upgrading a stable system.

Matteo Z (matteozandi)
Changed in restricted-manager:
importance: Undecided → Wishlist
description: updated
Revision history for this message
Martin Böhm (martin.bohm) wrote :

Is there a way to store the firmware file(s) in such a way that the upgrade won’t ignore the currently installed firmware (installed via restricted manager) ?

Revision history for this message
Martin Böhm (martin.bohm) wrote :

I have set linux-restricted-modules-2.6.22 as a possible "also affected" package. Restricted-manager should not really care about the firmware once it is installed (in Ubuntu). Please change the package if you feel that it should belong elsewhere.

Revision history for this message
none (ubuntu-bugs-nullinfinity-deactivatedaccount) wrote :

linux-restricted-modules-2.6.22 does not contain any files related to this bug.

The fix would be to make sure restricted-manager downloads the firmware to /lib/firmware instead of a subdirectory of /lib/firmware. If someone's feeling industrious, the file to change is /usr/lib/python2.5/site-packages/RestrictedManager/handlers/bcm43xx.py . But beware that right now restricted-manager writes a fake bcm43xx_microcode11.fw file into /lib/firmware.

Revision history for this message
Sandip Bhattacharya (sandipb) wrote :

Why is this on wishlist? This is a serious bug if you ask me.

Revision history for this message
Marco Scholl (traxanos) wrote :

i thik this is a big problem and it should be a bug

Revision history for this message
All Yours (sjy22kr) wrote :

Martin,

The following does the trick for me:

sudo cp /lib/firmware/`uname -r`/bcm43* /lib/firmware

This must be done after having installed the firmware via the Restricted Driver Manager.

Good Luck,

Revision history for this message
Martin Pitt (pitti) wrote :

restricted-manager has been superseded by 'jockey' in Ubuntu Hardy (a complete redesign and rewrite). Juggling tasks.

Changed in linux-restricted-modules-2.6.22:
status: New → Invalid
Changed in restricted-manager:
status: New → Won't Fix
Revision history for this message
Martin Pitt (pitti) wrote :

jockey uses b43-fwcutter now, which puts the firmware into a kernel ABI independent directory.

Changed in jockey:
status: New → Fix Released
Revision history for this message
f37u5g0d (enovak) wrote :

I experienced this problem exactly. When I tried to use the hardware drivers utility it attempted to re-install the restricted driver. It first tried to download a file. It failed and froze/crashed. I then found a set of instructions at http://www.linuxwireless.org/en/users/Drivers/b43#devicefirmware This got my wireless back but I am unable to actually connect to a network (although I think my internet [here at school] might be down). Not really sure.

Revision history for this message
f37u5g0d (enovak) wrote :

This morning I downloaded "Windows Wireless Drivers" from the add/remove applications. I restarted and without doing anything to restricted drivers (I don't even have it anymore for some reason) I have wireless again after restarting. I don't really know why it worked or if it will work with other machines but all I know is that I got ndiswrapper to work for a 4306 under 8.04 using nothing but add/remove applications.

Revision history for this message
Marion Schroefl (marion-webbutterfly) wrote :

My Wlan, Broadcom on HP-Mini 2133, works with no restricted driver on 2.6.27-9 out of the box
after upgrade to 2.6.27-11... no Wlan exist.. only I see me card by "lspci"
Broadcom Corporation BCM4312
When I boot in to the previous Kernel (2.6.27-9), works fine...

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.