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

    Selecting RETROPI SETTINGS causes Black screen

    Scheduled Pinned Locked Moved Help and Support
    blackscreen
    39 Posts 6 Posters 14.4k 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.
    • BuZzB
      BuZz administrators
      last edited by

      Made a few minor updates to the script above.

      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 0
      • RascasR
        Rascas @BuZz
        last edited by Rascas

        Nice. If the chvt isn't really needed anymore and can be replaced with fbset, I think something like this maybe better:

        #!/bin/sh
        
        save_mode() {
            local status="$(tvservice -s)"
            if echo "$status" | grep -qE "(PAL|NTSC)"; then
                MODE_TYPE=$(echo "$status" | grep -oE "(PAL|NTSC)")
                MODE_INFO=$(echo "$status" | grep -oE "([0-9]+\:[0-9]+)")
            else
                MODE_TYPE=$(echo "$status" | grep -oE "(CEA|DMT)")
                MODE_INFO=$(echo "$status" | grep -oE "\([0-9]+\)" | tr -d '()')
            fi
            ORIGINAL_DEPTH=`fbset | head -3 | tail -1 | cut -d " " -f 10`
        }
        
        restore_mode() {
            if [ "$MODE_TYPE" = "PAL" ] || [ "$MODE_TYPE" = "NTSC" ]; then
                tvservice -c "$MODE_TYPE $MODE_INFO" >/dev/null
            else
                tvservice -e "$MODE_TYPE $MODE_INFO" >/dev/null
            fi
            sleep 1
            fbset -depth 8 > /dev/null 2>&1
            fbset -depth $ORIGINAL_DEPTH > /dev/null 2>&1
        }
        
        save_mode
        
        # launch kodi
        
        restore_mode
        

        This is because, for example in PiPplware distribution, we use framebuffer_depth=32 which gives better quality image in some cases, like pictures / fotos in Kodi and LXDE/XFCE. Not sure if this gives better image quality in emulators though, probably not.

        BuZzB 2 Replies Last reply Reply Quote 0
        • BuZzB
          BuZz administrators
          last edited by BuZz

          That change looks good. You can probably save and restore the framebuffer width/height too although probably not needed in this case. We do this in runcommand as we allow changing of framebuffer resolution, and need to restore it correctly. We don't actually save the depth as above, so I will change that too.

          in the unlikely case that the framebuffer was in 8bit mode first, you would probably need to do fbset -depth 16; fbset -depth 8 (setting for to another depth to reset it). Although I don't think anyone runs in 8bit by default.

          Regarding 32 bit quality in emulators - I don't know - perhaps for some that run on the framebuffer - but there were some issues with 32bit in the past but I can't remember exactly what. I don't think this would affect retroarch/sdl2 etc.

          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 0
          • BuZzB
            BuZz administrators
            last edited by BuZz

            Also Kodi doesn't use the framebuffer but RPI dispmanx api etc so I wouldn't have thought you need to set framebuffer to 32bit mode for Kodi - for X applications though you would.

            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 0
            • BuZzB
              BuZz administrators
              last edited by

              @Rascas While on the subject of framebuffer depth - looks like 32 is the best choice now anyway - https://github.com/raspberrypi/firmware/issues/685

              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 0
              • BuZzB
                BuZz administrators @Rascas
                last edited by

                @Rascas any news on this ? More black screen reports have come in. If you are short on time, I might add a fbset workaround to the end of the Kodi launch or ES launch script via RetroPie-Setup.

                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 0
                • BuZzB
                  BuZz administrators @Rascas
                  last edited by

                  @Rascas also just FYI, framebuffer depth is now 32bit by default. https://github.com/raspberrypi/firmware/issues/685

                  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

                  RascasR 1 Reply Last reply Reply Quote 0
                  • RascasR
                    Rascas @BuZz
                    last edited by

                    @BuZz yes, I am a bit short on time, I will change kodi launch script when Kodi 17 comes out (it should be this month still) but change it where you see more fit if you want till there.

                    1 Reply Last reply Reply Quote 0
                    • M
                      Morphy
                      last edited by

                      Hi I have a very similar issue however I'm not using Kodi. For me it seems like the display sleeps but only for the RP scripts and other shell options. Emulationstation displays ok however if I enter a script the screen is blank. Also when I launch a game I dont see the press any key to configure menu either. When I connect a keyboard and press a key it appears again. The controllers I use dont wake it however. What is causing this and how do I change it please?

                      BuZzB 1 Reply Last reply Reply Quote 0
                      • BuZzB
                        BuZz administrators @Morphy
                        last edited by

                        @Morphy https://retropie.org.uk/forum/topic/7747/finally-got-everything-up-and-running-still-2-minor-issues/3

                        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

                        M 1 Reply Last reply Reply Quote 0
                        • M
                          Morphy @BuZz
                          last edited by

                          @BuZz said in Selecting RETROPI SETTINGS causes Black screen:

                          @Morphy https://retropie.org.uk/forum/topic/7747/finally-got-everything-up-and-running-still-2-minor-issues/3

                          Thanks however I don't have kodi installed on my RP installation?

                          BuZzB 1 Reply Last reply Reply Quote 0
                          • BuZzB
                            BuZz administrators @Morphy
                            last edited by BuZz

                            @Morphy I missed that - start a new topic after reading https://retropie.org.uk/forum/topic/3/read-this-first and I will advise.

                            I have no details about your set-up.

                            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 0
                            • RascasR
                              Rascas
                              last edited by

                              @BuZz sorry for the necro, is there a problem if we change this for Kodi 18, to instead of just saving the bitdepth, to save everything (including the resolution) and restore it back at exit ? That would be usefull for us to save some memory from the framebuffer when Kodi is running, since this new version can consume more than the default 256MB. You have the current Kodi 18 start script here if you need more info:
                              https://github.com/PIPplware/xbmc/blob/leia_new/tools/Linux/kodi.sh.in
                              Thanks

                              BuZzB 1 Reply Last reply Reply Quote 0
                              • BuZzB
                                BuZz administrators @Rascas
                                last edited by

                                @Rascas May be my memory but I thought we already saved everything ?

                                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

                                RascasR 1 Reply Last reply Reply Quote 0
                                • RascasR
                                  Rascas @BuZz
                                  last edited by

                                  @BuZz Ah yes, you are right, I was confusing 2 different fixes ... Anyway, there are some improvements that we can do for Kodi 18, when it approaches the final/stable version I will talk to you.

                                  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.