RetroPie forum home
    • Recent
    • Tags
    • Popular
    • Home
    • Docs
    • Register
    • Login
    Please do not post a support request without first reading and following the advice in https://retropie.org.uk/forum/topic/3/read-this-first

    Sudden change of resolution Pi4

    Scheduled Pinned Locked Moved Help and Support
    pi4resolution
    19 Posts 2 Posters 957 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.
    • mituM
      mitu Global Moderator @Stuffu
      last edited by

      Just tested it myself and the config.txt configurations are taken into account, so nothing changed here. Are you booting into the desktop environment by any chance ?

      S 1 Reply Last reply Reply Quote 0
      • S
        Stuffu @mitu
        last edited by

        @mitu nope, I’m using the official retropie image, nothing else added. If it doesn’t cause any problems elsewhere I’m fine using the current solution. But if you want me to investigate it further I’m happy to do so.

        1 Reply Last reply Reply Quote 0
        • mituM
          mitu Global Moderator
          last edited by mitu

          We can try debugging the bootloader. Add start_debug=1 at the end of the config.txt file, then re-boot (removing the cmdline.txt resolution setup, but leaving the config.txt settings for 1080p as they were initially).
          After the boot, run

          sudo vcdbg log msg
          

          and post the output on pastebin.com. It should show the bootloader debug messages.

          S 1 Reply Last reply Reply Quote 0
          • S
            Stuffu @mitu
            last edited by

            @mitu Here's the output https://pastebin.com/V2GygV9G

            mituM 1 Reply Last reply Reply Quote 0
            • mituM
              mitu Global Moderator @Stuffu
              last edited by

              Add

              gpu_mem=256
              

              to config.txt and retry.

              S 1 Reply Last reply Reply Quote 0
              • S
                Stuffu @mitu
                last edited by

                @mitu Sorry, retry with logging or try to run it as "default"?

                mituM 1 Reply Last reply Reply Quote 0
                • mituM
                  mitu Global Moderator @Stuffu
                  last edited by

                  Logging doesn't really matter - you can leave it on, just add the extra line and see if the PI starts in 1080p.

                  S 1 Reply Last reply Reply Quote 0
                  • S
                    Stuffu @mitu
                    last edited by Stuffu

                    @mitu It still 4k with gpu_mem=256

                    If we can't find a reason for this happening, is there a reason not the use the cmdline alternative? Or even using the hdmi1?

                    mituM 1 Reply Last reply Reply Quote 0
                    • mituM
                      mitu Global Moderator @Stuffu
                      last edited by

                      If it works via HDMI1 - with the same settings as before - then that's ok. The 1st HDMI port is the only one able to do 4k@60Hz, other than that they're identical.

                      S 1 Reply Last reply Reply Quote 1
                      • S
                        Stuffu @mitu
                        last edited by

                        @mitu I haven't noticed anything strange with hdmi1 so I'll stick with that. Thanks for the effort :)

                        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.