Bluetooth headset doesn't work with Broadcom BCM2045 on 2.6.24
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
In Hardy, on both vanilla and Ubuntu builds of the 2.6.24 kernel, trying to output sound to my Bluetooth headset produces the following flood in dmesg:
[ 398.069982] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
[ 398.069988] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
[ 398.071485] hci_scodata_packet: hci0 SCO packet for unknown connection handle 1
...
I can hear the headset activate, but it only outputs silence. The audio player hangs until I hit control-C, but the dmesg flood doesn't stop and the headset doesn't deactivate until I manually disconnect the headset in the Bluetooth preferences.
My Bluetooth chip is the following item from lsusb:
Bus 002 Device 002: ID 0a5c:2101 Broadcom Corp.
This is my .asoundrc file:
pcm.bluetooth {
type bluetooth
device 00:13:17:87:9A:47
profile voice
mode mono
}
ctl.bluetooth {
type bluetooth
}
pcm.headset {
type plug
slave {
pcm "bluetooth"
format S16_LE
channels 1
}
}
And I'm running the following command to play sound:
aplay -D headset /usr/share/
Hi Brian,
Thanks for your bug report and helping to make Ubuntu better. You mentioned that this issue also exists from an upstream vanilla kernel? If this is the case I'd actually encourage you to also open a bug report at the upstream bugzilla.kernel.org bug tracker. I've noticed many times that once a bug gets the attention of the upstream kernel community, there will be a quick resolution to the issue. Since the Ubuntu kernel rebases with the upstream vanilla kernel, once the fix is committed upstream for others to benefit from as well, the Ubuntu kernel would also pull in the fix. For help with making an upstream bug report, please refer to the "Reporting Bugs Upstream" section of the following link: https:/ /wiki.ubuntu. com/KernelTeamB ugPolicies. Please let us know if you open the report upstream. Thanks!