As the title says, some devices pair (headphones) and some (keyboard/numpad) don’t. At first I thought that this is something to do with the keyboard itself, but I tried pairing with a rapsberrypi running Debian 12 and bluez 5.66 and it connected just fine. Works on Windows 11 too. Yes it is a dual-boot. Yes, I have tried unpairing from Windows and resetting the keyboard itself. Bluetooth is enabled. I have tried pairing through KDE settings and bluetoothctl but it just says Failed to pair: org.bluez.Error.AuthenticationCanceled after a while. Any guesses?
Nov 30 05:57:49 Torrent-Linux systemd[1351]: Started bluedevil-wizard.
Nov 30 05:58:05 Torrent-Linux kernel: Bluetooth: Unexpected continuation frame (len 11)
Nov 30 05:58:29 Torrent-Linux bluedevil-wizard[65660]: PendingCall Error: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
Just tried LTS, same thing. It does connect to a Steam Deck which runs a 6.11 kernel. And as I said in the OP, it works with raspberry pi 4b with a kernel version 6.12.25. It’s weird because I can connect my phone, headphones and a different numpad without any issues. Thank you for trying to help anyway.
Corrupted or outdated cached profiles can sometimes cause problems. You can clear the cached bluetooth profiles and start the process over again scanning and connecting.
First make sure bluetooth service is active and running correctly.
Edit: Use bluetoothctl to run through all the commands necessary to connect a device and trust.
Well you can manually remove a specific device by the mac address using bluetoothctl. If you remove the cache then all devices would have to be paired and connected again. I would just remove the one you are having issues with and see if you can go through all the steps with bluetoothctl to get it see see the device, pair, connect, trust etc…. to get it working.
So I have tried clearing cache, deleting /var/lib/bluetooth/ as well as pairing from EOS, cachy, suse and ubuntu liveusb. Nothing worked. I would have to guess that this has something to do with the controller firmware. But then again, I think I wouldn’t be able to pair anything at all if that was the case. I guess this is not EOS related then.
I’m not that familiar with the hardware you are referring to. Here is what AI say’s about the original error messaging.
AI Overview
The
org.bluez.Error.AuthenticationCanceled error indicates that the pairing process was interrupted or canceled, often due to an issue with entering the passkey or a mismatch in how the host system and the keyboard/numpad handle the authentication.
Here are a few potential solutions, primarily focused on Linux environments where this error commonly occurs with bluez:
Troubleshooting Steps
Ensure Proper Pairing Mode: Long-press Fn + V on your Zoom 75 until the V key flashes to put it in Bluetooth pairing mode for a new connection. Do the same for the Zoompad (refer to its specific manual for key combinations).
Use bluetoothctl and Enter Passkey Blindly:
Open a terminal and run bluetoothctl.
Ensure the agent is active and the default: agent on followed by default-agent.
Start the scan: scan on.
Find the MAC address of your device(s).
Initiate pairing: pair <MAC_address>.
When prompted for a PIN code or passkey, you may need to type it on the keyboard itself and press Enter, even if you don’t see the input field or prompt in the terminal. This is a common fix for keyboards that require a passkey.
Clear Existing Pairings:
On the Keyboard/Numpad: Clear all stored Bluetooth profiles by performing a firmware reset or following the manufacturer’s instructions for clearing the connection memory.
On the Host System (Linux): Within bluetoothctl, use remove <MAC_address> and untrust <MAC_address> for any previous entries before attempting to re-scan and pair.
Restart Bluetooth Service: Sometimes simply restarting the Bluetooth service can resolve transient issues: sudo systemctl restart bluetooth.
Check ControllerMode (Advanced): If other devices pair correctly but these specific ones do not, you can check the ControllerMode in the Bluetooth configuration file. Ensure it is set to dual (which is usually the default).
Edit /etc/bluetooth/main.conf and ensure the line ControllerMode = dual is present and uncommented.
Verify with Another OS: The issue might be specific to the bluez stack on your current operating system. If possible, try pairing the devices with a Windows or macOS machine to confirm they are functional.
If the problem persists, it may be a compatibility issue with your specific kernel or bluez version, as reported by other users. You can monitor debug logs using btmon or journalctl -r for more detailed error information.
I basically already did all of that without success. I was referring to the network controller firmware on my Asus X670E-E. As far as I can tell it has Intel AX210 module built in. Since it only happens on this machine and only in linux. That’s my guess at least.
Maybe I’ll try opening an issue in bluez or iwlwifi repos. If I find a solution I’ll try to remember to post it here.
On these motherboards that have WiFi onboard and also bluetooth they can have problems when going into a powerdown mode. You have to shut down unplug the computer and hold down the power button for more than 30 seconds to drain the power. Then plug back in and restart the computer. This usually resets it and WiFi and or bluetooth should work again properly. I’m not sure if it will help with your particular issue but worth trying. I would also turn off the power manaegement on WiFi for the Intel iwlwifi.
