Flycast forcing reboot; time taken to do so dependant on overclock settings

stevas

Heh, yeah, and - phew (right?) - I've been one of them...

Anyway, think we're done here.

Also, once again, you're all fine people, and much appreciated for setting me straight.

Won't stop me trying to break this thing tho.

pjft

@stevas To be clear - and I've tried not to comment here as @quicksilver and @dankcushions have more experience in overclocking the Pi than I would have - the process to try to find out a stable overclocking for your Pi should still be the same.

The best help I found here was from a post from @quicksilver 2 years ago: https://retropie.org.uk/forum/topic/17032/stresstest-a-fanless-overclocked-pi-3-b-no?_=1593105029442

Probably Quake 3 is no longer a good stress test for the Pi 4 (on mine it never really made its CPU or even temperature rise a lot), but it still stands. Change one parameter at a time, then stress test for a while. Then readjust, adding more or less parameters.

I never overclocked my Pi 3 nor 3B as it was never really stable either. Start with core, then feel free to change others. Or start with others and keep core. Test and iterate. I spent the better part of a weekend on mine (and then reflashed the card in case some of the hangs would have corrupted it), and after a few weeks that wasn't stable so I took core down a bit more.

What I ended up stress testing with was Quake 3, per that post's suggestion, but afterwards lr-yabasanshiro, lr-flycast and lr-mame2016 running one of those Cave shooters from the previous thread, as it did seem to push the CPU quite a bit. I left them on for an hour or more in the attract modes. I did have a fan for some of them, when I saw the temperatures rising fast - lr-yabasanshiro was the biggest offender there, high-cpu all around.

Best of luck.

stevas

@pjft

Dude, thanks; I'll probably have a go at the cave stuff on 2016 now... Yeah, it does often feel like I need good fortune with this stuff...

quicksilver

@pjft said in Flycast forcing reboot; time taken to do so dependant on overclock settings:

lr-yabasanshiro was the biggest offender there, high-cpu all around

Or if you really want to slam your CPU just load up the main menu of lr-flappybirds 😂

pjft

@quicksilver I know it's a double-sided joke, but actually that game consistently crashed my Pi when overclocked - even with my currently "supposed stable overclock". I had to try out lower resolutions, otherwise after a few minutes of playing it would reboot our of the blue.

Disable threaded video on that one. It'll go back to less egregious resource consumption, and work a lot smoother (with G-Sync as well). But yes, if I recall correctly I think I left it on 720p.