Logitech F310 gamepad no longer recognized

[eurogomez]

Hi,
My gamepad is no longer recognized in steamlink. It used to work flawlessly.
In steamlink controller setup I see a device named 0x046d/0xc21d. I can't configure or test it. When I try to there's an output in log:

Couldn't open game controller with ID 0
Couldn't open joystick with ID 0

lsusb gives me:

Bus 001 Device 006: ID 046d:c21d Logitech, Inc. F310 Gamepad [XInput Mode]

Gamepad works as expected in osmc. cat /dev/input/js0 gives the expected results.
Can anyone please point me in the right direction to resolve this ?
Thanks.

[slouken]

I'll take a look at this tomorrow, thanks!

[slouken]

What distribution are you running?

Did you install the new udev rules? This should have been a terminal pop-up once after installing the last update.

What’s the output of id?

[slouken]

Actually, this should fix it:
sudo usermod -a -G input osmc

[eurogomez]

Hi,

Originally posted by slouken:

What distribution are you running?

Osmc on a pi 3. Retropie on top of it (via retrosmc[github.com]

Originally posted by slouken:

Did you install the new udev rules? This should have been a terminal pop-up once after installing the last update.

Definitely not. Didn't see any terminal pop-up. Are these the rules located in .local/share/SteamLink/udev/rules.d/55-steamlink.rules ?

Originally posted by slouken:

What’s the output of id?

uid=1000(osmc) gid=1000(osmc) groups=1000(osmc),4(adm),6(disk),7(lp),20(dialout),24(cdrom),29(audio),44(video),106(input)

Originally posted by slouken:

Actually, this should fix it:
sudo usermod -a -G input osmc

Unfortunately it didn't. I was already in the input group (the gamepad is working normally in osmc).
Definitely going to try to install those udev rules...
Many thanks.

edit: problem still occurs despite the added udev rules. I just plugged in another joystick and it just works. The problem is only with the F310 and only in steamlink.

[slouken]

Originally posted by eurogomez:

Hi,

Originally posted by slouken:

What distribution are you running?

Osmc on a pi 3. Retropie on top of it (via retrosmc[github.com]

Originally posted by slouken:

Did you install the new udev rules? This should have been a terminal pop-up once after installing the last update.

Definitely not. Didn't see any terminal pop-up. Are these the rules located in .local/share/SteamLink/udev/rules.d/55-steamlink.rules ?

Originally posted by slouken:

What’s the output of id?

uid=1000(osmc) gid=1000(osmc) groups=1000(osmc),4(adm),6(disk),7(lp),20(dialout),24(cdrom),29(audio),44(video),106(input)

Originally posted by slouken:

Actually, this should fix it:
sudo usermod -a -G input osmc

Unfortunately it didn't. I was already in the input group (the gamepad is working normally in osmc).
Definitely going to try to install those udev rules...
Many thanks.

edit: problem still occurs despite the added udev rules. I just plugged in another joystick and it just works. The problem is only with the F310 and only in steamlink.

Try rebooting to make sure the rules are picked up by udev? I just tested here on my Raspberry Pi running Raspbian and it's working fine.

[eurogomez]

I rebooted. Same result.
Sooo:
- F310 is correctly named and configured in osmc
- F310 is named after its hardware ID and doesn't work in steamlink
- another joystick (Mayflash F300) is correctly named and configured in both osmc & steamlink
Behaviour is constant with one, the other or both joysticks plugged in, in any usb port.
And F310 did work before
Filesystem corruption ? I don't know what else...

[slouken]

Ah, I know why...
Try this: sudo usermod -a -G plugdev osmc

[eurogomez]

Originally posted by slouken:

Ah, I know why...
Try this: sudo usermod -a -G plugdev osmc

And it works ! Many thanks.

[slouken]

Originally posted by eurogomez:

Originally posted by slouken:

Ah, I know why...
Try this: sudo usermod -a -G plugdev osmc

And it works ! Many thanks.

You're welcome! I added that to the troubleshooting, and it'll be in the udev update process in the future.

Thanks for the help troubleshooting!