[SOLVED] Bluetooth suddenly stopped working

pal_bjartan · 2023-03-28 21:28:02

Description of the problem

Bluetooth is shown as turned on in the system menu (top-right), and I find all my devices listed, but as disconnected. Attempts at manually trying to connect or re-pair the devices have been unsuccessful.

Backstory for context

I ran updates yesterday. Among the updates were a Linux kernel update (linux-6.2.8.arch1-1) For reasons described in a Reddit post, I held back the Nvidia graphics driver updates (nvidia-530.41.03-1). This rendered me unable to log in to my user session in GNOME on the `linux` kernel, but I was still able to log in on `linux-lts`. Seemingly, this can be attributed to holding back the driver update.

Describing steps taken

1. At first Bluetooth was working fine (on Linux LTS), then, after a reboot, **it suddenly stopped working**, and I was unable to connect my peripherals (keyboard, mouse, and controller). (linux-6.2.7-arch1-1 and nvidia-525.89.02-12)
2. I decided to roll-back my system to a pre-upgrade state (i.e. the last BTRFS snapshot taken prior to yesterday's upgrade, kernel linux-6.2.7-arch1-1 and nvidia-525.89.02-12). However, Bluetooth still didn't work!, even if my system was restored to a state Bluetooth worked without issue in the past.
3. I then completed the full upgrade of my system, and logged in on the regular linux-6.2.8-arch1-1 kernel with the nvidia-530.41.03-1 graphics driver. This didn't help either.

Any help at sorting this out would be most appreciated.

System info and troubleshooting

System info

OS: Arch Linux x86_64 
Host: 82JY Legion 5 17ACH6H 
Kernel: Linux 6.1.21-1-lts (step 1) / 6.2.7-arch1-1 (step 2) / Linux 6.2.8-arch1-1 (step 3) 
Resolution: 1920x1080 @ 144.00Hz, 3840x2160 @ 59.94Hz 
DE: GNOME 43.3 
CPU: AMD Ryzen 7 5800H with Radeon Graphics (16) @ 3.200GHz [41.8°C] 
GPU: NVIDIA GeForce RTX 3070 Mobile / Max-Q 
GPU: AMD ATI Radeon Vega Series / Radeon Vega Mobile Series 
GPU Driver: NVIDIA 525.89.02 (step 1 & 2)/ 530.41.03 (step 3)

Bluetooth adapter is found and no rfkill

% lsusb | grep Bluetooth
Bus 003 Device 003: ID 0489:e0cd Foxconn / Hon Hai MediaTek Bluetooth Adapter

% rfkill list
0: hci0: Bluetooth
	Soft blocked: no
	Hard blocked: no
1: ideapad_wlan: Wireless LAN
	Soft blocked: no
	Hard blocked: no
2: ideapad_bluetooth: Bluetooth
	Soft blocked: no
	Hard blocked: no
3: phy0: Wireless LAN
	Soft blocked: no
	Hard blocked: no

systemctl output

% sudo systemctl status bluetooth

● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; preset: disabled)
     Active: active (running) since Tue 2023-03-28 13:34:12 CEST; 51min ago
       Docs: man:bluetoothd(8)
   Main PID: 655 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 35897)
     Memory: 4.9M
        CPU: 465ms
     CGroup: /system.slice/bluetooth.service
             └─655 /usr/lib/bluetooth/bluetoothd

mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSink/aptx
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSource/aptx
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc_xq_453
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc_xq_453
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc_xq_512
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc_xq_512
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSink/sbc_xq_552
mars 28 13:35:16 user bluetoothd[655]: Endpoint registered: sender=:1.76 path=/MediaEndpoint/A2DPSource/sbc_xq_552

Journal output

% journalctl -b 0 -g 'bluetooth'

mars 28 13:34:09 user kernel: Bluetooth: Core ver 2.22
mars 28 13:34:09 user kernel: NET: Registered PF_BLUETOOTH protocol family
mars 28 13:34:09 user kernel: Bluetooth: HCI device and connection manager initialized
mars 28 13:34:09 user kernel: Bluetooth: HCI socket layer initialized
mars 28 13:34:09 user kernel: Bluetooth: L2CAP socket layer initialized
mars 28 13:34:09 user kernel: Bluetooth: SCO socket layer initialized
mars 28 13:34:09 user kernel: Bluetooth: hci0: Device setup in 154623 usecs
mars 28 13:34:09 user kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
mars 28 13:34:09 user kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
mars 28 13:34:10 user kernel: Bluetooth: hci0: AOSP extensions version v1.00
mars 28 13:34:10 user kernel: Bluetooth: hci0: AOSP quality report is supported
mars 28 13:34:12 user systemd[1]: Starting Bluetooth service...
mars 28 13:34:12 user bluetoothd[655]: Bluetooth daemon 5.66
mars 28 13:34:12 user systemd[1]: Started Bluetooth service.
mars 28 13:34:12 user systemd[1]: Reached target Bluetooth Support.
mars 28 13:34:12 user dbus-daemon[656]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.4' (uid=0 pid=655 comm="/usr/lib/bluetooth/bluet>
mars 28 13:34:12 user bluetoothd[655]: Bluetooth management interface 1.22 initialized
mars 28 13:34:12 user kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
mars 28 13:34:12 user kernel: Bluetooth: BNEP filters: protocol multicast
mars 28 13:34:12 user kernel: Bluetooth: BNEP socket layer initialized
mars 28 13:34:12 user kernel: Bluetooth: MGMT ver 1.22
mars 28 13:34:12 user NetworkManager[664]: <info>  [1680003252.8838] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.42.4-2/libnm-device-plugin-bluetooth.so)
mars 28 13:34:57 user kernel: Bluetooth: hci0: Device setup in 166958 usecs
mars 28 13:34:57 user kernel: Bluetooth: hci0: HCI Enhanced Setup Synchronous Connection command is advertised, but not supported.
mars 28 13:34:57 user kernel: Bluetooth: hci0: AOSP extensions version v1.00
mars 28 13:34:57 user kernel: Bluetooth: hci0: AOSP quality report is supported
mars 28 13:35:16 user pulseaudio[2241]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
mars 28 13:35:16 user kernel: Bluetooth: RFCOMM TTY layer initialized
mars 28 13:35:16 user kernel: Bluetooth: RFCOMM socket layer initialized
mars 28 13:35:16 user kernel: Bluetooth: RFCOMM ver 1.11
mars 28 13:39:08 user gnome-control-c[3814]: BluetoothHardwareAirplaneMode: 0
mars 28 13:39:08 user systemd[1953]: Starting Bluetooth OBEX service...
mars 28 13:39:08 user systemd[1953]: Started Bluetooth OBEX service.
mars 28 14:25:57 user dbus-daemon[656]: [system] Activating via systemd: service name='org.freedesktop.home1' unit='dbus-org.freedesktop.home1.service' requested by ':1.135' (uid=0 pid=6412 comm="sudo systemctl status bluetoo>
mars 28 14:26:05 user sudo[6412]: user : TTY=pts/0 ; PWD=/home/user ; USER=root ; COMMAND=/usr/bin/systemctl status bluetooth

user% journalctl -b 0 -g 'bluez'    

mars 28 13:34:12 user NetworkManager[664]: <info>  [1680003252.8838] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.42.4-2/libnm-device-plugin-bluetooth.so)
mars 28 13:35:16 user pulseaudio[2241]: Could not find org.bluez.BatteryProviderManager1.RegisterBatteryProvider(), is bluetoothd started with experimental features enabled (-E flag)?
mars 28 13:39:08 user dbus-daemon[1978]: [session uid=1000 pid=1978] Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' requested by ':1.97' (uid=1000 pid=3814 comm="/usr/bin/gnome-contro>
mars 28 13:39:08 user dbus-daemon[1978]: [session uid=1000 pid=1978] Successfully activated service 'org.bluez.obex'

Running Gnome control center from terminal:

% gnome-control-center
      
bluetooth-cc-panel-Message: 14:38:06.698: BluetoothHardwareAirplaneMode: 0

Not sure how to interpret thus. Is Bluetooth in airplane mode?

bluetoothctl also displays device as active, but unable to find devices

% sudo bluetoothctl

Agent registered
[CHG] Controller 10:6F:D9:F8:22:7A Pairable: yes

[bluetooth]# show
Controller 10:6F:D9:F8:22:7A (public)
	Name: user
	Alias: user
	Class: 0x007c010c
	Powered: yes
	Discoverable: no
	DiscoverableTimeout: 0x000000b4
	Pairable: yes
	UUID: Message Notification Se.. (00001133-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: OBEX Object Push          (00001105-0000-1000-8000-00805f9b34fb)
	UUID: Message Access Server     (00001132-0000-1000-8000-00805f9b34fb)
	UUID: PnP Information           (00001200-0000-1000-8000-00805f9b34fb)
	UUID: IrMC Sync                 (00001104-0000-1000-8000-00805f9b34fb)
	UUID: Vendor specific           (00005005-0000-1000-8000-0002ee000001)
	UUID: Headset                   (00001108-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
	UUID: Phonebook Access Server   (0000112f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
	UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree Audio Gateway   (0000111f-0000-1000-8000-00805f9b34fb)
	UUID: Audio Source              (0000110a-0000-1000-8000-00805f9b34fb)
	UUID: OBEX File Transfer        (00001106-0000-1000-8000-00805f9b34fb)
	Modalias: usb:v1D6Bp0246d0542
	Discovering: no
	Roles: central
	Roles: peripheral
Advertising Features:
	ActiveInstances: 0x00 (0)
	SupportedInstances: 0x14 (20)
	SupportedIncludes: tx-power
	SupportedIncludes: appearance
	SupportedIncludes: local-name
	SupportedSecondaryChannels: 1M
	SupportedSecondaryChannels: 2M
	SupportedSecondaryChannels: Coded

[bluetooth]# devices
Device F8:B5:1C:39:61:EE SteamController
Device E4:17:D8:64:4B:3B Pro Controller
Device CC:D4:8A:40:77:46 ProtoArc XK21
Device D8:39:F6:97:1F:00 ELECOM Relacon
Device D7:5E:C6:19:D7:6D StadiaV8W7-d76d
Device E4:17:D8:60:F7:79 8Bitdo SN30 Pro
Device FE:3D:47:33:DD:01 MX Ergo

I tried removing my mouse and keyboard, "MX Ergo" and "ProtoArc XK21", and then setting it in pairing mode and run `scan on` again:

[bluetooth]# remove FE:3D:47:33:DD:01
[DEL] Device FE:3D:47:33:DD:01 MX Ergo
Device has been removed

[bluetooth]# remove CC:D4:8A:40:77:46
[DEL] Device CC:D4:8A:40:77:46 ProtoArc XK21
Device has been removed

[bluetooth]# scan on
Discovery started

As you can see no devices are discovered even if they are in pairing mode.

Last edited by pal_bjartan (2023-03-29 09:05:03)

V1del · 2023-03-28 23:43:13

General note if you want to be holding back on nvidia drivers you should install nvidia-dkms of the held back version and install linux-headers of the current version of the kernel, that way whatever nvidia module version you are staying will get rebuilt for newer kernels.

For the actual issue, did "reboot" include a side step into Windows? Make sure fast-boot is disabled there. FWIW if both linux and linux-lts are affected it might also be a regression in the current stable patch series, but assuming the snapshot restored properly that might shoot that theory (might because there are some stipulation here, was this a proper RW restore?) Other than that it could be general firmware issues, might want to reset state here by shutting down unplugging battery and cable for a few seconds or if you can't take out the battery holding the power button while turned off for a few secs usually gets you the same end result.

pal_bjartan · 2023-03-29 09:02:54

V1del wrote:

General note if you want to be holding back on nvidia drivers you should install nvidia-dkms of the held back version and install linux-headers of the current version of the kernel, that way whatever nvidia module version you are staying will get rebuilt for newer kernels.

Thanks for that piece of vital information (This should probably have been made clearer in the Arch Wiki's Nvidia entry.), which leads to the following questions:

How do I install an older, specific version of a package, in this case nvidia-dkms?
Is there a way to select between drivers, or do I need to remove the nvidia package before installing nvidia-dkms?
Are there any drawbacks to using nvidia-dkms over nvidia?

V1del wrote:

For the actual issue, did "reboot" include a side step into Windows? Make sure fast-boot is disabled there. FWIW if both linux and linux-lts are affected it might also be a regression in the current stable patch series, but assuming the snapshot restored properly that might shoot that theory (might because there are some stipulation here, was this a proper RW restore?) Other than that it could be general firmware issues, might want to reset state here by shutting down unplugging battery and cable for a few seconds or if you can't take out the battery holding the power button while turned off for a few secs usually gets you the same end result.

Ok, so the problem sorted itself out after I fully powered down the computer overnight (instead of just rebooting).
I don't have dual-boot with Windows, so that can't be the issue. It could seem this might be an issue with the hardware/firmware, but at least it's working again for now.

V1del · 2023-03-29 11:01:48

For prosperity's sake:

https://wiki.archlinux.org/title/Arch_Linux_Archive
For the case we have here you'd remove the nvidia package
No, you increase the "installation time" during a kernel update by as long as it takes your computer to build the kernel module, other than that they will act the same (in fact the nvidia package is just a "prebuilt" of nvidia-dkms for the current kernel, your nvidia kernel modules always need to match the kernel they intend to be used with, nvidia-dkms automates that for every kernel whose headers are installed)

Also another note on the general note, you will also need to hold back {lib32-,}nvidia-utils to the relevantly matching actual nvidia version of the kernel module i.e. nvidia-utils 525.89.02 <-> nvidia 525.89.02 and so forth

Last edited by V1del (2023-03-29 11:05:54)

pal_bjartan · 2023-03-29 12:15:04

Thanks for your reply. I realized installing nvidia-dkms will automatically purge nvidia and nvidia-lts.

I was now able to log in after upgrading while holding back the Nvidia drivers (to see solution).

Arch Linux

#1 2023-03-28 21:28:02