Holy sh...! It's alive again! I cannot pin the reason down though, but I'm certain it was something I made wrong again and again. Maybe sth. to do with the windows ssh shell (didn't want to set putty up because I find that confusing). Anyway, thanks so much for guiding me through. :)

@rustymg I think select alone make the main device switch between mouse and joystick, maybe only when virtual keyboard is up

yes, if you are on a gpi case, it's only compatible with pi0

@paradadf said in the keyboard is not working!:

spacebar doesn’t work? And the letters which are in the place of A and S in a QUERTY keyboard?

Space, enter, cursor keys work. A,S - no. Keyboard QWERTY.
P.S. Sorry - features of machine translation:)

Well, I've now a general procedure to get Recalbox running on a Pimoroni Picade.
Because I think this could be a valueable information, I decided to finish this thread and to open a new and fresh one. So nobody has to read through all the posts in this thread to come to the solution.

@rk-aus-s

Ich kenne mich damit leider nicht gut aus.
Falls du noch einen Controller hast, verbinde ihn.
Und versuche damit "ok" auszulösen.
Oder mit dem Smartphone z.B. (http://recalbox oder http://recalbox.local)
Dort kann du den virtuellen Controller nutzen.

@kooper
Illegal stuff.

@sziszee it's recalbox, not retropie, you must configure your joysticks in EmulationStation, not retroarch

@aarenj

Have you tried this ?

https://forum.recalbox.com/topic/13906/update-18-04-2018-x86-x86_64-sound-problem

@Substring je comprend totalement.
La partie matériel est prévu, je vais en fabriquer une autre plus grande avec un teensy.

Je vais quand même chercher une astuce ou deux pour jouer sur cette game boy.

Pour la partie codage, je vais pas te mentir, ça ne m'a jamais vraiment attiré mais si je n'ai pas le choix, je m'y pencherais.

Merci en tout cas pour ton aide, si je trouve des truc, je les mettrais ici.

@dragu if you were looking for a CM3 project, here is one !

@stresstester hmmm if I remember well, Doom should run well on dosbox, maybe you have to tweak the con fil

@abunille Going to try this later today hopefully! Thank you so much.

For me keyboard was working well until i did upgrade to the latest updates that stoped working...

@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