[SOLVED] Steam Controller is Not Detected in steam but works as mouse and keyboard.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Except that solution does not seem to work.
Here's my dmesg output.
Code:
[ 5425.244809] usb 1-9: USB disconnect, device number 37
[ 5426.530965] usb 1-9: new full-speed USB device number 38 using xhci_hcd
[ 5426.696323] usb 1-9: New USB device found, idVendor=28de, idProduct=1102
[ 5426.696327] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 5426.696329] usb 1-9: Product: Wired Controller
[ 5426.696331] usb 1-9: Manufacturer: Valve Software
[ 5426.696529] usb 1-9: ep 0x81 - rounding interval to 64 microframes, ep desc says 80 microframes
[ 5426.696534] usb 1-9: ep 0x82 - rounding interval to 32 microframes, ep desc says 48 microframes
[ 5426.696539] usb 1-9: ep 0x83 - rounding interval to 32 microframes, ep desc says 48 microframes
[ 5426.697743] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.0/0003:28DE:1102.002E/input/input84546
[ 5426.748549] hid-generic 0003:28DE:1102.002E: input,hidraw4: USB HID v1.11 Keyboard [Valve Software Wired Controller] on usb-0000:00:14.0-9/input0
[ 5426.749253] input: Valve Software Wired Controller as /devices/pci0000:00/0000:00:14.0/usb1/1-9/1-9:1.1/0003:28DE:1102.002F/input/input84547
[ 5426.749450] hid-generic 0003:28DE:1102.002F: input,hidraw6: USB HID v1.11 Mouse [Valve Software Wired Controller] on usb-0000:00:14.0-9/input1
[ 5426.750357] hid-generic 0003:28DE:1102.0030: hiddev0,hidraw7: USB HID v1.11 Device [Valve Software Wired Controller] on usb-0000:00:14.0-9/input2
The udev rules seems to be adjusted in slackbuild accordingly to that previous issue. I've added myself to both input and plugdev groups. I also upgraded controllers firmware manually and then it was possible to do that via steam.
But controller just works as mouse and keyboard, X Y A B buttons does work in the Big picture mode correctly. But controller is not detected, not configurable and basically works entirely wrong in games, (well as a mouse and a bit of a keyboard).
P.S. Having no issues with cheap variant of PS3 controller.
I use a PS2 controller! The only advice I have is to plug it in another USB port. Sometimes Steam doesn't recognize my controller and I have to plug it into another USB port. I don't have a Steam Controller so I can't help.
It does not work on 14.2 for me but I just built that system as current was nuking too many things and I got tired of fixing them after each update.
It does not seem to work on current either. To be clear the steam does not see the controller on 14.2 on current it sees it but it acts like yours. Thinks its a mouse. Steam sees it and tries to use it but it does not show up in the game. Like in Trine it only sees the keyboard and mouse. It even says it loaded the config that I selected for it. But no joy.
OK it works fine in Serious Sam BFE. Not sure why it did not work on Trine as is says it has full controller support.
Not sure whats going on here but SS BFE does have an official Steam Controller config.
SO maybe you have to build the config to match the game I had to do that for a lot of games but I usually use an XBox one controller or a Xbox 360 controller never got the hang of the Steam controller.
Putting the following in /etc/udev/rules.d/99-steamcontroller.rules didn't work for you on -current? It definitely worked for me, although that was admittedly a while ago.
It does not work on 14.2 for me but I just built that system as current was nuking too many things and I got tired of fixing them after each update.
It does not seem to work on current either. To be clear the steam does not see the controller on 14.2 on current it sees it but it acts like yours. Thinks its a mouse. Steam sees it and tries to use it but it does not show up in the game. Like in Trine it only sees the keyboard and mouse. It even says it loaded the config that I selected for it. But no joy.
Not sure about other games.
Oh I forgot to mention it's 14.2 I'm using.
Quote:
Originally Posted by dugan
Putting the following in /etc/udev/rules.d/99-steamcontroller.rules didn't work for you on -current? It definitely worked for me, although that was admittedly a while ago.
there are these rules in /lib/udev/rules.d/60-steam-input.rules installed with steam slackbuild
Putting the following in /etc/udev/rules.d/99-steamcontroller.rules didn't work for you on -current? It definitely worked for me, although that was admittedly a while ago.
But I also have these first lines edited in /lib/udev/rules.d/60-steam-input.rules
Just so you're aware, the files in /lib/udev/rules.d/ aren't supposed to be edited by the end user. If you need to make changes, you're supposed to copy the file to /etc/udev/rules.d/ and then make any changes you need to make. If you have 2 files with the same name, one in /lib/udev/rules.d/ and one in /etc/udev/rules.d/, the one in /etc/ will always take precedence and will be the one that is used.
The reason behind this is the files in /lib/udev/rules.d/ can be updated at any time and you would lose all your changes. We haven't seen any udev updates in 14.2 since it was released (so far, but I suppose it's always possible), but if you ever run -current, it could be updated at any time and you'd lose all your changes.
Just so you're aware, the files in /lib/udev/rules.d/ aren't supposed to be edited by the end user. If you need to make changes, you're supposed to copy the file to /etc/udev/rules.d/ and then make any changes you need to make. If you have 2 files with the same name, one in /lib/udev/rules.d/ and one in /etc/udev/rules.d/, the one in /etc/ will always take precedence and will be the one that is used.
The reason behind this is the files in /lib/udev/rules.d/ can be updated at any time and you would lose all your changes. We haven't seen any udev updates in 14.2 since it was released (so far, but I suppose it's always possible), but if you ever run -current, it could be updated at any time and you'd lose all your changes.
Just some food for thought
I did not know that. Thanks for explaining. By the way do you need to reboot after editing udev rules or there is some other way for them to take effect ? I never really had any business with it in linux up to the steam controller.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.