lr-atari800 not starting after updating from 4.5.1

GeekOB

Thanks @BuZz , so I'm stuck with the broken lr-atari800 until the issue is addressed on a later RetroArch version?
I guess that's ok, I can use the atari800 emulator in the meantime.
Do you know if the issue is fixed in any of the versions between the RetroPie one and 1.8.3?

BuZz

@GeekOB possibly but not tested.

GeekOB

Understood @BuZz,
Please let me know if I can help with the testing, I'm happy to try any newer versions and report on core behaviour and functionality.

BuZz

Could downgrade RetroPie-Setup temporarily and install retroarch from source - SDL will probably be downgraded too. But should work ok.

git -C ~/RetroPie-Setup checkout ea69edb

BuZz

@mitu has a 1.8.3 branch I think. Or you could adjust the RetroPie-Setup source but not sure if our patches apply without rebasing.

GeekOB

@BuZz I can run the string you suggest above or wait for @mitu. Happy to connect over email if you want to give me more specific directions

BuZz

@GeekOB try the above. Will downgrade to RetroPie-Setup 4.5.6 with older retroarch. But you will need to use source install for retroarch. Will have the bug you mention of course in first post as it will be v1.7.6

GeekOB

Oh... the freezing on mouse click is an issue for me as well @BuZz.
Would it be possible to test out 1.8.3 from @mitu before?

mitu

@GeekOB You can test, but I'm not sure it will fix this probem

cd $HOME/RetroPie-Setup
git remote add mitu https://github.com/cmitu/RetroPie-Setup
git fetch mitu
git checkout mitu/ra_183

go into packages and install RetroArch from source to test. You should get 1.8.3 and see if it solves your problem.
To get back to the normal RetroPie repo:

cd $HOME/RetroPie-Setup
git checkout master
git remote remove mitu

GeekOB

There were some errors at the end of the update from source process, @mitu
See the log here: https://pastebin.com/pfzzgaEv
Should I still go ahead and test?

mitu

@GeekOB said in lr-atari800 not starting after updating from 4.5.1:

Should I still go ahead and test?

Well, the installation failed - so there's really nothing to test. Just revert back to the RetroPie's repository - as mentioned in my previous post. I'll see why that error you posted appears - didn't get that in my build, but maybe something changed upstream.

GeekOB

I noticed I'm getting these messages when updating the Pi @mitu

raspberrypi-bootloader was already set on hold.
libraspberrypi0 was already set on hold.
libraspberrypi-doc was already set on hold.
libraspberrypi-dev was already set on hold.
libraspberrypi-bin was already set on hold.
raspberrypi-kernel-headers was already set on hold.
raspberrypi-kernel was already set on hold.

Would this be related to the failed install?
How do I "release" the packages??

mitu

@GeekOB said in lr-atari800 not starting after updating from 4.5.1:

Would this be related to the failed install?

No, the main RetroPie script does that.

How do I "release" the packages??

You don't need to.

GeekOB

Thanks @mitu
I'll work on removing all bezels from my systems and then try the reverting instructions that @BuZz gave me. But I'm still very much interested in helping you guys test RetroArch 1.8.3 (if I can build it from source successfully that is), just let me know what I need to do.

mitu

@GeekOB said in lr-atari800 not starting after updating from 4.5.1:

But I'm still very much interested in helping you guys test RetroArch 1.8.3 (if I can build it from source successfully that is), just let me know what I need to do.

I'm trying to figure it out why it the installation errors out - works on a Pi4/Buster, but has the errors you found on a Pi3/Stretch installation.

GeekOB

Thanks @mitu, I'll keep checking this thread for any updates.

mitu

@GeekOB Thanks. I've fixed the error you reported, but there's a new error related to the - other - changes added in RetroArch, this time a dependency issue which requires disabling the FFMPEG core. I'll see what can be done.

GeekOB

What's the downside of disabling the FFMPEG core @mitu ?

BuZz

@GeekOB no screen recording.

GeekOB

Thanks @BuZz
I don't use this feature at all @mitu, happy to disable and test further if required.