Black screen on ES
-
@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.
-
@mitu updating individual packages? Except for retropie, I have not, infact. I'll report back tonight. Thank you for your help and time.
-
@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?
-
@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:
-
install the
gdb
package with
sudo apt install -y gdb
-
run EmulationStation through
gdb
:
gdb -q -ex run /opt/retropie/supplementary/emulationstation/emulationstation
NB: if you have
emulationstation-dev
installed, then run instead:
gdb -q -ex run /opt/retropie/supplementary/emulationstation-dev/emulationstation
-
after the 'Segmentation fault' error appears, just type
bt
and press enter at thegdb
prompt that appears. Post the output of the command. -
type
q
to exitgdb
and confirm withy
if prompted to kill/stop the running process.
-
-
@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) -
@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.
-
@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) -
@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 ? -
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 -
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.
-
@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...
-
@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 ?
-
@mitu I haven't. I just ordered a microHDMI to HDMI adapter to test it.
I edited my previous post but you replied in the meantime. Would you suggest to start over with a brand name SD card?
-
@SuperMazut said in Black screen on ES:
Would you suggest to start over with a brand name SD card?
I don't think the sdcard is at fault. You can try to reinstall again (OS + RetroPie), but I don't think that a faulty installation is the issue here (you already re-installed EmulationStation).
-
@mitu Ah, that sucks pretty bad actually. I will report back once I test the HDMI solution. It will take me a few days though until the adapter arrives.
I'm desperate. Is there anything I can do in the meantime? I saw a few people on Youtube that could run that exact configuration with the same screen I have. Any drivers? Man, I'd pay money if someone could get it running. 🥺
-
@SuperMazut said in Black screen on ES:
I saw a few people on Youtube that could run that exact configuration with the same screen I have.
With RetroPie or just RaspiOS Desktop ?
EDIT: did you try with a RaspiOS Desktop image to see if the screen works ? -
@mitu now that you mention it... The guy in the video used an older raspberry pi board
As for if I tested with RaspiOS alone, I haven't. But retropie is on top of it, right? Any command I can run to run the OS?
-
@SuperMazut said in Black screen on ES:
But retropie is on top of it, right? Any command I can run to run the OS?
RetroPie uses RaspiOS Lite, but not the desktop edition. You can flash the RaspiOS desktop edition and let it boot to see if it works fully.
-
@mitu Right. I'll flash a different SD card with the full OS and test that on the current screen. I'll report back tonight.
-
@mitu Oof, I have some very bad news:
It does work fully, infact. No problems at all.
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.