Hello everyone,
Garuda is my first Arch distro, and with it I've encountered an interesting problem. While Bluetooth is able to search for things just fine, and I believe even able to pair to them, it cannot connect properly. I was able to properly connect to my Bluetooth speaker just one time, and then later (upon noticing I did not have sound anymore) I was unable to Bluetooth connect to any device.
While trying to connect to a paired device, it will claim to do so (though without any function) for about 15 seconds and then disconnect itself. After reading through the forums, I've come across several suggestions such as installing/restarting pulseaudio-type packages and checking bluetoothctl (which logs that the devices disconnected, but did not report any issue connecting in the first place). I've tried a couple other minor things as well, like installing a different Bluetooth controller (blueman) but with no change.
At the moment, I am using pipewire because that is what the installation came with. Also, after having dealt with this for a while, I tried a live-boot of both Garuda and Linux Mint and discovered that this problem spanned across them all.
I am hoping, even if this is not necessarily an issue with Garuda itself, that Garuda has the tools necessary to fix it! I will provide as much information as I can going forward, though this is my first Arch distro so I may need a bit more detail on some things. Thank you to anyone who can offer any insight!
Things tried:
Output of inxi -Faz
System: Kernel: 5.14.9-zen2-1-zen x86_64 bits: 64 compiler: gcc v: 11.1.0
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen root=UUID=7884d1c2-67fb-4f58-b08f-7e574e71a3f9
rw rootflags=subvol=@ quiet splash rd.udev.log_priority=3 vt.global_cursor_default=0
systemd.unified_cgroup_hierarchy=1 loglevel=3
Desktop: KDE Plasma 5.22.5 tk: Qt 5.15.2 info: latte-dock wm: kwin_x11 vt: 1 dm: SDDM
Distro: Garuda Linux base: Arch Linux
Machine: Type: Desktop Mobo: ASRock model: B450M/ac serial: <filter> UEFI-[Legacy]: American Megatrends
v: P1.70 date: 12/17/2019
CPU: Info: 6-Core model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 family: 17 (23)
model-id: 71 (113) stepping: 0 microcode: 8701013 cache: L2: 3 MiB
flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 86231
Speed: 3536 MHz min/max: 2200/3600 MHz boost: enabled Core speeds (MHz): 1: 3536 2: 3518
3: 3593 4: 3504 5: 3603 6: 3587 7: 3599 8: 3591 9: 3657 10: 3590 11: 3594 12: 3599
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2
mitigation: Full AMD retpoline, IBPB: conditional, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics: Device-1: NVIDIA TU106 [GeForce RTX 2070] vendor: Micro-Star MSI driver: nvidia v: 470.74
alternate: nouveau,nvidia_drm bus-ID: 07:00.0 chip-ID: 10de:1f02 class-ID: 0300
Device-2: Logitech C920 HD Pro Webcam type: USB driver: snd-usb-audio,uvcvideo bus-ID: 5-3:2
chip-ID: 046d:0892 class-ID: 0102 serial: <filter>
Display: x11 server: X.Org 1.20.13 compositor: kwin_x11 driver: loaded: nvidia
unloaded: modesetting alternate: fbdev,nouveau,nv,vesa display-ID: :0 screens: 1
Screen-1: 0 s-res: 3840x1080 s-dpi: 93 s-size: 1049x323mm (41.3x12.7") s-diag: 1098mm (43.2")
Monitor-1: DP-0 res: 1920x1080 dpi: 90 size: 544x303mm (21.4x11.9") diag: 623mm (24.5")
Monitor-2: DP-2 res: 1920x1080 dpi: 90 size: 544x303mm (21.4x11.9") diag: 623mm (24.5")
OpenGL: renderer: NVIDIA GeForce RTX 2070/PCIe/SSE2 v: 4.6.0 NVIDIA 470.74 direct render: Yes
Audio: Device-1: NVIDIA TU106 High Definition Audio vendor: Micro-Star MSI driver: snd_hda_intel
v: kernel bus-ID: 07:00.1 chip-ID: 10de:10f9 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: ASRock driver: snd_hda_intel v: kernel
bus-ID: 09:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Logitech C920 HD Pro Webcam type: USB driver: snd-usb-audio,uvcvideo bus-ID: 5-3:2
chip-ID: 046d:0892 class-ID: 0102 serial: <filter>
Device-4: Logitech Yeti X type: USB driver: hid-generic,snd-usb-audio,usbhid bus-ID: 5-4:3
chip-ID: 046d:0aaf class-ID: 0300 serial: <filter>
Sound Server-1: ALSA v: k5.14.9-zen2-1-zen running: yes
Sound Server-2: JACK v: 1.9.19 running: no
Sound Server-3: PulseAudio v: 15.0 running: no
Sound Server-4: PipeWire v: 0.3.38 running: yes
Network: Device-1: Intel Dual Band Wireless-AC 3168NGW [Stone Peak] driver: iwlwifi v: kernel
bus-ID: 04:00.0 chip-ID: 8086:24fb class-ID: 0280
IF: wlp4s0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169
v: kernel port: f000 bus-ID: 05:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp5s0 state: down mac: <filter>
IF-ID-1: ztugaw5fxo state: unknown speed: 10 Mbps duplex: full mac: <filter>
Bluetooth: Device-1: Intel Wireless-AC 3168 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-1:2
chip-ID: 8087:0aa7 class-ID: e001
Report: bt-adapter ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
hardware: no software: yes address: <filter>
Drives: Local Storage: total: 4.55 TiB used: 262.26 GiB (5.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD serial: <filter>
rev: 1B4QFXO7 temp: 40.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Samsung model: SSD 870 QVO 2TB size: 1.82 TiB block-size:
physical: 512 B logical: 512 B speed: 6.0 Gb/s type: SSD serial: <filter> rev: 2B6Q scheme: MBR
Partition: ID-1: / raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 262.26 GiB (28.2%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-2: /home raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 262.26 GiB (28.2%) fs: btrfs
dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /var/log raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 262.26 GiB (28.2%)
fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
ID-4: /var/tmp raw-size: 931.51 GiB size: 931.51 GiB (100.00%) used: 262.26 GiB (28.2%)
fs: btrfs dev: /dev/nvme0n1p1 maj-min: 259:1
Swap: Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: zram size: 31.28 GiB used: 0 KiB (0.0%) priority: 100 dev: /dev/zram0
Sensors: System Temperatures: cpu: 59.5 C mobo: N/A gpu: nvidia temp: 41 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 32%
Info: Processes: 289 Uptime: 35m wakeups: 0 Memory: 31.28 GiB used: 2.79 GiB (8.9%) Init: systemd
v: 249 tool: systemctl Compilers: gcc: 11.1.0 Packages: pacman: 1673 lib: 490 Shell: fish
v: 3.3.1 default: Bash v: 5.1.8 running-in: konsole inxi: 3.3.06
I have, when testing, removed the rfk-block that appears in the above output.
I have freshly reinstalled Garuda, as well as freshly installing a Debian based distro (Linux Mint) with no change.
Having been told that it may be a 'dual-boot' issue, I attempted to pair a device that had previously never paired to the machine, with no difference in behavior.
I have created the file /etc/modprobe.d/iwlwifi.conf and pasted options iwlwifi bt_coex_active=0 inside and restarted, in case it was a coexistence issue, but nothing changed.
When using blueman, the error I receive after 30 seconds of having been connected is 'Connection Failed: Connection timed out' and then it disconnects.
Here is the output of bluetoothctl throughout the process:
Agent registered
[bluetooth]# info FC:03:9F:E9:51:DA
Device FC:03:9F:E9:51:DA (public)
Name: [AV] Samsung Soundbar N400 N-Series
Alias: [AV] Samsung Soundbar N400 N-Series
Class: 0x00000414
Icon: audio-card
Paired: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
[bluetooth]# connect FC:03:9F:E9:51:DA
Attempting to connect to FC:03:9F:E9:51:DA
[CHG] Device FC:03:9F:E9:51:DA Connected: yes
[CHG] Device FC:03:9F:E9:51:DA ServicesResolved: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device FC:03:9F:E9:51:DA ServicesResolved: no
[CHG] Device FC:03:9F:E9:51:DA Connected: no
