Can't find bluetooth devices after reboot/update

[Nils]

Hi,

Today I tried to turn on my bluetooth speakers and it failed to pair.

I removed the device from the list to try to pair it again. But it would not be found.

I enabled bluetooth on other devices, like my phone, but it doesn’t appear for the computer.

[picture of the bluetooth searching for devices - it doesn’t let me add images/links here]

Also, my phone can see everything as avaialbe, including the computer.

But when I try to connect from the phone to the computer, it gets stuck in “Connect” until it fails and resets the list.

The phone connects without a problem to the bluetooth speaker.

I tried:

• to turn on/off the bluetooth device
• to power off/on the computer.
• to scan for other bluetooth devices besides the speaker (it cannot find a thing)
• to follow the troubleshoot in (arch linux bluetooth page) it doesn’t let me add url
• reset the CMOS (as I saw in some posts here that people had success reseting CMOS)

Yesterday was the first time I powered off the computer in a while.
The last thing I did with the bluetooth was to watch some netflix before bedtime, then before I turned the computer off I also updated 2 packages:

• manjaro-hello
• obs-studio-git

Past week I also updated a bunch of packages:

• ell
• pacman
• linux58
• nvidia-450
• vivaldi
• g13-git
• mhwd
• …

Here are some of the commands that I used when following the troubleshoot:

systemctl status bluetooth

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Fri 2020-09-18 15:13:13 MDT; 1min 39s ago
       Docs: man:bluetoothd(8)
   Main PID: 1259 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38449)
     Memory: 2.8M
     CGroup: /system.slice/bluetooth.service
             └─1259 /usr/lib/bluetooth/bluetoothd

set 18 15:13:13 pc bluetoothd[1259]: Bluetooth daemon 5.54
set 18 15:13:13 pc systemd[1]: Started Bluetooth service.
set 18 15:13:13 pc bluetoothd[1259]: Starting SDP server
set 18 15:13:13 pc bluetoothd[1259]: Bluetooth management interface 1.17 initialized
set 18 15:13:16 pc bluetoothd[1259]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/A2DPSink/sbc
set 18 15:13:16 pc bluetoothd[1259]: Endpoint registered: sender=:1.53 path=/MediaEndpoint/A2DPSource/sbc
set 18 15:13:20 pc bluetoothd[1259]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSink/sbc
set 18 15:13:20 pc bluetoothd[1259]: Endpoint unregistered: sender=:1.53 path=/MediaEndpoint/A2DPSource/sbc
set 18 15:13:22 pc bluetoothd[1259]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSink/sbc
set 18 15:13:22 pc bluetoothd[1259]: Endpoint registered: sender=:1.82 path=/MediaEndpoint/A2DPSource/sbc

bluetoothctl show

Controller AD:DR:ES:SM:AC (public)
	Name: pc
	Alias: pc
	Class: 0x00000000
	Powered: yes
	Discoverable: yes
	DiscoverableTimeout: 0x00000000
	Pairable: yes
	UUID: Message Notification Se.. (UUID)
	UUID: A/V Remote Control        (UUID)
	UUID: OBEX Object Push          (UUID)
	UUID: Message Access Server     (UUID)
	UUID: PnP Information           (UUID)
	UUID: IrMC Sync                 (UUID)
	UUID: Vendor specific           (UUID)
	UUID: Headset AG                (UUID)
	UUID: A/V Remote Control Target (UUID)
	UUID: Generic Attribute Profile (UUID)
	UUID: Phonebook Access Server   (UUID)
	UUID: Audio Sink                (UUID)
	UUID: Generic Access Profile    (UUID)
	UUID: Headset                   (UUID)
	UUID: Audio Source              (UUID)
	UUID: OBEX File Transfer        (UUID)
	Modalias: usb:ID
	Discovering: no
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x05 (5)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedSecondaryChannels: 1M
	SupportedSecondaryChannels: 2M
	SupportedSecondaryChannels: Coded

hcitool lescan

Set scan parameters failed: Connection timed out

lsmod | grep blue

bluetooth             720896  43 btrtl,btintel,btbcm,bnep,btusb,rfcomm
ecdh_generic           16384  2 bluetooth
rfkill                 28672  8 bluetooth,cfg80211
crc16                  16384  2 bluetooth,ext4

hcitool dev

Devices:
	hci0	AD:DR:ES:SM:AC

rfkill list

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

bluetoothctl scan on

First it shows nothing. If I run it again I get
Failed to start discovery: org.bluez.Error.InProgress

Does anyone have any idea what else should I try or what I am missing here ?

Thank you very much.

[Nils]

Here in the forum there is a bunch of people were having problems with bluetooth when the kernel is changed. In special with the linux58

Upgrade to Kernel 5.8.0-2 breaks bluetooth magic keyboard

I use an Apple magic keyboard over bluetooth, which has been working fine up until today when I upgraded my Kernel to 5.8.0-2. I am able to boot back into the 5.7.14-1 kernel and connect again, so it must be something related to kernel updates. I started the bluetooth daemon in debug mode and captured the output for both kernels (see below). I see some connection errors, but nothing that is really helpful. Are there any other troubleshoothing steps I could take that might provide helpful infor…

Failed to start load kernel modules and /boot/efi

I was running on 5.4 and tried to get my bluetooth to work. So I tried all of the possible kernels up from 5.4 and installed all of them. Tested them and none worked, i was on kernel 5.9 (experimental) and then i uninstalled all of them except 5.4. I was running 5.9 when i uninstalled it. Then i restarted and after selecting manjaro in grub menu i got this error Failed to start: Load Kernel Modules Failed to mount /boot/efi Dependency Failed for local File system … After that I followed thi…

But when I try to boot on any other kernel from the bootloader Manjaro cannot mount the /home and other locations. So I tried to force it.

I fixed it by running

sudo mhwd-kernel -i linux57 rmc

*rmc will not work if you have dependencies on linux58
*I also recommend you to try a kernel that was working for you before.

I found it here.
https://wiki.manjaro.org/index.php/Manjaro_Kernels#Selecting_Kernels

[tafkamax]

Thank you for the response. At the moment I got everything working again, by reinstalling Manjaro and I am using 5.4 LTS kernel at the moment and haven’t changed to a newer one.