Such a condition is not needed when b43 is a module as the user-space The problem is that user space is not yet started when b43 asks for theįirmware. Usual solution to switch to asynchronous firmware loading is a poor option forī43 as it loads multiple firmware files, and the number depends on the model.Īccordingly, I selected a solution that initiates the firmware load from a work Loads fail when the firmware loading is initiated from the probe routine. Recent modifications in udev make synchronous firmware I was able to reproduce your result when b43 is built into the kernel, and it I don't know if it matters, but b43 is statically compiled in the kernel. The only obvious change is 6b6fa5868eec26bdc6a83543cebb8cf832a2645a by Larryįinger. This is from Debian's firmware-b43-installer package, version 1:015-14.Ġ2:00.0 Network controller : Broadcom Corporation BCM4322 802.11a/b/g/n Here's the firmware it claims doesn't exist:
I'm probably missing something obvious, but when going from 3.3 to 3.4 the b43ĭriver throws up an error, saying it can't find the firmware - but it reallyī43-phy0 ERROR: Firmware file 'b43/ucode16_mimo.fw' not foundī43-phy0 ERROR: Firmware file 'b43-open/ucode16_mimo.fw' not foundĬorrect firmware for this driver version.
