Ubuntu
linux-restricted-modules package

missing firmware for bcm2033

Bug #64792 reported by Dan Lipsitt
6
Affects Status Importance Assigned to Milestone
linux-restricted-modules (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

I have a bluetooth dongle that uses the bcm2033 chipset. When I plug it in, I get the following in /var/log/syslog:

10/09/2006 12:52:12 AM localhost kernel [17183624.308000] usb 2-7.3: new full speed USB device using ehci_hcd and address 4
10/09/2006 12:52:13 AM localhost firmware_helper[5934] main: error loading '/lib/firmware/BCM2033-MD.hex' for device '/class/firmware/2-7.3' with driver 'usb'
10/09/2006 12:52:13 AM localhost kernel [17183624.400000] usb 2-7.3: configuration #1 chosen from 1 choice
10/09/2006 12:52:13 AM localhost kernel [17183624.436000] bcm203x_probe: Mini driver request failed
10/09/2006 12:52:13 AM localhost kernel [17183624.436000] bcm203x: probe of 2-7.3:1.0 failed with error -5

The command "find /lib/firmware -iname '*bcm*'" turns up nothing. The necessary file is available in the following packages:

http://bluez.sourceforge.net/download/bluez-firmware-1.2.tar.gz
http://packages.debian.org/unstable/admin/bluez-firmware

Ubuntu appears not to have this package.

There is also a package called http://bluez.sourceforge.net/download/debian/bluez-bcm203x_2.10-5_i386.deb , but I think it is related to kernel 2.4.

Revision history for this message
Dan Lipsitt (danlipsitt) wrote :

bluez-firmware_1.2-1_all.deb puts the driver in /usr/lib/firmware/ rather than /lib/firmware/. When I create a symlink the driver loads.

Revision history for this message
Onkar Shinde (onkarshinde) wrote :

Looking at the debian copyright file, it should be possible to include 'bluez-firmware' in restricted repository.

Can someone confirm?

Revision history for this message
Eugenia Loli-Queru (eloli) wrote :

Yes, please include the firmwares on restricted.

Revision history for this message
Rodrigo Donado (frezeeer) wrote :

Hi I move the files as Dan Lipsitt said:
"find /lib/firmware -iname '*bcm*'"
/lib/firmware/2.6.20-15-386/BCM2033-MD.hex
/lib/firmware/2.6.20-15-386/BCM-LEGAL.txt
/lib/firmware/2.6.20-15-386/BCM2033-FW.bin

still nothing happens:
hcitool dev
Devices:

Any ideas?

Revision history for this message
Michael Hackett (at217) wrote :

Rodrigo,

It appears that the files must be right in the /lib/firmware directory, not in one of the kernel-specific subdirectories.

This raises a question: if Ubuntu is not going to include these files in a package, and the Debian package puts the files in an incompatible location, the proper place for user-installed files would probably be /usr/local/lib/firmware. But whatever it is that is looking for the firmware in this case does not appear to check that location. Should that be filed as a bug? And against which package?

Revision history for this message
Michael Hackett (at217) wrote :

Oops, my mistake. I forgot that I am still running dapper on the system that I did this on. I cannot say if the same is still true for feisty or later versions. I will be upgrading it soon and will check again.

Revision history for this message
Daniel T Chen (crimsun) wrote :

Available in 8.10 alpha.

Changed in bluez-utils:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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