Issues with lr-atari800 setup on new build... worked on previous build.

jamrom2

@mitu I'll give it a shot tomorrow, but I thought I was updated. I'm at 4.6.7 Setup Script, and have the most recent image on my machine (4.6) .

So just update Retroarch? I haven't done that yet.... but ss for lr-atari800, I did that already... I even tried installing from Source and updating... but I still got the same results... which is why I threw in the towel and came here.

mitu

@jamrom2 said in Issues with lr-atari800 setup on new build... worked on previous build.:

I'm at 4.6.7 Setup Script, and have the most recent image on my machine (4.6) .

Your RetroArch version is not the latest (1.8.8 vs 1.8.5).

EDIT: One other thing you can try - even without updating - is disabling the menu widgets by adding to \\retropie\configs\atari800\retroarch.cfg:

menu_enable_widgets = "false"

jamrom2

@mitu aaahhhh... ok. I think we're on to something. BTW.. I really appreciate all your help... as always.

jamrom2

@mitu said in Issues with lr-atari800 setup on new build... worked on previous build.:

@jamrom2 said in Issues with lr-atari800 setup on new build... worked on previous build.:

I'm at 4.6.7 Setup Script, and have the most recent image on my machine (4.6) .

Your RetroArch version is not the latest (1.8.8 vs 1.8.5).

EDIT: One other thing you can try - even without updating - is disabling the menu widgets by adding to \\retropie\configs\atari800\retroarch.cfg:
menu_enable_widgets = "false"

I wanted to mention this as well. I noticed that when I make changes to this version of Retroach config files, it seems whatever I do, is dumped when I leave the core, regardless if I save or not. Meaning... if I add an overlay. I save it, exit, go back in and the overlay is not displayed until I select it again, and save again. Very odd behavior I've never seen in the past.

jamrom2

@mitu
Update:
I updated lr-atari800 to 1.8.8 - no change.

Adding that statement did the trick. Atari 800 comes right up, and works great. A5200 I still have to press a button for the emulator to start. It loads, but sits at a black screen waiting for input.

I added that statement to the a5200 retroarch.cfg file as well. No change.

jamrom2

Nevermind... I forgot to turn on the auto-detect a5200 cart. It's working now. Comes right up.

So that statement you posted was the fix for me... and I'm guessing for anyone having this issue.

Thanks for the mega fast response with a great fix included!

mitu

@jamrom2 said in Issues with lr-atari800 setup on new build... worked on previous build.:

I updated lr-atari800 to 1.8.8 - no change.

Hm, RetroArch's version is 1.8.8, not lr-atari. Did you update both ?

jamrom2

@mitu yes. I went back in to the lr-atari800 core and all it gives me is a re-install option. So I'm guessing I'm at the most recent binary build

mitu

I'm not asking about lr-atari, I'm asking about the retroarch package - did you update it ?

jamrom2

@mitu oh, sorry.. yes. updated.

jamrom2

@mitu what i was saying is that I updated to 1.8.8 and tried to run a800. It failed the same.

Once I added that statement it worked. If I take that statement out... it fails again

mitu

@jamrom2 OK, thanks for the confirmation - have fun playing !

EDIT: you should close the issue you opened on the atari800 upstream repository, since it's not a bug in their emulator.

jamrom2

@mitu will do... thanks again! Great find and fix!

jf

Wanted to say THANKS for the "menu_enable_widgets" fix and to share some more info.

First, it was interesting that ROMs were fine and that ATR disks were all failing.

I tracked down the segmentation violation in the /dev/shm/run command.log:

/opt/retropie/supplementary/runcommand/runcommand.sh: line 1283: 31257 Segmentation fault      /opt/retropie/emulators/retroarch/bin/retroarch -L /opt/retropie/libretrocores/lr-atari800/atari800_libretro.so --config /opt/retropie/configs/atari800/retroarch.cfg "/home/pi/RetroPie/roms/atari800/Mule.atr" --verbose --appendconfig /dev/shm/retroarch.cfg

I took a look at line 1283:

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

All this is doing is running the right command, explicitly getting input from the tty, and tying file descriptors to the log.

I ran the command from the console and it worked fine without redirecting STDIN/STDERR. It also worked fine just redirecting STDOUT (fd 1). But every time I redirected STDERR (fd 2), I got a segmentation violation.

Not sure what exactly the widgets have to do with this, but apparently they do. If anybody wants a strace of this I would be happy to provide.

I hope this is helpful, and again, thanks for the fix!