-
-
Notifications
You must be signed in to change notification settings - Fork 224
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
XBox360 Controller Not Accessible #447
Comments
From https://www.kernelconfig.io/config_joystick_xpad it looks like you need a special driver (xpad), which needs to be enabled in the kernel (which it isn't in the default WSL kernel). Follow https://github.com/dorssel/usbipd-win/wiki/WSL-support#building-your-own-usbip-enabled-wsl-2-kernel and build your own kernel with this driver enabled. |
And you may also like https://www.kernelconfig.io/CONFIG_JOYSTICK_XPAD_FF |
I actually did that. Compiled my own linux kernel with xbox drivers enabled and I still get
when trying to attach device Tested controller model: My guess is that the device is some weird msft interface driver that all X-Input devices are automatically assigned to when connected which requires special handling. EDIT: Gamepads listed as a normal |
"Device busy" means exactly what it says. Looks like something on the host (service/software/driver) is holding an exclusive lock. Either stop that service/software, or use |
Obviously yes. The service that has exclusive lock is probably one of those xbox services. I didn't bother checking because after badly wanting the Anyway, this should help random internet travelers and this issue can be closed if the OP doesn't have anything to add anymore. |
@Diztruxion |
@dorssel |
I'm having this issue as well; I'm using a Logitech F310 USB gamepad (currently showing up as
However, I am able to run I have built a kernel following #building-your-own-usbip-enabled-wsl-2-kernel and
|
Hi,
I'm attempting to get a XBox360 USB controller to pass from Windows 10 into WSL2 using Ubuntu 18.04 LTS to create inputs to a Robot Operating System (ROS) simulation environment.
So far I've been successful in installing all required packages, finding the device in PS with usbipd wsl list. I've successfully attached the device using the busid, and I can see in the Ubuntu terminal that it has registered the device as a controller:
However, I'm not sure how the device should be accessible now. I can see that the device is created when I call lsusb:
![image](https://user-images.githubusercontent.com/38913498/189261275-a9b30a21-107b-4cbd-97ca-467f56e7183e.png)
From my reading, the developer of the simulation environment indicates that these controllers should be accessible using the jstest-gtk tool, and registers in /dev/input/js###
I know this might be a bit outside the scope of the windows side, just wondering if anyone has seen this before.
Thanks.
The text was updated successfully, but these errors were encountered: