USB Keyboard disabled after exiting Mupen64Plus and ES?
-
Run an N64 Game. Use Start + Select to exit to ES. Exit ES via menu or F4. Now try and type into the terminal, nothing works.
RPI3 - Stock, no OC
5.1V 2.5A Power supply
RetroPie 4.1 (tried Prebuilt, also Updated from Source/Binary)
105 key generic Acer USB Keyboard (set to US in /etc/default/keyboard) and Wired genuine PS3 controller connectedruncommand.log:
Parameters: Executing: /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh mupen64plus-video-GLideN64 "/home/pi/RetroPie/roms/n64/Mario Kart 64 (US).n64" 320x240 Generated a 884 x 18 (15 kb) texture atlas /opt/retropie/emulators/mupen64plus/bin/mupen64plus.sh: line 292: 1039 Segmentation fault SDL_VIDEO_RPI_SCALE_MODE=1 "$rootdir/emulators/mupen64plus/bin/mupen64plus" --noosd --windowed $RES --rsp ${RSP_PLUGIN}.so --gfx ${VIDEO_PLUGIN}.so --audio ${AUDIO_PLUGIN}.so --configdir "$configdir/n64" --datadir "$configdir/n64" "$ROM"
Emulator is mupen64plus-GLideN64
Restarting fixes the problem, however I would not like to do this every time. Any workarounds?
-
Hi there
I face almost the exact same issue !
Only keyboard, no controller
-
Can play on mastersystem with keyboard, exit with start+select... all good
-
Can start stock N64 emulator, but keyboard do not work within the emulator (I read it was a known problem - possibly comming from the ROM)
The only way to exit the N64 emulator is Esc of F4
Once in emulationstation, I can use the keyboard to navigate and exit
Back on the terminal, keyboard is not working but one touch, the tiny 2 bellow Esc
If I unplug and replug the keyboard, Pixel is displayed...
I can then navigate from terminal to pixel with Ctrl + Alt + F1 to F7
RPI3 - Stock, no OC
5.1V 2.5A Power supply
REtroPie 4.2 setup script on top of Raspbian NOOBs installed following this tuto
HP USB wireless keyboard+mouse "Desktop C7000"
Locale set to Fr
No controller -
-
I have the same issue, the keyboard does not respond after I quit Retropie back to the shell whenever I play a N64 game. I had hope that 4.2 would fix the problem. I prefer to kill my bash session from another terminal instead of restarting the Pi.
-
Just gonna jump in with me too. Rebooting using ssh is no big deal but it's a minor annoyance.
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.