Did you do a big system upgrade recently and notice you're having gamepad issues? You're not alone. Time to downgrade perhaps.
To be clear this might only be an issue for the more bleeding-edge distributions which update more often, or those of you who are doing some manual updates to their system. The distributions that update more slowly like Ubuntu are likely unaffected right now.
First we have systemd version 243 released around September 3rd, this appears to be causing problems with Steam Input. A Valve developer jumped into the comments there, to note that the update seems to have broken Steam's udev rules to support gamepads—ouch. The systemd developers have been responsive trying to fix it, so hopefully it won't be too long before the issue is solved there.
Another problem is the more recent release of the Linux Kernel 5.3, which appears to have a regression with the DualShock 4 over Bluetooth not working. As of yet, no Kernel developer has commented on that report.
Hat tip to Vash63.
Article taken from GamingOnLinux.com.
Some you may have missed, popular articles from the last month:
The comments on this article are closed.
I've had 5.3 rc7 and 243 for a while (manjaro reverted back to 242 in the meantime), and didn't notice any issues with my xbox 360. At least not in Project Cars 2.
0 Likes
So that's why controllers in steam stopped working last week. Loading the module 'uinput' fixes it, as that is what Steam uses to create virtual controllers.
3 Likes, Who?
I have severe problems with Dualshock4 and the Switch Pro-controller on Debian 10 after updating to Kernel 5.2 via Backports. It could run deeper than just Kernel 5.3 and new systemd
0 Likes
This new systemd messed me up as well. I have to do a
Even after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.
sudo modprobe uinput to get the Steam Controller working in-game.Even after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.
2 Likes, Who?
Yes, I'm having some issues with my Nintendo Wii U Pro controller. I hope they will fix this soon.
0 Likes
Yep, 1 week without controller in game but it works on Steam menu.
Thank you for the tip, I didn't found any solution before.
Thank you for the tip, I didn't found any solution before.
1 Likes, Who?
Ouch.
Have not played games with a controller recently.
Hope the modprobe is enough to fix it.
Have not played games with a controller recently.
Hope the modprobe is enough to fix it.
0 Likes
hallieballie Sep 16, 2019
I really do not understand why systemd is so great, it is an annoying system to deal with.
When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.
The time with init scripts was heaven, now we are in hell.
When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.
The time with init scripts was heaven, now we are in hell.
3 Likes, Who?
Quoting: hallieballieI really do not understand why systemd is so great, it is an annoying system to deal with.
When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.
The time with init scripts was heaven, now we are in hell.
When you need to debuf from a rescue environment with the old init scripts you would be lucky if you where able to find any form of logs at all. On a systemd system though everything can be found with journalctl, even things that daemons wrote to stderr or stdout are caught.
As a server admin, systemd is the single best thing that have happened to Linux since the kernel.
14 Likes, Who?
Avehicle7887 Sep 16, 2019
Seems I'm in luck this time around, my systemd is a bit old (232) and my gamepad is so crappy that it doesn't work with almost none of my games regardless of which kernel I use, I have to use Antimicro to game with it.
On the other hand however, I upgraded to 5.3 this morning and everything went smooth, the nvidia driver also works fine with it. Also worth pointing out that this release contains a fix for system hangs when using Vulkan on Intel HD with Kabylake (7xxx CPUs).
Last edited by Avehicle7887 on 16 September 2019 at 9:41 pm UTC
On the other hand however, I upgraded to 5.3 this morning and everything went smooth, the nvidia driver also works fine with it. Also worth pointing out that this release contains a fix for system hangs when using Vulkan on Intel HD with Kabylake (7xxx CPUs).
Last edited by Avehicle7887 on 16 September 2019 at 9:41 pm UTC
0 Likes
Quoting: F.UltraQuoting: hallieballieI really do not understand why systemd is so great, it is an annoying system to deal with.
When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.
The time with init scripts was heaven, now we are in hell.
When you need to debuf from a rescue environment with the old init scripts you would be lucky if you where able to find any form of logs at all. On a systemd system though everything can be found with journalctl, even things that daemons wrote to stderr or stdout are caught.
As a server admin, systemd is the single best thing that have happened to Linux since the kernel.
I do like the features of systemd but I also think some of the detractors make sense.
It has a feature creep and seems to expand into a lot of things.
2 Likes, Who?
Quoting: FaalhaasEven after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.Reinstalled! :O Yikes!
I guess I haven't used my controller for over a month. I've been on systemd 243 for quite a while now.
Which OS distributed linux 5.3 already? Arch is pushing out 5.2.14 at the moment.
0 Likes
slaapliedje Sep 17, 2019
I'm running Debian Sid here, and only have systemd 242 and kernel 5.2.9. Just tested the Steam Controller. Don't have uinput loaded, but it still worked in Atari Vault.
0 Likes
Quoting: 14Quoting: FaalhaasEven after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.Reinstalled! :O Yikes!
I guess I haven't used my controller for over a month. I've been on systemd 243 for quite a while now.
Which OS distributed linux 5.3 already? Arch is pushing out 5.2.14 at the moment.
No idea if any OSes have distributed it to their core repos but I'm on Arch and I tested it a few hours after it released by compiling my own build.
0 Likes
Quoting: Vash63Are you the Vash6318 from the Battlefield 1942 days that's on my Steam friends list?Quoting: 14Quoting: FaalhaasEven after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.Reinstalled! :O Yikes!
I guess I haven't used my controller for over a month. I've been on systemd 243 for quite a while now.
Which OS distributed linux 5.3 already? Arch is pushing out 5.2.14 at the moment.
No idea if any OSes have distributed it to their core repos but I'm on Arch and I tested it a few hours after it released by compiling my own build.
Fancy seeing you here!
0 Likes
Quoting: FaalhaasThis new systemd messed me up as well. I have to do asudo modprobe uinputto get the Steam Controller working in-game.
Even after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.
Was one of those games Rocket League by any chance? The modprobe command didn't seem to do anything to get my steam controller working again.
0 Likes
Quoting: razing32Quoting: F.UltraQuoting: hallieballieI really do not understand why systemd is so great, it is an annoying system to deal with.
When you need to debug form a rescue environment, it is very difficult to see what went wrong, to access logging is science these days.
The time with init scripts was heaven, now we are in hell.
When you need to debuf from a rescue environment with the old init scripts you would be lucky if you where able to find any form of logs at all. On a systemd system though everything can be found with journalctl, even things that daemons wrote to stderr or stdout are caught.
As a server admin, systemd is the single best thing that have happened to Linux since the kernel.
I do like the features of systemd but I also think some of the detractors make sense.
It has a feature creep and seems to expand into a lot of things.
Yeah, boo on software that innovates and creates new useful features ;). What those detractors never recognise is that the "feature creep" is not in systemd the init daemon but systemd the project (that consists of independent applications, all of which are completely optional) where the aim is to create a common plumbing layer for Linux (aka system admins can expect to have access to the same set of tools regardless of system).
Few people complained when the GNU project forked all the unix tools back in the day and implemented their own set of useful extensions, most people only notice that when they happen to use some system that don't use the GNU versions (like Solaris or the BSD:s) at which point many feel constrained and crippled by the lack of those extensions (the countless times I've cursed when administrating some Solaris machines...).
0 Likes
Quoting: bradgyQuoting: FaalhaasThis new systemd messed me up as well. I have to do asudo modprobe uinputto get the Steam Controller working in-game.
Even after that, some games did not detect my buttons, so I even reinstalled the OS. Now it's working with modprobe.
Was one of those games Rocket League by any chance? The modprobe command didn't seem to do anything to get my steam controller working again.
No, it was Celeste. :) But I messed around a bit with the controller config, before I found out systemd was trolling. :D
1 Likes, Who?
I run Kernel 5.3.0 and Systemd 243.0, My controllers are all working just fine with Steam and anywhere else actually. I use Xbox One S controllers and Dualshock 4 controllers I use them all using Bluetooth.
0 Likes
Patreon
PayPal
See more from me