Bluetooth not able to Connect

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 [email protected] 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

Welcome :slight_smile:

Then why don't you post the output of

inxi -Faz

as requested by the template?

1 Like

Certainly, I apologize, I must have missed that request. Here it is:

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 [email protected] 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
1 Like

This could be your problem.
Try
sudo rfkill unblock all

3 Likes

Unfortunately not. I am also capable of removing the soft block through the GUI, and while both methods change the output of inxi -Faz it does nothing to resolve the issue itself. Thank you for your suggestion, though!

1 Like

I tried :frowning:
Maybe give a look at the Arch wiki:
https://wiki.archlinux.org/title/Bluetooth
I'd particularly check chapter 6.12, which actually just links to this:
https://wiki.archlinux.org/title/Network_configuration/Wireless#Bluetooth_coexistence
It doesn't look like your case, but maybe you could try...

2 Likes

Having followed both links, it is worth noting that the devices I have been trying to connect were all previously connected to Windows 10 on this same system. However, I am unable to recover the key, as I no longer have access the Windows system drive. I also followed the second link you sent regarding Bluetooth coexistence, but I am unable to locate /etc/modprobe.d/iwlwifi.conf to make any changes.

Also, I am going to be heading out to work shortly, so while I will retain remote access to my PC, I won't be in a position to try pairing any Bluetooth devices for a while. I will still be able to respond, though!

1 Like

I believe this has to be "manually" created, just
sudo micro /etc/modprobe.d/iwlwifi.conf

1 Like

Alright, I've created that file, entered what the Wiki suggested and restarted, but no luck. Also, I paired a fresh Bluetooth device that had never previously been connected to the old Windows, but also no luck.

I thought that it may be helpful for me to post the output of bluetoothctl throughout the connecting process, so people can see just what I mean when I say it can't connect. I started to connect too early in the middle, but the rest of the output is consistent with what I've been getting this whole time.

[bluetooth]# power on
Changing power on succeeded
[bluetooth]# agent on
Agent is already registered
[bluetooth]# default-agent
Default agent request successful
[bluetooth]# scan on
Discovery started
[CHG] Controller CC:F9:E4:36:B8:0B Discovering: yes
[NEW] Device 72:35:B7:14:87:A8 72-35-B7-14-87-A8
[NEW] Device FC:03:9F:E9:51:DA [AV] Samsung Soundbar N400 N-Series
[NEW] Device 78:83:F4:A3:1B:F4 78-83-F4-A3-1B-F4
[NEW] Device 53:8A:B6:4B:3D:FB 53-8A-B6-4B-3D-FB
[NEW] Device 00:1F:FF:6A:75:4D PR BT 309F
[bluetooth]# trust FC:03:9F:E9:51:DA
[CHG] Device FC:03:9F:E9:51:DA Trusted: yes
Changing FC:03:9F:E9:51:DA trust succeeded
[CHG] Device 53:8A:B6:4B:3D:FB RSSI: -56
[CHG] Device 78:83:F4:A3:1B:F4 ManufacturerData Key: 0x004c
[CHG] Device 78:83:F4:A3:1B:F4 ManufacturerData Value:
10 05 0d 1c 03 be 48                             ......H
[bluetooth]# pair FC:03:9F:E9:51:DA
Attempting to pair with FC:03:9F:E9:51:DA
[CHG] Device FC:03:9F:E9:51:DA Connected: yes
[CHG] Device 78:83:F4:A3:1B:F4 RSSI: -75
[[AV] Samsung Soundbar N400 N-Series]# connect FC:03:9F:E9:51:DA
Attempting to connect to FC:03:9F:E9:51:DA
Failed to connect: org.bluez.Error.InProgress
[CHG] Device 53:8A:B6:4B:3D:FB RSSI: -65
[CHG] Device 72:35:B7:14:87:A8 RSSI: -65
[CHG] Device FC:03:9F:E9:51:DA ServicesResolved: yes
[CHG] Device FC:03:9F:E9:51:DA Paired: yes
Pairing successful
[CHG] Device FC:03:9F:E9:51:DA ServicesResolved: no
[CHG] Device FC:03:9F:E9:51:DA Connected: 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 72:35:B7:14:87:A8 RSSI: -76
[CHG] Device 78:83:F4:A3:1B:F4 RSSI: -66
[CHG] Device 78:83:F4:A3:1B:F4 RSSI: -74
[CHG] Device 53:8A:B6:4B:3D:FB RSSI: -56
[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
[CHG] Device 53:8A:B6:4B:3D:FB RSSI: -66
[bluetooth]#

After having fully reinstalled, the issue has persisted. I also wiped Garuda, temporarily, and replaced it with Linux Mint (which used pulseaudio by default, rather than pipewire) and that did not help. I've ready quite a bit about the issue from various sources, and the thing that I currently think may be the issue is an inconsistency somewhere with Bluetooth profiles. I'm trying to research that more now.

1 Like

When using 'blueman', the error that I receive after 30 seconds or so of connecting is 'Connection Failed: Connection timed out'. I'm going to start updating the original post with all this information, since I'm sure it is hard to find everything I've provided spread across all these messages.

1 Like

I've just tried downgrading the various bluez packages down to 5.58-1 as suggested here. https://www.reddit.com/r/archlinux/comments/o7sig7/psa_for_anyone_having_issues_with_bluetooth/

After following those steps, it didn't change anything. I also tried switching to bluez-git, also no change.

Does anyone know if there is some final step to that process that I need to do to solidify those changes, potentially? I restarted after each change I made.

Also, something that I have noticed is that, after a restart, a notification will appear that says 'Connected to ' before disconnecting again. The reason that's odd to me is because the device in question was off at the time, so it shouldn't have taken 30-40 seconds for an auto-reconnect to fail, right?

I dual boot Garuda Linux alongside Windows 10. So when I connect a bluetooth device to Win10 and then later come back to Garuda to connect, it doesn't connect immediately. I have to remove the device from paired devices, then then pair with it again. After that I have no problems with connecting them.

1 Like

What is concerning me is that the issue persists even with a different distro (and Mint I guess uses also an older Kernel, which might have been an option to try) and with devices never paired with Windows before.
My wits end would be to update the BIOS, although I see no references to bluetooth fixes in their page the descriptions are really minimal, so, who knows...?:

I hope it is not an HW problem...
In addition to that, I just found this:
https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#firmware
It looks like that "Those devices will not be supported by the newest firmware versions: ... 3168's latest firmware version is -29.ucode".
I have no idea what that might mean and if that might play a role in this...

2 Likes

I don't know much about the iwlwifi firmware either, though I would imagine that if my wireless was not supported I should expect some kind of WiFi issues as well, but my WiFi is exactly the same as it's always been (in regards to download/upload).

I suppose the question with iwlwifi would be 'what happens when you're not supported'. I will look into that as a possible cause.

Alright, I believe we're in the clear with the iwlwifi firmware.

I went into /lib/firmware and discovered that I do have iwlfifi-3168-29.ucode installed. I want to trust that these various distros are capable of using that installed firmware, but I am not sure how I would check. Of course, I do have WiFi and the ability to scan for Bluetooth devices, so I want to say that the firmware is all good.

1 Like

Alright, it's been resolved! The solution was to install bluez-git, delete /var/lib/bluetooth and, most importantly drain the power from my PC. I tried the first two steps a while back, which was detailed in a different thread. I never drained the power because most people said that their issue was resolved after the first two steps, so I figured there was no need.

But I found one other person who, like me, was only able to finalize those changes after draining the power. I'm not entirely sure how that is different that a restart, but I'll take it!

Thank you @filo for your assistance throughout this process. I'm sure I wouldn't have eventually found my way to that solution without your helping me research. Thank you very much!

This is my first time using the forum, so I'll try to 'resolve' this thread properly, but please let me know if there's another step I need to go through. Thanks again!

2 Likes

Draining the power! That sounds interesting!

1 Like

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.