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

    Mouse not working in lr-mame2003

    Scheduled Pinned Locked Moved Help and Support
    mousemame2003
    54 Posts 8 Posters 8.8k Views
    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.
    • OliBO
      OliB
      last edited by

      Maybe this might helps

      under:
      opt/retropie/configs/all/
      edit
      retroarch-core-options.cfg

      insert:
      mame2003-mame_current_mouse_enable = "enabled"

      Also the same line for mame2010 and so on....

      1 Reply Last reply Reply Quote 0
      • A
        albecacif
        last edited by

        @Frogger1108 said in Mouse not working in lr-mame2003:

        [ERROR] [udev] Failed to open device: /dev/input/event1 (Success).

        Hi,
        I still get the same error:

        [ERROR] [udev] Failed to open device: /dev/input/event1 (Success).

        I tried the evtest command and I get input when I move either the mouse or the trackball.

        I also tried with an old image that I had with RP 4.2 and Retroarch 1.6.7. And the trackball works fine with MAME2003 there. Then I upgraded the Retroarch Version to 1.7.X and it stopped working with the same error.

        Seems that there is some kind of problem with the 1.7.x RA with mouses and trackball.
        thanks

        1 Reply Last reply Reply Quote 0
        • G
          grant2258 Banned
          last edited by

          download retroarch for windows or linux and try your mouse and trackball there. If it still doesnt work its a RA issue else its a retropie issue

          1 Reply Last reply Reply Quote 0
          • H
            hhromic
            last edited by

            there is another user having the exact same issue for NES cores (fceumm and nestopia tested) here: https://retropie.org.uk/forum/topic/20004/mouse-as-a-zapper-lr-fceumm-rpi-3-b/

            The error reported [ERROR] [udev] Failed to open device: /dev/input/event1 (Success). is indeed very indicative of a programming bug in RA's input system error handling.
            Further debugging is required at RA's level if anyone has the experience/time :) And report back to RA's maintainers.

            1 Reply Last reply Reply Quote 0
            • G
              grant2258 Banned
              last edited by grant2258

              im betting its permissions not being set right issue this command

               sudo usermod -a -G input `whoami`

              reboot and try ( i dont think a reboot is requiredjust on the off chance)

               ls -al /dev/input/
total 0
drwxr-xr-x   4 root root     140 Dec  9 18:35 .
drwxr-xr-x  14 root root    3300 Dec  9 18:35 ..
drwxr-xr-x   2 root root      80 Dec  9 18:35 by-id
drwxr-xr-x   2 root root      80 Dec  9 18:35 by-path
crw-rw----+  1 root input 13, 64 Dec  9 18:35 event0
crw-rw----+  1 root input 13,  0 Dec  9 18:35 js0
crw-rw----   1 root input 13, 63 Dec  9 18:35 mice
              H 1 Reply Last reply Reply Quote 1
              • H
                hhromic @grant2258
                last edited by

                @grant2258 ah good idea! in the other thread I asked the user to check the input devices FILE permissions, and they seemed right.. but didn't think that the current user might not be in the input group. If that is the case then it would be simply a matter of adding the user to the input group. Let's see!

                And yes a reboot is not necessary, just re-login the session.

                1 Reply Last reply Reply Quote 0
                • G
                  grant2258 Banned
                  last edited by grant2258

                  i figured saying reboot would be quicker than explaining to a new user to login again either way will work. I didnt even check i just checked my command syntax before posting so I dont know if this is set by default

                  H 1 Reply Last reply Reply Quote 0
                  • H
                    hhromic @grant2258
                    last edited by

                    @grant2258 in some older Stretch images I think the input group was forgotten to be set by default, but in recent releases this is corrected and works out of the box. I have installed various stretch images in recent months and they all come with the user correctly configured.

                    Let's see if the user manages to fix the problem with your suggestion, that would be great news for the other guy on the other thread.

                    1 Reply Last reply Reply Quote 0
                    • G
                      grant2258 Banned
                      last edited by

                      well i just checked my standard stretch x64 install the input group isint added there i think this probably is the issue people have been having the good thing is if it is this its so easily fixed on the updated script

                      H 1 Reply Last reply Reply Quote 0
                      • H
                        hhromic @grant2258
                        last edited by

                        @grant2258 sorry, I meant Raspbian Stretch for the RPI :)

                        1 Reply Last reply Reply Quote 0
                        • G
                          grant2258 Banned
                          last edited by

                          ill install a fresh image rpi and check

                          H 1 Reply Last reply Reply Quote 0
                          • H
                            hhromic @grant2258
                            last edited by

                            @grant2258 sure, but no need to install anything, as I said, in recent images it comes correctly configured: https://github.com/RPi-Distro/pi-gen/blob/master/stage2/01-sys-tweaks/01-run.sh#L39

                            1 Reply Last reply Reply Quote 0
                            • H
                              hhromic
                              last edited by

                              @grant2258 .. but on a second thought, the report said:

                              I also tried with an old image that I had with RP 4.2 and Retroarch 1.6.7. And the trackball works fine with MAME2003 there. Then I upgraded the Retroarch Version to 1.7.X and it stopped working with the same error.
                              Seems that there is some kind of problem with the 1.7.x RA with mouses and trackball.
                              thanks

                              If the user is not in the input group, the older RA should also have failed. Anyway let's wait for the feedback, your suggestion still makes a lot of sense.

                              1 Reply Last reply Reply Quote 0
                              • G
                                grant2258 Banned
                                last edited by

                                not necessarily the older ra could have used linuxraw as the input driver. I guess we can just wait for feedback. I would suggest a reboot though as emulation station is already running

                                H 1 Reply Last reply Reply Quote 0
                                • H
                                  hhromic @grant2258
                                  last edited by

                                  @grant2258 yes agreed, a reboot would be a definitive approach

                                  1 Reply Last reply Reply Quote 0
                                  • A
                                    albecacif
                                    last edited by

                                    @grant2258 said in Mouse not working in lr-mame2003:

                                    ls -al /dev/input/

                                    Hi,

                                    I changed the user´s persmissions:

                                    pi@retropie:~ $ ls -al /dev/input/
                                    total 0
                                    drwxr-xr-x 4 root root 240 Dec 11 17:24 .
                                    drwxr-xr-x 15 root root 3420 Dec 11 17:24 ..
                                    drwxr-xr-x 2 root root 140 Dec 11 17:24 by-id
                                    drwxr-xr-x 2 root root 140 Dec 11 17:24 by-path
                                    crw-rw---- 1 root input 13, 64 Dec 11 17:24 event0
                                    crw-rw---- 1 root input 13, 65 Dec 11 17:24 event1
                                    crw-rw---- 1 root input 13, 66 Dec 11 17:24 event2
                                    crw-rw----+ 1 root input 13, 67 Dec 11 17:24 event3
                                    crw-rw----+ 1 root input 13, 0 Dec 11 17:24 js0
                                    crw-rw---- 1 root input 13, 63 Dec 11 17:24 mice
                                    crw-rw---- 1 root input 13, 32 Dec 11 17:24 mouse0
                                    crw-rw---- 1 root input 13, 33 Dec 11 17:24 mouse1

                                    But still the same failure :(

                                    INFO] [udev]: Keyboard #0 (/dev/input/event0).
                                    [INFO] [udev]: Keyboard #1 (/dev/input/event2).
                                    [INFO] [udev]: Keyboard #2 (/dev/input/mouse1).
                                    [ERROR] [udev] Failed to open device: /dev/input/event1 (Success).
                                    [INFO] [udev]: Mouse #0 (/dev/input/mouse0).
                                    [ERROR] [udev] Failed to open device: /dev/input/event2 (Success).
                                    [INFO] [udev]: Mouse #1 (/dev/input/mouse1).
                                    [INFO] [udev]: Plugged pad: 8Bitdo NES30 Arcade (0:0) on port #0.
                                    [INFO] [udev]: Pad #0 (/dev/input/event3) supports 0 force feedback effects.

                                    H 1 Reply Last reply Reply Quote 0
                                    • H
                                      hhromic @albecacif
                                      last edited by

                                      @albecacif just to confirm, can you execute groups ? this should show you all the groups the user belongs to. Did you reboot right?

                                      1 Reply Last reply Reply Quote 0
                                      • A
                                        albecacif
                                        last edited by

                                        pi@retropie:~ $ groups
                                        pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi

                                        Yes, I rebooted the system

                                        1 Reply Last reply Reply Quote 0
                                        • G
                                          grant2258 Banned
                                          last edited by grant2258

                                          can you the output of

                                           ls -al /dev/input/by-path/

                                          and

                                          ls -al /dev/input/by-id/
                                          1 Reply Last reply Reply Quote 0
                                          • A
                                            albecacif
                                            last edited by

                                            @grant2258 said in Mouse not working in lr-mame2003:

                                            ls -al /dev/input/by-path/
                                            pi@retropie:~ $ ls -al /dev/input/by-path/
                                            total 0
                                            drwxr-xr-x 2 root root 140 Dec 11 17:54 .
                                            drwxr-xr-x 4 root root 200 Dec 11 17:54 ..
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 platform-3f980000.usb-usb-0:1.2:1.0-event-kbd -> ../event0
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 platform-3f980000.usb-usb-0:1.2:1.1-event-mouse -> ../event1
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 platform-3f980000.usb-usb-0:1.2:1.1-mouse -> ../mouse0
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 platform-3f980000.usb-usb-0:1.4:1.2-event-mouse -> ../event2
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 platform-3f980000.usb-usb-0:1.4:1.2-mouse -> ../mouse1

                                            pi@retropie:~ $ ls -al /dev/input/by-id/
                                            total 0
                                            drwxr-xr-x 2 root root 140 Dec 11 17:54 .
                                            drwxr-xr-x 4 root root 200 Dec 11 17:54 ..
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 usb-13ba_Barcode_Reader-event-kbd -> ../event0
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 usb-13ba_Barcode_Reader-if01-event-mouse -> ../event1
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 usb-13ba_Barcode_Reader-if01-mouse -> ../mouse0
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 usb-Logitech_USB_Receiver-if02-event-mouse -> ../event2
                                            lrwxrwxrwx 1 root root 9 Dec 11 17:54 usb-Logitech_USB_Receiver-if02-mouse -> ../mouse1

                                            Note that I have a keyboard with an integrated pad (mouse) and the USB trackball connected

                                            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.