bcm203x firmware will not load
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-source-2.6.20 (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned | ||
linux-source-2.6.22 (Ubuntu) |
Fix Released
|
Medium
|
Ben Collins |
Bug Description
Binary package hint: linux-source-2.6.20
Not sure if this is a kernel bug but my Broadcom USB bluetooth dongle is not working on feisty.
It appears that the firmware is not being uploaded successfully to the dongle. I have the
BCM2033-FW.bin and BCM2033-MD.hex files located in /lib/firmware. These are the same files that worked under Dapper.
lsusb output:
Bus 003 Device 008: ID 04b8:0005 Seiko Epson Corp. Stylus Printer
Bus 003 Device 006: ID 047b:0001 Silitek Corp.
Bus 003 Device 005: ID 09da:0006 A4 Tech Co., Ltd Optical Mouse WOP-35 / Trust 450L Optical Mouse
Bus 003 Device 002: ID 05e3:0606 Genesys Logic, Inc.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 005: ID 0a5c:2033 Broadcom Corp. BCM2033 Bluetooth
Bus 001 Device 001: ID 0000:0000
dmesg output is attached. The critical line being "[34921.387254] bcm203x_complete: URB failed with status -108". I beleive this indicates that the firmware was not successfully uploaded.
Related branches
Changed in linux-source-2.6.20: | |
status: | Confirmed → Needs Info |
Changed in linux-source-2.6.22: | |
assignee: | nobody → ubuntu-kernel-team |
importance: | Undecided → Medium |
status: | New → Triaged |
Changed in linux-source-2.6.20: | |
assignee: | kyle → nobody |
status: | Incomplete → Won't Fix |
Thanks for taking the time to report this bug. Unfortunately we can't fix it, because your description didn't include enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available here: <http:// wiki.ubuntu. com/DebuggingKe rnelProblems> Thanks!