Launching ROM sends me back to ROM list

retrogamer0897

Hello,

I'm new to the Raspberry Pi community, however I do have some Linux experience which is helping me to learn quicker on Raspberry Pi.

I've worked out some other issues I had earlier, but I've been experiencing an issue with loading roms. I've experienced this with multiple systems so far, but when I try to launch a rom, the screen goes black and fades back to the rom list.

I've seen this so far with Gameboy and Gameboy Color, Sega Master System, Playstation, and Intellivision. While I don't expect the problem for all of them to be the same, I just wanted to find out if there is something I can do, or a log I can check to see what may have caused the problem. Some are roms that I know work for sure with other emulators.

It seems like games such as Gameboy should pretty much not have any problems, since they're so basic.

I did try resetting the permissions on the rom folders via the option in RetroPie Setup, but this did not solve the problem.

Any suggestions are much appreciated, as I don't want to tinker around too much and make my system stop booting!

Thank you!

Pi Model: Pi 3 - Model B
RetroPie Version Used: 4.1
Built From: Pre-made image on official RetroPie website
USB Devices connected: None, Bluetooth PS3 controller
Controller used: PS3 Controller
Error messages received: No errors
Log found in /dev/shm/runcommand.log (if relevant): N/A
Guide used: N/A
File: /home/pi/RetroPie/roms/NAME_OF_SYSTEM/ROM_Files
Emulator: Gambatte for Gameboy, PicoDrive for SMS, PCSX ReArmed for PSX, Jzintv for Intellivision
Attachment of config files: Need assistance with finding these config files
How to replicate the problem: Select ROM from the menu of any system specified above, the screen fades to black as if it is loading the rom, then the rom list appears again.

BuZz

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

retrogamer0897

Thank you, I have updated my post.

overlord73978

Having the same issue over here, specifically with mame4all.

This is in /dev/shm/runcommand.log when launched with verbose logging

/opt/retropie/supplementary/runcommand/runcommand.sh: line 941:  1928 Bus error               /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-imame4all/mame2000_libretro.so --config /opt/retropie/configs/mame-mame4all/retroarch.cfg "/home/pi/RetroPie/roms/mame-mame4all/DKONG.ZIP" --verbose --appendconfig /dev/shm/retroarch.cfg

The bus error points to this in runncommand.sh

 eval $COMMAND </dev/tty &>>"$LOG"

So it seems something is trying to use /dev/tty but cant?

rbaker

@overlord73978 What romset are you using with Mame4all?

BuZz

@retrogamer0897 I will need to see the contents of /dev/shm/runcommand.log after a rom fails to launch. Please launch in "Verbose mode", by entering the runcommand menu before the rom loads https://github.com/retropie/retropie-setup/wiki/runcommand and choosing the option to Launch with verbose logging.

then using sftp copy the log at /dev/shm/runcommand.log off and post it on a pastebin site or similar.

BuZz

@overlord73978 You should start a new thread - your issue is likely unrelated. Also we need more information a mentioned clearly in https://retropie.org.uk/forum/topic/3/read-this-first

retrogamer0897

Thank you for those instructions! This is what I was looking for, some type of failure log to give me an idea of what the issue is.

I was able to resolve it! I found that some of my rom files had a space before the extension.

For example, Super Mario .nes instead of Super Mario.nes. This was due to a mass rename I did.

I corrected the file names and magically everything works the way it should. Thank you for your help! I'm going to hold onto those instructions as that's really useful.

The Playstation games might be a different story, but just knowing how to get a hold of the logs is really what I needed.

Thanks again.

overlord73978

@rbaker How would I find that info?

rbaker

@overlord73978 You should have downloaded a complete set of roms that is labelled accordingly. For Mame4All you need roms from the 0.37b5 set. I am guessing that because you don't know, you just downloaded a few random roms and tried to launch them in a mame emulator? A common mistake and the path to great frustration. MAME requires patience and an accurate set of roms that match the emulator of your choice. You can verify the roms you have using clrmamepro. The best way to use MAME in an "enjoyable" way currently is to first choose an emulator - lr-mame2003 - then find a set of roms that is compatible with it, i.e. the 0.78 romset. Before proceeding, you should read this very carefully as it will demolish any confusion you may have......
https://retropie.org.uk/forum/topic/2859/how-to-use-mame-with-retropie-help-guide