Xb1 classic controller driver
![xb1 classic controller driver xb1 classic controller driver](http://gam3gear.com/wp-content/uploads/2016/07/pc-010042bk-09.jpg)
usb 1-2: new full-speed USB device number 11 using xhci_hcd Looks like this is "PowerA Wired Controller for Xbox One - Thunder Cloud Camo" with vendor ID 0x24c6, product ID 0x581a.
![xb1 classic controller driver xb1 classic controller driver](https://i.ytimg.com/vi/WUQ6GWcKb6c/maxresdefault.jpg)
usb 1-2: device not accepting address 15, error -71 usb usb1-port2: unable to enumerate USB deviceĪs requested as well, a product listing of the controller im using, the product number is 1508490-01 if that helps Product link usb 1-2: Device not responding to setup address. usb 1-2: device not accepting address 14, error -71 usb 1-2: new low-speed USB device number 15 using xhci_hcd usb 1-2: Device not responding to setup address. usb 1-2: new full-speed USB device number 11 using xhci_hcd usb 1-2: New USB device found, idVendor=24c6, idProduct=581a, bcdDevice= 1.01 usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 usb 1-2: Product: XB1 Classic Controller usb 1-2: Manufacturer: BDA usb 1-2: SerialNumber: 0000143C150C53A7 input: Generic X-Box pad as /devices/pci0000:00/0000:00:14.0/usb1/1-2/1-2:1.0/input/input22 usb 1-2: USB disconnect, device number 11 usb 1-2: new low-speed USB device number 12 using xhci_hcd usb 1-2: device descriptor read/64, error -110 usb 1-2: device descriptor read/64, error -110 usb 1-2: new low-speed USB device number 13 using xhci_hcd usb 1-2: device descriptor read/64, error -110 usb 1-2: device descriptor read/64, error -110 usb usb1-port2: attempt power cycle usb 1-2: new low-speed USB device number 14 using xhci_hcd usb 1-2: Device not responding to setup address. Running dmesg returns a good bit of info, although this appears to be the most relevant: If there's already an XPAD_XBOXONE_VENDOR line for your vendor ID and the controller still doesn't work then the verbose lsusb output may help explain why. XPAD_XBOXONE_VENDOR(0x045e), /* Microsoft X-Box One controllers */ The vendor ID for your controller needs to be in one of the XPAD_XBOXONE_VENDOR lines.įor 045e there's one of each since Microsoft makes both Xbox 360 and Xbox One controllers: XPAD_XBOX360_VENDOR(0x045e), /* Microsoft X-Box 360 controllers */
![xb1 classic controller driver xb1 classic controller driver](https://i.pinimg.com/originals/54/8c/6b/548c6beee979b6b35cc123d74478821e.jpg)
There's an xpad_table with some XPAD_XBOX360_VENDOR and XPAD_XBOXONE_VENDOR lines below it. To see if the controller should already be recognized by xpad, look at the source here.
Xb1 classic controller driver driver#
The xpad driver detects Xbox 360 and Xbox One controllers using a combination of the vendor ID and the interfaces exposed by the controller. To get verbose information for a specific device (replace the IDs first): lsusb -v -d 045e:028eįor my controller this lists information about all the USB interfaces exposed by the controller. In this case I have a wired Xbox 360 controller so it has the vendor ID for Microsoft ( 045e) and the product ID for the Xbox 360 wired controller ( 028e). Run the command lsusb to list information about connected USB devices, there should be a line for your controller that looks something like: Bus 002 Device 012: Id: 045e:028e Microsoft Corp. For most wired Xbox controllers, if a controller isn't recognized by xpad then it won't work at all. On Linux, the xpad driver is only used if the driver recognizes the device. Which controller do you have? There are dozens of Xbox One wired controllers. If you see messages from usb but not xpad or input then it's probably not recognized as a supported Xbox One controller. (I get one xpad error: "xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19" but the controller still works.) Maybe a device error or a driver bug? If you get any errors, please share. If you see xpad errors or usb errors, they could be relevant. If things are working you should see a message from the input subsystem: input: Microsoft X-Box 360 pad as /devices/pci0000:00/0000:00:14.0/usb2/2-10/2-10:1.0/input/input32 Try reconnecting the controller and then printing the logs: sudo dmesg First, for the benefit of any future visitors, please add a link to an Amazon page or something so people can see which controller you're talking about.Ĭheck the dmesg logs.