• Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login
RetroPie forum home
  • Recent
  • Tags
  • Popular
  • Home
  • Docs
  • Register
  • Login

Overclocking wiki page rewritten

Scheduled Pinned Locked Moved General Discussion and Gaming
wikioverclockoverclockingperformancedocumentation
6 Posts 5 Posters 2.2k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • S
    suprjami
    last edited by 16 Oct 2016, 13:42

    What started out as a formatting tidy resulted in me documenting most of what I know about the Raspberry Pi and overclocking it.

    https://github.com/RetroPie/RetroPie-Setup/wiki/Overclocking

    Enjoy!

    B C B 3 Replies Last reply 16 Oct 2016, 14:42 Reply Quote 10
    • B
      BuZz administrators @suprjami
      last edited by 16 Oct 2016, 14:42

      @suprjami nice job! Thanks :-)

      To help us help you - please make sure you read the sticky topics before posting - https://retropie.org.uk/forum/topic/3/read-this-first

      1 Reply Last reply Reply Quote 1
      • C
        cyperghost @suprjami
        last edited by 17 Oct 2016, 09:53

        @suprjami Nice one!

        1 Reply Last reply Reply Quote 1
        • B
          Brunnis @suprjami
          last edited by Brunnis 26 Oct 2016, 06:20

          @suprjami Awesome job! This is a great reference. I have found two issues, though:

          You mention several times that force_turbo = 1 voids the warranty. However, the formula for voiding the warranty is:

          (force_turbo || current_limit_override || temp_limit>85) && over_voltage>0

          See https://www.raspberrypi.org/forums/viewtopic.php?p=176865#p176865 It's an old post, but I haven't seen anything that suggests this was changed.

          The second issue I found is that according to https://www.raspberrypi.org/documentation/configuration/config-txt.md the gpu_freq setting actually sets core_freq and all other GPU related frequencies to the same value. The wiki page makes it seem as if core_freq and gpu_freq are unrelated. Or maybe that page on raspberrypi.org is outdated? Could be, since all overclocking related info in it seems to be RPi 1 related.

          S 1 Reply Last reply 27 Oct 2016, 07:25 Reply Quote 1
          • S
            suprjami @Brunnis
            last edited by suprjami 27 Oct 2016, 07:25

            @Brunnis hey thanks for the references! i've been meaning to test those, but have had some other stuff going on and haven't been near the computer much

            i also find a lot of overclocking info for the Pi is either outdated or conflicting or just wrong. like the Pi 3 and Zero come with core and GPU at different speeds, so maybe one doesn't set the other there? i haven't tried yet

            as i understand it, if the two core and gpu are set to different things, an unexpected frequency may result which can be calculated with: https://github.com/superjamie/snippets/blob/master/pioc.py

            i figured it was best to err on the side of caution and explicitly set both. tbh i don't think there are super-huge gains to be had by clocking them differently, at least not for N64/Dreamcast/PSP purposes

            i will test more and update the wiki page when i get back into it

            1 Reply Last reply Reply Quote 0
            • S
              Shakz
              last edited by Shakz 27 Oct 2016, 14:53

              Excellent work....very very thorough. Love it!

              RetroPie tips, tricks, and tweaks: https://www.youtube.com/eazyhax

              1 Reply Last reply Reply Quote 0
              • First post
                Last post

              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.

                This community forum collects and processes your personal information.
                consent.not_received