Problems recognizing mouse and keyboard with moonlight in recalbox 4.1

[André Alcover Rodrigues]

Thanks for the interest forum colleagues.

I have the latest version of recalbox 4.1 installed on my raspberry pi 3 on which I am successfully using moonlight to play steam games. however I can not use a mouse and a tactile that work well in the recalbox interface.

anyone know how to make moonlight recognize these devices?

[Substring]

@andré-alcover-rodrigues there is an issue in gutlab explaining how to do it. I can't tell if the trick still works

[André Alcover Rodrigues]

I could not find it.
Can you help me with this?

[André Alcover Rodrigues]

@substring I could not find it.
Can you help me with this?

[Substring]

@andré-alcover-rodrigues https://gitlab.com/recalbox/recalbox-configgen/issues/41#note_29018385

[Substring]

@substring this means you must know what you /dev/input/eventX refer to

[André Alcover Rodrigues]

This post is deleted!

[André Alcover Rodrigues]

@substring
Thank you very much for the help, but if you will allow me I would like to abuse your goodwill a little more.

I do not speak a word of English and I get a very bad translation of google, so some questions remain.

First. is it possible to open through the graphical interface moonlight.conf and insert the command lines through the notepad or it will not work?

for me it was not clear what these 2 lines are and nor the correct way to insert them in case it is not possible to access the folders over the network.

Can you tell me more about what these two lines are?

another issue that was not clear is the number of drivers

the final is possible to keep 2 arcade controls and 2 xbox controls working together with keyboard and mouse both in the moonligth and emulators of the recalbox or at some point any of them will fail?

thanks again for the attention and pasciencia with my ignorance.

[Substring]

@andré-alcover-rodrigues I'll try to make it simple.

Linux input devices (= keybooard, mouse pads etc ...) can all be accessed through the /dev/input folder. In that folder you'll notice some files that look like event+ a number behind. All those eventX correspond ton an input device.

The trick is to find which eventX corresponds to your keyboard and mouse. So here are a few things to keep in mind :

• those evenX can change depending on devices plugged. Your keyboard can be event1, and another day, event0
• the evtestcommand will show you which inputs correspond to each eventX. You should try each to make sure you found your keyboard and mouse. Press CTRL+C to quit
• once you found, in the current session, which events are your keyboard and mouse, make a ls -l /dev/input/by-id (I hope it's the right one, no Recalbox at hand for now). You shouls see some lines ending with something like -> ../eventX. This means the files listed are some shortcuts to eventX. The good news is that this part never changes. So in the moonlight.conf, you should add these path (the complete filename without the -> ../eventX)

You can edit the moonlight.conf file with no problem through network as long as you use a Unix compatible text editor. We recommend using Notepad++. Everytime you edit a line, no need to reboot Recalbox, just launch moonlight.

Give a try to my explanations. If you're lost please send me the output of ls -lR /dev/input and i'll help you.

[André Alcover Rodrigues]

@substring

I understood that maybe I have to do this every time I play, however the way to proceed is not very clear, but I executed the command that asked me and I received it back.

ls -lR /dev/input

/dev/input:
total 0
drwxr-xr-x 2 root root 220 Jan 1 1980 by-id
drwxr-xr-x 2 root root 220 Jan 1 1980 by-path
crw-rw---- 1 root input 13, 64 Jan 1 1980 event0
crw-rw---- 1 root input 13, 65 Jan 1 1980 event1
crw-rw---- 1 root input 13, 66 Jan 1 1980 event2
crw-rw---- 1 root input 13, 67 Jan 1 1980 event3
crw-rw---- 1 root input 13, 68 Jan 1 1980 event4
crw-rw---- 1 root input 13, 69 Jan 1 1980 event5
crw-rw---- 1 root input 13, 70 Jan 1 1980 event6
crw-rw---- 1 root input 13, 71 Jan 1 1980 event7
crw-rw-r-- 1 root input 13, 0 Jan 1 1980 js0
crw-rw-r-- 1 root input 13, 1 Jan 1 1980 js1
crw-rw-r-- 1 root input 13, 2 Jan 1 1980 js2
crw-rw-r-- 1 root input 13, 3 Jan 1 1980 js3
crw-rw---- 1 root input 13, 63 Jan 1 1980 mice
crw-rw---- 1 root input 13, 32 Jan 1 1980 mouse0

/dev/input/by-id:
total 0
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-18f8_USB_OPTICAL_MOUSE-event-mouse -> ../event2
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-18f8_USB_OPTICAL_MOUSE-if01-event-kbd -> ../event3
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-18f8_USB_OPTICAL_MOUSE-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-Holtek_Controller_0C214B4-event-joystick -> ../event0
lrwxrwxrwx 1 root root 6 Jan 1 1980 usb-Holtek_Controller_0C214B4-joystick -> ../js0
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-Inno_GamePad.._Inno_GamePad.._0000001-event-joystick -> ../event1
lrwxrwxrwx 1 root root 6 Jan 1 1980 usb-Inno_GamePad.._Inno_GamePad.._0000001-joystick -> ../js1
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-SEMICO_USB_Keyboard-event-kbd -> ../event4
lrwxrwxrwx 1 root root 9 Jan 1 1980 usb-SEMICO_USB_Keyboard-if01-event-kbd -> ../event5

/dev/input/by-path:
total 0
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.2:1.0-event-joystick -> ../event0
lrwxrwxrwx 1 root root 6 Jan 1 1980 platform-3f980000.usb-usb-0:1.2:1.0-joystick -> ../js0
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.3:1.0-event-joystick -> ../event1
lrwxrwxrwx 1 root root 6 Jan 1 1980 platform-3f980000.usb-usb-0:1.3:1.0-joystick -> ../js1
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.4:1.0-event-mouse -> ../event2
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.4:1.0-mouse -> ../mouse0
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.4:1.1-event-kbd -> ../event3
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.5:1.0-event-kbd -> ../event4
lrwxrwxrwx 1 root root 9 Jan 1 1980 platform-3f980000.usb-usb-0:1.5:1.1-event-kbd -> ../event5

[Substring]

@andré-alcover-rodrigues so you have a SEMICO USB keyboard. It has 2 possible events. You should start evtest and test bith to see which one is responding when you're typing on it. Write down its name, and find to which /dev/input/by-id it corresponds to

Next, in the moonlight.conf, simply add that /dev/inout/by-id/blablabla that worked