{"id":207,"date":"2019-11-19T00:17:38","date_gmt":"2019-11-18T23:17:38","guid":{"rendered":"https:\/\/synt4x.org\/blog\/?p=207"},"modified":"2019-12-31T16:23:10","modified_gmt":"2019-12-31T15:23:10","slug":"getting-rumble-on-the-8bitdo-sn30-pro-to-work-properly-with-linux","status":"publish","type":"post","link":"https:\/\/synt4x.org\/blog\/index.php\/2019\/11\/19\/getting-rumble-on-the-8bitdo-sn30-pro-to-work-properly-with-linux\/","title":{"rendered":"Getting rumble on the 8BitDo SN30 Pro+ to work properly with Linux"},"content":{"rendered":"\n

TLDR: <\/strong>After having owned the controller for a while I noticed that every time you install a new kernel update the fixes are undone again, and have to be re-applied. I also discovered that the controller UID is the same for all SN30 Pro+ controllers. So I’ve made the following script that fixes everything automatically instead. Save it somewhere, check that the config file paths are correct, install xpadneo using the github instructions<\/a>, then run the script as root.<\/p>\n\n\n

\n#!\/bin\/bash\n\nif [[ $EUID -ne 0 ]]; then\n    echo "This script must be run as root"\n    exit 1\nfi\n\n# Config file paths\nMP_PATH="\/etc\/modprobe.d\/99-xpadneo-bluetooth.conf"\nUDEV_PATH="\/etc\/udev\/rules.d\/99-xpadneo.rules"\nENV_PATH="\/etc\/environment"\n\n# Look for already applied fixes\nMPFIXED=$(grep -c "disable_ff=2" $MP_PATH)\nUDEVFIXED=$(grep -c "RUN+=\\"\/bin\/sh -c 'echo xpadneo udev: \\$kernel > \/dev\/kmsg && { echo \\$kernel > \/sys\/bus\/hid\/drivers\/hid-generic\/unbind; echo \\$kernel > \/sys\/bus\/hid\/drivers\/microsoft\/unbind; echo \\$kernel > \/sys\/bus\/hid\/drivers\/xpadneo\/bind; }; '\\"" $UDEV_PATH)\nENVFIXED=$(grep -c "8BitDo SN30 Pro+" $ENV_PATH)\n\nif [[ $MPFIXED -eq 0 ]]; then\n  # Turn off trigger rumble\n  echo "options hid_xpadneo debug_level=0 disable_ff=2 trigger_rumble_damping=4 fake_dev_version=4400 combined_z_axis=n" >> $MP_PATH\n  echo "Applied fix to $MP_PATH."\nelse\n  echo "Fix already applied to $MP_PATH. Skipping."\nfi\n\nif [[ $UDEVFIXED -eq 0 ]]; then\n  # Apply dirty fix to udev rules\n  sed -i 's\/RUN\/#RUN\/g' $UDEV_PATH\n  echo "RUN+=\\"\/bin\/sh -c 'echo xpadneo udev: \\$kernel > \/dev\/kmsg && { echo \\$kernel > \/sys\/bus\/hid\/drivers\/hid-generic\/unbind; echo \\$kernel > \/sys\/bus\/hid\/drivers\/microsoft\/unbind; echo \\$kernel > \/sys\/bus\/hid\/drivers\/xpadneo\/bind; }; '\\"" >> $UDEV_PATH\n  echo "Applied fix to $UDEV_PATH"\nelse\n  echo "Fix already applied to $UDEV_PATH. Skipping."\nfi\n\nif [[ $ENVFIXED -eq 0 ]]; then\n  # Add SDL_CONTROLLERCONFIG environment variable\n  echo "SDL_GAMECONTROLLERCONFIG=\\"050000005e040000e002000030110000,8BitDo SN30 Pro+,platform:Linux,a:b0,b:b1,x:b2,y:b3,back:b6,guide:b8,start:b7,leftstick:b9,rightstick:b10,leftshoulder:b4,rightshoulder:b5,dpup:h0.1,dpdown:h0.4,dpleft:h0.8,dpright:h0.2,leftx:a0,lefty:a1,rightx:a3,righty:a4,lefttrigger:a2,righttrigger:a5,\\"" >> $ENV_PATH\n  echo "Added 'SDL_CONTROLLERCONFIG' variable to $ENV_PATH."\nelse\n  echo "'SDL_CONTROLLERCONFIG' variable already present in $ENV_PATH. Skipping."\nfi\n<\/pre><\/div>\n\n\n
Original post follows:<\/p>\n\n\n\n
I recently bought an 8BitDo SN30 Pro+<\/a> since my old gamepad was an ancient Logitech Dual Action. I wanted a gamepad that was wireless as well as having support for XInput. When I heard about the SN30 Pro+ I couldn’t contain myself, so I went and bought it the same day after reading a bit about it and how it works on Linux. It’s not officially supported, and there wasn’t really much definitive information regarding Linux compatibility, other than that the older SN30 Pro worked fine and it works on the raspberry pi. So I just took a gamble and bought it.<\/p>\n\n\n\n\n\n\n\n
And it does work pretty well with a standard Linux kernel (currently I’m running 5.3.11 on Arch Linux) out of the box. Holding X + Start<\/code> on the controller will boot it up in XInput mode. B + Start<\/code> is the old DInput mode. And Y + Start<\/code> will make it behave like a Switch Pro controller. All of these different modes paired just fine with my Bluetooth adapter. (I have not tested the Apple mode A + Start<\/code>). It’s just overall a really nice controller.<\/p>\n\n\n\n
But there was one thing that was missing when using it on Linux. Rumble! Rumble was only working when plugging the controller in through USB. When doing that, the kernel recognizes it as an Xbox 360 controller and uses the xpad kernel module. But connecting it with Bluetooth the xpad module is not used for some reason.<\/p>\n\n\n\n
After some experimenting it seemed like it was a limitation with evdev or the kernel modules or something like that, and I was ready to just give up on getting rumble to work for now. But then I read about xpadneo<\/a>, which is a kernel module specifically for the Xbox One Wireless Controller.<\/p>\n\n\n\n
The SN30 Pro+ is obviously not an Xbox One gamepad, but it identifies as one when you connect it wirelessly using the XInput mode. And as it turns out, xpadneo will make the SN30 Pro+ work with rumble over Bluetooth! There’s some setup required to make it work properly however.<\/p>\n\n\n\n
Installation and configuration<\/h3>\n\n\n\n
Here’s what we need to do:<\/p>\n\n\n\n