RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Retropie recognizes only one controller with the "USB Twin pad" adapter

    Scheduled Pinned Locked Moved
    Help and Support
    usb controller retropie
    2
    8
    330
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • B
      bethory
      last edited by

      Hello dear community, I hope you can help me with this:

      I have a PS1 to USB controller adapter (USB TWIN PAD) that works perfectly in windows showing me the two controllers independently, however in Retropie it only recognizes one controller.
      Searching in the forum I found that Xin-Mo could be the solution however this did not work, I would like to know if there is another solution or should I keep insisting on the Xin-Mo method?

      Here is the information of my system:

      • Pi Model or other hardware: raspberry pi model b+ v1.2
      • Power Supply used: Canakit 5V ~2.5A
      • RetroPie Version: v4.8
      • Built From: Pre made SD Image on RetroPie
      • USB Devices connected: USB TWIN PAD, logitech unifying receiver
      • Controller used: Simmilar to this adapter with two PS1 controllers
      • Error messages received: None
      • Verbose log: N/A
      • Guide used: https://retropie.org.uk/docs/Xin-Mo-Controller/
      • File: N/A
      • Emulator: all of them
      • How to replicate the problem: It seems that the error happens with all USB to two controllers adapters

      Thanks in advance for your help!

      mituM 1 Reply Last reply Reply Quote 0
      • mituM
        mitu Global Moderator @bethory
        last edited by

        Searching in the forum I found that Xin-Mo could be the solution however this did not work...

        What exactly have you tried ? Did you apply the same quirks or did you add the VID/PID for your device to the quirks command ?

        How to replicate the problem: It seems that the error happens with all USB to two controllers adapters

        No, that's not it.
        I have a few 'classic-to-USB' adapters (none for PS1 though) and they don't behave like that. Do you have a vendor page for the adapter or does the vendor has Linux support specified on their site/documentation ?

        B 1 Reply Last reply Reply Quote 0
        • B
          bethory @mitu
          last edited by bethory

          Hello @mitu, thanks for your response.

          I created the file rp-usbhid-quirks.conf using the command sudo nano /etc/modprobe.d/rp-usbhid-quirks.conf and inside I wrote only the following information:
          usbhid.quirks=0x05e3:0x1065:0x040
          (I checked that the information was saved by re-running sudo nano...)

          Internally I put the VendorID and ProductID obtained with lsusb (I know it's correct because it's the only one that appears when plugging the USB adapter).

          Finally I restarted the Rpi but when entering the controllers configuration menu it still shows only one detected controller.

          No I don't have the vendor page, or any more information. I think it is a very generic product.

          mituM 1 Reply Last reply Reply Quote 0
          • mituM
            mitu Global Moderator @bethory
            last edited by

            @bethory said in Retropie recognizes only one controller with the "USB Twin pad" adapter:

            I created the file rp-usbhid-quirks.conf using the command sudo nano /etc/modprobe.d/rp-usbhid-quirks.conf and inside I wrote only the following information:
            usbhid.quirks=0x05e3:0x1065:0x040

            That's not what the file should contain. You use the usbid.quirks=... syntax if you add the info to cmdline.txt, for the modprobe configuration file the syntax is different (as explain the doc page):

            options usbhid quirks=0x05e3:0x1065:0x040
            B 1 Reply Last reply Reply Quote 0
            • B
              bethory @mitu
              last edited by

              Hello @mitu

              Sorry I made a mistake in writing this article, I assure you that the .conf file was set to options usbhid quirks=0x05e3:0x1065:0x040.

              and as I indicated, it still does not work

              Thanks in advance for your help

              mituM 1 Reply Last reply Reply Quote 0
              • mituM
                mitu Global Moderator @bethory
                last edited by

                @bethory I don't have any other ideas - the quirks are the only thing that sprung to mind when having this issue.

                B 2 Replies Last reply Reply Quote 0
                • B
                  bethory @mitu
                  last edited by

                  Hello @mitu, thank you for your help

                  I will try modifing /boot/cmdline.txt as soon as i can, I'll let you know.

                  1 Reply Last reply Reply Quote 0
                  • B
                    bethory @mitu
                    last edited by

                    Hello @mitu

                    As i promised, I modify the /boot/cmdline.txt file from windows and it worked!

                    Thank you for your support

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post

                    Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

                    Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.