My device is 0a5c:21f4 in a Lenovo Edge E135 and I think I am affected by this bug on an up-to-date install of raring. In quantal all below described devices worked (although not very reliably). Since upgrading to raring only my bluetooth mouse is still working. Here's what I tried to solve the problem:
I downloaded the Windows XP driver from the Lenovo Support Website and extracted it via Wine. In a file
~/.wine/drive_c/DRIVERS/BLUETOOTH_Combo/Win64/drivers/btwusb.inf
I found information that suggests I need the RAMPatchFile `BCM20702A1_001.002.014.0889.0899.hex`. I used hex2hcd to obtain `fw-0a5c_21f4.hcd` which I placed in `/lib/firmware/`. From the output of `dmesg | grep -i bluetooth` (see attachment), I figure that the firmware does get loaded. The bluetooth mouse still works (as it did before). Also my phone and a A2DP device get detected, which they didn't before. However I still cannot connect to the latter two devices...
Is my problem related to this bug? Any suggestions to solve the problem?
My device is 0a5c:21f4 in a Lenovo Edge E135 and I think I am affected by this bug on an up-to-date install of raring. In quantal all below described devices worked (although not very reliably). Since upgrading to raring only my bluetooth mouse is still working. Here's what I tried to solve the problem:
I downloaded the Windows XP driver from the Lenovo Support Website and extracted it via Wine. In a file wine/drive_ c/DRIVERS/ BLUETOOTH_ Combo/Win64/ drivers/ btwusb. inf 001.002. 014.0889. 0899.hex` . I used hex2hcd to obtain `fw-0a5c_21f4.hcd` which I placed in `/lib/firmware/`. From the output of `dmesg | grep -i bluetooth` (see attachment), I figure that the firmware does get loaded. The bluetooth mouse still works (as it did before). Also my phone and a A2DP device get detected, which they didn't before. However I still cannot connect to the latter two devices...
~/.
I found information that suggests I need the RAMPatchFile `BCM20702A1_
Is my problem related to this bug? Any suggestions to solve the problem?