Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Author
    Posts
  • dudesdude
    Participant

    I had a very similar issue and this is how I overcame it so hopefully it helps you too.

    What I did was I entered the Retroarch GUI.

    I went to settings, input, and then USER one settings. I mapped my controls the way I wanted them and did the same for user 2 and the hot keys.

    I then backed out into the intro menu for the Retroarch GUI. I went down to save new configuration.

    I saved the new configuration and ssh from my laptop into my pi.

    I went to the research.cfg and the retroarch.cfg.bad files and removed them both and renamed the newly saved configuration as retroarch.cfg and retroarch.cfg.bak

    I rebooted the pi.

    Low and behold it all worked.

    If you try and do it for a specific game, hit f1 on your keyboard right before the game loads.

    So, after selecting a game in your menu, hit f1 and the retroarch configuration will come up and you be able to map controls for that game specifically .

    dudesdude
    Participant

    I fixed my issue.

    For anyone else who uses a Pi 3 or Retropie 3.6 here is how to make both gamepads be detected.

    Go to sudo nano /boot/cmdline.txt.

    Do exactly what DuckClimber says in his usbquirks post.

    So, go to the end of the first line, hit the spacebar after the last word in the first line.

    Paste this usbhid.quirks=0x16c0:0x05e1:0x040

    Warning: Your usbid may be different.

    Use lsusb to check.

    From here if you already configured a gamepad (I did in my case so the config menu was not coming back up in emulationstation) delete this file.

    This is the command exactly.

    sudo rm /home/pi/.emulationstation/es_input.cfg

    Reboot.

    In the commandline type reboot

    Now when you reboot you should have the configuration menu come up and two game pads should be detected.

    If you ever need to check your joysticks, install this.

    sudo apt-get install joystick

    Then to test your joysticks, do this.

    jstest /dev/input/js0

    and

    jstest /dev/input/js1

    Results will be something like this.

    Axes: 0: 0 1: 0: Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off

    dudesdude
    Participant

    Hello DuckClimber!

    I am using a Raspberry Pi 3 and RetroPie 3.6 with the Xin Mo Board. I tried the Kernel fix last night, but I forgot that didn’t support the Pi 3 because it wasnt out yet. This resulted in a brick system haha.

    dudesdude
    Participant

    I need your help, I tried figuring out which usb was which.

    When I type lsusb I get:

    Bus 001 Device 005: ID 04f3:0103 Elan Microelectronics Corp. ActiveJet K-2024 Multimedia Keyboard
    Bus 001 Device 004: ID 16c0:05e1 Van Ooijen Technische Informatica Free shared USB VID/PID pair for CDC devices
    Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter
    Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp.
    Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

    I have a hunch my xin mo is:
    Bus 001 Device 004: ID 16c0:05e1 Van Ooijen Technische Informatica Free shared USB VID/PID pair for CDC devices

    When I tried the usbquirk method, nothing changed.

    EDIT: Something did change, my buttons act like there is nothing assigned to them now.

    dudesdude
    Participant

    [quote=121277]

    Got mine to work with Raspberry pi 3!

    Kernel wasn’t needed, just added the usbquirks line. Make sure your device ID is correct! Mine wasn’t the same as what is listed under the instructions with the usbquirks step. 0314:0326 instead. Sub-in whats listed when you run lsusb. rebooted and emulation station picked up two players. Configured in mame4all with use of xbox 360 controllers for players 3 and 4, works great. Works in retroarch as well.

    You are awesome! Thank you so much for sharing that! I’ll try it as soon as I get home.

    [/quote]

    Out of curiosity what was the USB labeled as? I have five listings that show up on lsusb and none of them look like they would belong to the xin mo haha.

    I tried lsusb -t and I have sorting out to do.

    I just ssh’d in from my computer and removed my usbs to figure it out.

    dudesdude
    Participant

    [quote=121275]Got mine to work with Raspberry pi 3!

    Kernel wasn’t needed, just added the usbquirks line. Make sure your device ID is correct! Mine wasn’t the same as what is listed under the instructions with the usbquirks step. 0314:0326 instead. Sub-in whats listed when you run lsusb. rebooted and emulation station picked up two players. Configured in mame4all with use of xbox 360 controllers for players 3 and 4, works great. Works in retroarch as well.

    [/quote]

    You are awesome! Thank you so much for sharing that! I’ll try it as soon as I get home.

    dudesdude
    Participant

    [quote=121027]I tried the kernel with a raspberry Pi 3 and retropie 3.6….rainbow screen of death on reboot. Don’t repeat my mistake! Hopefully a new kernel comes our way soon :) thanks to everyone who works on this stuff so we can enjoy!

    [/quote]

    Hey, I also have Pi 3. I tried the kernel on mine last night. This is before I read what happened with your results or I wouldn’t have tried it haha. I had the same results, rainbow screen of death on reboot and every boot after that. I spent all night wiping my SD card, downloading Raspbian, installing Raspbian, downloading and installing RetroPie on spotty internet to get back to where I was haha.I should have realized that the Kernel probably wasn’t going to work on the Pi 3, but I was desperate. I have tried everything else up to that point and I just wanted it to work.

    I’ll update my post if I find anything out.

Viewing 7 posts - 1 through 7 (of 7 total)