Comment 90 for bug 1065400

Hello Jesse,

I followed your instructions from comment 11 and bluetooth stops working while booting with fw-0a5c_21e8.hcd is in the /lib/frimware/ directory

I used hex3hcd tool with RAMUSB21E8 / BCM20702A1_001.002.014.0889.0896.hex for IOGEAR GBU521 / 0a5c:21e8

here is the dmesg | grep Bluetooth output while fw-0a5c_21e8.hcd is in the /lib/frimware/ directory:

[ 19.567221] Bluetooth: Core ver 2.16
[ 19.567277] Bluetooth: HCI device and connection manager initialized
[ 19.567287] Bluetooth: HCI socket layer initialized
[ 19.567291] Bluetooth: L2CAP socket layer initialized
[ 19.567299] Bluetooth: SCO socket layer initialized
[ 20.533843] Bluetooth: firmware loaded
[ 20.916739] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.916744] Bluetooth: BNEP filters: protocol multicast
[ 20.916755] Bluetooth: BNEP socket layer initialized
[ 20.917965] Bluetooth: RFCOMM TTY layer initialized
[ 20.917978] Bluetooth: RFCOMM socket layer initialized
[ 20.917980] Bluetooth: RFCOMM ver 1.11
[ 23.016021] Bluetooth: hci0 command 0x0c56 tx timeout
[ 25.020019] Bluetooth: hci0 command 0x0c6d tx timeout
[ 27.024044] Bluetooth: hci0 command 0x0c1a tx timeout
[ 29.028013] Bluetooth: hci0 command 0x0c24 tx timeout

and here the output while bluetooth partially working and fw-0a5c_21e8.hcd isn't in the /lib/frimware/ director:

[ 20.186088] Bluetooth: Core ver 2.16
[ 20.208815] Bluetooth: HCI device and connection manager initialized
[ 20.208827] Bluetooth: HCI socket layer initialized
[ 20.208831] Bluetooth: L2CAP socket layer initialized
[ 20.208839] Bluetooth: SCO socket layer initialized
[ 20.330770] Bluetooth: can't load firmware, may not work correctly
[ 21.719953] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 21.719957] Bluetooth: BNEP filters: protocol multicast
[ 21.719968] Bluetooth: BNEP socket layer initialized
[ 21.724278] Bluetooth: RFCOMM TTY layer initialized
[ 21.724294] Bluetooth: RFCOMM socket layer initialized
[ 21.724297] Bluetooth: RFCOMM ver 1.11

and yes if I do a boot into windows with the proper drviers installed and then restarted into linux it fully functional (both a2dp and hsp/hfp work) as long as fw-0a5c_21e8.hcd isn't in the /lib/frimware/ director in linux and when I turn off the computer the bluetooth only works with a2dp again and not hsp/hfp

note: In windows is says the device is a BCM20702A0 in device under control panel while looking at the tbcbtums-win7x86-brcm.inf info for 0a5c:21e8 it says its a 20702A1 dongle