OK. Picking this up again as it's not working again - not quite sure when it broke.
The driver for the bluetooth thumb is bcm203x. When booting I get this (dmesg | grep bcm)
[ 12.981820] bcm203x_probe: Mini driver request failed [ 12.981831] bcm203x: probe of 1-2:1.0 failed with error -5
Strings on the binary driver reveals these interesting strings:
firmware=BCM2033-FW.bin firmware=BCM2033-MD.hex
I have some files _almost_ named that:
# locate BCM2033-FW (nothing) # locate bcm2033-fw /lib/firmware/bcm2033-fw.bin # locate bcm2033-md /lib/firmware/bcm2033-md.bin # dpkg -S /lib/firmware/bcm2033-md.bin /lib/firmware/bcm2033-fw.bin linux-firmware: /lib/firmware/bcm2033-md.bin linux-firmware: /lib/firmware/bcm2033-fw.bin # dpkg -l | grep restricted-modules-2.6.27-9 ii linux-restricted-modules-2.6.27-9-generic 2.6.27-9.13 Non-free Linux kernel modules for version 2.
So yes, we can rule out the restricted-modules package as source for this firmware.
# apt-cache policy linux-firmware linux-firmware: Installed: 1.2 Candidate: 1.2 Version table: *** 1.2 0 500 http://no.archive.ubuntu.com intrepid/main Packages 100 /var/lib/dpkg/status
That's good then.
Hum, the casing...
# cd /lib/firmware/ # ln -s bcm2033-fw.bin BCM2033-FW.bin # less bcm2033-md.bin (The file looks like it's hex code) # ln -s bcm2033-md.bin BCM2033-MD.hex # modprobe -rv bcm203x rmmod /lib/modules/2.6.27-9-generic/kernel/drivers/bluetooth/bcm203x.ko # modprobe -v bcm203x insmod /lib/modules/2.6.27-9-generic/kernel/drivers/bluetooth/bcm203x.ko # dmesg | tail [1405602.103828] firmware: requesting BCM2033-MD.hex [1405602.105783] firmware: requesting BCM2033-FW.bin [1405602.107804] bcm203x_probe: Firmware request failed [1405602.107814] bcm203x: probe of 1-2:1.0 failed with error -5 [1405602.107843] usbcore: registered new interface driver bcm203x [1405621.780508] usbcore: deregistering interface driver bcm203x
[1405627.253211] Bluetooth: Broadcom Blutonium firmware driver ver 1.2 [1405627.253830] firmware: requesting BCM2033-MD.hex [1405627.256246] firmware: requesting BCM2033-FW.bin [1405627.270019] usbcore: registered new interface driver bcm203x
We seem to have a winner! Looks like there is a packaging problem in linux-firmware - modifying the package name for this bug. Hope the right people will get time to fix this.
Regards, Nicolai
OK. Picking this up again as it's not working again - not quite sure when it broke.
The driver for the bluetooth thumb is bcm203x. When booting I get this (dmesg | grep bcm)
[ 12.981820] bcm203x_probe: Mini driver request failed
[ 12.981831] bcm203x: probe of 1-2:1.0 failed with error -5
Strings on the binary driver reveals these interesting strings:
firmware= BCM2033- FW.bin BCM2033- MD.hex
firmware=
I have some files _almost_ named that:
# locate BCM2033-FW bcm2033- fw.bin bcm2033- md.bin bcm2033- md.bin /lib/firmware/ bcm2033- fw.bin bcm2033- md.bin bcm2033- fw.bin modules- 2.6.27- 9 d-modules- 2.6.27- 9-generic 2.6.27-9.13 Non-free Linux kernel modules for version 2.
(nothing)
# locate bcm2033-fw
/lib/firmware/
# locate bcm2033-md
/lib/firmware/
# dpkg -S /lib/firmware/
linux-firmware: /lib/firmware/
linux-firmware: /lib/firmware/
# dpkg -l | grep restricted-
ii linux-restricte
So yes, we can rule out the restricted-modules package as source for this firmware.
# apt-cache policy linux-firmware no.archive. ubuntu. com intrepid/main Packages dpkg/status
linux-firmware:
Installed: 1.2
Candidate: 1.2
Version table:
*** 1.2 0
500 http://
100 /var/lib/
That's good then.
Hum, the casing...
# cd /lib/firmware/ 2.6.27- 9-generic/ kernel/ drivers/ bluetooth/ bcm203x. ko 2.6.27- 9-generic/ kernel/ drivers/ bluetooth/ bcm203x. ko
# ln -s bcm2033-fw.bin BCM2033-FW.bin
# less bcm2033-md.bin
(The file looks like it's hex code)
# ln -s bcm2033-md.bin BCM2033-MD.hex
# modprobe -rv bcm203x
rmmod /lib/modules/
# modprobe -v bcm203x
insmod /lib/modules/
# dmesg | tail
[1405602.103828] firmware: requesting BCM2033-MD.hex
[1405602.105783] firmware: requesting BCM2033-FW.bin
[1405602.107804] bcm203x_probe: Firmware request failed
[1405602.107814] bcm203x: probe of 1-2:1.0 failed with error -5
[1405602.107843] usbcore: registered new interface driver bcm203x
[1405621.780508] usbcore: deregistering interface driver bcm203x
[1405627.253211] Bluetooth: Broadcom Blutonium firmware driver ver 1.2
[1405627.253830] firmware: requesting BCM2033-MD.hex
[1405627.256246] firmware: requesting BCM2033-FW.bin
[1405627.270019] usbcore: registered new interface driver bcm203x
We seem to have a winner! Looks like there is a packaging problem in linux-firmware - modifying the package name for this bug. Hope the right people will get time to fix this.
Regards,
Nicolai