Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Author
    Posts
  • in reply to: Change order of controllers in Jessie #117212
    monchote
    Participant

    [quote=117199]see this video for reference:[/quote]

    No luck. No matter what port I connect them to, the controllers keep the same order.

    in reply to: Change order of controllers in Jessie #117198
    monchote
    Participant

    [quote=117196]Swap USB ports[/quote]

    I tried this before I start using udev rules but I’ll give it another go.

    in reply to: Forcing controllers to js0, js1 etc #117197
    monchote
    Participant

    [quote=116949]I tried doing what was in here

    http://ubuntuforums.org/showthread.php?t=1595666&p=9974813#post9974813

    Issue is, I don’t get the output he is getting. I tried using any unique identifier I could find from my output but sadly that didn’t work.[/quote]

    Unfortunately those udev renaming rules are no longer supported and won’t work.

    I just opened a similar thread before I saw this one: https://www.petrockblock.com/forums/topic/change-order-of-controllers-in-jessie/

    in reply to: Autofire on the axis #104803
    monchote
    Participant

    [quote=104802]Then i don’t need to install the custom kernwell. I need only to write the line in cmdline.txt to let retropie recognize the xin-mo as 2 controller, right?
    [/quote]

    Correct (for Retropie 3.0 only though).

    in reply to: Autofire on the axis #104541
    monchote
    Participant

    [quote=104538]If we’ve already patched the kernel, should we somehow re-patch to the original kernel? Or would an apt-get update take care of that?[/quote]

    The ‘axis autofire’ and the ‘2-player controller’ issues are separate so as long as you’re not getting autofire, don’t worry about the kernel patch. Adding the string in my previous post to /boot/cmdline.txt should make the Xin-mo be recognised as 2 controllers.

    in reply to: Autofire on the axis #104433
    monchote
    Participant

    I’ve finally had some time to test the Xin-mo dual controller with a fresh installation of RetroPie 3.0 and the autofire on the axis issue no longer exists, so applying the previous patch is not needed anymore. Great news!

    With regards to it not being recognised as 2 controllers, I’ve tested the addition to /boot/cmdline.txt method that @feederchain describes above and it also works with the Xin-mo dual controller. The code to add to the end of the line (after a white space) is:

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

    Reboot required after saving the file.

    Having reached this solution, I’m not going to bother trying to patch the kernel as this fix is simple enough for those of us with the Xin-mo.

    Thanks very much to @feeder for all the help and effort!

    in reply to: Autofire on the axis #104284
    monchote
    Participant

    @feederchain: No worries, I’ll test it out on mine and if it works, I’ll post the patch here for the other people to test it on the 2-player configuration.

    If it fixes both the autofire and 2-player issues, I plan to submit the kernel patch upstream so it works out-of-the-box in the future. If you find the vendor id for your adapter and it works, send it my way and I’ll include it in the patch.

    in reply to: Autofire on the axis #104274
    monchote
    Participant

    @feederchain I’ve been doing some more investigation and I think this patch could be the real fix for both the autofire and the 2-player input.

    The author never submitted the kernel patch upstream and thus it’s still not fixed.

    I won’t have time to compile and test the patch until the weekend so if you happen to do it before then, please let us know!

    in reply to: Autofire on the axis #104193
    monchote
    Participant

    Thanks a lot for double checking and uploading the patch.

    Out of curiosity, couldn’t this be submitted as a pull-request to the RetroPie Github repo so it’s fixed for future releases?

    in reply to: Autofire on the axis #103998
    monchote
    Participant

    Does anybody know whether this is fixed in 3.0?

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