-
Notifications
You must be signed in to change notification settings - Fork 112
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
Support for device id 0B22 #338
Comments
It looks like new firmware emerges as PID FWIW, a proper fix to add your controller may be to use this commit as a template. I suspect that your firmware also needs the If you'd like to submit a PR, I'd happily consider it for merging.
Well, bind and unbind need the kernel device name which may be different, see here: Tho, for subsystem hid, it should be exactly what you provided. So probably, yes, the PID is probably missing in the device database in the source code, and adding it should get you one step further. If possible, please also document the USB PID because xpadneo is supposed to support USB mode in a future version. |
I also have a controller with a 0B22 device id. Rumble feels weird and sometimes as if it were "saving up" (after a longish period of rumbling, it just kept going for a few more seconds). This sounds just like #337 Since you asked for the USB PID: |
Closes: atar-axis#338 See-also: atar-axis#344 Signed-off-by: Kai Krakow <kai@kaishome.de>
Closes: atar-axis#338 See-also: atar-axis#344 Signed-off-by: Kai Krakow <kai@kaishome.de>
Closes: atar-axis#338 See-also: atar-axis#344 Signed-off-by: Kai Krakow <kai@kaishome.de>
Is your feature request related to a problem? Please describe.
Xbox Elite Series 2 Controller on latest firmware is not recognised/bound by xpadneo driver
Describe the solution you'd like
Controller/device is detected and bound by the xpadneo driver
Describe alternatives you've considered
Works over USB still using the Xpad driver
Additional context
I have a series 2 elite controller, writing on the back claims model 1797. This was updated to the latest firmware yesterday, by connecting to a windows laptop over USB and updating via the Xbox Accessories app.
Controller Firmware version is now at 5.13.3143.0
Kernel 5.16.11-arch1-2
Relevant output from dmesg indicates this device id is now 0B22:
The device is bound by the hid-generic driver and is largely unusable, axis and button mappings are all screwed. As stated earlier though still working fine over USB.
I hadn't used xpadneo prior to today, I'd always connected via usb cable. Recently I purchased a bluetooth adapter (TP-Link UB500), I updated the firmware after reading about various problems with BTLE, which the recent firmware is meant to address I think.
I spent some time mucking with /etc/modprobe.d/xpadneo.conf and udev rules thinking if I could get them to match the id then the device would bind.
I then resorted to trying to manually unbind/bind the driver. Successfully unbinds from hid-generic, but when attempting to bind to xpadneo:
Even though the device is definitely present and shows under /sys/bus/hid/devices/
Reading indicates this error is generic and not necessarily descriptive of the exact issue.
Poking around in ./hid-xpadneo/src/hid-xpadneo.c seems to indicate this device id is not currently supported, which might be why it refuses to bind? Possibly device id changed with latest firmware, sorry I can't confirm what it was prior to update.
The text was updated successfully, but these errors were encountered: