login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
If anyone know more about this, please tell us.
disclaimer: you should never run scripts from the internet without reading them first.
I wish that Steam would have a "fallback" recognition program that even allowed you to properly map the buttons.
---EDIT---
Turned out currently there's a problem with steam-devices package. Due to that Steam can't access uinput and create Steam controller device.
If you see this error in ~/.steam/error.log
Couldn't initialize virtual gamepad: Couldn't open /dev/uinput for writing
... you have file /lib/udev/rules.d/99-steam-controller-perms.rules
... and "getfacl /dev/input"'s output looks like this:
getfacl: Removing leading '/' from absolute path names
# file: dev/uinput
# owner: root
# group: root
user::rw-
group::---
other::---
Then you might be able to fix the issue:
sudo mv /lib/udev/rules.d/99-steam-controller-perms.rules /lib/udev/rules.d/60-steam-input.rules
sudo udevadm control --reload
sudo udevadm trigger
After that "getfacl /dev/uinput" should look like this:
getfacl: Removing leading '/' from absolute path names
# file: dev/uinput
# owner: root
# group: root
user::rw-
user:<user>:rw-
group::---
mask::rw-
other::---
and Steam should be able to access uinput.
Some cable are not working properly which can mislead some users
The light on the Steam controller might turn on but, to be sure the cable is 100% compatible you need to hear the beep sound that the controller makes when it connect to the PC
No beep sound= the cable is not compatible.
Happened to me and i was really wondering what was going on
Me i use "sudo apt install steam-devices" and it always worked fine
Tried on a Windows only hdd and it works.
so it's not a controller problem.
Currently running Pop_OS! 20.04.