https://bugzilla.kernel.org/show_bug.cgi?id=99371 --- Comment #7 from Sumit Khanna <notify@xxxxxxxxxxxxxxxxx> --- I wish the bluetooth kernel mailing list had a nice mailman thread view so I could like to the massive thread about this (maybe it does and I just can't find it). Anyway, here was the last e-mail I sent about this: http://permalink.gmane.org/gmane.linux.bluez.kernel/63192 and then I gave up and bought and external bluetooth dongle...which broke last week. So I finally replied to that e-mail. So according to that thread, I don't actually have an ath3k card. It's uses the same USB ID number, but it's actually a QCA Rome chipset. So that patch tries to get the kernel to ignore the ath3k match and instead load the QCA firmware. On my MSI WS-60, it loads the firmware, then fails when I try to run "power on" within the "bluetoothctl" command line app (same if I use hciconfig instead as started in a previous e-mail in that thread). [ 11.128970] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin [ 11.128972] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111 [ 11.184335] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin [ 6886.445648] Bluetooth: hci0: using rampatch file: qca/rampatch_usb_00000200.bin [ 6886.445656] Bluetooth: hci0: QCA: patch rome 0x200 build 0x299, firmware rome 0x200 build 0x111 [ 6886.499929] Bluetooth: hci0: using NVM file: qca/nvm_usb_00000200.bin and after trying to turn it on: [10052.098236] Bluetooth: hci0: Failed to access otp area (-108) According to the label on the bottom of my laptop: RF Module inside: Qualcomm Atheros QCNFA34AC ...but I don't know if that's just the Wi-Fi or Wi-Fi+BT. (Wi-fi works fine in stock 4.3.0 with ath10k_pci) -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
