lr-MAME2010 Update Issue / Update Startup Script Fails

hooperre

Thank you, @BuZz, @mitu, and @herb_fargus. This fixed the Startup Script Issue. Appreciate all y'all's help. MAME2010 issue in my OP still persists. Just goes to a black screen. Probably not more info to give than that, unfortunately.

I should note that it worked with my ROMs previously and the ROMs work in MAME2014 despite being from the 0.139 romset, leading to my working thought that it is indeed the lr-MAME2010 at fault.

hooperre

Is there a way to clean any files associated with MAME2010 from my SD? I've updated the startup script successfully, but still not getting MAME2010 to install correctly. I've tried removing and re-installing it from source and binary multiple times. Thanks.

dankcushions

@hooperre said in lr-MAME2010 Update Issue / Update Startup Script Fails:

Is there a way to clean any files associated with MAME2010 from my SD? I've updated the startup script successfully, but still not getting MAME2010 to install correctly. I've tried removing and re-installing it from source and binary multiple times. Thanks.

what makes you think it hasn't installed correctly? do you get an error during build/install?

hooperre

This post is deleted!

hooperre

@dankcushions I haven't got an error but all my roms that were previously working with lr-MAME2010 no longer work after an accidental 'update all' that stalled and required a hard reset during update. (Could I have SSH'd and safely rebooted? I think I tried.) So I've attempted to rebuild with source and binary since with no luck. About 6 times a piece. In the past, specifically with lr-MAME2010 I would have to rebuild (and I think I was only successful with building from source) about 3 times before I would get it to work. The other times it would go to a black screen, then back to ES. I've tested the roms in MAME2014 and the all seem to work... Maybe I just roll with that for now until I start fresh.

dankcushions

@hooperre i'm sorry i still don't understand. when you update something (from binary or source), it has two results: it either completes successfully, and goes back to the setup script, or it fails, and says it has failed. what exactly happens when you try and update it? i'm not talking about when you run a game - one step at a time.

hooperre

@dankcushions Sure thing. I appreciate your patience with me and willingness to help me here.

When I update from binary or source, it returns to the setup script without an error.

dankcushions

@hooperre sounds good so far! i think everything will be installing correctly.

now could you try and launch a game that previously worked, and then after it fails, could you please retrieve /dev/shm/runcommand.logand paste the contents here?

hooperre

@dankcushions

Parameters: 
Executing: SDL_VIDEO_EGL_DRIVER=/opt/vc/lib/libEGL.so SDL_VIDEO_GL_DRIVER=/opt/vc/lib/libGLESv2.so /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2010/mame2010_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/asteroid.zip" --appendconfig /dev/shm/retroarch.cfg'|'"/home/pi/RetroPie/roms/arcade/asteroid.zip.cfg"
value: enabled
value: enabled
value: enabled
value: enabled
value: disabled
/opt/retropie/supplementary/runcommand/runcommand.sh: line 1013:  1652 Segmentation fault      SDL_VIDEO_EGL_DRIVER=/opt/vc/lib/libEGL.so SDL_VIDEO_GL_DRIVER=/opt/vc/lib/libGLESv2.so /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-mame2010/mame2010_libretro.so --config /opt/retropie/configs/arcade/retroarch.cfg "/home/pi/RetroPie/roms/arcade/asteroid.zip" --appendconfig /dev/shm/retroarch.cfg'|'"/home/pi/RetroPie/roms/arcade/asteroid.zip.cfg"

dankcushions

@hooperre thanks - 'segmentation fault' is a crash, so it looks like mame2010 is broken.

i don't use it, but maybe someone else who does can say if the latest version is working or not.

i guess my favourite suggestion is to stop using mame2010 ;)

hooperre

@dankcushions Posted on the github for lr-mame2010. In the meantime, I'll take your advice :). Thanks again for your patience.

hooperre

@dankcushions ~~it looks like my if and statement says 'fi' instead of 'if' in my runcommand.sh.~~

function launch_command() {
    local ret
    # launch the command
    echo -e "Parameters: $@\nExecuting: $COMMAND" >>"$LOG"
    if [[ "$CONSOLE_OUT" -eq 1 ]]; then
        # turn cursor on
        tput cnorm
        eval $COMMAND </dev/tty 2>>"$LOG"
        ret=$?
        tput civis
    else
        eval $COMMAND </dev/tty &>>"$LOG"
        ret=$?
    fi
    return $ret
}

~~My python skills are still a work in progress, but I'm guessing that 'fi' doesn't even need to be there?~~ Nvm there are "fi's" everywhere. Not familiar with that one.

Anyway, the eval $COMMAND </dev/tty 2>>"$LOG" line causes the fragmentation error.

dankcushions

@hooperre FI is closing the IF block. bash scripts are weird.

you don't have an error there - the errors are within the mame2010 executable, not the launcher. you won't be able to track down any further without running it in debug mode with gdb. this is complex. like i said, you should wait for someone else to confirm your issues before progressing this, especially to git.

hooperre

@dankcushions Damn. Okay. Others on Reddit said they were able to update from binary successfully. I think it’s a me issue. 2010 for some reason has been trouble since jump for me.

Thanks again.