Last active
November 14, 2025 18:39
-
-
Save pocobio/3921e097d0f8fb36f34a3d90a61d5e84 to your computer and use it in GitHub Desktop.
Run 8BitDo Ultimate Software V2 under Linux
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| In this guide i will teach you how to run 8BitDo Ultimate software v2 under Linux | |
| Some people tried running it under clear wine and failed, i found out the issue, you need tts-ms-win10 | |
| https://github.com/streetsamurai00mi/ttf-ms-win10 All you have to do is follow installation guide on this repo | |
| After you successfully launched your software, you have to map udev rules | |
| At first, type lsusb. It will list your usb devices. Find your device there. I am using keyboard as an example | |
| Bus 003 Device 013: ID 2dc8:5200 8BitDo 8BitDo Retro Keyboard | |
| Do the same for wireless usb dongle | |
| Now, we have to create the rule. I am using Kate as an example | |
| kate /etc/udev/rules.d/99-8bitdo.rules | |
| Input your rules there, here`s an example | |
| SUBSYSTEM=="hidraw", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="5200", MODE="0666" | |
| SUBSYSTEM=="hidraw", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="5201", MODE="0666" | |
| idvendor is the first line in bold text, idproduct is second | |
| 5200 is my keyboard, 5201 is usb dongle | |
| Now, reload udev rules and your done | |
| sudo udevadm control --reload-rules | |
| sudo udevadm trigger | |
| If you found this guide helpful, upvote for others to see it! |
Author
Thank you very much, everything works now! I didn't even need to restart the software, when I put udevadm trigger the software showed my Ultimate 2 controller just fine.
I have an 8bitdo Pro 2 and a 8bitdo dongle. I am able to launch the Ultimate software through Lutris but the moment I use sudo udevadm trigger the software crashes with the following, any idea?
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0x1d1
Serial number of failed request: 2329
Current serial number in output stream: 2329
X Error of failed request: XI_BadDevice (invalid Device parameter)
Major opcode of failed request: 131 (XInputExtension)
Minor opcode of failed request: 3 (X_OpenDevice)
Device id in failed request: 0x139
Serial number of failed request: 329
Current serial number in output stream: 329
Monitored process exited.
Initial process has exited (return code: 256)
Exit with return code 256
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
yeah about that, i tried posting on official reddit but it were flagged as malicious xDD