8BitDo Ultimate 2.4GHz wifi working in linux

8BitDoUltimateWifi_Linux.MD

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'"

3. Run the following command in a terminal: sudo udevadm control --reload
4. 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

@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.

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

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.

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

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 

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

Thank you, worked on my Powkiddy x55 running JELOS!

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?

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.

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!

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.

This was a big help, thanks!

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

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

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.

For anyone who is looking to just make the controller work but not make it "cheat" the OS. You can use udev to give its input files read/write permissions.

1. create a /etc/udev/rules.d/99-8bitdo-xinput.rules with your favorite editor
2. inside the file, add the following:
   1. ACTION=="add", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="3016", MODE="0666"
   2. This gives the input file of any 8bitdo controller R/W permissions automatically when connected.
3. reload udev with sudo udevadm control --reload-rules or just reboot your computer.

This is helpful when you want to just read the controller's input according to SDL, not remapping to an xbox controller. Example use case is when you want it to work with ROS (https://answers.ros.org/question/384456/ros2-joy_node-debugging/)

FYI always check your model. the new ultimate 2.4ghz w/ the hall effect joysticks have id of 3109.

FYI always check your model. the new ultimate 2.4ghz w/ the hall effect joysticks have id of 3109.

Yeah, I haven't actually been using any of the udev rules here, been writing my own. I updated to kernel 6.9.5 and haven't had any issues with the controller not working since, but still not seeing power/wakeup support. Wondering if they shipped the new hall effect ultimate controllers with a worse dongle.

cat "${${$(grep 3109 /sys/bus/usb/devices/*/idProduct):0:-5}/idProduct/power/wake}"
cat: /sys/bus/usb/devices/1-3/power/wake: No such file or directory

Certainly seems like they shipped the new ones with a crappier dongle, if this does turn out to be the case, they've definitely lost a customer in me, given they marketed this controller around the steam deck, knowing full well that the steam deck community wants a controller that can wake the system remotely.

I bought the Bluetooth/dongle version earlier this year, while the dongle is still causing problems with constant disconnects when using Bluetooth it works out of the box and can be tested with evtest.

I worked for me on Lubuntu 22.04 for the "8Bitdo Ultimate C 2.4g".
Thank you!

Just as described:

1️⃣ I ran: sudo nano /etc/udev/rules.d/99-8bitdo-xinput.rules and typed my computer password

2️⃣ I pasted the following line:
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'"

3️⃣ I pressed: CTRL + X

4️⃣ I typed "y" and then "ENTER" to save the buffer

5️⃣ I pressed "ENTER" one again

6️⃣ I ran: sudo udevadm control --reload

7️⃣ Disconnected the 2.4g receiver

8️⃣ Connected the 2.4g receiver

9️⃣ I pressed and held the "X button + 8bitdo button" in the controller until it did a small vibration

🔟 DONE!

Anyone managed to get the gyro working?

Anyone managed to get the gyro working?

There is no gyro on the 8bitdo Ultimate 2.4Ghz.

@mercster i see. I bought the wrong one. There's another one with gyro. Thanks!

@mercster i see. I bought the wrong one. There's another one with gyro. Thanks!

I wouldn't expect the gyro to work under Linux at any rate. Good luck?

Yeah, I realize now. I wanted the 8bitdo because of the 2.4 dongle.

The ps5 controller has gyro, but I get weird delays (which is a problem on eldenring and wukong)
It went away with the 8bitdo.

i guess I'll use both controllers and change depending on the game.

this also works for the new Ultimate 2C, except the product id is 310a instead of 3106

ACTION=="add", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="310a", RUN+="/sbin/modprobe xpad", RUN+="/bin/sh -c 'echo 2dc8 310a > /sys/bus/usb/drivers/xpad/new_id'"

@YusefOuda This is awesome I was looking for this exactly! My question is how do you find this ID of the product to know that it was 310a vs 3106?

@kody-oneill you can use lsusb

@kody-oneill you also see it in your syslog as soon as you power the controller on:

input: 8BitDo 8BitDo Ultimate 2C Wireless Controller Keyboard as /devices/pci0000:00/0000:00:01.2/0000:02:00.0/usb1/1-4/1-4:1.1/0003:2DC8:310A.000B/input/input38

Does anyone know how extra buttons work with xpad though? I expected to see R4/L4 as additional joystick buttons, same with the mapping and star button, but they are not, there's only 11 buttons listed, those 4 seem to be missing.

Edit: L4/R4 can be remapped via the controller itself to other buttons, then they work, but of course acting as these other buttons. I was hoping to see two additional buttons for custom stuff like next/previous song.

For anyone who is looking to just make the controller work but not make it "cheat" the OS. You can use udev to give its input files read/write permissions.

1. create a `/etc/udev/rules.d/99-8bitdo-xinput.rules` with your favorite editor

2. inside the file, add the following:
   
   1. `ACTION=="add", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="3016", MODE="0666"`
   2. This gives the input file of any 8bitdo controller R/W permissions automatically when connected.

3. reload udev with `sudo udevadm control --reload-rules` or just reboot your computer.

This is helpful when you want to just read the controller's input according to SDL, not remapping to an xbox controller. Example use case is when you want it to work with ROS (https://answers.ros.org/question/384456/ros2-joy_node-debugging/)

Debian 12 Bookworm
I am using the 8BitDo Ultimate C 2.4G Wireless Controller
working file: /etc/udev/rules.d/99-8bitdo-xinput.rules

So I tried to blindly use the original post code shown below to see if I could get this working ..

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'"

and then trying to either reboot or running udevadm control --reload with disconnecting and reconnecting the device, and that worked ..
however what I really want is this to work without hacky stuff .. so I tried what @Edwardius suggested, like so;

ACTION=="add", ATTRS{idVendor}=="2dc8", ATTRS{idProduct}=="3016", MODE="0666"

then I did a reboot and the whole udevadm control --reload with disconnecting and reconnecting the device .. didn't work .. so I did more research and after trying lsusb I found that my device is actually called out as 2dc8:3016. So how is it that the original setup works with the hacky stuff and the wrong idProduct but the controller is not recognized in MODE="0666" with the correct idProduct ? Any assistant is greatly appreciated :)

side note: is it possible that by doing the hacky version first I've screwed up the native support ? how would I reverse that ?