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

    Black screen on ES

    Scheduled Pinned Locked Moved
    Help and Support
    black screen manual install retropie 4.8 raspberry os
    2
    52
    3.9k
    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
      SuperMazut @SuperMazut
      last edited by

      Also, maybe I should add that "$HOME/.emulationstation/es_log.txt" gives me "Access denied".

      Also forgot to add that the touch screen works automatically. Nothing has been modified.

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

        @SuperMazut said in Black screen on ES:

        i.ibb .co/cyHG02L/greska1.png (without the space between ibb and .co because apparently my reputation's too low to post links?)

        There's no link posting restriction, I don't understand why you think so. You can also drag-n-drop the picture into the post to include it directlu, without resorting to a 3rd party hosting site (with a reasonable image size).

        I can see that the DSI connector is printed and the resolution (800x480) is detected.

        While emuationstation --debug gives me this:
        ibb .co/VMGt6hW

        I don't see any error here but also there's no video output - if the picture your posted is what you see on the screen. For text files, enable SSH and copy the file with WinSCP, then post the contents directly intot he post. The end of the log file is missing.

        Also, maybe I should add that "$HOME/.emulationstation/es_log.txt" gives me "Access denied".

        Yes, you can't execute a text file, which is what your command tries to do. You need to view the file with less or more if you're looking at it from the terminal. Or just copy it with WinSCP like I mentioned it earlier.

        If you run kmstest from the command line (or via SSH), do you get a colour pattern on the screen ?

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

          @mitu If I try to post links or images, forum gives me a message that my reputation needs to be at least 0 to do that.

          Anyway, this is the beggining of es_log.txt
          ibb .co/sqhNLbg

          kmstest does give me a color pattern.

          Also for some reason I get access denied if I try to SSH into pi@(my IP address) via powershell or WinSCP.

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

            @SuperMazut said in Black screen on ES:

            @mitu If I try to post links or images, forum gives me a message that my reputation needs to be at least 0 to do that.

            Ah, yes, your reputation is less than 0 at the moment.

            Anyway, this is the beggining of es_log.txt
            ibb .co/sqhNLbg

            It doesn't really help, since the error crashing ES is at the end of the file - as I said before. You posted the same log previously, so nothing new here.

            kmstest does give me a color pattern.

            That's good.

            Also for some reason I get access denied if I try to SSH into pi@(my IP address) via powershell or WinSCP.

            If you're sure you have enabled SSH, double-check you're entering the password correctly (it's raspberry).

            S 2 Replies Last reply Reply Quote 0
            • S
              SuperMazut @mitu
              last edited by

              @mitu Yeah, low reputation is probably due to me being an impatient bitch at the start... I'm really sorry about that. I've been stressed out lately.

              Here's the thing:
              I got SSH running, works. SCPing into it also works but:

              1. In Powershell, when I do what you told me (more or less in combination with $HOME/.emulationstation/es_log.txt - Tried with and wthout doing emulationstation --debug) it basically gives me the exact same log that I posted already.

              2. In WinSCP, I can't seem to find that text file anywhere. (I searched in both folders at - home -> pi. Namely RetroPie and RetroPieSetup) nothing relevant shows up.

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

                TERM environment variable not set.
                tput: No value for $TERM and no -T specified
                Jul 21 21:22:45 lvl2: EmulationStation - v2.11.2rp, built Jul 13 2024 - 22:05:36
                Jul 21 21:22:45 lvl2: Parsing XML file "/opt/retropie/supplementary/emulationstation/resources/mamenames.xml"...
                Jul 21 21:22:45 lvl2: Parsing XML file "/opt/retropie/supplementary/emulationstation/resources/mamebioses.xml"...
                Jul 21 21:22:45 lvl2: Parsing XML file "/opt/retropie/supplementary/emulationstation/resources/mamedevices.xml"...
                Jul 21 21:22:45 lvl2: Creating window...
                Jul 21 21:22:45 lvl2: Created window successfully.
                Jul 21 21:22:45 lvl2: GL vendor: Broadcom
                Jul 21 21:22:45 lvl2: GL renderer: V3D 7.1
                Jul 21 21:22:45 lvl2: GL version: 3.1 Mesa 23.2.1-1~bpo12+rpt3
                Jul 21 21:22:45 lvl2: Checking available OpenGL extensions...
                Jul 21 21:22:45 lvl2: ARB_texture_non_power_of_two: ok
                Jul 21 21:22:45 lvl2: Loading system config file /etc/emulationstation/es_systems.cfg...
                Jul 21 21:22:45 lvl1: System "amstradcpc" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "arcade" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "atari2600" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "atari5200" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "atari7800" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "atari800" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "atarilynx" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "channelf" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "coleco" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "fba" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "fds" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "gamegear" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "gb" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "gba" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "gbc" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "mame-libretro" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "mastersystem" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "megadrive" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "msx" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "n64" has no games! Ignoring it.
                Jul 21 21:22:45 lvl1: System "neogeo" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "nes" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "ngp" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "ngpc" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "pcengine" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "psx" has no games! Ignoring it.
                Jul 21 21:22:46 lvl2: Parsing XML file "/home/pi/.emulationstation/gamelists/retropie/gamelist.xml"...
                Jul 21 21:22:46 lvl1: System "sega32x" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "segacd" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "sg-1000" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "snes" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "vectrex" has no games! Ignoring it.
                Jul 21 21:22:46 lvl1: System "zxspectrum" has no games! Ignoring it.
                Jul 21 21:22:46 lvl3: SystemView::getViewElements()
                Segmentation fault
                /usr/bin/emulationstation: line 22: /dev/tty: No such device or address
                tput: No value for $TERM and no -T specified

                Is this of value?

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

                  The crash is the segmentation fault message at the end:

                  Jul 21 21:22:46 lvl3: SystemView::getViewElements()
                  Segmentation fault

                  The reason it crashes is not printed though, you can usually get that by running the program through a source code debugger like gdb, but that's a bit more complicated. Just to rule out any issues with the resources used by EmulationStation, can you try and update/reinstall theemulationstation package ? Or install the emulationstation-dev package from the experimental packag section and try starting the frontend (emulationstation) again.

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

                    @mitu will do tonight after work.

                    Just to be sure, how would I reinstall and/or update the packages? Any specific commands? Just a few pointers? :)

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

                      @SuperMazut said in Black screen on ES:

                      Just to be sure, how would I reinstall and/or update the packages? Any specific commands? Just a few pointers? :)

                      You did this during the installation, right ? See https://retropie.org.uk/docs/Updating-RetroPie/#updatinginstalling-individual-packages.

                      S 2 Replies Last reply Reply Quote 0
                      • S
                        SuperMazut @mitu
                        last edited by

                        @mitu updating individual packages? Except for retropie, I have not, infact. I'll report back tonight. Thank you for your help and time.

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

                          @mitu My attempts were not successful.

                          I reinstalled ES (from source), then I tried it again after updating ES, same thing. I then got the experimental dev package for ES which also crashes and gives the same error in the logs. Unless I was supposed to uninstall ES first, then get the dev package?

                          Am I in a big mess here?

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

                            @SuperMazut said in Black screen on ES:

                            Unless I was supposed to uninstall ES first, then get the dev package?

                            No, that's not needed, installing one of them will uninstall the other, so there's no need to run the uninstall first.

                            I then got the experimental dev package for ES which also crashes and gives the same error in the logs.

                            Ok, so the crash is not caused by a missing/malformed resource. At this point the only way to find out what's causing the crash is to run it through gdb.

                            Form a SSH session:

                            1. install the gdb package with
                              sudo apt install -y gdb

                            2. run EmulationStation through gdb:
                              gdb -q -ex run /opt/retropie/supplementary/emulationstation/emulationstation

                            NB: if you haveemulationstation-dev installed, then run instead:
                            gdb -q -ex run /opt/retropie/supplementary/emulationstation-dev/emulationstation

                            1. after the 'Segmentation fault' error appears, just type bt and press enter at the gdb prompt that appears. Post the output of the command.

                            2. type q to exit gdb and confirm with y if prompted to kill/stop the running process.

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

                              @mitu Today Emulationstation worked... briefly, it crashed again after restart. I then proceeded to do what you told me and it doesn't give me the desired results. It throws me a bunch of "undefined commands":

                              pi@retropie:~ $ sudo apt install -y gdb
                              Reading package lists... Done
                              Building dependency tree... Done
                              Reading state information... Done
                              gdb is already the newest version (13.1-3).
                              The following package was automatically installed and is no longer required:
                              libcamera0.2
                              Use 'sudo apt autoremove' to remove it.
                              0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded.
                              pi@retropie:~ $ gdb -q -ex /opt/retropie/supplementary/emulationstation-dev/emulationstation
                              Undefined command: "". Try "help".
                              (gdb)

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

                                @SuperMazut said in Black screen on ES:

                                Undefined command: "". Try "help".

                                Sorry, I've missed a word in the command - it's corrected now in my post.

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

                                  @mitu we seem to be getting somewhere:

                                  gdb -q -ex run /opt/retropie/supplementary/emulationstation-dev/emulationstation
                                  Reading symbols from /opt/retropie/supplementary/emulationstation-dev/emulationstation...
                                  (No debugging symbols found in /opt/retropie/supplementary/emulationstation-dev/emulationstation)
                                  Starting program: /opt/retropie/supplementary/emulationstation-dev/emulationstation
                                  [Thread debugging using libthread_db enabled]
                                  Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
                                  [New Thread 0x7ffff4d6edc0 (LWP 1126)]
                                  [New Thread 0x7fffe7ccadc0 (LWP 1127)]

                                  Thread 1 "emulationstatio" received signal SIGSEGV, Segmentation fault.
                                  0x00007ffff2d85130 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  (gdb) bt
                                  #0 0x00007ffff2d85130 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  #1 0x00007ffff2d8fd10 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  #2 0x00007ffff2d8bdb0 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  #3 0x00007ffff2da29a0 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  #4 0x00007ffff24b4ed0 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  #5 0x00007ffff218b660 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                  #6 0x00005555556e6164 in ImageComponent::render(Transform4x4f const&) ()
                                  #7 0x0000555555699864 in SystemView::renderExtras(Transform4x4f const&, float, float) ()
                                  #8 0x00005555556999dc in SystemView::render(Transform4x4f const&) ()
                                  #9 0x00005555556a3654 in ViewController::render(Transform4x4f const&) ()
                                  #10 0x00005555556d14b8 in Window::render() ()
                                  #11 0x00005555555c3120 in main ()
                                  (gdb)

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

                                    @SuperMazut said in Black screen on ES:

                                    #5 0x00007ffff218b660 in ?? () from /usr/lib/aarch64-linux-gnu/dri/v3d_dri.so
                                    #6 0x00005555556e6164 in ImageComponent::render(Transform4x4f const&) ()

                                    Looks like the crash is in the DRI driver for the GPU (v3d), outside EmulationStation code. This makes it difficult to diagnose, since it's not part of RetroPie.
                                    My guess is that the crash is related to the screen (DSI), since normally (via HDMI/composite) this crash doesn't happen. But I'm afraid I have no more ideas on how to get a diagnostic out of it and what could possibly the at fault here.

                                    Do any errors show in the system logs ? Can you run dmesg | tail -n 20 and post the output ?

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

                                      @mitu

                                      dmesg | tail -n 20
                                      [ 13.150732] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150736] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150740] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150743] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150747] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150751] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150754] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150758] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150762] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150765] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150769] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150772] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150776] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150780] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150784] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150787] hid-generic 0003:C0F4:09F0.0002: unknown main item tag 0x0
                                      [ 13.150791] hid-generic 0003:C0F4:09F0.0002: unbalanced collection at end of report description
                                      [ 13.150799] hid-generic: probe of 0003:C0F4:09F0.0002 failed with error -22
                                      [ 13.216418] systemd[974]: memfd_create() called without MFD_EXEC or MFD_NOEXEC_SEAL set
                                      [ 73.553533] usb 1-2: USB disconnect, device number 2

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

                                        The log doesn't show anything about the GPU, just some errors/messages related to USB/input devices (the controller). There is a disconnect message ath the end, not sure if you disconnected the gamepad yourself or it has - erroneously - disconnected itself.

                                        You may try without the controller connected, but I'd say is a slim chance this is causing the ES issue.

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

                                          @mitu The controller wasn't plugged in, just the keyboard alone which, as I said, causes ES to give me the "ES crashed!" message. When the controller is plugged in, it doesn't do that but instead shows a black screen.

                                          So, are you saying it's not a screen issue after all?

                                          EDIT: Would you suggest to start over with a better SD card perhaps? The one I'm using was a noname one I got from the post office...

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

                                            @SuperMazut said in Black screen on ES:

                                            So, are you saying it's not a screen issue after all?

                                            No, as I said it was just a slim chance that the controller would disconnect and cause the crash, but that doesn't seem the case.

                                            Did you test the system with a HDMI connected display ?

                                            S 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.