Skip to content

Instantly share code, notes, and snippets.

@ammuench
Last active May 15, 2024 04:09
Show Gist options
  • Save ammuench/0dcf14faf4e3b000020992612a2711e2 to your computer and use it in GitHub Desktop.
Save ammuench/0dcf14faf4e3b000020992612a2711e2 to your computer and use it in GitHub Desktop.
8BitDo Ultimate 2.4GHz wifi working in linux

FROM https://www.reddit.com/r/Fedora/comments/zmvkdj/8bitdo_ultimate_bluetooth_controller_working_in/


I've bought this new controller from 8BitDo and wished to use on linux, to my sadness the controller didn't work out of the box, neither by cable, the 2.4G dongle or bluetooth.

So I've tried a number of solutions and this one from u/GodOfEmus over in the 8bitdo community was the one to work for me:

  1. Create a new file /etc/udev/rules.d/99-8bitdo-xinput.rules
  2. Paste this udev rule in there, then save and exit the file:
  ACTION=="add", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="3106", RUN+="/sbin/modprobe xpad", RUN+="/bin/sh -c 'echo 2dc8 3106 > /sys/bus/usb/drivers/xpad/new_id'"
  1. Run the following command in a terminal: sudo udevadm control --reload
  2. Unplug and replug the controller if it was already plugged in, it might take a second if you have the bluetooth version

It will basically "cheat" the OS to see the controller as an generic xbox device, so sadly no bluetooth nor gyro control if you care about that, but the rumbling is working for me.

Link to the original post: https://www.reddit.com/r/8bitdo/comments/ykdsmv/ultimate_24_ghz_model_right_analog_not_working_in/

And link to the comment of u/GodOfEmus with the solution: https://www.reddit.com/r/8bitdo/comments/ykdsmv/comment/iv48s4k/?utm_source=share&utm_medium=web2x&context=3

Sharing this solution here to spread the word in our community

@awilkins
Copy link

@catrock31 The where is in the first line comment ; it's a udev rule. On Linux, these are triggered by devices being added to the system - so in this case, it detects the Switch Pro controller "aspect" of the controller (you can see this turn up in the middle of my logs), and loads the hid-nintendo Switch Pro controller driver.

RUN+="/sbin/modprobe hid-nintendo"

And then it sends the controller ID to the driver (here I am just copying what the original poster wrote).

RUN+="/bin/sh 'echo 057e 2009 > /sys/bus/hid/drivers/nintendo/new_id'"

If it worked - you might have to pick a rule depending on which controller you wanted.

Sadly, it doesn't work. Here's the rule from the top post - loads the XBox driver, registers the pad.... then the controller switches itself off. Something must be needed to keep it awake.

[ 1211.121953] usb 3-2: new full-speed USB device number 9 using xhci_hcd
[ 1211.295474] usb 3-2: New USB device found, idVendor=2dc8, idProduct=3106, bcdDevice= 1.14
[ 1211.295479] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1211.295481] usb 3-2: Product: Ultimate Wireless Controller
[ 1211.295483] usb 3-2: Manufacturer: 8BitDo
[ 1211.295484] usb 3-2: SerialNumber: 9c1257d817e4
[ 1211.315613] input: Generic X-Box pad as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.3/usb3/3-2/3-2:1.0/input/input30
[ 1211.317741] usb 3-2: USB disconnect, device number 9
[ 1211.317847] xpad 3-2:1.0: xpad_try_sending_next_out_packet - usb_submit_urb failed with result -19

Here's what you get when you hook it up on the wire.

[ 1380.432980] usb 1-2.1: new full-speed USB device number 15 using xhci_hcd
[ 1380.548716] usb 1-2.1: New USB device found, idVendor=057e, idProduct=2009, bcdDevice= 2.00
[ 1380.548722] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1380.548724] usb 1-2.1: Product: Pro Controller
[ 1380.548726] usb 1-2.1: Manufacturer: Nintendo.Co.Ltd.
[ 1380.548727] usb 1-2.1: SerialNumber: 000000000001
[ 1380.624856] input: Nintendo.Co.Ltd. Pro Controller as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-2/1-2.1/1-2.1:1.0/0003:057E:2009.0017/input/input31
[ 1380.625054] hid-generic 0003:057E:2009.0017: input,hidraw4: USB HID v1.11 Joystick [Nintendo.Co.Ltd. Pro Controller] on usb-0000:06:00.1-2.1/input0
[ 1383.789155] usb 1-2.1: USB disconnect, device number 15
[ 1384.080884] usb 1-2.1: new full-speed USB device number 16 using xhci_hcd
[ 1384.198314] usb 1-2.1: New USB device found, idVendor=2dc8, idProduct=3106, bcdDevice= 1.14
[ 1384.198319] usb 1-2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 1384.198322] usb 1-2.1: Product: 8BitDo Ultimate Controller
[ 1384.198323] usb 1-2.1: Manufacturer: 8BitDo
[ 1384.198324] usb 1-2.1: SerialNumber: cf33ecd817e4
[ 1384.267836] input: Generic X-Box pad as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/0000:03:08.0/0000:06:00.1/usb1/1-2/1-2.1/1-2.1:1.0/input/input32

Again, both devices are announced, but the controller rapidly switches to the XBox mode. The controller sticks around though, instead of shutting off.

Not all the buttons register - the back paddles and two extra buttons in the middle don't show up.

The wifi mode works fine for me ; as long as I have Steam running when the controller comes online.

Tellingly, there's a little twitch on the vibration motor - I get this when I remove the controller from the dock on Windows as well. There must be some traffic that needs to go back to the controller to tell it that it's been registered, that triggers the twitch. If I have jstest-gtk open when I close Steam, the controller stays alive - until I close jstest-gtk - then it goes offline again.

Given that the controller seems to offer up the Switch Pro mode as an option - regardless of whether it's on wifi or wired USB - it would also seem that if you can "grab" this controller profile instead, you could use it.

@mercster
Copy link

@awilkins Did you try adding that USB quirk value to grub?

@Shaun-Schwartz
Copy link

Thanks a lot! This worked for me. If the udev rule isn't working for you try changing the idProduct. 3106 did not work for me but 3016 did. Not sure why. dmesg showed several different idProduct numbers and 3106 was one of them.

@lefuz
Copy link

lefuz commented Dec 22, 2023

Hello, can you explain step by step how to "Create a new file /etc/udev/rules.d/99-8bitdo-xinput.rules"? Thx.

@ammuench
Copy link
Author

Hello, can you explain step by step how to "Create a new file /etc/udev/rules.d/99-8bitdo-xinput.rules"? Thx.

# To create it
sudo touch /etc/udev/rules.d/99-8bitdo-xinput.rules
# To edit it (you can also use vim, gedit, whatever) 
sudo nano /etc/udev/rules.d/99-8bitdo-xinput.rules 

@CtodGit
Copy link

CtodGit commented Jan 2, 2024

you just got me up and running, thanks!

Now I'm trying to see if there is a way to wake my pc with the 2.4Ghz USB on controller boot...

update to that wake venture, I got it working with these two articles (I had an issue with rc.local on debian 12 so the second article is for that):

USB Wake:
https://www.makeuseof.com/wake-your-linux-pc-from-suspend-using-usb-devices/

Enable rc.local:
https://www.linuxbabe.com/linux-server/how-to-enable-etcrc-local-with-systemd

@Cereal-Killa
Copy link

Thank you, worked on my Powkiddy x55 running JELOS!

@BigBoyBarney
Copy link

BigBoyBarney commented Jan 4, 2024

The original instructions work for me on Fedora 39, thank youi!! I was wondering if there was a way to get the paddles on the back working?

@ammuench
Copy link
Author

ammuench commented Jan 4, 2024

The original instructions work for me on Fedora 39, thank youi!! I was wondering if there was a way to get the paddles on the back working?

To the best of my understanding the paddles are programmed at the firmware level have to be assigned to another button or macro in the 8BitDo software. I loaded up the tool in a Windows VM, did USB passthrough with the controller, and wrote the firmware with the new assignments there. Once I saved it they worked back in my linux machine when connected as set.

@BigBoyBarney
Copy link

BigBoyBarney commented Jan 4, 2024

Wow, that's very interesting!
Which mode are you using it in? The controller reports itself as 8BitDo Pro 2 Wired Controller in jstest with only 10 buttons
How does yours report itself?

EDIT: I just tried what @ammuench mentioned, set what I wanted to the paddles in a Windows VM, and now the paddles work as expected, as do the profiles / profile switching. Amazing stuff, thank you so much!

@davcri
Copy link

davcri commented Jan 27, 2024

JFYI: it works out of the box on latest Linux Mint 21.3 with 6.5 kernel. Also it works out of the box on Steam Deck.

@holotone
Copy link

This was a big help, thanks!

@aragubas
Copy link

aragubas commented May 3, 2024

Works out of the box in Fedora 40 now! I just bought the controller, plugged the 2.4GHz dongle in and it just works! also works via cable. Tho I only tested X input mode

@Hatsune-Cthulhu
Copy link

Hatsune-Cthulhu commented May 9, 2024

Annoyingly the wireless dongle doesn't seem to have power/wakeup support, also, controller just doesn't work in general for me on Kernel 6.8

@justinnichols
Copy link

Annoyingly the wireless dongle doesn't seem to have power/wakeup support, also, controller just doesn't work in general for me on Kernel 6.8

I concur. I'm having issues where sometimes Garuda Linux will see it connected, and sometimes it won't. The udev rule in this gist also didn't help fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment