You can sign up to get a daily email of our articles, see the Mailing List page!
Support us on Patreon to keep GamingOnLinux alive. This ensures we have no timed articles and no paywalls. Just good, fresh content! Alternatively, you can donate through Paypal, Flattr and Liberapay.!

After updating to Ubuntu 18.10 today I noticed that a lot of games were either crashing to the desktop, not detecting my Steam Controller at all or detecting it as a second player.

With the Linux Kernel version 4.18, a driver is now included for the Steam Controller named "hid_steam" which seems to currently be conflicting with how Steam and plenty of games handle the Steam Controller resulting in behaviour we don't want.

For now, it seems you will need to blacklist that "hid_steam" module from loading if you want to continue using the Steam Controller as normal.

You can test it yourself, using this terminal command to see if it fixes it:

sudo modprobe -r hid_steam

That was only temporary though, a reboot quickly made it break once again (but it works for now). To have it permanently stay, you can do this:

sudo bash -c "echo 'blacklist hid_steam' > /etc/modprobe.d/sc.conf"

I did also run this command so the above was correctly detected:

sudo update-initramfs -u

Once you reboot, that will then make it stick.

Hopefully this situation will get sorted out, because that's really not ideal right now. For newer users especially, it's not a good look. I've opened a bug report with the Ubuntu team.

Update: As noted in our comments, there is a Kernel patch available if you wish to patch it manually yourself if you're confident doing that sort of thing. Hopefully the Ubuntu maintainers can pull it in for everyone.

14 Likes, Who?
We do often include affiliate links to earn us some pennies. We are currently affiliated with GOG and Humble Store. See more information here.
22 comments
Page: 1/3»
  Go to:

theghost 18 October 2018 at 11:58 am UTC
Thx for the quick fix.
I wonder if I still need sc-controller with Kernel 4.18 and hid_steam for Dead Cell's ?


Last edited by theghost at 18 October 2018 at 11:58 am UTC
JungleRobba 18 October 2018 at 12:02 pm UTC
The writer of the module is aware of the issue and seems to be working on a fix:
https://github.com/ValveSoftware/steam-for-linux/issues/5645#issuecomment-429647198


Last edited by JungleRobba at 18 October 2018 at 12:05 pm UTC
liamdawe 18 October 2018 at 12:10 pm UTC
JungleRobbaThe writer of the module is aware of the issue and seems to be working on a fix:
https://github.com/ValveSoftware/steam-for-linux/issues/5645#issuecomment-429647198
Thanks, added a note about it.
slaapliedje 18 October 2018 at 12:20 pm UTC
View PC info
  • Supporter
Hmm, I have been running 4.18 on Debian Sid for a long time now and haven't had an issue. It has ran about the same as it always has. Wonder if they already blacklist it. Will have to check.
Keyrock 18 October 2018 at 1:27 pm UTC
The title of this article could also use quick a fix.

Yeah, I'm that guy.

/hides
MayeulC 18 October 2018 at 1:32 pm UTC
sudo bash -c "echo 'blacklist hid_steam' > /etc/modprobe.d/sc.conf"

how about making it

echo blacklist hid_steam | sudo tee /etc/modprobe.d/sc.conf

Instead? Does it make it simpler?
liamdawe 18 October 2018 at 1:49 pm UTC
KeyrockThe title of this article could also use quick a fix.

Yeah, I'm that guy.

/hides
Well then. That was embarrassing.
Beamboom 18 October 2018 at 2:24 pm UTC
But the case of;
Quotea lot of games were crashing to the desktop
that was only related to the issue with the controller? So after this fix there was no more crashing to the desktop?
liamdawe 18 October 2018 at 2:38 pm UTC
BeamboomBut the case of;
Quotea lot of games were crashing to the desktop
that was only related to the issue with the controller? So after this fix there was no more crashing to the desktop?
Bingo. A bunch of Unity games completely crashed to the desktop with the Steam Controller turned on without blacklisting it.

Edit: Spelling.


Last edited by liamdawe at 18 October 2018 at 2:38 pm UTC
Oli 18 October 2018 at 2:50 pm UTC
QuoteThen reboot.

Seems a bit redundant. The first commands handles this session The second and third handle future sessions. Just run all three once and get on with your life.
  Go to:
While you're here, please consider supporting GamingOnLinux on Patreon or Liberapay. We have no adverts, no paywalls, no timed exclusive articles. Just good, fresh content. Without your continued support, we simply could not continue!

We also accept Paypal donations and subscriptions! If you already are, thank you!

Due to spam you need to Register and Login to comment.


Or login with...

Livestreams & Videos
Community Livestreams
See more!
Popular this week
View by Category
Contact
Latest Comments
Latest Forum Posts