Failed to pair with bluetooth controller

Hey @all,

why I’m here
I’m new to Garuda and I’m on my way to completely switch from Win 10 to Garuda, mainly for gaming and working on light office tasks, etc.

why do I post this issue
I search for your help to get my controller working.
I hope to find the culprit and hope that my PC with 7 years old hardware is not getting too old now…

what have I done before I post here
I installed Garuda a few weeks ago and don’t know if I did something wrong, so I did a fresh install of Garuda.
I updated my system with the Garuda Welcome Assistant.
I searched the web, forums and wiki to get a solution.
The most issues about the same or similar topic are a few years old (2016 to 2023) and the solution most of the time was an system update to the current version…

what is my problem
I want to connect my Stadia Controller with my PC via bluetooth, but it is not possible.
Yes, the bluetooth mode is enabled and the controller is working on other devices (Android Smartphone, SteamDeck, Surface Go (Win10)).
I got six different Stadia Controllers and all are working fine with other devices.

what have I done to fix the problem
After I tried to connect my Controller with the system settings → bluetooth I only got an error message without good informations (“There was en Error during Setup deivce XX”), so I used
bluetoothctlscan onpair with [MAC ADRESS]
My controller is found, but does not connect and I get this error message:
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationCanceled

Here is the output:

╭─chris@Isboks in ~ 
╰─λ bluetoothctl
[bluetooth]# Agent registered
[bluetooth]# scan on
[bluetooth]# SetDiscoveryFilter success
[bluetooth]# Discovery started
[bluetooth]# [CHG] Controller XX:XX:01 Discovering: yes
[bluetooth]# [CHG] Device XX:XX:02 RSSI: 0xffffffd1 (-47)
[bluetooth]# [CHG] Device XX:XX:02 TxPower: 0xfffffff8 (-8)
[bluetooth]# [CHG] Device XX:XX:03  RSSI: 0xffffffd4 (-44)
[bluetooth]# [CHG] Device XX:XX:03  RSSI: 0xffffffd6 (-42)
[bluetooth]# pair XX:XX:02 
Attempting to pair with XX:XX:02 
[StadiaHSQP-73ec]# [CHG] Device XX:XX:02  Connected: yes
[bluetooth]# [CHG] Device XX:XX:02  Connected: no
[bluetooth]# Failed to pair: org.bluez.Error.AuthenticationCanceled
[bluetooth]# [CHG] Device XX:XX:02  WakeAllowed: yes

Garuda-inix output

╭─chris@Isboks in ~ 
╰─λ garuda-inxi
System:
Kernel: 6.12.4-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=9398512b-020f-44b1-a0f1-0b3c53af6144 rw rootflags=subvol=@
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.2.4 tk: Qt v: N/A info: frameworks v: 6.9.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: ASUS product: All Series v: N/A
serial: <superuser required>
Mobo: ASUSTeK model: STRIX X99 GAMING v: Rev 1.xx
serial: <superuser required> part-nu: All uuid: <superuser required>
UEFI: American Megatrends v: 2101 date: 07/10/2019
CPU:
Info: model: Intel Core i7-6850K bits: 64 type: MT MCP arch: Broadwell
gen: core 6 level: v3 note: check built: 2015-18 process: Intel 14nm
family: 6 model-id: 0x4F (79) stepping: 1 microcode: 0xB000040
Topology: cpus: 1x dies: 1 clusters: 6 cores: 6 threads: 12 tpc: 2
smt: enabled cache: L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB
desc: 6x256 KiB L3: 15 MiB desc: 1x15 MiB
Speed (MHz): avg: 3508 min/max: 1200/4000 scaling: driver: intel_cpufreq
governor: performance cores: 1: 3508 2: 3508 3: 3508 4: 3508 5: 3508 6: 3508
7: 3508 8: 3508 9: 3508 10: 3508 11: 3508 12: 3508 bogomips: 86341
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3
Vulnerabilities: <filter>
Graphics:
Device-1: Advanced Micro Devices [AMD/ATI] Navi 31 [Radeon RX 7900 XT/7900
XTX/7900 GRE/7900M] vendor: Sapphire NITRO+ driver: amdgpu v: kernel
arch: RDNA-3 code: Navi-3x process: TSMC n5 (5nm) built: 2022+ pcie:
gen: 3 speed: 8 GT/s lanes: 16 link-max: gen: 4 speed: 16 GT/s ports:
active: DP-1,HDMI-A-1 empty: DP-2,HDMI-A-2,Writeback-1 bus-ID: 03:00.0
chip-ID: 1002:744c class-ID: 0300
Display: wayland server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.4
compositor: kwin_wayland driver: X: loaded: amdgpu
unloaded: modesetting,radeon alternate: fbdev,vesa dri: radeonsi
gpu: amdgpu d-rect: 3640x3360 display-ID: 0
Monitor-1: DP-1 pos: bottom-r res: 2560x1440 size: N/A modes: N/A
Monitor-2: HDMI-A-1 pos: primary,top-left res: 1080x1920 size: N/A
modes: N/A
API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
device: 1 drv: swrast gbm: drv: kms_swrast surfaceless: drv: radeonsi
wayland: drv: radeonsi x11: drv: radeonsi
API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.1-arch1.3
glx-v: 1.4 direct-render: yes renderer: AMD Radeon RX 7900 XTX (radeonsi
navi31 LLVM 18.1.8 DRM 3.59 6.12.4-zen1-1-zen) device-ID: 1002:744c
memory: 23.44 GiB unified: no display-ID: :1.0
API: Vulkan v: 1.4.303 layers: 10 device: 0 type: discrete-gpu name: AMD
Radeon RX 7900 XTX (RADV NAVI31) driver: N/A device-ID: 1002:744c
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
18.1.8 256 bits) driver: N/A device-ID: 10005:0000
surfaces: xcb,xlib,wayland
Audio:
Device-1: Intel C610/X99 series HD Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8d20
class-ID: 0403
Device-2: Advanced Micro Devices [AMD/ATI] Navi 31 HDMI/DP Audio
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
link-max: gen: 4 speed: 16 GT/s bus-ID: 03:00.1 chip-ID: 1002:ab30
class-ID: 0403
Device-3: Trust USB microphone driver: hid-generic,snd-usb-audio,usbhid
type: USB rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-10.4:9
chip-ID: 145f:02d9 class-ID: 0300 serial: <filter>
API: ALSA v: k6.12.4-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: N/A
Server-1: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Ethernet I218-V vendor: ASUSTeK driver: e1000e v: kernel
port: f000 bus-ID: 00:19.0 chip-ID: 8086:15a1 class-ID: 0200
IF: eno1 state: down mac: <filter>
Device-2: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
vendor: ASUSTeK driver: ath10k_pci v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 bus-ID: 07:00.0 chip-ID: 168c:003e class-ID: 0280 temp: 57.0 C
IF: wlp7s0 state: down mac: <filter>
Device-3: ASIX AX88179 Gigabit Ethernet driver: cdc_ncm type: USB rev: 3.2
speed: 5 Gb/s lanes: 1 mode: 3.2 gen-1x1 bus-ID: 6-1:2 chip-ID: 0b95:1790
class-ID: 0a00 serial: <filter>
IF: enp8s0u1c2 state: up speed: N/A duplex: half mac: <filter>
Info: services: NetworkManager, smbd, systemd-timesyncd, wpa_supplicant
Bluetooth:
Device-1: ASUSTek Qualcomm Bluetooth 4.1 driver: btusb v: 0.8 type: USB
rev: 1.1 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 2-10.1:8
chip-ID: 0b05:1825 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.1
lmp-v: 7 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 953.87 GiB used: 23.79 GiB (2.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 960 PRO 1TB
size: 953.87 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: 1B6QCXP7 temp: 31.9 C
scheme: GPT
Partition:
ID-1: / raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 23.79 GiB (2.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 584 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 23.79 GiB (2.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 23.79 GiB (2.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 953.57 GiB size: 953.57 GiB (100.00%)
used: 23.79 GiB (2.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 31.25 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 12
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 27.0 C mobo: N/A gpu: amdgpu temp: 42.0 C
mem: 36.0 C
Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
Memory: total: 32 GiB available: 31.25 GiB used: 5.15 GiB (16.5%)
Processes: 361 Power: uptime: 1h 19m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 12.49 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 2044 libs: 594 tools: octopi,paru Compilers:
clang: 18.1.8 gcc: 14.2.1 Shell: garuda-inxi default: fish v: 3.7.1
running-in: konsole inxi: 3.3.36
Garuda (2.6.26-1):
System install date:     2024-12-21
Last full system update: 2024-12-21 ↻
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

Thanks in advance
0point0

https://bbs.archlinux.org/viewtopic.php?id=290888

Reboot is waiting too.

1 Like

Hey SGS,

thanks for your very fast response!

Thanks, done that.
No change, still the same problem.

This is what I described within “what have I done to fix the problem”.
Here is a Screenshot of the kde default bluetooth manager.
But the error message doesn’t get me any further…
That’s why I tried bluetoothctl to see what is going on.

I tried it again with the kde default bluetooth manager and let bluetoothctl running in console and get this output while I try to pair my controller:

[bluetooth]# [NEW] Device XX:XX:02 StadiaHSQP-73ec
[StadiaHSQP-73ec]# [CHG] Device XX:XX:02 Connected: yes
[bluetooth]# [CHG] Device XX:XX:02Connected: no
[bluetooth]# [CHG] Device XX:XX:02 RSSI: 0xffffffca (-54)
[bluetooth]# [CHG] Device XX:XX:02 TxPower: 0xfffffff8 (-8)
[bluetooth]# [CHG] Device XX:XX:02 Appearance: 0x03c4 (964)
[bluetooth]# [CHG] Device XX:XX:02 Icon: input-gaming
[bluetooth]# [CHG] Device XX:XX:02 AdvertisingFlags:
[bluetooth]#   05           

What you suggested is what I described within “what have I done before I post here”"
The person from the screenshot of your search result had issues with his bluetooth device and solved it with a firmware update.
My Stadia Controller is working fine with other devices, the same as my other controllers.
So I suggest there is no firmware issue.

Oh, I didn’t mention, that I got an onboard bluetooth chip and no bluetooth adapter…

Do you got any other tips?

From template

  • Show us the results of your searches, and what you’ve tried

This general phrase is usually answered by people who have not made any effort to search themselves. You didn’t explicitly mention that you already made my reference to the system settings. It frustrates helpers when they have to read that all of their hints have already been tried, but the helper didn’t mention it beforehand.

The Whoogle image should show how to narrow down the troubleshooting.

I think it was “fix with kde default bluetooth manager”, but if you follow all links and nothing help, I can’t help too. :slight_smile:

1 Like

Ok, I get that it can frustrate the helpers!
Sorry about that :upside_down_face:

I didn’t want to mention all of my search results, because of the many, many results… :sweat_smile:
But I think I searched for all bluetooth issues on Garuda and Arch…

Is there a way to troubleshoot any issues with my network or bluetooth chip on my motherboard?
Maybe my hardware is getting to old now and that is where my issue is…

I know that that they have WiFi and USB-C connectivity have you tried connecting that way?
Also welcome from a new user that picked Garuda for similar reasons.

Try this one:

Bluetooth headset - ArchWiki

Pairing fails with AuthenticationFailed

If pairing fails, you can try enabling or disabling SSPMode with:

# btmgmt ssp off

or

# btmgmt ssp on

You may need to turn off BlueTooth while you run this command.

2 Likes

Thanks, I hope more people see the end of support of Win10 and the “SpyWin11” as an issue big enough to change some things :slight_smile:

I tried it both with Secure Simple Pairing off and on.

Sadly the same issue…

On my way to test my hardware I successfully paired my Bluetooth Speaker JBL Charge 4 and everything worked fine…

I also tested my Stadia Controller via USB cable and it worked fine.

Meanwhile I tested a udev rule (stadia-controller-udev ).
Even after a restart the same issue…

what I tried so far

I installed google-chrome via octopi and hoped for wonders, but nope. (Here is why)

I also tried xboxdrv and xbox-generic-controller , also via octopi. Same old, same old. (Why? - I am grasping for straws)

It is strange, because even other users mention, that this controller works natively with linux…
And yeah I checked the links to reddit and the comments on too.

Maybe another person with more knowledge can help me?
Puss In Boots Please GIF by Laff

The controller may still be under the influence of Windows. This may sound strange, but sometimes it happens with various sorts of hardware, and resetting the controller to factory defaults may help.

2 Likes

take a look there

and

1 Like

Good idea!
I did a factory reset on my Stadia Controller.
My controller got a new MAC-Adress (I don’t know why :thinking:).
The issue remains the same.

Thanks for your help, like I said my controller is already in bluetooth mode and I also tried the udev rule…
Also like I said I don’t think this is a issue with the controller, because the controller works fine with my SteamDeck (SteamOS).

more info to my ongoing research
I searched more and tried bluetuithagain…
This time I got a strange behavior, but watch yourself (sry for the bad quality).

Any ideas?
Is there something else I can configure to solve this issue?

Welcome to the Garuda community @0point0. :wave: :smiley:

I would try disabling MAC Address Randomization and after doing so, reboot both your router and computer.

It also might not hurt to install an alternate Bluetooth manager such as blueman and give it a try.

3 Likes

Thanks :wave: :smiley:

the random MAC Adresses are not the main issue, but thanks :sweat_smile:
If this is a problem regarding my issue I will try it!

I installed blueman, but got the same result like I showed in my video.
The controller pairs, keeps connected for a second or two an then disconnects again.

The kernel in use has a big bearing on Bluetooth performance. I would test out at least three alternate kernels if I were you.

3 Likes

Ok, other Kernels…
Now it’s getting deep into linux, at least for me. :sweat_smile:

What should I do to change a kernel or to test different kernels?
Is there a guide for newbies? :see_no_evil:

First, use octopi just for searching software, then install it with pacman in terminal.

Install kernel and headers are simple and explained 453 times in this forum.

sudo pacman -S linux-lts linux-lts-headers

and so on.
On grub open advanced and select the kernel you need.

Also in terminal use pacseek for searching and install.

4 Likes

But this is a good approach to rule out that the WiFi/Bluetooth combo card is the cause.

Check if you have the same issue with a USB Bluetooth dongle.

2 Likes

I would disable the onboard Bluetooth in BIOS for this test.

First of all, thanks for all your tips and suggestions!

I don’t own a bluetooth dongle, since I always had onboard bluetooth…
I need to buy one, this may take a few days due to the holidays.

Meanwhile I gonna test different kernels.
Right now on the linux-lts kernel the issue stays the same. :face_with_diagonal_mouth:
I keep you updated!

Everyone who reads this:
Merry Christmas :christmas_tree: