Forum Replies Created
feederchainParticipant03/30/2016 at 03:00Post count: 83
I’d have to go back and look at what others have for that controller. I actually don’t have it. I’m surprised to not see a listing for it from lsusb. I don’t think there is a need to update the kernel for you.
I personally wouldn’t bother with permissions. Just pull the sd card and pop it in another computer and update the cmdline.txt on that. Always been the easiest for me.feederchainParticipant03/30/2016 at 02:32Post count: 83
@janmilpol… That sounds familiar. I seem to recall someone earlier in this thread mentioning it worked for them. Although, now I don’t think the custom kernel is needed. It’s only the cmdline.txt that needs to be done for those controllers.
@sduckie2…. I don’t see a controller listed there… Or at least none jump out at me as being a controller. That ID you see there is what would need to be added to cmdline.txtfeederchainParticipant03/23/2016 at 19:14Post count: 83feederchainParticipant03/23/2016 at 01:11Post count: 83
OK, I’ve done a bit of research and it appears that the v2/v3 kernel should be the same. Bare with me… I didn’t do a whole bunch of research. Anyway… I don’t have a way of testing this because I don’t have a Piv3. But here’s the new link.
Is someone willing to give this a test?
ThanksfeederchainParticipant03/22/2016 at 17:15Post count: 83feederchainParticipant03/21/2016 at 15:20Post count: 83feederchainParticipant03/06/2016 at 19:44Post count: 83feederchainParticipant03/03/2016 at 03:02Post count: 83
OK, I just installed v3.6 and installed the latest custom kernel I have and I didn’t see any issues with the right and down directions.feederchainParticipant03/02/2016 at 19:36Post count: 83feederchainParticipant02/22/2016 at 02:19Post count: 83feederchainParticipant02/09/2016 at 18:21Post count: 83feederchainParticipant01/28/2016 at 05:33Post count: 83
OK, github fixed whatever problem they were having so i was able to get a new compile done.
Note: It’s getting late here, so I didn’t get a chance to test this kernel at all. So use at your own risk. If you want to wait until I have a chance to try it on my testbed Pi. Hopefully I can get a chance tomorrow.feederchainParticipant01/28/2016 at 02:41Post count: 83feederchainParticipant01/28/2016 at 02:36Post count: 83feederchainParticipant01/12/2016 at 16:56Post count: 83
Yep, just run lsusb at the command prompt once you drop out of emulation station. I’m not near my pi right now so I can’t give you an example of the output, but wade back through this thread> I’m pretty sure there is more information in one of my posts about it. When I had to find my vendor id.feederchainParticipant01/11/2016 at 19:33Post count: 83feederchainParticipant12/26/2015 at 17:52Post count: 83
@bigjohnnz. So you used the command mentioned early to find your vendor id?
@amaar221. You are the first person that I recall having that issue. The last kernel I created is getting old. I have not bothered in a while to upgrade my Pi. So maybe there are issues with the latest updates and the older kernel. That doesn’t sound too likely though. Did the kernel install without errors? The commands, for the vendor id, were mentioned earlier. But I’ll paste them here
You can find the vendor/product using
returned this for me
Bus 001 Device 005: ID 1292:4745 Innomedia
That all being said. It looks like p4r4d0x86 may have a fix if the quirks aren’t being recognized.feederchainParticipant12/21/2015 at 13:52Post count: 83feederchainParticipant12/17/2015 at 02:17Post count: 83
You are probably clicking on an old link.
Note that this is still a pretty old kernel. I haven’t needed to do a newer version.
Hope it helps.feederchainParticipant11/14/2015 at 18:14Post count: 83
RetroPie currently now shares the configs over a windows (samba) share. So if you look up \\RASPBERRYPI in windows explorer, you should be able to make the changes needed by looking for the mame directory.
I’m not near my Pi right now, so I’m just going by memory right now.feederchainParticipant10/29/2015 at 04:51Post count: 83
So that sounds like when you run jstest on js0, you are seeing all buttons from controller one and two there?
If the quirk had worked you should be seeing controller one’s buttons on js0 and controller two’s on js1. If they are all on the same then it’s not being picked up. Which seems odd to me.
I was hoping to take emulationstation out of the equation while using jstest.
Oh… I think I see why it’s not working
usbhid.quirks=0x16c0:0x05e1:0x040 <— correct
usbhid.quirks=0x16c0:0x05el:0x040 <— what you pasted
the top one is “five e one”feederchainParticipant10/29/2015 at 03:40Post count: 83
Have you tried to see if the second joystick is picked up by jstest? I seem to recall that if I ran emulationstation and setup the controllers. It never told me again how many gamepads were detected. unless I connected a completely different device. I could be remembering incorrectly though.
When you added the quirk to the end of cmdline.txt. It was at the end of the single line. Correct? You can’t create a new line.feederchainParticipant10/23/2015 at 06:16Post count: 83feederchainParticipant10/22/2015 at 01:59Post count: 83
@gaus, I’m using a Genesis USB adapter made by Retrobit (or RetroLink?) and this was the reason I needed to create the kernel. So it wouldn’t surprise me if it did work.
The latest I compiled is here
I know there are some saying that the kernel isn’t up on dropbox anymore, but they must just be clicking on the first one I created.
As you can see from the date, I haven’t bothered updating the kernel in a long time. So when running apt-get after installing, the kernel will probably get overwritten with the latest and not work anymore.
If there is a need for a newer version, I will try and make time to compile up another one.feederchainParticipant10/10/2015 at 09:25Post count: 83
If you don’t want to change the wiring. You could probably tell retropie to use the opposite using the config file. There are examples of button mappings in this thread. All you should need to do is swap the index value.
As for the n64 problems. Sorry I can’t be of much help. I’ve never used that emulator.feederchainParticipant10/10/2015 at 04:15Post count: 83feederchainParticipant10/09/2015 at 16:16Post count: 83
It may be just that simple. Have you tried checking the controllers with jstest?
Drop out of emulationstation and run
That should show you the buttons on joystick 1. In your case I guess you should check js1 or js2 since the ps3 is on 0.feederchainParticipant10/09/2015 at 06:41Post count: 83
@enigma90 Quotes or no quotes. It doesn’t matter. As for the button map. You’ll have to check back in this thread to find what others have used. I find it odd that player 1 is mapped to index 1 and 2 is mapped to 0. That would probably swap them around. Also it’s odd that the button numbers don’t match between player 1 and 2. You can use jstest as a way to check which button does what.
@luckylocky Is you button mapping swapped? As in player 1 index is mapped to 1 and player 2 is mapped to 0. Or is it wired up wrong? There is references earlier to using jstest to check the buttons. You could use the that to see if it’s just the emulators that are seeing you controllers wrong or not.feederchainParticipant09/11/2015 at 15:33Post count: 83
@stephane… That doesn’t quite feel like the same issue that I had happening. I was experiencing more of a pulsing. As in the direction would flip on and off.
Have you tried the latest kernel compile in this thread?feederchainParticipant09/11/2015 at 04:13Post count: 83feederchainParticipant08/20/2015 at 04:12Post count: 83
OK… so monchote…. you sparked something in my brain with your talk of quirks. Or at least that patch you referenced.
While I has dealing with this months ago I remembered reading something about adding a quirk on boot. But I didn’t get it to work. Looking back now, it’s because I didn’t know what I was really doing then.
Anyway… So I figured out my vendor/product ids 1292/4745.
Which is when the spark happened. So you are allowed to add the following to the end of /boot/cmdline.txt
The first two numbers are my vendor/product. The third is the quirk. Found here http://lxr.free-electrons.com/source/include/linux/hid.h#L313
So the 40 is for multi input.
So with my kernel and this above. I was seeing two controllers and they both worked.
You can find the vendor/product using
returned this for me
Bus 001 Device 005: ID 1292:4745 Innomedia
So the next logical step was to try and use HID_QUIRK_NOGET with a virgin kernel and see if the directionals work. Replaced the 40 with the 8.
Unfortunately that didn’t work for me.
Hopefully for you compiling in the quirk will help.feederchainParticipant08/19/2015 at 18:12Post count: 83feederchainParticipant08/19/2015 at 15:50Post count: 83
@hijinksensue… It’s true that they did make it so that the controller setup in 3.0 would also go to retroarch. My assumption is that they would just be writing that button mapping into the retroarch.cfg. I didn’t confirm that. I assumed that I was still going to have the issue with both controllers on the same joystick port. So one of the first things I did was replace retroarch.cfg.
@monchote… I’ve run into a couple quirks earlier that reported to fix the multi input of my adapter, but they never worked. I’ve never seen the NOGET one mentioned before. I’ll have to look into this.
That being said. This looks specific to the Xin Mo. I’ll have to figure out the vendor id for my adapter. As it is that patch won’t do me any good. I’m not using that controller.feederchainParticipant08/19/2015 at 04:12Post count: 83
@monchote… The directional fix, as I understand it, is that the device not really behaving properly. The kernel is filtering out these out of bound inputs. The patch here just stops that filtering. I may have read wrong information in the past, but when I was first searching for this problem I recall that being an issue. I don’t know if it causes issues with other devices. That could be the reason why it hasn’t gone into anything. I’d have to double check but I’m pretty sure it’s the same issue in other distros not related to the raspberry pi.
@hijinksensue… Ya this never fixed the device being seen as two separate joysticks. I didn’t try and get the second controller to work in emulation station itself. I don’t need the second controller working there. As for RetroPie itself. I keep a backup of my retroarch.cfg. So I just put that one into the config/all directory that was samba shared for me. That worked without a hitch.feederchainParticipant08/18/2015 at 05:00Post count: 83
OK, had a chance to just compile the one change to hid-input.c (2 directions to working) and install it on my fresh install of v3.0. It all appears to work fine. Well at least the controller was recognized and setup fine in emulationstation. I only setup the first joystick. Didn’t setup the second.
Anyway here is the dropbox link.
Same install instructions.