Controller stopped working after update.

UDb23

Several people having this issue after 3.8 update (see here), in particular with Logitech gamepads. xbox 360 pc gamepad on the other hand still works fine.
Can developers please look into this ? Thanks.

BuZz

@UDb23 we are not responsible for the Kernel/OS - it needs reporting to https://github.com/raspberrypi/linux - did you try downgrading the kernel as described in this thread https://retropie.org.uk/forum/topic/1640/xbox360-wireless-controllers-receiver-connectivity-issues ?

UDb23

@BuZz Thanks! I'll report it at the github link you provided.
And try the suggested downgrade.

BuZz

@UDb23 did you try xinput mode as well as directinput?

UDb23

@BuZz Rumblepad 2 used to work under 3.7 and previous. Under 3.8 it is still correctly detected by Emulation station but ALL buttons are inactive and I cannot therefore configure it.
On the other hand a brand new wired Xbox 360 PC controller seems to work fine under 3.8.
Will do some further testing as soon as I have some time.

UDb23

@BuZz It seems Kernel has been updated to fix this issue ( https://github.com/raspberrypi/linux/issues/1496).
I just updated with
sudo apt-get update
and
sudo apt-get dist-upgrade
Unfortunately Rumblepad 2 still not working. BTW it has no xinput mode.
Any suggestions ?
Thanks.

BuZz

the kernel is not yet packaged - you need to use rpi-update to get it.

UDb23

@BuZz Used rpi-update, thanks. Pad still not working. :-(

mediamogul

Do the controllers register at all in a jstest or evtest?

BuZz

@UDb23 what's the output of uname -a

UDb23

@BuZz Linux retropie 4.4.13-v7+ #893 SMP Wed Jun 8 14:39:18 BST 2016 armv7l GNU/Linux

UDb23

@mediamogul I used jtest as suggested and Rumblepad is detected and buttons working !!
Still ES would not detect it even if it was working before 3.8 update.
I then rebooted connecting the Rumblepad (as a second pad) together with the currently working Xbox360 Pad. That allowed me to enter Input configuration in ES and, finally, it detected rumblepad and I was able to configure it. :-)
Everything back working now !
Basically for those still having the issue, you can solve it by rpi-update command plus reconfinguring it.
Thank you all for the support!