bcm203x firmware improperly capitalized

Bug #156133 reported by janl
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux-firmware (Ubuntu)
Fix Released
Low
Tim Gardner
Intrepid
Won't Fix
Low
Stefan Bader
Jaunty
Fix Released
Low
Tim Gardner
Karmic
Fix Released
Low
Tim Gardner

Bug Description

Hi,

My Feisty (x86_64) lacks the bluez-firmware package needed to get my broadcom bluetooth thumb going.

I subscribe to "main restricted universe multiverse". I found the package in debian, in the non-free repo for all architectures. This package seems to work fine.

Regards,
  Nicolai

Revision history for this message
Justin Dugger (jldugger) wrote :

Can someone affected by this bug please attach the results of the following commands (while the bluetooth adapter is plugged in) ?

* uname -a > uname-a.log

* cat /proc/version_signature > version.log

* dmesg > dmesg.log

* sudo lspci -vvnn > lspci-vvnn.log

* sudo lsusb -v > lsusb-v.log

Revision history for this message
Justin Dugger (jldugger) wrote :

Incomplete until adequate logs are provided confirming the bug

Changed in bluez-utils:
status: New → Incomplete
Revision history for this message
janl (janl) wrote :

The machine in question now has a broken onboard videocard and my replacement machine runs 32 bit hardy. Still with the same bluetooth thumb though. lsusb-v.log attached.

I have no machines running 64 bit OS at this time.

Nicolai

Michael Nagel (nailor)
Changed in bluez-utils:
status: Incomplete → New
Revision history for this message
Onkar Shinde (onkarshinde) wrote :

The firmware is included in linux-restricted-modules package. Can you please install that and see if your bluetooth dongle works.

Revision history for this message
Justin Dugger (jldugger) wrote :

Marked incomplete until linux-restricted-modules is ruled out as sufficient

Changed in bluez-utils:
status: New → Incomplete
Revision history for this message
janl (janl) wrote :

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

Daniel T Chen (crimsun)
Changed in linux-firmware:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Low
status: Incomplete → Triaged
Revision history for this message
Pete Graner (pgraner) wrote :

I'm cleaning up the firmware package, I get this one while I'm in there.

Changed in linux-firmware:
assignee: ubuntu-kernel-team → pgraner
milestone: none → jaunty-alpha-6
assignee: nobody → stefan-bader-canonical
importance: Undecided → Low
milestone: none → intrepid-updates
status: New → Triaged
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Uploaded linux-firmware_1.9

Changed in linux-firmware:
assignee: pgraner → timg-tpi
status: Triaged → Fix Released
Stefan Bader (smb)
Changed in linux-firmware:
status: Triaged → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote :

This doesn't seem to be a regression of hardy to intrepid or anything like that. Therefore I'm hesitant to accept this into stable, since suddenly enabling that driver could have unwanted side effects and changes behaviour (or it could even not work and crash your kernel).

It does not really fit the SRU criteria.

Please let me know if you disagree, then we can reopen this.

Changed in linux-firmware:
status: Fix Committed → Won't Fix
Revision history for this message
janl (janl) wrote : Re: [Bug 156133] Re: bcm203x firmware improperly capitalized

Martin Pitt wrote:
> This doesn't seem to be a regression of hardy to intrepid or anything
> like that. Therefore I'm hesitant to accept this into stable, since
> suddenly enabling that driver could have unwanted side effects and
> changes behaviour (or it could even not work and crash your kernel).

It has been broken for years in release after release it appears.

> It does not really fit the SRU criteria.

Read them now. I have to agree.

> ** Changed in: linux-firmware (Ubuntu Intrepid)
> Status: Fix Committed => Won't Fix

Forward to jaunty?

Nicolai

Revision history for this message
Justin Dugger (jldugger) wrote :

It should already be fixed in Jaunty.

Revision history for this message
Fredrik Olofsson (frol-hupp) wrote :

On my just installed Karmic, linux-firmware ships the firmware with all CAPS:

/lib/firmware# dpkg -S /lib/firmware/BCM2033-FW.BIN /lib/firmware/BCM2033-MD.BIN
linux-firmware: /lib/firmware/BCM2033-FW.BIN
linux-firmware: /lib/firmware/BCM2033-MD.BIN

the kernel requests the firmware with the extension in non caps:

[ 2034.337633] usb 5-2: firmware: requesting BCM2033-MD.hex
[ 2034.343046] usb 5-2: firmware: requesting BCM2033-FW.bin

So I guess this bug (or a reincarnation of it) is still present.

Then again, I can't get my Bluetooth dongle to work reliably anyway. But after renaming the files, at least the firmware loads.

/Fredrik

Revision history for this message
Tim Gardner (timg-tpi) wrote :

SRU Justification

Impact: Firmware won't load
Fix: Name the firmware file with the correct alphanumeric case.
Patch: http://kernel.ubuntu.com/git?p=ubuntu/linux-firmware-karmic.git;a=commit;h=f921956e1ecfd0a4b2832b9958b3a80ab185a6ea

Changed in linux-firmware (Ubuntu Karmic):
assignee: nobody → Tim Gardner (timg-tpi)
importance: Undecided → Low
milestone: none → karmic-updates
status: New → Fix Committed
Revision history for this message
Fredrik Olofsson (frol-hupp) wrote :

Sorry I wasn't completely correct in my previous comment. The extensions are requested in lower case as I wrote, but the BCM2033-MD.hex should have ".hex" instead of ".bin".

Thanks
/Fredrik

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

Tim, can you please reupload without using some weird -v option? The current upload's source.changes includes all changelogs it ever had, which will look confusing. Thanks!

Revision history for this message
Tim Gardner (timg-tpi) wrote :

Martin - done, though I used the same '-v' option that I use for the kernel package.

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

Tim Gardner [2009-11-09 13:39 -0000]:
> Martin - done

Thanks, looks fine now.

> though I used the same '-v' option that I use for the kernel package.

That might have been the very problem, since linux-firmware has a
completely different versioning scheme. :-) Usually you shouldn't need
-v at all, just for including several past changelog records; this
only happens during merges at the start of the cycle, or when stacking
several -proposed uploads on top of each other when the previous
versions didn't reach -updates yet.

Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted linux-firmware into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

tags: added: verification-needed
Revision history for this message
Martin Pitt (pitti) wrote :

Since lucid and karmic have the same linux-firmware package, I don't think that this is fixed in lucid yet. I'll copy the karmic-propsoed package to lucid once it built.

Changed in linux-firmware (Ubuntu):
milestone: jaunty-alpha-6 → none
status: Fix Released → In Progress
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Martin - I'm redoing the Lucid linux-firmware package so that its based on David Woodhouse's firmware repository. Its format is somewhat different, and BCM2033-FW does not yet exist in his repo.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 1.25

---------------
linux-firmware (1.25) karmic-proposed; urgency=low

  * Rename BCM2033 firmware files with lower case extension
    -LP: #156133
 -- Tim Gardner <email address hidden> Sat, 07 Nov 2009 08:19:30 -0700

Changed in linux-firmware (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
Martin Pitt (pitti) wrote :

copied karmic-proposed to lucid.

Changed in linux-firmware (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Fredrik Olofsson (frol-hupp) wrote : Re: [Bug 156133] Re: bcm203x firmware improperly capitalized

I don't think the patch is correct. Sorry, but I wasn't completely
correct in my first report of this bug, I tried to make you aware of
it. The BCM2033-MD.hex file should have ".hex" instead of ".bin"
extension.

https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/156133/comments/14

/Fredrik

On Mon, Nov 23, 2009 at 09:27:41AM -0000, Martin Pitt wrote:
> copied karmic-proposed to lucid.
>
> ** Changed in: linux-firmware (Ubuntu)
> Status: In Progress => Fix Released
>
> --
> bcm203x firmware improperly capitalized
> https://bugs.launchpad.net/bugs/156133
> You received this bug notification because you are a direct subscriber
> of the bug.

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

Reopening then.

Changed in linux-firmware (Ubuntu):
status: Fix Released → Triaged
Changed in linux-firmware (Ubuntu Karmic):
status: Fix Released → Triaged
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Upload linux-firmware_1.26 with the naming fix. I verified it against kernel sources.

Changed in linux-firmware (Ubuntu Karmic):
status: Triaged → Fix Committed
Revision history for this message
Martin Pitt (pitti) wrote : Please test proposed package

Accepted linux-firmware into karmic-proposed, the package will build now and be available in a few hours. Please test and give feedback here. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you in advance!

Changed in linux-firmware (Ubuntu):
status: Triaged → Fix Committed
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

setting Fix Released per TGardner.

-JFo

Changed in linux-firmware (Ubuntu):
status: Fix Committed → Fix Released
Changed in linux-firmware (Ubuntu Karmic):
status: Fix Committed → Fix Released
Revision history for this message
Fredrik Olofsson (frol-hupp) wrote :

I just tested the new fix, the filenames are correct. Thanks guys :-)

Sorry for not getting around to try it sooner.
/Fredrik

Revision history for this message
Julian Wiedmann (jwiedmann) wrote :

1.26 is still sitting in karmic-proposed, not released yet.

Changed in linux-firmware (Ubuntu Karmic):
status: Fix Released → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 1.26

---------------
linux-firmware (1.26) karmic-proposed; urgency=low

  * Erroneously renamed BCM2033-MD.hex
    -LP: #156133
 -- Tim Gardner <email address hidden> Mon, 23 Nov 2009 08:06:20 -0700

Changed in linux-firmware (Ubuntu Karmic):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

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