Linux Mint 19 - No Bluetooth adapters found

[jaspergrond]

I have been using my new laptop (Dell XPS 15 9570) with Linux Mint 19 Cinnamon edition for a month now and bluetooth has been working flawlessly. Today I boot it up and the bluetooth app did not start automatically. I started the bluetooth app and the message "No Bluetooth adapters found" was displayed.

After some researching of the problem I could not find an solution for myself but did find some diagnostic steps I will present now:

This is the version of the kernel I am using. I have been using it since Nov 15th (I think, but for a couple of weeks at least) with no bluetooth issue until today.

Code: Select all

$ uname -a
Linux jaari 4.15.0-42-generic #45-Ubuntu SMP Thu Nov 15 19:32:57 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

I think ath10k is referring to the the bluetooth firmware which is apparently failing with error -2

Code: Select all

$ lsmod | grep bluetooth; dmesg | egrep -i 'blue|firm'
[    0.043524] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.244448] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    2.116716] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)
[    5.381824] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3b:00.0.bin failed with error -2
[    5.381831] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/cal-pci-0000:3b:00.0.bin failed with error -2
[    5.384210] ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb

In a similar forum post viewtopic.php?t=212778 the previous step did not show an error message so they went a step further. However I do see an error message in reference to ath10k_pci and am not sure where to go from here. Any help would be greatly appreciated!

[ClixTrix]

The 4.15.0-42 kernel just came available recently. If you still have the 4.15.0-39 (or older) Kernel installed, try selecting that kernel(s) from Grub menu for a test to see if the firmware errors occur.

[JeremyB]

Those firmware errors have been around for a while and concern the wifi not the Bluetooth

[jaspergrond]

While attempting to get the grub menu to show up (following viewtopic.php?f=90&t=183449#p951025 and failing) bluetooth started working again after a few reboots.
Not sure if this helps but now the lsmod output looks like:

Code: Select all

$ lsmod | grep bluetooth; dmesg | egrep -i 'blue|firm'
bluetooth             548864  43 btrtl,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           24576  2 bluetooth
[    0.043503] Spectre V2 : Enabling Restricted Speculation for firmware calls
[    0.244586] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    2.327925] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_01.bin (v1.1)
[    6.370934] Bluetooth: Core ver 2.22
[    6.370946] Bluetooth: HCI device and connection manager initialized
[    6.370948] Bluetooth: HCI socket layer initialized
[    6.370950] Bluetooth: L2CAP socket layer initialized
[    6.370954] Bluetooth: SCO socket layer initialized
[    6.651848] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    6.651849] Bluetooth: BNEP filters: protocol multicast
[    6.651851] Bluetooth: BNEP socket layer initialized
[    6.782001] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/pre-cal-pci-0000:3b:00.0.bin failed with error -2
[    6.782007] ath10k_pci 0000:3b:00.0: Direct firmware load for ath10k/cal-pci-0000:3b:00.0.bin failed with error -2
[    6.784378] ath10k_pci 0000:3b:00.0: firmware ver WLAN.RM.4.4.1-00079-QCARMSWPZ-1 api 6 features wowlan,ignore-otp crc32 fd869beb
[   15.251862] Bluetooth: RFCOMM TTY layer initialized
[   15.251867] Bluetooth: RFCOMM socket layer initialized
[   15.251871] Bluetooth: RFCOMM ver 1.11
[   87.528498] Bluetooth: hci0: last event is not cmd complete (0x0f)

[ClixTrix]

While attempting to get the grub menu to show up (following viewtopic.php?f=90&t=183449#p951025 and failing) bluetooth started working again after a few reboots.

My thinking now falls to hardware problem with bluetooth. Although I agree with JeremyB on the error being wifi, I'm still curious if the problem has any relationship to newer/newest kernel. You did say it's a brand new laptop.

On not being able to see Grub boot menu, I assume you tried holding SHIFT key and that isn't producing the boot menu. I know that change to GRUB_TIMEOUT_STYLE="menu" on that same post you reference should work. However, I would also adjust the parameter GRUB_TIMEOUT= to something other than 0, e.g. 3.

Make sure you run sudo update-grub after the change.

[JeremyB]

You could try blacklisting one bluetooth module and then load it later to see if there is some firmware loading issue

Code: Select all

echo "blacklist btusb" | sudo tee /etc/modprobe.d/btusb.conf

Reboot, wait 15 seconds after everything is loaded and in terminal

Code: Select all

sudo modprobe btusb

See if you have better results

[jaspergrond]

While attempting to get the grub menu to show up (following viewtopic.php?f=90&t=183449#p951025 and failing) bluetooth started working again after a few reboots.

On not being able to see Grub boot menu, I assume you tried holding SHIFT key and that isn't producing the boot menu. I know that change to GRUB_TIMEOUT_STYLE="menu" on that same post you reference should work. However, I would also adjust the parameter GRUB_TIMEOUT= to something other than 0, e.g. 3.

Thanks ClixTrix, the timeout value being zero was the issue there.

[jaspergrond]

You could try blacklisting one bluetooth module and then load it later to see if there is some firmware loading issue

Code: Select all

echo "blacklist btusb" | sudo tee /etc/modprobe.d/btusb.conf

Reboot, wait 15 seconds after everything is loaded and in terminal

Code: Select all

sudo modprobe btusb

See if you have better results

Thanks JeremyB, before I do anything I want to make sure I know what I am doing.

Does the tee command write "blacklist btusb" to /etc/modprobe.d/btusb.conf thus blacklisting the btusb module?
Then, modeprobe manually loads the module?
Afterwards when I want to unblacklist it do I just edit /etc/modprobe.d/btusb.conf and remove the "blacklist btusb" line?

Also, is observing what happens when the module loads what we are trying to accomplish here now that the problem has ceased to show itself? Will modprobe return an error to the terminal if something is wrong?

Thanks for the help.

[JeremyB]

If it works, I would not delete the blacklist until a different solution can be found. I think it might be an issue with the timing of the firmware load

[jaspergrond]

Sorry for the delay, had to wait for the problem to reappear.

Blacklisting and reloading does not seem to work. After following your instructions (rebooting, waiting and loading via "sudo modprobe btusb") still gets me the "No bluetooth adapters found" error in the bluetooth manager.

Since it did not work, do you recommend rolling back to the previous version of the kernel and seeing if the problem is fixed by that? I am on 4.15.0-43-generic and have the following kernels available to roll back to:

Code: Select all

ii  linux-image-4.15.0-38 4.15.0-38.41    amd64           Signed kernel image generic
ii  linux-image-4.15.0-39 4.15.0-39.42    amd64           Signed kernel image generic
ii  linux-image-4.15.0-42 4.15.0-42.45    amd64           Signed kernel image generic
ii  linux-image-4.15.0-43 4.15.0-43.46    amd64           Signed kernel image generic
ii  linux-image-generic   4.15.0.43.45     amd64           Generic Linux kernel image

[jaspergrond]

Update: I went ahead and loaded 4.15.0-42-generic and bluetooth has now resumed working. I'll keep note if the issue reappears on this kernel.

[jaspergrond]

I just remembered 4.15.0-42 is what I started with... I guess I'll go back one more to be safe. But note that changing kernels immediately fixed the problem (unless it was a lucky coincidence).

[jaspergrond]

Update: The issue has occurred again on 4.15.0-39-generic.

[n42]

Hi jaspergrond,

Did you find fix for the bluetooth ?
Have the same issue here with XPS 9570 and the killer card / ath10k failing with error -2

[JeremyB]

Hi jaspergrond,

Did you find fix for the bluetooth ?
Have the same issue here with XPS 9570 and the killer card / ath10k failing with error -2

The ath10k error is not bluetooth related as the ath10k module is wifi only btusb and btqca handle the bluetooth

[nvanevski]

Hi all,
I have this same configuration (Dell XPS 9570 with Killer card, kernel 4.15.0.50); installed Mint 19.1 immediately and used the bluetooth with mouse with no issues for a few weeks. Today, I booted my machine and the Bluetooth was not working (Bluetooth manager showed "No bluetooth devices").

I tried every solution on this page and nothing worked. As a last resort, I booted into Mint 19.1 live USB and the bluetooth was working properly! I rebooted immediately from HDD and bluetooth was working again!

Is there some specific process in the live USB that "resets" the adapter behavior? If so, can it be applied to the normal boot as well?

Regards,

/N