Flycast forcing reboot; time taken to do so dependant on overclock settings
-
@quicksilver
Well... Yeah. But it feels like I've found a safe OC for everything else but flycast, which doesn't like any form of OC at all.And I'm still unclear on whether I should use gpu_freq or not.
Edit
To be clear: I just thought I'd seen someone refer to a safe level of overclocking, and my mind immediately went to "oh, there's an agreed level of overclocking by the community"; i.e. not recommended necessarily by the manufacturer etc, but something you should generally get away with - if you get me? -
@mitu said in Flycast forcing reboot; time taken to do so dependant on overclock settings:
@stevas said in Flycast forcing reboot; time taken to do so dependant on overclock settings:
Could someone direct me to what actual safe overclock settings are?
I don't think there are 100% 'safe' settings - it depends on the board. You'll need to experiment with different values and test each configuration until you reach a stable configuration.
Also, how could I tell if I had an early board with dodgy components?
Which components ?
Sorry, thread is moving quicker than I anticipated!
I was referring to the "faulty" comment here?Gah, which of course I forgot to paste:
https://retropie.org.uk/forum/post/228172 -
@stevas said in Flycast forcing reboot; time taken to do so dependant on overclock settings:
@quicksilver
Well... Yeah. But it feels like I've found a safe OC for everything else but flycast, which doesn't like any form of OC at all.A marginally stable overclock is still an unstable overclock. You aren't likely to cause any damage to your pi this way but over time you are risking corrupting sd card.
And I'm still unclear on whether I should use gpu_freq or not.
GPU freq should be fine, it just will not affect core freq like it used to. Or to simplify things just overclock v3d freq because we don't care about the other blocks of the GPU anyway.
-
@stevas said in Flycast forcing reboot; time taken to do so dependant on overclock settings:
@quicksilver
Well... Yeah. But it feels like I've found a safe OC for everything else but flycast, which doesn't like any form of OC at all.it makes sense that a sophisticated 3d emulator, likely hammering the gpu, cpu, system bus and so on, is going to be more sensitive to instability than a simpler 2d one.
To be clear: I just thought I'd seen someone refer to a safe level of overclocking, and my mind immediately went to "oh, there's an agreed level of overclocking by the community"; i.e. not recommended necessarily by the manufacturer etc, but something you should generally get away with - if you get me?
anecdotally, the "safe" overclocking guides for pi3, including the ones on our wiki, are not safe at all, IMO. they certainly weren't close to the settings i was able to get away with my pi3. ETA prime's insane overclocking guide must have been the source of 100s of "why is my retropie crashing?!" support requests...
-
Many thanks, I will remove gpu_freq going forward and just use v3d and arm now.
-
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.
-
@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.
-
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...
-
@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 😂
-
@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.
Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.
Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.