up & down (y-axis) not working in 3.8

seekay08

it still doesn't work on 4.1 :(

jretropie

BuZz

@jretropie going to have to wait till raspberry pi moves to kernel 4.9+ (which won't be for some time I guess) unless someone can persuade raspberrypi to include a backported patch to the current 4.4.x series.

I can ask them I guess - I'll see if the patch applies cleanly to 4.4.x

BuZz

Is there anyone here who can test/confirm that the patches in https://retropie.org.uk/forum/post/28586 fix the issue before I submit them to the raspberry pi kernel github ?

retropiepghguy

@BuZz As soon as 4.1 came out, I did the Daphne Dragon's Lair mode button test. Same issue. You still need the mode button wired for the game to work.

BuZz

@retropiepghguy you compiled own kernel with those 2 patches?

retropiepghguy

@BuZz nope

BuZz

@retropiepghguy ok then it won't work since the fix isn't in the Raspbian kernel (yet). However, it has been merged into the rpi 4.4 kernel so will reach Raspbian soonish. see https://retropie.org.uk/forum/topic/5962/dragonrise-usb-driver-issue

BuZz

rpi-update can also be used if you need this fix and want the very latest kernel (As it is now available - https://github.com/raspberrypi/firmware/commit/6d45dcf869688163fa1c745cb059b14baf61b8fd) - https://github.com/Hexxeh/rpi-update

retropiepghguy

@BuZz Thanks so much. I just did an "update all packages" and the fix was not in the download. So you are saying if I do an rpi-udate, that is a different update?

BuZz

@retropiepghguy yes. read the instructions in the second link.

retropiepghguy

@BuZz So I did an install of rpi-update and ran the kernel update. Works great. However, it did change the axis and button configs. So I had to rerun the Retropie controller config, jstest, and re-edit dapinput.ini. But it works great now. Thanks a bunch!!!!!

Rene957

So, i had this problem too and doing rpi-update fixed the issue with the y axis on Neo Geo system, but now my gamepad doesn't work on when i launch a SNES game. It worked fine before the rpi-update, in fact the y axis problem was not present on SNES, only on Neo Geo. Any ideas what went wrong?

Rene957

@Rene957 Well i've solved it, for some reason the configurations of snes got deleted. Just had to run ES config again.

DancingPigeon

I actually got the fix backported into 4.4 but it hasn't fixed the issue entirely for me.

Here's what I was experiencing previously:

https://retropie.org.uk/forum/topic/5962/dragonrise-usb-driver-issue

The generic DragonRise based N64 controllers that you get off of ebay appear to have an issue with how their axes work. Currently they register Joystick movements in jstest in a really odd manner:

DPAD-L: Axis -0
DPAD-R: Axis +0
DPAD-U: Axis -3
DPAD-D: Axis +3

Joystick-L: Axis -2 (Axis -0 Binary)
Joystick-R: Axis +2 (Axis 0 Binary)
Joystick-U: Axis -3 Binary
Joystick-D: Axis +3 Binary

As you can see, the driver is currently interpreting Joystick X movement as both Axis 0 and 3, with 3 displaying the analog data, and 0 replicating the same input data but in binary form i.e. either fully press or no press. Unfortunately the Joystick Y movement is completely broken and only interprets binary Y movement and has no analog data at all. Reportedly this problem does not exist in Windows, although I am experiencing it on mac using both Joystick and Gamepad Tester and Controllers Lite (can't confirm the duplication, can confirm the input Axis being used), and haven;t been able to confirm.

https://github.com/raspberrypi/linux/issues/1755#issuecomment-265983761

After doing apt-get update I'm still suffering from the same problem. I'm going to try rpi-update and see if that fixes the problem.

BuZz

@DancingPigeon you will need to use RPI update until the latest kernels get packaged.

seekay08

everything worked great for me. thanks all!

DancingPigeon

@BuZz Thanks Buzz- I figured that it might take a little bit for the apt-get package to be updated.

I'll do a backup of my current image and try rpi-update. Will report back on how the axes work in jstest.

DancingPigeon

Good news and bad news.

Good news is the Axis are now reporting correctly- 0 and 1.

Bad news is Y axis movement is still binary (at least for my n64 controller replica). Its not the worst but its not ideal.

jretropie

@DancingPigeon What is the effect when the Y axis is binary?