[feederchain]

OK, I’ve checked and my controller adapter still has the issue where it doesn’t see the up and left directions. (I think I remember those correctly…. Anyway) So that means that one of the things I fixed (pulsing) doesn’t need to be in the kernel. So within the next couple days I’ll remove that part of the patch and try it with v3.0.

[feederchain]

I’ve had no experience with 3.0. The patch here is pretty small to the kernel. I can’t see anything that is in it would cause any issues to anything.

That being said. I have a couple micro sd cards lying around. I’ll try installing from scratch. I’ll let everyone know what I find with my adapter.

[feederchain]

Are you sure you are trying to download the one from this post?

Autofire on the axis

It appears to still be working for me.

[feederchain]

Does the USB key mount properly and everything? Can you see the downloaded file?

If so just run the commands found in the above post.

Autofire on the axis

[feederchain]

I haven’t heard of anyone else having this issue. I have not upgraded my version since when I uploaded the last kernel. Are you getting any type of output/error?

[feederchain]

Glad I could help. Awesome cabinet!

[feederchain]

My setup has the joystick mappings right in retroarch.cfg. Are there some there that take precedent? I haven’t upgraded my version of RetroPie since I got it all working. So maybe the config stuff has changed since I installed.

[feederchain]

There are controller mappings and such starting on page one of this thread. It will all depend on the controller you are using, for what buttons should be mapped to what.

[feederchain]

I can only assume that is exactly what you typed. In which case you have the file name wrong. You are missing the 0 before the 6.

Here’s a tip. In the linux command line the tab key can be very useful. For example if you type the following

tar xf custom

then hit the tab key. It should auto complete to the file name. If there are more than one file name that starts with “custom” you will have to hit it twice to get the list of possibles.

[feederchain]

You don’t need to unzip the file before moving it to the Pi. In fact you probably shouldn’t.

I setup RetroPie to have a samba share so that it would like a windows share. That’s how I transferred the gz file to mine.

Once you have it there, just run these three commands

tar xf custom_kernel_1.20150619-1.tar.gz
cd custom_kernel_1.20150619-1
sudo ./install.sh

The first command unpacks the file into a new directory.
The second changes into that directory
The third installs the kernel

[feederchain]

OK, so it looks like an apt-get update does update the kernel and mess with this. My custom kernel above is 3.18.7. I did a new compile and it’s now 3.18.9.

https://www.dropbox.com/s/l96mgbsc2r8b7wf/custom_kernel_1.20150619-1.tar.gz?dl=0

I did notice something interesting though. Before I tried my new kernel, I noticed that the “auto-fire” issue appears to have disappeared from the vanilla kernel. So there might only be the issue with directional pad left. Which may not get fixed because of non-compliance. I’ll have to try to see if one of the patches can be removed.

Anyway, the above should be the latest and work for you.

[feederchain]

It’s usually ok to update. The issue is when a new kernel is released. Since I got my PI to where I wanted it, I didn’t really have a need to compile the changes in to the latest kernel.

I will try and take the time in the next day or so to recompile a new kernel and post it here.

As for getting this code patched in… I don’t really have an answer for that. I’m not associated to the project at all. I assume someone that is would have to evaluate the changes and decide.

The directional pad issue was because of non-compliant hardware so that might be a stretch to get it in. The second “rapid fire” issue did turn up because of a fix to something. Do recall what it was off the top of my head.

[feederchain]

No that doesn’t really make any sense. Did you run an apt-get update or anything? I know that if a new kernel shows up it will most likely overwrite this one. I haven’t run an update since I installed, and have had my PI on and off since. Possibly even there being a two week stretch without it on. But can’t say for sure.

Definitely odd if you didn’t update, because I don’t think there is an auto update.

[feederchain]

You can try without the patch from scratch. I have not upgraded my pie since I installed my patch. So I don’t know if some of these issues have been addressed in the vanilla code.

I’m a bit surprised that a button setup for one person wouldn’t work for someone else. All else being equal.

[feederchain]

Does the mapping here not work?

Autofire on the axis

[feederchain]

Sorry I haven’t been able to jump on these as fast as in the past. It’s been a couple exhausting days. But it looks like others have me covered!! Thanks everyone!

[feederchain]

I thought they were assigned to the start or select buttons. I haven’t tried to use mame yet though so I can’t say with any certainty.

[feederchain]

If you only had to swap the axis on one of the controllers that would sound like a wiring issue. Especially if it works correctly in in the emulators and not ES. That sounds like setup is correct in one and not the other.

As for your other buttons. I don’t know know why they wouldn’t map as the others. If you see them in jstest, you should be able to map them to a retroarch input.

[feederchain]

Is the first set of mappings exactly as seen in the cfg file? As in, are the #’s there? They shouldn’t be. You have to remove those.

So both sets should probably look the same as what you pasted as working except

input_player2_joypad_index = 1

You can use jstest to figure out which button is which to map to the button in retroarch. But if you say that the uncommented button map works for player 1. Player 2’s should match.

[feederchain]

The # is used to comment out the line. Which means it will be ignored. So any line that you want to use you would remove the # from the start. So for example when it comes to the button mappings. You find those lines. Remove the # and change the assigned button at the end of the line. Copy and paste lines for joystick 1. Place them below. Changing these new lines to represent joystick 2.

It doesn’t really matter too much where the lines are located in the file. You just need to know that the later lines override anything before it if you have duplicates. You would probably be pretty safe copying and pasting other’s input lines from earlier.

[feederchain]

There are posts above describing the button maps needed for the controller you are having issues with. So you will need to add them into the retroarch.cfg file. Usually use the one in the all directory, unless you need something specific for a particular emulator.

Player 2 can be added right below player 1. You can do this by using the text editor nano

nano retroarch.cfg

Or if you feel more at home with a gui, you can always startx from the command line and work in there.

[feederchain]

Ya.. sorry I screwed up on remembering the config file name.

I find it odd that with the latest version of the kernel I have posted

(https://www.petrockblock.com/forums/topic/autofire-on-the-axis/page/2/#post-91680)

you are unable to get player two to work. Are there input_player2 lines added to the .cfg file?

[feederchain]

So have you added the input set up in

/opt/retropie/configs/all/retropie.cfg

?

If not you should find some examples of the button mapping earlier in this thread.

[feederchain]

All this praise is going to start going to my head if you all aren’t careful! :-)

[feederchain]

Sure, you can find the latest kernel version that I created for another user last night here

Autofire on the axis

[feederchain]

If this ends up kinda being a double post… Sorry. I posted 10 minutes ago, but it has yet to show up.

Short answer is that this may be the issue

https://github.com/adafruit/Adafruit-Pi-Kernel-o-Matic/issues/11

I’ll see if I can get a new kernel with the latest tool.

edit:
Here it is. This is the latest kernel with all the updates in this thread. I have not tested it. It’s too late for me to want to try it tonight, but I figured I’d post. Install at your own risk!!

https://www.dropbox.com/s/f610y6q91mfv9zb/custom_kernel_1.20150317-1.tar.gz?dl=0

[feederchain]

Appreciate it. Once again, glad I could help.

[feederchain]

@krauthaus.. It’s good to hear this is working for so many people. Unfortunately I have not looked into running ScummVM yet. So I don’t think I can provide much help on that front.

@yves1984.. There are examples of button maps earlier in this thread that appeared to be working for others. Have you tried running jstest to see if the buttons all map out and function properly? I don’t recall if jstest is installed by default in retropie or not.

If it isn’t simply run

sudo apt-get install joystick
jstest /dev/input/js0

ctrl-c anytime to close the program

[feederchain]

Any time, glad to hear that you are getting somewhere.

[feederchain]

I don’t have the controller setup that you are using. It just happened my issue was showing up the same as with what you are trying to use. I’m guessing since the custom kernel didn’t install, this would be the reason that it still doesn’t work. (Although since I don’t have this exact setup, maybe I messed up the compile)

So how are you transferring the download above to the raspberry pi? It seems odd that if you see the install.sh it doesn’t run.

Unless you are unpacking it before moving it to the pi. This might cause you to lose the executable permission.

Without knowing the exact steps you used I can only guess as to what the issue might be at this point.

The following are the steps that should work.

Download the latest kernel I compiled above.
Copy it to your raspberry pi somewhere.
Go to this directory on your raspberry pi
Run the following 3 commands.

tar -xf custom_kernel_1.20150306-1.tar.gz
cd custom_kernel_1.20150306-1
sudo ./install.sh

If this doesn’t work, I think I’ll need a clearer picture of the steps you used to get to this point.

Thanks

[feederchain]

If that is the install command you used that is slightly wrong.
Lower case ‘s’ and no ‘:’

sudo ./install.sh

sudo is the command used to run the install.sh script with superuser priveledges.

[feederchain]

That is a good question, when I first recompiled this custom kernel it was only because of the left and down directions not working and that appeared to be because some hardware isn’t following spec, or compliant with a standard. I don’t know if that could get in. The issue described here was a bit different. In that I found the code that went it that caused it, because it became an issue between kernels. But I honestly didn’t do a whole bunch of research into what I was backing out. This started as just something I needed :-)

[feederchain]

Glad to hear it.

[feederchain]

I think that you should be good with those steps. I created my build a few months ago compiling from source. This takes alot of time. But I’m sure the image is fine. The custom kernel I posted fixes some of the issues. According to buzz’s post above, there is a fix for player 2. That is not in my custom kernel. If you like, I could compile that in, if no one has done that yet.

EDIT: I actually had some time. Made the code change and compiled. Here is the link.

https://www.dropbox.com/s/yr8ab00crk30nyc/custom_kernel_1.20150306-1.tar.gz?dl=0

Note that I haven’t even tested this at all. Just compiled and uploaded.

[feederchain]

No problem.

Unfortunately (or fortunately) have not had that issue. Did a quick search and the following looks like a thread you may want to follow.

Nothing Shows after exiting EmulationStation

[Author]

Posts