Bluetooth issues with keyboard

Hey Endeavour.

Once again I’m calling for help with keyb related issues. I’m trying to connect my keyboard to my PC running KDE Plasma and EndeavourOS. I’ve made sure I’ve got packages mentioned on Arch Wiki such as Bluez and bluez-utils. Tried to connect with bluetoothctl and KDE bluedevil.

Bluetooth confirmed working with a PS3 controller. Keyboard confirmed working with my laptop.

Anyone got any ideas what I could be forgetting?

  1. systemctl status bluetooth`
  2. use bluetoothctl tool as root to pair trust and connect device if it fails on first connection:
sudo bluetoothctl
power on
default-agent
pairable on
scan on
pair XX:XX:XX:XX:XX 
trust XX:XX:XX:XX:XX
connect XX:XX:XX:XX:XX

replce XX:XX:XX:XX:XX with the UUD of the keyboard will be shown on scan (out keyboard in pairing mode before)

Tried this already, no devices (apart from myself I’m guessing) shows up :confused:

could be hardware incompatible… i also would not recommend BT input devices at all :wink:
Better use RF ones…

And tried bluetoothctl as root or normal user?

Both!

I have a trusty good ol’ cable, but my desk-ocd would love some wireless bluetooth keyb (also my lazy self when I put my chair back)

Is there a clever way to check whether my bluetooth is faulty somehow? systemctl status bluetooth throws this:

bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Sat 2021-03-06 13:53:32 CET; 4h 28min ago
       Docs: man:bluetoothd(8)
   Main PID: 1302 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 38413)
     Memory: 2.2M
     CGroup: /system.slice/bluetooth.service
             └─1302 /usr/lib/bluetooth/bluetoothd

Mar 06 13:53:32 endeavour systemd[1]: Starting Bluetooth service...
Mar 06 13:53:32 endeavour bluetoothd[1302]: Bluetooth daemon 5.56
Mar 06 13:53:32 endeavour systemd[1]: Started Bluetooth service.
Mar 06 13:53:32 endeavour bluetoothd[1302]: Starting SDP server
Mar 06 13:53:32 endeavour bluetoothd[1302]: Bluetooth management interface 1.19 initialized
Mar 06 17:52:27 endeavour bluetoothd[1302]: Controller resume with wake event 0x0

Hmm hilariously enough I’ve so far been able to connect my phone to my PC, my phone to my keyb. I’m going to have a look in BIOS to see if I can get smarter that way :d

can you give hardware info on the two BT devices?
lsusb // lspci
and Manufacturer and model from the keyboard

1 Like

Keyboard is, according to lsusb a:


Bus 001 Device 013: ID 1ea7:0907 SHARKOON Technologies GmbH Keyboard

Also known as a GK61X

Output of lspci:

00:00.0 Host bridge: Intel Corporation Device 9b33 (rev 05)                                                                                     19:41:27
        00:01.0 PCI bridge: Intel Corporation 6th-9th Gen Core Processor PCIe Controller (x16) (rev 05)
        00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller
        00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller
        00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM
        00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi
        00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller
        00:17.0 SATA controller: Intel Corporation Device 06d2
        00:1b.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #17 (rev f0)
        00:1b.4 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #21 (rev f0)
        00:1c.0 PCI bridge: Intel Corporation Device 06b8 (rev f0)
        00:1c.4 PCI bridge: Intel Corporation Device 06bc (rev f0)
        00:1d.0 PCI bridge: Intel Corporation Comet Lake PCI Express Root Port #9 (rev f0)
        00:1d.4 PCI bridge: Intel Corporation Device 06b4 (rev f0)
        00:1f.0 ISA bridge: Intel Corporation Device 0685
        00:1f.3 Audio device: Intel Corporation Comet Lake PCH cAVS
        00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller
        00:1f.5 Serial bus controller [0c80]: Intel Corporation Comet Lake PCH SPI Controller
        01:00.0 VGA compatible controller: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] (rev a1)
        01:00.1 Audio device: NVIDIA Corporation GP106 High Definition Audio Controller (rev a1)
        02:00.0 Non-Volatile memory controller: Intel Corporation Device faf0 (rev 03)
        05:00.0 Ethernet controller: Intel Corporation Ethernet Controller I225-V (rev 02)

My mobo is a Z490 Aorus Pro AX

and BT is integrated into wifichipset? as i do not see BT device

Hello again Joe Kamprad

I figured out the issue. It was infact a shared wifi / bluetooth card. It turns out bluetooth is very temperalmental unless you plug in the arial into the wificard - so seems everything works now!

1 Like

Whats funny is both my phone, my playstation controller and my laptop all connected fine. Oh well, tech I don’t understand I guess heh.

because of something like that i do ask for it :wink:

1 Like

I’m back now again with more stupid questions.

I updated and rebooted my PC, and now bluetoothctl throws a ‘yes no’

[CHG] Device DC:2C:26:DC:93:D8 Connected: yes
[CHG] Device DC:2C:26:DC:93:D8 Connected: no
[CHG] Device DC:2C:26:DC:93:D8 Connected: yes
[CHG] Device DC:2C:26:DC:93:D8 Connected: no
[CHG] Device DC:2C:26:DC:93:D8 Connected: yes
[CHG] Device DC:2C:26:DC:93:D8 Connected: no

… and so on. I tried to pair, which gave me an expected failed to pair: org.bluez.Error.AlreadyExists. I then tried to connect, which threw a 'Failed to connect: org.bluez.Error.Failed.

The connected: yes, connected: no has been rolling in my terminal for a little while now. Any ideas what I could do?

I tried to remove DC:2C:26:DC:93:D8, then pair it again, which throws a quick connected: yes, before a Failed to pair: org.bluez.Error.AuthenticationRejected, before a connected: no.

And a new output! I did connect once again, and it threw me a:

[bluetooth]# connect DC:2C:26:DC:93:D8
Attempting to connect to DC:2C:26:DC:93:D8
[CHG] Device DC:2C:26:DC:93:D8 Connected: yes
[CHG] Device DC:2C:26:DC:93:D8 Modalias: usb:v0A5Cp4502d011B
[CHG] Device DC:2C:26:DC:93:D8 UUIDs: 00001000-0000-1000-8000-00805f9b34fb
[CHG] Device DC:2C:26:DC:93:D8 UUIDs: 00001124-0000-1000-8000-00805f9b34fb
[CHG] Device DC:2C:26:DC:93:D8 UUIDs: 00001200-0000-1000-8000-00805f9b34fb
[CHG] Device DC:2C:26:DC:93:D8 ServicesResolved: yes
[CHG] Device DC:2C:26:DC:93:D8 WakeAllowed: yes
Failed to connect: org.bluez.Error.Failed
[CHG] Device DC:2C:26:DC:93:D8 ServicesResolved: no
[CHG] Device DC:2C:26:DC:93:D8 Connected: no
[DEL] Device DC:2C:26:DC:93:D8 GK61XS KB

Try install bluez-hid2hci with pacman

I tried it, bluetoothctl still spamming ‘yes no’ - my keyb doesn’t use a usb bluetooth dongle tingy though. Nothing is plugged into my PC (except for my native bluetooth chip heh)

by any chance you where dualbooting?

https://wiki.archlinux.org/index.php/Bluetooth#Dual_boot_pairing

I actually am, but I haven’t booted up my windows install since this friday - way before I got my keyboard working