You are not logged in.
Folks, I am at my wit's end.
At some point, (I don't remember when) my Steam controller stopped working properly on arch. The problem is that I can only seem to get the controller to work as a keyboard/mouse. When I plug the dongle in to the usb port and then activate the controller with Steam+A, it seems to activate properly. I can get the controller to emit the little tone by identifying it, and I can browse the big picture mode just fine. No games I launch however seem to detect the steam controller as a controller. For example, Dead cells tells me that the game is best played with a controller.
I feel like I've tried everything to fix this problem. I've looked at the following litany of forum posts, bugs, and docs: https://wiki.archlinux.org/index.php/Ga … Controller, https://wiki.archlinux.org/index.php/Ga … ot_pairing, https://bugs.archlinux.org/task/46752, and https://bugs.archlinux.org/task/47330.
None of the solutions offered have worked for me. Steam has already fixed the udev priority issue by renaming their rules to '70-steam-input.rules', Adding 0666 permissions to a '99-steam-controller-permission.rules' rule file didn't work. Rebooting with or without the dongle in doesn't seem to matter either. There was something mentioned about /dev/uinput not being the right permissions, and indeed I had '---' as well, so I tried chmoding it to 0666, but this didn't work either. I'm pretty sure the controller itself is fine since I have in the past used it just fine through the steam link and with my Windows VM using passthrough. Its very frustrating because it seems like all of the existing posts end with one of these types of solutions which fix their problem but not mine. I feel like I didn't read something right or I just don't understand what the issue is.
Another symptom seems to be that I cannot follow the firmware flashing procedure here: https://steamcommunity.com/sharedfiles/ … =572740074 namely, connecting the controller by usb doesn't seem to give me any events in dmesg indicating a new /dev partition or anything. I actually don't really want to flash my firmware, but I've been trying anything at this point. The fact that I can't do it might be a clue.
I feel like I'm missing some diagnostic tool or method to look at /dev and udev and so on to figure out what the problem is. Can somebody who knows what they're doing guide me through trouble shooting this problem? I'm all out of ideas and I wonder whether there are any others like me.
Offline
Okay, I fussed over this today, and I think I found the answer (at least for the moment) in case anybody sees this message.
It sounds like this is an issue with the new hid_steam kernel module from 4.18 and on. The way to deal with it is to first apply the udev patch mentioned in https://github.com/ValveSoftware/steam- … ssues/5645, then blacklist the hid_steam module also mentioned in that link.
The clue came when I was trying different games and tried with hollow knight which crashed. Launching steam from the terminal revealed a stack trace with a crash inside libmono. Searching for this error brought me to https://github.com/ValveSoftware/steam- … ssues/5841 which links to the solution above.
I was also trying to get the steam controller to work with Dead Cells and the above fixes didn't work for that game either, however searching the issue brings me to: https://steamcommunity.com/app/588650/d … 678/?ctp=2 So it's a game bug.
I think now my steam controller issues seem solved. I'll try to update if the hid_steam module gets fixed.
Offline