Mouse not working in lr-mame2003

hhromic

@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.

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

hhromic

@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.

grant2258

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

hhromic

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

grant2258

ill install a fresh image rpi and check

hhromic

@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

hhromic

@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.

grant2258

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

hhromic

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

albecacif

@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.

hhromic

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

albecacif

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

Yes, I rebooted the system

grant2258

can you the output of

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

and

ls -al /dev/input/by-id/

albecacif

@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

grant2258

is your Logitech working when you select mouse index 1 in RA?

albecacif

No, I´ve just set it in RA and is not responding

grant2258

i can tell you mouse is working fine in ra in my windows machine will need to plug a mouse and keyboard in my pi and see if it works there

albecacif

The keyboard is working fine. Only the mouse fails.

grant2258

i was asking because of this in your log

[INFO] [udev]: Keyboard #0 (/dev/input/event0).
[INFO] [udev]: Keyboard #1 (/dev/input/event2).
[INFO] [udev]: Keyboard #2 (/dev/input/mouse1).