Latest upgrade from 2.6.22-13 to 2.6.22-14 Ubuntu Gutsy Beta makes Broadcom WLAN stop working

[andreasg]

Binary package hint: bcm43xx-fwcutter

Not sure about the correct package above!

The following happened:
Yesterday wireless worked OK (2.6.22-13-generic kernel). Then I installed yesterdays update and after restart with new kernel 2.6.22-14 my broadcom wireless nic 4318/4319 stopped working. Iwconfig says Access point invalid.

Confirmed that it stills works by booting with 2.6.22.13-kernel still.

Hardware is a HP Pavillion DV8000 with onboard broadcom nic.

[andreasg (andreas-goransson-itg)]

Looked into the issue about firmware in /lib/firmware mentioned in other similar reports.
In /lib/firmware is bcm43xx_microcode11.fw .

In /lib/firmware/2.6.22-13-generic (the version of the working update/kernel) is the following files related to bcm:
andreas@andreas-laptop:/lib/firmware/2.6.22-13-generic$ ls | grep bcm
bcm43xx_initval01.fw
bcm43xx_initval02.fw
bcm43xx_initval03.fw
bcm43xx_initval04.fw
bcm43xx_initval05.fw
bcm43xx_initval06.fw
bcm43xx_initval07.fw
bcm43xx_initval08.fw
bcm43xx_initval09.fw
bcm43xx_initval10.fw
bcm43xx_microcode11.fw
bcm43xx_microcode2.fw
bcm43xx_microcode4.fw
bcm43xx_microcode5.fw
bcm43xx_pcm4.fw
bcm43xx_pcm5.fw

In the /lib/firmware/2.6.22-14-generic is the following files related to bcm:
andreas@andreas-laptop:/lib/firmware/2.6.22-14-generic$ ls | grep bcm
andreas@andreas-laptop:/lib/firmware/2.6.22-14-generic$

[andreasg (andreas-goransson-itg)]

Update was done through automatic updating, launched by clicking the update available icon.

The issued was resolved by copying all files beginning with bcm from /lib/firmware/2.6.22-13-generic to /lib/firmware/2.6.22-14-generic. Wlan-card worked after reboot and booting in 2.6.22-14-generic. Seems to be an issue about installed firmware not being moved to new directory when upgrading?

[Launchpad Janitor (janitor)]

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!