Patreon Logo Support us on Patreon to keep GamingOnLinux alive. This ensures all of our main content remains free for everyone. Just good, fresh content! Alternatively, you can donate through PayPal Logo PayPal. You can also buy games using our partner links for GOG and Humble Store.
Title: Ubuntu 17.10 and problems with Steam Controller
Page: 1/2
  Go to:
Mountain Man 6 Nov 2017
User Avatar
Edit: It seems that disabling "Generic controller support" is the solution. Go into Big Picture Mode, click the gear icon in the upper right corner, and then look for Steam Controller settings.

Original post follows:

----------

Putting this here in case anybody does a random internet search and wants some information about this problem. It seems that the Ubuntu 17.10 update broke the Steam Controller. In my case, the Controller would work correctly on the desktop, in Big Picture Mode, and in some games like XCOM 2 and Rogue Legacy, but not in other games like Mad Max, Shadow of Mordor, and Dying Light even though it seemed to load the correct profile based on what I could tell from the haptic feedback -- the games in question simply didn't recognize the controller. Rolling back to Kubuntu 16.04.3 LTS resolved the issue, and now my Steam Controller is 100% functional again.

Here's the thread I started on the Steam Forums where a couple other people confirmed the issue:

http://steamcommunity.com/app/353370/discussions/0/1480982971174005978/

And a thread I stumbled across on the Ubuntu forums describing the same problem:

https://ubuntuforums.org/showthread.php?t=2375973

Hopefully it gets fixed and I can go back to 17.10, but I guess sticking with a long-term service release isn't so bad.
Arehandoro 8 Nov 2017
User Avatar
Funny enough, I stumbled upon this post searching for this same issue. Though I'm on Debian unstable. I don't exactly know when this started to happen but noticed it yesterday after doing some full-upgrade, that changed few dependencies, to get few new nvidia packages and gnome updates. Since Ubuntu 17.10 has changed to gnome, could the latest version of any its packages be the culprit?

Will try to check what upgrades were left out in the process and see if I can find something.
Mountain Man 9 Nov 2017
User Avatar
I'm actually running Kubuntu which uses KDE, so it seems the problem is not tied to any one desktop environment.
Arehandoro 9 Nov 2017
User Avatar
Quoting: Mountain ManI'm actually running Kubuntu which uses KDE, so it seems the problem is not tied to any one desktop environment.
Oh I see, hopefully it's fixed by Saturday cause have some mates coming over and would love to play with the steam controllers instead of reinstalling other os from scratch haha.
Arehandoro 9 Nov 2017
User Avatar
I'm at work and can't test this yet, although I might have an idea why this happened to me and maybe potential Ubuntu users.

I recently updated the kernel to 4.13, which is the same that Ubuntu 17.10 uses, and probably that's the moment my Steam Controller started misbehaving. Last night thought of it, tried to start the PC with kernel 4.12.2 but failed. First I thought this could be due to the full-upgrade and the newly installed nvidia packages from it so didn't try this further, was very late and didn't want to continue, but now I'm thinking that the combination of these two could be the cause of the problem.

I will try to downgrade the kernel tonight and post here the results.
Redface 9 Nov 2017
I just tried Mad Max vulkan beta on Ubuntu 17.10 and kernel 4.13 and my steam controller worked. I only walked a around a bit so didnt check all actions.

Do you have the steam-devices package installed? It contains the udev rules for the steam and other controllers.
Arehandoro 10 Nov 2017
User Avatar
Quoting: RedfaceI just tried Mad Max vulkan beta on Ubuntu 17.10 and kernel 4.13 and my steam controller worked. I only walked a around a bit so didnt check all actions.

Do you have the steam-devices package installed? It contains the udev rules for the steam and other controllers.
Yeah, and also checked the udev rules and are still there (both in /etc/udev/rules.d/ and in /usr/lib/udev/rules.d) although I only could find two rules, one from the sc controller app and the other from the steam controller itself... I would have thought there were more.

The udev rule looked like this:

# This rule is needed for basic functionality of the controller in Steam and keyboard/mouse emulation
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"

# This rule is necessary for gamepad emulation; make sure you replace 'pgriffais' with a group that the user that runs Steam belongs to
KERNEL=="uinput", MODE="0660", GROUP="pgriffais", OPTIONS+="static_node=uinput"

# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"

# Valve HID devices over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*28DE:*", MODE="0666"

# DualShock 4 over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666"

# DualShock 4 wireless adapter over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666"

# DualShock 4 Slim over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666"

# DualShock 4 over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"

# DualShock 4 Slim over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"
And it had rw_r_r permissions and user and group ownership were for root, in case that's wrong.

I have also bumped into this https://github.com/ValveSoftware/steam-for-linux/issues/5169 right now but not very sure whether that could be the problem, would have to check tonight again.

I tried with kernel 4.12 and 4.9 and didn't fix it (would have been too much luck haha)

EDIT: Worth saying that this is driving me bonkers just because of Rocket League and my mates coming over on the weekend, the other games that I usually play so far work as usual xD
Redface 10 Nov 2017
I only have it at /lib/udev/rules.d/99-steam-controller-perms.rules

and it looks like this:

more /lib/udev/rules.d/99-steam-controller-perms.rules
# Valve USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess"

# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"

# Valve HID devices over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*28DE:*", MODE="0666"

# DualShock 4 over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666
"

# DualShock 4 wireless adapter over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666
"

# DualShock 4 Slim over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666
"

# DualShock 4 over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"

# DualShock 4 Slim over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"

with these permissions:

ls -l /lib/udev/rules.d/99-steam-controller-perms.rules
-rw-r--r-- 1 root root 901 Nov 24  2016 /lib/udev/rules.d/99-steam-controller-perms.rules

I just checked Rocket League and Dying Lights and my steam controller worked in both
drlamb 10 Nov 2017
Same issue here. Running the latest kernel with AMD_Staging stuff and the latest MESA/LLVM, but I doubt that has anything to do with it. Hasn't worked since day one on 17.10. Frustrating.

Edit: I just realized my udev rules had preceding #s due to the way I copied them. I'll need to retest once I get home from work but I imagine it will work now. I'm an idiot sometimes.
Arehandoro 11 Nov 2017
User Avatar
Quoting: RedfaceI only have it at /lib/udev/rules.d/99-steam-controller-perms.rules

and it looks like this:

more /lib/udev/rules.d/99-steam-controller-perms.rules
# Valve USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess"

# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"

# Valve HID devices over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*28DE:*", MODE="0666"

# DualShock 4 over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666
"

# DualShock 4 wireless adapter over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666
"

# DualShock 4 Slim over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666
"

# DualShock 4 over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"

# DualShock 4 Slim over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"

with these permissions:

ls -l /lib/udev/rules.d/99-steam-controller-perms.rules
-rw-r--r-- 1 root root 901 Nov 24  2016 /lib/udev/rules.d/99-steam-controller-perms.rules

I just checked Rocket League and Dying Lights and my steam controller worked in both
I have removed the rules from the other entries and left only one as you have it, copying also the info just in case I had a typo but still same issue :/

Thanks for your help though :)

EDIT: Changed back to "Opt out of Steam Betas" and the controller started working on all the games now. As usual, I should have started from the most basic thing xD I hope this also can fix the issue to everyone else.
Mountain Man 12 Nov 2017
User Avatar
Quoting: RedfaceI only have it at /lib/udev/rules.d/99-steam-controller-perms.rules

and it looks like this:

more /lib/udev/rules.d/99-steam-controller-perms.rules
# Valve USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0666"
# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess"

# Valve HID devices over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="28de", MODE="0666"

# Valve HID devices over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*28DE:*", MODE="0666"

# DualShock 4 over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="05c4", MODE="0666
"

# DualShock 4 wireless adapter over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="0ba0", MODE="0666
"

# DualShock 4 Slim over USB hidraw
KERNEL=="hidraw*", ATTRS{idVendor}=="054c", ATTRS{idProduct}=="09cc", MODE="0666
"

# DualShock 4 over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:05C4*", MODE="0666"

# DualShock 4 Slim over bluetooth hidraw
KERNEL=="hidraw*", KERNELS=="*054C:09CC*", MODE="0666"

with these permissions:

ls -l /lib/udev/rules.d/99-steam-controller-perms.rules
-rw-r--r-- 1 root root 901 Nov 24  2016 /lib/udev/rules.d/99-steam-controller-perms.rules

I just checked Rocket League and Dying Lights and my steam controller worked in both
No luck. I did a fresh install of Kubuntu 17.10, created the udev rules, and exact same behavior as before: game doesn't detect the Steam Controller even though the correct profile is loaded. I'm not opted into the Steam beta.
Mountain Man 12 Nov 2017
User Avatar
Steam Controller seems to be working fine with a fresh install of 17.04.

I'm going to update the software and hope it doesn't break anything.
Mountain Man 12 Nov 2017
User Avatar
Fully updated with backports and everything, and no problems. Steam Controller works as expected. I have a feeling it's something to do with the kernel since I'm running the 4.10.0-38 kernel.
Mountain Man 12 Nov 2017
User Avatar
Quoting: RedfaceI just tried Mad Max vulkan beta on Ubuntu 17.10 and kernel 4.13 and my steam controller worked. I only walked a around a bit so didnt check all actions.

Do you have the steam-devices package installed? It contains the udev rules for the steam and other controllers.
I'm curious, has there been any updates to 17.10 since this problem was reported? Now that I think about it, I didn't update my install of 17.10 when I tried it just a few hours ago. If you're running the very latest update of 17.10 then maybe it pulled in a fix.

I'm not eager to try it, because if it doesn't work then it will mean another reinstall, which isn't difficult, just time consuming. Somebody else take one for the team! Haha!
Arehandoro 13 Nov 2017
User Avatar
Quoting: Mountain ManFully updated with backports and everything, and no problems. Steam Controller works as expected. I have a feeling it's something to do with the kernel since I'm running the 4.10.0-38 kernel.
In the midst of all the things I tried the other day to fix the controller, forgot to mention that after updating to kernel 4.13, on boot up my rig was complaining about something, but then booting normally, and that I should update the firmware. I think the error was related to TSC_DEADLINE error due to errata.

After some research saw there was a package on for that error -intel-microcode- and installed it. That was when I also reverted back to Steam client without betas. I don't really know what that package does, could it be that is also missing from your PC?

On Sat when my mates came over also had to uninstall xpad, the computer saw my xbox controller as if I had two of them plugged. All actions were mirrored onto a ghost 3rd player, funny but annoying xD
Mountain Man 13 Nov 2017
User Avatar
Quoting: ArehandoroAfter some research saw there was a package on for that error -intel-microcode- and installed it. That was when I also reverted back to Steam client without betas. I don't really know what that package does, could it be that is also missing from your PC?
I have an AMD CPU, so I doubt Intel CPU firmware would do me any good.

Also, it's not installed at the moment on my system, so it would not seem to be the culprit.
Arehandoro 13 Nov 2017
User Avatar
Quoting: Mountain Man
Quoting: ArehandoroAfter some research saw there was a package on for that error -intel-microcode- and installed it. That was when I also reverted back to Steam client without betas. I don't really know what that package does, could it be that is also missing from your PC?
I have an AMD CPU, so I doubt Intel CPU firmware would do me any good.

Also, it's not installed at the moment on my system, so it would not seem to be the culprit.
Oh, crap. Sorry can't be of better help :/
wojtek88 13 Nov 2017
Recently I started to have issue with my Steam controller as well. The issue in my case is that while using [sc-controller](https://github.com/kozec/sc-controller) 2 buttons are always interpreted as keyboard buttons, even if I map them to gamepad buttons.
If I use controller in Steam it works fine, it works fine also if I use [steam controller](https://github.com/ynsta/steamcontroller) directly.

I didn't figure out what causes the issue, so if someone had the same problem and solved it, just drop me a line.
Shakey 15 Nov 2017
I have been having the same issue (not in the steam beta) with my steam controller, xbox one controller via usb and wireless xbox 360 controllers since the fedora 27 beta with kernel 4.13. However, if I go back to fedora 26 and update the kernel to 4.13 I don't have the problem. Has anyone found what might be causing the issue?
Arehandoro 17 Nov 2017
User Avatar
Guys, I think we all missed this post from @debianxcfe in the Native Linux gaming forum and maybe solve the issue for some people:

I have played Rocket League with the Logitech usb game pad and Shanwan/Panhai PS3 bluetooth game pad years and now that is impossible. The Steam application works with the game pads and the Saints Row 2 Steam game too. Do other Rocket League players have the same problem?

My game pads are configured in the steam big picture mode and I have tried the xboxdrv driver, no help.

Update: I made a bug report with the psyonix.com web form and their response is that only Steam OS is supported while the Steam store page says Steam OS + Linux. They do not support my controllers either that is funny. I just installed free The Pirate: Plague of the Dead game and my PS3 controller works fine. Luckily I did not buy the Rocket league game, my kid has shared it to me. I tested with wine-staging too and the Logitech gamepad did work partially. Log files are in: ~/.local/share/Rocket League/TAGame/Logs/

Update. Steam client update at 30.9.2017 caused this problem propably. Now generic game controller support must be disabled in the big picture mode controller settings. Shut down your controller, disable generic game controller support and turn your controller on again.
Mountain Man 17 Nov 2017
User Avatar
Update. Steam client update at 30.9.2017 caused this problem propably. Now generic game controller support must be disabled in the big picture mode controller settings. Shut down your controller, disable generic game controller support and turn your controller on again.
That doesn't seem likely to me, because the problem only started when I upgraded to Kubuntu 17.10. There are no problems with earlier versions like 16.04.3 and 17.04. Unless it's a combination of 17.10 and the latest Steam client? I'm hesitant to update and try it, because if it doesn't work, it'll mean having to reinstall my OS again.
While you're here, please consider supporting GamingOnLinux on:

Reward Tiers: Patreon Logo Patreon. Plain Donations: PayPal Logo PayPal.

This ensures all of our main content remains totally free for everyone! Patreon supporters can also remove all adverts and sponsors! Supporting us helps bring good, fresh content. Without your continued support, we simply could not continue!

You can find even more ways to support us on this dedicated page any time. If you already are, thank you!
Login / Register
Register Forgot Login?
★ Support Us
Popular this week
Search or view by category
Contact
Latest Guides
MorrowindHow to setup OpenMW for modern Morrowind on Linux / SteamOS and Steam Deck
By Liam Dawe,
10
Hollow Knight: SilksongHow to install Hollow Knight: Silksong mods on Linux, SteamOS and Steam Deck
By Liam Dawe,
1
> View more Tips & Guides
Buy Games
Buy games with our affiliate / partner links:
Latest Forum Posts
Misc