With the patch, cold-boot (nothing works, rfkill, hciconfig does not see the device): :~$ dmesg | grep -i "btusb\|bluetooth\|ath3k\|firmware" [ 0.165234] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 5.132502] Bluetooth: Core ver 2.20 [ 5.132522] Bluetooth: HCI device and connection manager initialized [ 5.132529] Bluetooth: HCI socket layer initialized [ 5.132532] Bluetooth: L2CAP socket layer initialized [ 5.132538] Bluetooth: SCO socket layer initialized [ 5.139655] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 5.139659] Bluetooth: BNEP filters: protocol multicast [ 5.139691] Bluetooth: BNEP socket layer initialized [ 5.139947] Bluetooth: RFCOMM TTY layer initialized [ 5.139953] Bluetooth: RFCOMM socket layer initialized [ 5.139958] Bluetooth: RFCOMM ver 1.11 [ 5.321921] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 6.336151] usbcore: registered new interface driver btusb [ 6.419089] usbcore: registered new interface driver ath3k [ 9.918557] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ 9.918572] Bluetooth: Loading patch file failed [ 9.918584] ath3k: probe of 2-5:1.0 failed with error -110
With the patch, when rebooting from **Windows** (Everything is working): :~$ dmesg | grep -i "btusb\|bluetooth\|ath3k\|firmware" [ 0.165411] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored [ 7.277840] [Firmware Bug]: ACPI(PEGP) defines _DOD but not _DOS [ 7.338358] Bluetooth: Core ver 2.20 [ 7.338382] Bluetooth: HCI device and connection manager initialized [ 7.338391] Bluetooth: HCI socket layer initialized [ 7.338394] Bluetooth: L2CAP socket layer initialized [ 7.338402] Bluetooth: SCO socket layer initialized [ 7.349094] Bluetooth: RFCOMM TTY layer initialized [ 7.349108] Bluetooth: RFCOMM socket layer initialized [ 7.349145] Bluetooth: RFCOMM ver 1.11 [ 7.350880] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7.350884] Bluetooth: BNEP filters: protocol multicast [ 7.350892] Bluetooth: BNEP socket layer initialized [ 8.173590] usbcore: registered new interface driver btusb [ 8.187979] usbcore: registered new interface driver ath3k [ 22.291160] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 22.291174] Bluetooth: HIDP socket layer initialized [ 22.293873] input: Bluetooth Laser Travel Mouse as /devices/pci0000:00/0000:00:14.0/usb2/2-5/2-5:1.0/bluetooth/hci0/hci0:21/0005:046D:B008.0002/input/input16 [ 22.294028] hid-generic 0005:046D:B008.0002: input,hidraw1: BLUETOOTH HID v3.18 Mouse [Bluetooth Laser Travel Mouse] on 10:08:b1:c7:88:62 2015-01-13 23:07 GMT+01:00 Sujith Manoharan <suj...@msujith.org>: > Sekou DIAKITE wrote: >> I've installed the latest backport driver and added the "btcoex_enable=1". >> It doesn't change the behavior (bluetooth works only after a reboot >> from Windows). > > From the askubuntu page, 0489:e076 is the USB ID for your card. > It doesn't appear to be present in the kernel and I don't think > ath3k would be loaded. > > I have a patch to add this ID to ath3k, can you apply it in > backports-20141221 and check ? > > http://msujith.org/dir/patches/wl/Jan-14-2015/0013-ath3k-Add-new-AR3012-device.patch > > Inside backports: > > patch -p1 < 0013-ath3k-Add-new-AR3012-device.patch > > And then, do a "make menuconfig" to select ath9k/ath3k > and install. > > Sujith > _______________________________________________ > ath9k-devel mailing list > ath9k-devel@lists.ath9k.org > https://lists.ath9k.org/mailman/listinfo/ath9k-devel _______________________________________________ ath9k-devel mailing list ath9k-devel@lists.ath9k.org https://lists.ath9k.org/mailman/listinfo/ath9k-devel
