[SOLVED] Steam "No controllers detected" / can't get Steam controller out of lizard mode

trite · 07-09-2019, 04:59 PM

Using steam from slackbuilds (if that makes any difference?)

Have this in dmesg:

Code:

[14518.899235] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:28DE:1102.0016/input/input38
[14699.073127] udevd[667]: worker [7353] /devices/pci0000:00/0000:00:14.0/usb1/1-3 timeout; kill it
[14699.073133] udevd[667]: seq 8592 '/devices/pci0000:00/0000:00:14.0/usb1/1-3' killed
[14699.073287] udevd[667]: worker [7353] failed while handling '/devices/pci0000:00/0000:00:14.0/usb1/1-3'
[14882.252115] udevd[667]: worker [7574] /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0 timeout; kill it
[14882.252122] udevd[667]: seq 8593 '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0' killed
[14882.252247] udevd[667]: worker [7574] failed while handling '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0'
[15065.435600] udevd[667]: worker [7681] /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:28DE:1102.0016/input/input38 timeout; kill it
[15065.435607] udevd[667]: seq 8595 '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:28DE:1102.0016/input/input38' killed
[15065.435786] udevd[667]: worker [7681] failed while handling '/devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:28DE:1102.0016/input/input38'

Controller is stuck in "lizard mode" which makes it act as a keyboard/mouse so the X,Y,A,B buttons are not working and steam doesn't find the controller.

Found some reddit thread saying that he had the same problem and that he installed ubuntu package "steam-devices" and I checked the file contents of that package and it was just some udev rules which I already have.
Except that my udev rules had a "TAG+=uaccess".

There is some slackbuild named steam-xpad, maybe I need this?
https://slackbuilds.org/repository/1.../steamos-xpad/

The slackbuilds for steam does install a few rules, hmm...

oh wait I see it now I think I need to change MODE="0660" to MODE="0666" in the existing rules

yep that did it, after reboot steam prompted me to update firmware the first thing it did
marking as solved

dugan · 07-09-2019, 05:06 PM

This gets it working for me on -current:

https://www.linuxquestions.org/quest...ml#post5953609

Part of the reason it works is that -current has user accounts in the "input" group by default.

Hint: launch Steam from the terminal, and then try to configure the controller in Big Picture Mode. If it doesn't work, look at the terminal. There reason should be in Steam's terminal output.

trite · 07-09-2019, 05:30 PM

thanks I changed it back to 0660 (to not make it world readable) and added the GROUP="input", thats better

chris.willing · 07-10-2019, 02:35 AM

Quote:

Originally Posted by trite

thanks I changed it back to 0660 (to not make it world readable) and added the GROUP="input", thats better

Was that GROUP change made to the /lib/udev/rules.d/60-steam-input.rules file that's part of the installation by SBo's steam.SlackBuild? If so, I can change it in the SlackBuild so others won't have the same problem in future.

chris

trite · 07-10-2019, 03:01 AM

Quote:

Originally Posted by chris.willing

Was that GROUP change made to the /lib/udev/rules.d/60-steam-input.rules file that's part of the installation by SBo's steam.SlackBuild? If so, I can change it in the SlackBuild so others won't have the same problem in future.

chris

Yes, or well the udev rules is part of the steam .tar.gz so its not really the slackbuilds rules but in the slackbuild script it copies those files from the steam.tar.gz into your udev rules.d.

So we should write a sed s/foo/bar/g thingy in the slackbuild script or what is the best way forward?

I'm guessing you could do something like this, although I have no idea on what is considered best practice

Code:

sed 's/KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput"/KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", GROUP="input", OPTIONS+="static_node=uinput"/g' lib/udev/rules.d/60-steam-input.rules > lib/udev/rules.d/60-steam-input.rules

maybe sed -i is better

Code:

sed -i 's/KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput"/KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", GROUP="input", OPTIONS+="static_node=uinput"'/ lib/udev/rules.d/60-steam-input.rules

Anyway you just have to add GROUP="input" to that line, and there is only one line of which to replace.

Aaah, you are the maintainer of the steam sbo package?

chris.willing · 07-10-2019, 05:35 AM

Quote:

Originally Posted by trite

Aaah, you are the maintainer of the steam sbo package?

Yes but unfortunately I don't have a Valve controller to test any changes with. For 14.2 (which SBo is targeting) I'm inclined to use the plugdev group (rather than input) since most 14.2 users will be members of the plugdev group already. Anyone using -current should be able to use that setting as well but I could change the group to input when 15.0 is released and becomes SBo's official target.

Since I can't test it myself, I wonder if you might find some time to test for me? I"m fairly confident the proposed change will work but it would be nice to know for sure ...
If so, could you change the rule to:

Code:

KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput" GROUP="plugdev"

which would be generated in the SlackBuild by adding:

Code:

sed -i -e 's/^KERNEL=="uinput".*/& GROUP="plugdev"/' $PKG/lib/udev/rules.d/60-steam-input.rules

Thanks,
chris

dugan · 07-10-2019, 12:06 PM

Quote:

Originally Posted by chris.willing

Yes but unfortunately I don't have a Valve controller to test any changes with.

You just need to test Steam's Big Picture Mode input remapping. If that works, then the Valve Steam Controller works.

trite · 07-10-2019, 01:49 PM

Quote:

Originally Posted by chris.willing

Yes but unfortunately I don't have a Valve controller to test any changes with. For 14.2 (which SBo is targeting) I'm inclined to use the plugdev group (rather than input) since most 14.2 users will be members of the plugdev group already. Anyone using -current should be able to use that setting as well but I could change the group to input when 15.0 is released and becomes SBo's official target.

Since I can't test it myself, I wonder if you might find some time to test for me? I"m fairly confident the proposed change will work but it would be nice to know for sure ...
If so, could you change the rule to:

Code:

KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", OPTIONS+="static_node=uinput" GROUP="plugdev"

which would be generated in the SlackBuild by adding:

Code:

sed -i -e 's/^KERNEL=="uinput".*/& GROUP="plugdev"/' $PKG/lib/udev/rules.d/60-steam-input.rules

Thanks,
chris

Ok I changed the group in udev rules from input to "plugdev" (then rebooted) and the controller seems to be detected still so I guess it works aswell?

Am I supposed to have the input group or plugdev for -current?

Also I might add that I did not follow your instructions exactly d:
But it should not make any difference because the only thing that differs is the order.

Code:

bash-5.0$ head -5 /lib/udev/rules.d/60-steam-input.rules 
# Valve USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0660", TAG+="uaccess"

# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", GROUP="plugdev", OPTIONS+="static_node=uinput"
bash-5.0$

and if you want me to try anything for the steam controller I guess I can try it for you if its not too much of a hassle (I also have first gen HTC Vive but its not set up atm)

trite · 07-10-2019, 01:59 PM

Also heeyyy were making progress here on a package for Slackware, great stuff! thank you chris d:

chris.willing · 07-10-2019, 05:15 PM

Quote:

Originally Posted by trite

Ok I changed the group in udev rules from input to "plugdev" (then rebooted) and the controller seems to be detected still so I guess it works aswell?

Am I supposed to have the input group or plugdev for -current?

Also I might add that I did not follow your instructions exactly d:
But it should not make any difference because the only thing that differs is the order.

Code:

bash-5.0$ head -5 /lib/udev/rules.d/60-steam-input.rules 
# Valve USB devices
SUBSYSTEM=="usb", ATTRS{idVendor}=="28de", MODE="0660", TAG+="uaccess"

# Steam Controller udev write access
KERNEL=="uinput", SUBSYSTEM=="misc", TAG+="uaccess", GROUP="plugdev", OPTIONS+="static_node=uinput"
bash-5.0$

and if you want me to try anything for the steam controller I guess I can try it for you if its not too much of a hassle (I also have first gen HTC Vive but its not set up atm)

Your change of order shouldn't matter.

Which is correct group to use? For 15.0, it probably is "input" group. Although that group already exists in 14.2, new users are not automatically made members of that group when their accounts are created. That means users would have to have their group membership changed for GROUP=input to be beneficial. Therefore in this case (14.2) I think GROUP=plugdev is better. When 15.0 is released and new users are automatically members of "input" group, then GROUP=input will be better. Therefore on -current, the input group makes more sense. Luckily, plugdev group is OK too since new -current users are already made members of plugdev group too.

Thanks for testing - very helpful for 14.2 users.

chris