[SOLVED] Bluetooth (ath10k) on Dell XPS 9560 not working

[JohanHarmsen]

Hello

I installed Mint 18.2 on a new Dell XPS 9560 laptop in a dual boot configuration along side Window 10 (UEFI), works like a champ, but I have one small problem.
I cannot get my (Logitec M535) bluetooth mouse to work. It does work with Windows 10.
I've read a lot of posts, but none of the suggested solutions appeared to help.
Blueman and Blueberry cannot find the device, when I look with dmesg | egrep 'blue|firm'

Code: Select all

[    2.461149] [drm] GuC firmware load skipped
[    4.752444] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[    4.752449] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    4.752661] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    4.752662] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[    4.754r648] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5

The file firware-5,bin does indeed not exits in the /lib/firmware folder, firmware-4.bin and firmware-6.bin do exist.
Tried to copy the file hw2.1/firmware-5.bin to the hw3.0 directory but then the Wireless network stopped working.

Attempted to reinstall linux-firmware: sudo apt install --reinstall linux-firmware (no effect, no changes in the .../ath10/QCA6174/hw3.0 directory)
Attempted to boot the original Mint 18.2 kernel: 4.8.0-53, no effect (Currently I'm running 4.10.0-40)

Have not tried to download and install the driver from https;//github.com/kvalo/ath10k-firmware, because I only see firmware-4.bin there and that is the one I already have and that is not used by the system. I have no clue where the information to load firmware-5.bin is stored, tried to search the /etc/ directory but got no hits.

Some other information that may be helpfull

Code: Select all

lspci -knn | grep Net
02:00.0 Network controller [0280]: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter [168c:003e] (rev 32)
	Subsystem: Bigfoot Networks, Inc. QCA6174 802.11ac Wireless Network Adapter [1a56:1535]

Code: Select all

rfckill list all
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

Code: Select all

lswh -C Network
  *-network               
       description: Wireless interface
       product: QCA6174 802.11ac Wireless Network Adapter
       vendor: Qualcomm Atheros
       physical id: 0
       bus info: pci@0000:02:00.0
       logical name: wlp2s0
       version: 32
       serial: 9c:b6:d0:eb:92:4f
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=ath10k_pci driverversion=4.10.0-40-generic firmware=WLAN.RM.2.0-00180-QCARMSWPZ-1 ip=192.168.2.24 latency=0 link=yes 

Code: Select all

ls -l /lib/firmware/at/h10k/QCA6174/hw3.0
-rw-r--r-- 1 root root 337204 Oct 16 23:25 board-2.bin
-rw-r--r-- 1 root root   8124 Mar 30  2017 board.bin
-rw-r--r-- 1 root root 733784 Mar 30  2017 firmware-4.bin
-rw-r--r-- 1 root root 711408 Aug 17 18:09 firmware-6.bin
-rw-r--r-- 1 root root  79689 Mar 30  2017 notice_ath10k_firmware-4.txt
-rw-r--r-- 1 root root  82663 Aug 17 18:09 notice_ath10k_firmware-6.txt

Any suggestions will be greatly appreciated

Johan

[JeremyB]

Can you post results for

Code: Select all

dmesg | egrep -i 'blue|firm'; lsusb

[JohanHarmsen]

Code: Select all

dmesg | egrep -i 'firm|blue'
[    0.187935] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    2.461149] [drm] GuC firmware load skipped
[    4.386822] Bluetooth: Core ver 2.22
[    4.386833] Bluetooth: HCI device and connection manager initialized
[    4.386835] Bluetooth: HCI socket layer initialized
[    4.386836] Bluetooth: L2CAP socket layer initialized
[    4.386840] Bluetooth: SCO socket layer initialized
[    4.391982] Bluetooth: HCI UART driver ver 2.3
[    4.391983] Bluetooth: HCI UART protocol H4 registered
[    4.391983] Bluetooth: HCI UART protocol BCSP registered
[    4.391983] Bluetooth: HCI UART protocol LL registered
[    4.391984] Bluetooth: HCI UART protocol ATH3K registered
[    4.391984] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    4.392004] Bluetooth: HCI UART protocol Intel registered
[    4.392012] Bluetooth: HCI UART protocol Broadcom registered
[    4.392012] Bluetooth: HCI UART protocol QCA registered
[    4.392013] Bluetooth: HCI UART protocol AG6XX registered
[    4.392013] Bluetooth: HCI UART protocol Marvell registered
[    4.752444] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:02:00.0.bin failed with error -2
[    4.752449] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/cal-pci-0000:02:00.0.bin failed with error -2
[    4.752661] ath10k_pci 0000:02:00.0: Direct firmware load for ath10k/QCA6174/hw3.0/firmware-5.bin failed with error -2
[    4.752662] ath10k_pci 0000:02:00.0: could not fetch firmware file 'ath10k/QCA6174/hw3.0/firmware-5.bin': -2
[    4.754648] ath10k_pci 0000:02:00.0: firmware ver WLAN.RM.2.0-00180-QCARMSWPZ-1 api 4 features wowlan,ignore-otp,no-4addr-pad crc32 75dee6c5
[    5.540648] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    5.540649] Bluetooth: BNEP filters: protocol multicast
[    5.540651] Bluetooth: BNEP socket layer initialized
[   19.122376] Bluetooth: RFCOMM TTY layer initialized
[   19.122381] Bluetooth: RFCOMM socket layer initialized
[   19.122384] Bluetooth: RFCOMM ver 1.11


lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
Bus 001 Device 003: ID 1bcf:2b95 Sunplus Innovation Technology Inc. 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

[JeremyB]

Strange, post results for

Code: Select all

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

[JohanHarmsen]

usb-devices | awk '/e300/' RS=
T: Bus=01 Lev=01 Prnt=01 Port=03 Cnt=02 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.01 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=e300 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

[JeremyB]

So are you rebooting from Windows into Linux or doing a complete shutdown, then startup and boot into Linux. I don't see any info about firmware loading for the bluetooth and it might be because the Windows firmware hasn't been purged by powering off the device

[JohanHarmsen]

I tried both, shutdown/wait a few minutes, start Mint. also restart Mint->Mint and Windows->Mint but the result is always the same.

[JeremyB]

After Linux Mint boots up,

Code: Select all

sudo modprobe -r btusb && sleep 20 && sudo modprobe btusb

See if that gets bluetooth running

[JohanHarmsen]

sudo modprobe -r btusb && sleep 20 && sudo modprobe btusb
No messages, dmesg | tail
[ 136.581298] usbcore: deregistering interface driver btusb
[ 136.581519] Bluetooth: hci0 urb ffff9c1ca1dcc240 failed to resubmit (2)
[ 156.667131] usbcore: registered new interface driver btusb

No change, bt Mouse still not showing in Bluetooth Manager (Blueberry)
Out of frustration shaked the mouse, and for a moment the name of the mouse flashed up in the bt manager. Too short to select it. This was repeatable,

Wireshark :

13 0.276070 Logitech_53:a7:44 () localhost () L2CAP 15 Sent Information Request (Extended Features Mask)

Frame 13: 15 bytes on wire (120 bits), 15 bytes captured (120 bits) on interface 0
Bluetooth
Bluetooth HCI H4
Bluetooth HCI ACL Packet
Bluetooth L2CAP Protocol
Length: 6
CID: L2CAP Signaling Channel (0x0001)
Command: Information Request
Command Code: Information Request (0x0a)
Command Identifier: 0x01
Command Length: 2
Information Type: Extended Features Mask (0x0002)

19 0.280601 localhost () Logitech_53:a7:44 () L2CAP 21 Rcvd Information Response (Extended Features Mask, Success)

Frame 19: 21 bytes on wire (168 bits), 21 bytes captured (168 bits) on interface 0
Bluetooth
Bluetooth HCI H4
Bluetooth HCI ACL Packet
Bluetooth L2CAP Protocol
Length: 12
CID: L2CAP Signaling Channel (0x0001)
Command: Information Response
Command Code: Information Response (0x0b)
Command Identifier: 0x01
Command Length: 8
Information Type: Extended Features Mask (0x0002)
Result: Success (0x0000)
Features: FixedChan Unicast
.... .... .... .... .... .... .... ...0 = Flow Control Mode: 0
.... .... .... .... .... .... .... ..0. = Retransmission Mode: 0
.... .... .... .... .... .... .... .0.. = Bi-Directional QOS: 0
.... .... .... .... .... .... .... 0... = Enhanced Retransmission Mode: 0
.... .... .... .... .... .... ...0 .... = Streaming Mode: 0
.... .... .... .... .... .... ..0. .... = FCS: 0
.... .... .... .... .... .... .0.. .... = Extended Flow Specification for BR/EDR: 0
.... .... .... .... .... .... 1... .... = Fixed Channels: 1
.... .... .... .... .... ...0 .... .... = Extended Window Size: 0
.... .... .... .... .... ..1. .... .... = Unicast Connectionless Data Reception: 1

20 0.280663 Logitech_53:a7:44 () localhost () L2CAP 15 Sent Information Request (Fixed Channels Supported)

Frame 20: 15 bytes on wire (120 bits), 15 bytes captured (120 bits) on interface 0
Bluetooth
Bluetooth HCI H4
Bluetooth HCI ACL Packet
Bluetooth L2CAP Protocol
Length: 6
CID: L2CAP Signaling Channel (0x0001)
Command: Information Request
Command Code: Information Request (0x0a)
Command Identifier: 0x02
Command Length: 2
Information Type: Fixed Channels Supported (0x0003)

25 0.288093 localhost () Logitech_53:a7:44 () L2CAP 25 Rcvd Information Response (Fixed Channels Supported, Success)

Frame 25: 25 bytes on wire (200 bits), 25 bytes captured (200 bits) on interface 0
Bluetooth
Bluetooth HCI H4
Bluetooth HCI ACL Packet
Bluetooth L2CAP Protocol
Length: 16
CID: L2CAP Signaling Channel (0x0001)
Command: Information Response
Command Code: Information Response (0x0b)
Command Identifier: 0x02
Command Length: 12
Information Type: Fixed Channels Supported (0x0003)
Result: Success (0x0000)
Fixed Channels Supported:
.... .... .... .... .... .... .... ...0 = Null identifier: 0
.... .... .... .... .... .... .... ..1. = L2CAP signaling channel: 1
.... .... .... .... .... .... .... .1.. = Connectionless reception: 1
.... .... .... .... .... .... .... 0... = AMP Manager protocol: 0
0... .... .... .... .... .... .... .... = AMP Test Manager: 0

This does not help me further. In anther post I found bluetoothctl, this reports:

[NEW] Device 34:88:5D:53:A7:44 Bluetooth Mouse M336/M337/M535
[CHG] Device 34:88:5D:53:A7:44 Connected: no
[DEL] Device 34:88:5D:53:A7:44 Bluetooth Mouse M336/M337/M535

These events occur with minimal time delay between them.
It almost looks as if the mouse is recognized, but for some reason not registered, and stopped before it can be paired.

Checked which bluetoothr elated processes are runnng:

root 1170 1 0 19:21 ? 00:00:00 /usr/lib/bluetooth/bluetoothd
johan 1874 1585 0 19:22 ? 00:00:00 blueberry-obex-agent
johan 1914 1 0 19:22 ? 00:00:00 /usr/lib/bluetooth/obexd
johan 1981 1585 0 19:22 ? 00:00:00 /usr/bin/python /usr/bin/blueberry-tray
johan 1982 1981 0 19:22 ? 00:00:00 sh -c /usr/lib/blueberry/blueberry-tray.py
johan 1983 1982 0 19:22 ? 00:00:00 python2 /usr/lib/blueberry/blueberry-tray.py
johan 1585 1570 0 19:22 ? 00:00:00 cinnamon-session --session cinnamon

Connected with strace to /usr/lib/bluetooth/bluetoothd
Found a cache /var/lib/bluetooth/9C:B6:D0:EB:92:50/cache/34:88:5D:53:A7:44, cleaned in, restart, same result.

[JeremyB]

This might be a bug in the 4.10 kernels. Use the Mint Update Manager through View/linux kernels to install the newest 4.4.0 kernel 101 I think
Reboot and use the grub menu to boot using the 4.4 kernel

[JohanHarmsen]

Hi Jeremy
That did the trick, after installation of kernel 4.4.0-101 and a reboot, the mouse appeared in the bt manager and was successfully paired.
Thanks for all your help ! I'll periodically test with new kernels to see if the problem is solved

Best regards

Johan

[hcom01]

I have the same mouse and linuxmint 20 mate edition, i was able to connect the mouse by removing blueberry and installing blueman, same thing with my galaxy buds. good luck with future blue tooth devices, this is not 100 percent efficient.