Boot to rom using lr-mame2003-plus

mahoneyt944

@grant2258 ok I added the sudo -u pi part and was able to boot into verbose logging heres the file with error: https://pastebin.com/Jn7782aU
still didn't boot with sudo command added.

grant2258

do you have a extra newline somewhere ?

Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003-plus/mame2003_plus_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/tron2.zip
" --verbose --appendconfig /dev/shm/retroarch.cfg

grant2258

try

sudo -u pi -- /opt/retropie/supplementary/runcommand/runcommand.sh 0 SYS arcade /home/pi/RetroPie/roms/arcade/cclimber.zip

mahoneyt944

@grant2258 I tried

sudo -u pi -- /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade /home/pi/RetroPie/roms/arcade/tron2.zip

and

sudo -u pi /opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade /home/pi/RetroPie/roms/arcade/tron2.zip

in my autostart file neither work....

mitu

@mahoneyt944 the (1st) log file you posted doesn't show an error, except this one:

[libretro ERROR] cpunum_get_localtime() called for invalid cpu num!

which I don't know if it's fatal (the ROMs seem to load fine), but doesn't look like there's any other error. Maybe there's a timing problem during boot that prevents RA from starting - can you disable the splashscreen (image/video) from the RetroPie-Setup ?

I see you're using RetroArch 1.7.1 and an older Mame2003-plus version, what version of RetroPie are you using ? Please add more details about it - https://retropie.org.uk/forum/topic/3/read-this-first.

I'll try to replicate the issue, but I'll have to install Mame2003+ first.

@grant2258 autostart.sh is executed as the pi user, after autologin; the initial command line was probably truncated during copy/paste.

mitu

OK, so it works for me, here's the content of my autostart.sh:

/opt/retropie/supplementary/runcommand/runcommand.sh 0 _SYS_ arcade /home/pi/RetroPie/roms/arcade/tron2.zip
# emulationstation #auto

For the record, my splashscreen is set to a static image, the default one in RetroPie.

mahoneyt944

@mitu I just fully installed a new image , it's 4.4.9 I believe. I could try to update retroarch though, not sure why it wouldn't be the newest... And my arcade cores too. I also use a video splash screen, the sonic one where he runs back and forth to make the retropie lettering. It seems my issue is specific to mame2003plus as I can boot to any rom using Mame2003 as the emulator.

What is the default retroarch when installing the new 4.4 image? Maybe retroarch has updated since that image was made.

Also, did you look at the second log file I posted?
https://pastebin.com/Jn7782aU
See the end of the log where it fails.

Retropie 4.4.9
Rpi3b+ over clocked
New image installed beginning of March.

mitu

@mahoneyt944 said in Boot to rom using lr-mame2003-plus:

It seems my issue is specific to mame2003plus as I can boot to any rom using Mame2003 as the emulator.

Is the ROM working when launched through Emulationstation ? You said it does.

What is the default retroarch when installing the new 4.4 image? Maybe retroarch has updated since that image was made.

Most likely yes, there is an update to 1.7.6 since the 4.4 image was released.

Also, did you look at the second log file I posted?
https://pastebin.com/Jn7782aU
See the end of the log where it fails.

That one fails because if you're using su for the command line, so it's normal. The error message means that the ROM file cannot be found.

Retropie 4.4.9
Rpi3b+ over clocked
New image installed beginning of March.

Is this a RetroPie image or a 3rd party image ? A fresh RetroPie image does not have the version 4.4.9.

I also use a video splash screen, the sonic one where he runs back and forth to make the retropie lettering.

DId you try disabling the splashscreen, as I said earlier, and see if the ROM starts ?

BuZz

The error in your last log is due to a linefeed in the rom path.

Executing: /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2003-plus/mame2003_plus_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/tron2.zip
" --verbose --appendconfig /dev/shm/retroarch.cfg

and here:

[libretro INFO] [MAME 2003+] Content path: /home/pi/RetroPie/roms/arcade/tron2.zip
.

you need to put it all on one line without a newline in the middle.

mahoneyt944

@mitu the image came from retropie, but I did update the script, update all from source, etc. I didn't try disabling the splash yet but I will in a bit.

The rom works perfectly launched from es and when I exit es and input it manually, just not from autostart.sh

mahoneyt944

@BuZz my autostart.sh only uses a single line. If it's getting more than that it Isnt from how it's typed in autostart.sh but maybe happening from something else or being interpreted oddly

BuZz

@mahoneyt944 I can only say what's going on in the log - and in the log it has a LF or CR character before the end of the content. copy the autostart off your machine and upload it somewhere (so it's unmodified).

mahoneyt944

@BuZz
I removed the #emulationstation #auto line 2 of the autostart.sh, and it worked. I didn't think that line would matter since it doesn't effect mame2003 roms launched the same way. Why does multi lines cause this issue? Is there a way to include multiple lines?