You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a device that is a BLE Gamepad that i'm trying to use on a RaspberryPI 5 running bookworm. When i pair through the gui, it loads the HID device just fine, but if i either reboot the machine, or instead try pairing through bluetoothctl, it doesn't load the HID device, even though it says it's connected just fine. Does anyone have any ideas on where i can look? How does the device load differently when paired through the gui?
Other points of note:
udevadm monitor shows 2 entries when it doesn't work, 14 entries when it does. The first two entries of the happy path are identical to the failure case except for expected sequence and time values.
debug level udev logs show similar to udevadm monitor; The happy path has all the entries of the failure and just has more after. No extra errors or branching behavior from what i can tell.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a device that is a BLE Gamepad that i'm trying to use on a RaspberryPI 5 running bookworm. When i pair through the gui, it loads the HID device just fine, but if i either reboot the machine, or instead try pairing through
bluetoothctl
, it doesn't load the HID device, even though it says it's connected just fine. Does anyone have any ideas on where i can look? How does the device load differently when paired through the gui?Other points of note:
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions