Atheros AR9462 Bluetooth cannot detect other devices

This change was made by a bot.

If you post a question at askubuntu.com and use the bluetooth tag, link to this bug report and Pilot6 will likely find it and be able to get the fixes submitted upstream as your bluetooth device is not supported in any linux kernel at this time

I've built a t4est module for this device. Install it this way:

wget https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542564-dkms_0.1_all.deb
sudo dpkg -i btusb-lp1542564-dkms_0.1_all.deb

Then power off the laptop and power it on.

If BT does not work right away, you may need firmware installed too. Then post output of

dmesg | grep Bluetooth

And please also post output of

usb-devices | awk '/3395/' RS=

Thank you for your quick response. I am currently at work and not able to perform the test at this time. I will do so as soon as I get home and post the requested information.

I installed the patch just as you specified. I then power-cycled the computer and attempted to connect a bluetooth mouse. It did not detect the device. Following are the outputs you requested.

christopher@christopher-laptop:~$ dmesg | grep Bluetooth
[ 4.134678] Bluetooth: Core ver 2.20
[ 4.134712] Bluetooth: HCI device and connection manager initialized
[ 4.134716] Bluetooth: HCI socket layer initialized
[ 4.134719] Bluetooth: L2CAP socket layer initialized
[ 4.134727] Bluetooth: SCO socket layer initialized
[ 4.228587] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.228590] Bluetooth: BNEP filters: protocol multicast
[ 4.228594] Bluetooth: BNEP socket layer initialized
[ 19.347052] Bluetooth: RFCOMM TTY layer initialized
[ 19.347061] Bluetooth: RFCOMM socket layer initialized
[ 19.347066] Bluetooth: RFCOMM ver 1.11

christopher@christopher-laptop:~$ usb-devices | awk '/3395/' RS=
T: Bus=03 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3395 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb

It might still need firmware, so try

wget http://download.windowsupdate.com/d/msdownload/update/driver/drvs/2014/01/20623393_919a4673931aa789f0b1c3eeafb360b36097894a.cab

sudo cabextract 20623393_919a4673931aa789f0b1c3eeafb360b36097894a.cab -F *.dfu -d /lib/firmware/ar3k

It is two commands, the first goes from wget to 894a.cab

Then shutdown and boot it up

Thank you for your response. I installed the cab file as specified. There were no errors. I shutdown the computer, as stated, and then powered it up. Once again, I attempted to connect a bluetooth mouse but it could not detect the device.

Christopher,

I always forget to change module version for btusb to pass sanity check.
I fixed it. Run this:

sudo dpkg -r btusb-lp1542564-dkms
wget https://launchpad.net/~hanipouspilot/+archive/ubuntu/bluetooth/+files/btusb-lp1542564-dkms_0.2_all.deb

Reboot.

It should work after that.
Then post again

dmesg | grep Bluetooth

to see whish firmware file it loads.

I forgot to add the install command in the previous post

sudo dpkg -i btusb-lp1542564-dkms_0.2_all.deb

Awesome! It worked like a charm. The bluetooth mouse and bluetooth headphones were detected and connected without any problems. This works for Ubuntu 15.10 with kernel 4.2.0-29-generic. Will it also work in Ubuntu 14.04.3 with kernel 3.19.0-49?
Following is the output you requested.

christopher@christopher-laptop:~$ dmesg | grep Bluetooth
[ 4.240395] Bluetooth: Core ver 2.20
[ 4.240415] Bluetooth: HCI device and connection manager initialized
[ 4.240420] Bluetooth: HCI socket layer initialized
[ 4.240423] Bluetooth: L2CAP socket layer initialized
[ 4.240430] Bluetooth: SCO socket layer initialized
[ 5.429775] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.429779] Bluetooth: BNEP filters: protocol multicast
[ 5.429783] Bluetooth: BNEP socket layer initialized
[ 19.393458] Bluetooth: RFCOMM TTY layer initialized
[ 19.393467] Bluetooth: RFCOMM socket layer initialized
[ 19.393479] Bluetooth: RFCOMM ver 1.11

christopher@christopher-laptop:~$ dmesg | egrep 'ath3|ar3|Bluet'
[ 4.240395] Bluetooth: Core ver 2.20
[ 4.240415] Bluetooth: HCI device and connection manager initialized
[ 4.240420] Bluetooth: HCI socket layer initialized
[ 4.240423] Bluetooth: L2CAP socket layer initialized
[ 4.240430] Bluetooth: SCO socket layer initialized
[ 4.382769] usbcore: registered new interface driver ath3k
[ 5.429775] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.429779] Bluetooth: BNEP filters: protocol multicast
[ 5.429783] Bluetooth: BNEP socket layer initialized
[ 19.393458] Bluetooth: RFCOMM TTY layer initialized
[ 19.393467] Bluetooth: RFCOMM socket layer initialized
[ 19.393479] Bluetooth: RFCOMM ver 1.11
[ 109.408391] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 109.408399] Bluetooth: HIDP socket layer initialized
[ 390.592254] Bluetooth: hci0 SCO packet for unknown connection handle 31

It looks like it does not report the firmware file if it is successfully loaded.

You can try to temporary remove firmware from /lib/firmware/ar3k and try it again.

But this is not crucial. I will send a patch upstream shortly.

The patch has been sent upstream.

https://lkml.org/lkml/2016/2/10/240

Regarding Ubuntu 14.04.3 with 3.19 kernel.

It will work as soon as the patch reaches the stable Ubuntu kernels.
The current patch probably will not work with 3.19.

The easiest way is to upgrade the kernel in 14.04.3 by

sudo apt-get install linux-generic-lts-wily

This kernel will be default in 14.04.4 that will come out this month.
If it is a serious problem to use 4.2, I can build a module for 3.19 as well.
But I do not really think it is necessary.

I think you are right, and that it is not necessary to build anything for 3.19. I will install the 4.2 kernel and then report any issues that may arise. Thank you Pilot6 for all the effort you put in to making this work. And thank you Jeremy, for your assistance as well.

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-trusty' to 'verification-done-trusty'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-vivid' to 'verification-done-vivid'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-wily' to 'verification-done-wily'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I have tested this patch with linux-generic-lts-wily and can confirm that it works without issue.

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-xenial' to 'verification-done-xenial'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

I have tested and can confirm this works without issue in linux-generic-lts-xenial.

I marked vivid and trusty testing as done since the xenial and wily testing went fine.

This bug was fixed in the package linux - 4.4.0-22.38

---------------
linux (4.4.0-22.38) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
    - LP: #1573817

  * autoreconstruct: need to also generate extend-diff-ignore options for links
    (LP: #1574362)
    - [Packaging] autoreconstruct -- generate extend-diff-ignore for links

  * tipc: missing linearization of sk_buff (LP: #1567064)
    - tipc: move linearization of buffers to generic code

  * [Hyper-V] In-flight PCI Passthrough Patches (LP: #1570124)
    - SAUCE:(noup) drivers:hv: Lock access to hyperv_mmio resource tree
    - SAUCE:(noup) drivers:hv: Call vmbus_mmio_free() to reverse
      vmbus_mmio_allocate()
    - SAUCE:(noup) drivers:hv: Reverse order of resources in hyperv_mmio
    - SAUCE:(noup) drivers:hv: Track allocations of children of hv_vmbus in
      private resource tree
    - SAUCE:(noup) drivers:hv: Record MMIO range in use by frame buffer
    - SAUCE:(noup) drivers:hv: Separate out frame buffer logic when picking MMIO
      range

  * vbox: resync with 5.0.18-dfsg-2build1 (LP: #1571156)
    - ubuntu: vbox -- update to 5.0.18-dfsg-2build1

  * CONFIG_AUFS_XATTR is not set (LP: #1557776)
    - [Config] CONFIG_AUFS_XATTR=y

  * CVE-2016-3672 (LP: #1568523)
    - x86/mm/32: Enable full randomization on i386 and X86_32

  * CVE-2016-3955 (LP: #1572666)
    - USB: usbip: fix potential out-of-bounds write

  * Xenial update to v4.4.8 stable release (LP: #1573034)
    - hwmon: (max1111) Return -ENODEV from max1111_read_channel if not
      instantiated
    - PKCS#7: pkcs7_validate_trust(): initialize the _trusted output argument
    - parisc: Avoid function pointers for kernel exception routines
    - parisc: Fix kernel crash with reversed copy_from_user()
    - parisc: Unbreak handling exceptions from kernel modules
    - ALSA: timer: Use mod_timer() for rearming the system timer
    - ALSA: hda - Asus N750JV external subwoofer fixup
    - ALSA: hda - Fix white noise on Asus N750JV headphone
    - ALSA: hda - Apply fix for white noise on Asus N550JV, too
    - mm: fix invalid node in alloc_migrate_target()
    - powerpc/mm: Fixup preempt underflow with huge pages
    - libnvdimm: fix smart data retrieval
    - libnvdimm, pfn: fix uuid validation
    - compiler-gcc: disable -ftracer for __noclone functions
    - arm64: opcodes.h: Add arm big-endian config options before including arm
      header
    - drm/dp: move hw_mutex up the call stack
    - drm/udl: Use unlocked gem unreferencing
    - drm/radeon: add a dpm quirk for sapphire Dual-X R7 370 2G D5
    - drm/radeon: add another R7 370 quirk
    - drm/radeon: add a dpm quirk for all R7 370 parts
    - drm/amdgpu/gmc: move vram type fetching into sw_init
    - drm/amdgpu/gmc: use proper register for vram type on Fiji
    - xen/events: Mask a moving irq
    - tcp: convert cached rtt from usec to jiffies when feeding initial rto
    - tunnel: Clear IPCB(skb)->opt before dst_link_failure called
    - net: jme: fix suspend/resume on JMC260
    - net: vrf: Remove direct access to skb->data
    - net: qca_spi: Don't clear IFF_BROADCAST
    - net: qca_spi: clear IFF_TX_SKB_SHARING
    - net: fix bridge multicas...

This bug was fixed in the package linux - 4.4.0-22.39

---------------
linux (4.4.0-22.39) xenial; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
    - LP: #1578721

  * LP: #1578705
    - bpf: fix double-fdput in replace_map_fd_with_map_ptr()

 -- Kamal Mostafa <email address hidden> Thu, 05 May 2016 09:30:58 -0700