This script should no longer be necessary thanks to the latest changes made to the master branch of the xpad [https://github.com/paroj/xpad] driver, please give it a try and report any regressions you find.

fixcontroller.py

#!/usr/bin/env python3

import os
import sys


try:
    import usb.core
    import usb.util
except ImportError:
    print("First, install the pyusb module with PIP or your package manager.")
else:
    if os.geteuid() != 0:
        print("You need to run this script with sudo")
        sys.exit()

    dev = usb.core.find(find_all=True)

    for d in dev:
        if d.idVendor == 0x045e and d.idProduct == 0x028e:
            d.ctrl_transfer(0xc1, 0x01, 0x0100, 0x00, 0x14)
finally:
    sys.exit()

@grka

What do you mean? A driver update may have caused the problem or a driver update would maybe solve it?

And would I update the xpad driver? By upgrading the kernel?

@ghistes

I moved from xpad driver to the xboxdrv and it can now use my gamepad (I initialize this script before running the xboxdrv)

thanks for the script! Any way to make it permanent? Every time I unplug usb I have to rerun the script.

@randomparanoia I have a udev rule in /etc/udev/rules,d/80-controller.conf, adjust as needed for your controller's USB ID :)

ACTION=="add", ATTRS{idProduct}=="<product ID>", ATTRS{idVendor}=="<vendor ID>", DRIVERS=="usb", RUN+="<path to fixcontroller.py>"

ATTRS{idProduct}=="", ATTRS{idVendor}==""

Don't work for me.

This is what I have, it's some Amkette gamepad, stored this script in /usr/local/bin/fix_controller

ACTION=="add", ATTRS{idProduct}=="028e", ATTRS{idVendor}=="045e", DRIVERS=="usb", RUN+="/usr/local/bin/fix_controller"

This is what I have, it's some Amkette gamepad, stored this script in /usr/local/bin/fix_controller

ACTION=="add", ATTRS{idProduct}=="028e", ATTRS{idVendor}=="045e", DRIVERS=="usb", RUN+="/usr/local/bin/fix_controller"

Ahh ok, I was putting 0x028e and 0x045e

Hi,

I used this script to make work my controller. And it worked ... Since I updated to linux kernel 5.9 from 5.8
I don't know if it's related or not ?

Here is dmesg related

[ 6420.822948] xpad 1-2.2:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19
[ 6423.200370] usb 1-2.2: new full-speed USB device number 12 using xhci_hcd
[ 6423.532529] usb 1-2.2: New USB device found, idVendor=2563, idProduct=0575, bcdDevice= 2.00
[ 6423.532532] usb 1-2.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6423.532534] usb 1-2.2: Product: PS3/PC Gamepad
[ 6423.532535] usb 1-2.2: Manufacturer: SHANWAN
[ 6423.565903] input: SHANWAN PS3/PC Gamepad as /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-2/1-2.2/1-2.2:1.0/0003:2563:0575.000A/input/input31

And lsusb

Bus 001 Device 013: ID 045e:028e Microsoft Corp. Xbox360 Controller

Any idea ?

Thank's !

i just tried it for the first time with a gamepad from the same manufacturer and it works. i'm on kernel 5.10

@dnmodder thanks a lot mate! i finally have this thing working as it was supposed to.

Thank you for the fix! My gamepad 'GameSir G3w' now works great on MX Linux.

Edit: I notcied that you have to run the script each time after a reboot. It's no big deal, but is there a way to make the changes permanently?

I forked this into a standalone udev rule that doesn't require an external script to run: https://gist.github.com/pavel-kirienko/86b9d039151405451130a0fb3896887c

Thank you for the fix! My gamepad 'GameSir G3w' now works great on MX Linux.

Edit: I notcied that you have to run the script each time after a reboot. It's no big deal, but is there a way to make the changes permanently?

If you still didn't resolved your question, add udev rule as in https://gist.github.com/dnmodder/de2df973323b7c6acf45f40dc66e8db3#gistcomment-3582029 or https://gist.github.com/pavel-kirienko/86b9d039151405451130a0fb3896887c

Thank you!

This also fixes Corsair Esperanza EG106 wired PC/PS2/PS3 controller :-)

Had to modify this script to make it work with my ANT Esports GP100 controller. I have posted the modified script to https://github.com/flashrocket/shanwan-controller-fix.

wow, its working on Trust GXT540
Bus 001 Device 005: ID 045e:028e Microsoft Corp. Xbox360 Controller

THANKS ~!

Guys. The xpad driver now has the shanwan controller support built in. No need for workaround scripts. You can install the new driver from https://github.com/paroj/xpad and help test the controller and iron out any problems.

@flashrocket any idea if they're planning on upstreaming those changes to mainline later?

@Technohacker No idea bud. @paroj may be able to let us know.

these changes are now in https://github.com/paroj/xpad master. If they turn out to work without side-effects, we can think of sending them to linux upstream.

thank you so much for this

@lumin4ry you can use the new xpad driver itself instead of using the script.

(FIXED)when i try to execute the script it tells me to install the pyusb module even tho i installed it already. i don't know whats wrong
I install pyusb then i do "python fixcontroller.py" and then it says ''First, install the pyusb module with PIP or your package manager.''

I was using pythton 2.7 then i switch to python 3.8 and the it worked

If you are using ubuntu try installing using apt. That seems to work for me.

thank you so much for this fix.
Can confirm it makes my USB device 045e:028e work on Ubuntu 20.04 with kernel 5.15.0-52-generic
Both xpad kernel module and xboxdrv receive no events from the joystick until I run this fix, and then the controller works fine after.

@Breakthru have you tried using the updated xpad driver?

No, I haven't tried.

…

On Sat, 12 Nov 2022, 16:13 Amardhruva N Prabhu, ***@***.***> wrote: ***@***.**** commented on this gist. ------------------------------ @Breakthru <https://github.com/Breakthru> have you tried using the updated xpad driver? — Reply to this email directly, view it on GitHub <https://gist.github.com/de2df973323b7c6acf45f40dc66e8db3#gistcomment-4367217> or unsubscribe <https://github.com/notifications/unsubscribe-auth/AA4DU4JRTP2MCZOLBF3CMFLWH66ZBBFKMF2HI4TJMJ2XIZLTSKBKK5TBNR2WLJDHNFZXJJDOMFWWLK3UNBZGKYLEL52HS4DFQKSXMYLMOVS2I5DSOVS2I3TBNVS3W5DIOJSWCZC7OBQXE5DJMNUXAYLOORPWCY3UNF3GS5DZVRZXKYTKMVRXIX3UPFYGLK2HNFZXIQ3PNVWWK3TUUZ2G64DJMNZZDAVEOR4XAZNEM5UXG5FFOZQWY5LFVA4TGMRSGQ2TQONHORZGSZ3HMVZKMY3SMVQXIZI> . You are receiving this email because you were mentioned. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

Try the one in paroj xpad repo with branch fantech. It has all the fixes for the game pad and needs more testing.

(FIXED)when i try to execute the script it tells me to install the pyusb module even tho i installed it already. i don't know whats wrong I install pyusb then i do "python fixcontroller.py" and then it says ''First, install the pyusb module with PIP or your package manager.''

I was using pythton 2.7 then i switch to python 3.8 and the it worked

I'm facing the same problem, Please tell me how you managed to fix this issue.

@itsSagarBro
Two options.

sudo apt install python3-pyusb
sudo pip3 install pyusb

@amardhruva I have tried the xpad kernel driver and can confirm it fixes the problem without having to run the workaround script.

Thank you! I've tried everything on the net and this fixed my controller being detected but not outputting anything on Kali Linux 6.0.0