Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluetoothctl not creating an event* #606

Open
jesusramondovale opened this issue Sep 18, 2023 · 3 comments
Open

Bluetoothctl not creating an event* #606

jesusramondovale opened this issue Sep 18, 2023 · 3 comments

Comments

@jesusramondovale
Copy link

I'm using a DEBIX-Board Model-A with a DEBIX-modified Ubuntu22 image installed. I'm trying to connect via Bluetooth an Xbox Series X controller to it (using bluetoothctl on terminal)

So I started the Bluetooth service, and successfully connected my controller using bluetoothctl as I can see on bluetoothctl console prompt, and also in the Bluetooth monitor (btmon), when I touch my controller I can see all the messages successfully arriving on the board.

The problem is that no event is created on /dev/input/.

Does anyone know why is this happening? Must I be creating the event myself?

EDIT: this is the bluetoothctl info of my Xbox controller:

[Xbox Wireless Controller]# info 0C:35:26:49:44:6C
Device 0C:35:26:49:44:6C (public)
        Name: Xbox Wireless Controller
        Alias: Xbox Wireless Controller
        Appearance: 0x03c4
        Icon: input-gaming
        Paired: yes
        Trusted: yes
        Blocked: no
        Connected: yes
        WakeAllowed: yes
        LegacyPairing: no
        UUID: Vendor specific           (00000001-5f60-4c4f-9c83-a7953298d40d)
        UUID: Generic Access Profile    (00001800-0000-1000-8000-00805f9b34fb)
        UUID: Generic Attribute Profile (00001801-0000-1000-8000-00805f9b34fb)
        UUID: Device Information        (0000180a-0000-1000-8000-00805f9b34fb)
        UUID: Battery Service           (0000180f-0000-1000-8000-00805f9b34fb)
        UUID: Human Interface Device    (00001812-0000-1000-8000-00805f9b34fb)
        Modalias: usb:v045Ep0B13d0517
        ManufacturerData Key: 0x0006
        ManufacturerData Value:
  03 00 80                                         ...
        Battery Percentage: 0x32 (50)

Thank you!

@Vudentz
Copy link
Contributor

Vudentz commented Sep 18, 2023

@jesusramondovale what version of BlueZ? Note that it seems 5.69 has some problem with input devices: #594

@jesusramondovale
Copy link
Author

jesusramondovale commented Sep 19, 2023

I'm using BlueZ 5.66 Isn't it the last version available? Thanks for answering.

But I think that's not the problem because the bluetooth pairing works perfectly and almost instantly, also with btmon I can see all messages on my hci0 interface. The only thing is that I don't know where is the /dev/input event being created.

Do you know who is responsible for creating the event at /dev/input?

@macmpi
Copy link

macmpi commented Sep 21, 2023

is uinput driver loaded on your system? (check modinfo uinput or lsmod | grep uinput)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants