You are not logged in.
As of late, I have migrated to Arch and have been enjoying the ride. Initially, bluetooth worked without a issue but, suddenly it stop working. Currently I am using gnome with the gnome-bluetooth-3.0 (which worked in the past). Here is some info about my system.
rfkill list:
0: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
1: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
bluetoothctl show:
No default controller available
/usr/lib/bluetooth/bluetoothd -n -d:
bluetoothd[14380]: Bluetooth daemon 5.76
bluetoothd[14380]: src/main.c:parse_config() parsing /etc/bluetooth/main.conf
D-Bus setup failed: Name already in use
bluetoothd[14380]: src/main.c:main() Unable to get on D-Bus
dmesg | grep -iE 'blue|firm':
[ 0.092313] Spectre V2 : Enabling Speculation Barrier for firmware calls
[ 0.289860] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[ 0.319229] acpi PNP0A08:00: [Firmware Info]: ECAM [mem 0xf8000000-0xfbffffff] for domain 0000 [bus 00-3f] only partially covers this bridge
[ 5.750993] [drm] Found VCN firmware Version ENC: 1.15 DEC: 3 VEP: 0 Revision: 0
[ 5.751004] amdgpu 0000:03:00.0: amdgpu: Will use PSP to load VCN firmware
[ 8.211733] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
[ 8.469283] rtw_8822be 0000:01:00.0: Firmware version 27.2.0, H2C version 13
[ 81.753719] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 181.593732] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 416.452509] Bluetooth: Core ver 2.22
[ 416.452566] NET: Registered PF_BLUETOOTH protocol family
[ 416.452568] Bluetooth: HCI device and connection manager initialized
[ 416.452575] Bluetooth: HCI socket layer initialized
[ 416.452579] Bluetooth: L2CAP socket layer initialized
[ 416.452585] Bluetooth: SCO socket layer initialized
[ 427.758486] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 427.758493] Bluetooth: BNEP filters: protocol multicast
[ 427.758500] Bluetooth: BNEP socket layer initialized
[ 523.567509] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 773.594154] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 1045.593607] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 1229.703585] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 1341.700499] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 1391.620235] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 1670.663541] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
[ 1720.580230] rtw_8822be 0000:01:00.0: firmware failed to leave lps state
Last edited by Armgun (2024-06-11 00:24:19)
Offline
Actually, after a couple of reboots, not only was my bluetooth controller picked up but, is is even usable in Gnome.
bluetoothctl show:
Controller 20:4E:F6:2D:59:D6 (public)
Manufacturer: 0x005d (93)
Version: 0x08 (8)
Name: AlexAr
Alias: AlexAr
Class: 0x00000000 (0)
Powered: no
PowerState: off-blocked
Discoverable: no
DiscoverableTimeout: 0x000000b4 (180)
Pairable: yes
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree Audio Gateway (0000111f-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: Audio Source (0000110a-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Generic Access Profile (00001800-0000-1000-8000-00805f9b34fb)
UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
UUID: Device Information (0000180a-0000-1000-8000-00805f9b34fb)
UUID: Vendor specific (03b80e5a-ede8-4b33-a751-6ce34ec4c700)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
Modalias: usb:v1D6Bp0246d054C
Discovering: no
Roles: central
Roles: peripheral
Advertising Features:
ActiveInstances: 0x00 (0)
SupportedInstances: 0x05 (5)
SupportedIncludes: appearance
SupportedIncludes: local-name
Offline