Recalbox 8.0: (ERROR) : [SDL2] Fatal error initializing SDL2

[davidb2111]

@fh1105 said in Recalbox 8.0: (ERROR) : [SDL2] Fatal error initializing SDL2:

I think it didn't enter recovery, even though I did the power-off-power-on-15-second loop at least 4 times ... can I trigger it manually? Also, it doesn't seem to come back to the network (it's LAN connected, but I can't reach the 'recalbox' host from the network anymore).

The screen shows 'Experimental Pi' twice while booting, then remains black.

I do have a keyboard connected, which I could use to press something to interrupt the failing boot sequence?

Thanks! @davidb2111

Ok, so you have things connected to GPIO. That may be the reason.
Could you connect through ssh and execute:

/usr/bin/piboy-tester

David.

[davidb2111]

@fh1105
And to force boot without detecting case, you may:

1. set case=none:1 in /boot/recalbox-boot.conf
2. execute rm -rf /overlay/upper/*

and reboot

[davidb2111]

@fh1105
And finally, I've modified the code that detects the piboy. Could you please test it on your setup ?

Simply put piboy-tester in /tmp of your recalbox and run /tmp/piboy-tester and give me the output.

Thanks

[fh1105]

This post is deleted!

[fh1105]

@davidb2111 said in Recalbox 8.0: (ERROR) : [SDL2] Fatal error initializing SDL2:

/tmp/piboy-tester

Yes, this is it:

try 0, CRC error
try 1, CRC error
try 2, CRC error
try 3, CRC error
try 4, CRC error
try 5, CRC error
try 6, CRC error
try 7, CRC error
try 8, CRC error
try 9, CRC error
piboy not found

[fh1105]

@davidb2111 said in Recalbox 8.0: (ERROR) : [SDL2] Fatal error initializing SDL2:

@fh1105
And to force boot without detecting case, you may:

1. set case=none:1 in /boot/recalbox-boot.conf
2. execute rm -rf /overlay/upper/*

and reboot

I tried this, but still the screen remains black.

[fh1105]

Before the modified tester, the output was:

CRC error
198

[davidb2111]

Hi @fh1105

Great news, that helps me a lot. I will include a fixed piboy-tester that will not wrongly detect a PiBoy when something is connected to GPIO.

At the moment, you can cleanup overlay and set case=none:1 to disable autodection.
The fix will be included in the next release a few days (weeks)

David

[davidb2111]

@fh1105

Hum, what type of screen do you have ?
Could you please execute cat /sys/class/drm/card*/modes and put result here ?

[fh1105]

@davidb2111 said in Recalbox 8.0: (ERROR) : [SDL2] Fatal error initializing SDL2:

cat /sys/class/drm/card*/modes

It's a HDMI-connected HD screen – normal 'office type'.

cat /sys/class/drm/card*/modes

returns nothing at all.

[fh1105]

But here's me exploring that directory:

# pwd
/sys/class/drm
# ls
card0           card0-HDMI-A-1  renderD128      version
# cd card0-HDMI-A-1
# ls
device     edid       modes      status     uevent
dpms       enabled    power      subsystem
# cd modes
-bash: cd: modes: Not a directory
# ls
device     edid       modes      status     uevent
dpms       enabled    power      subsystem
# cat modes
# cd ..
# ls
card0           card0-HDMI-A-1  renderD128      version
# cd card0
# ls
card0-HDMI-A-1  device          subsystem
dev             power           uevent
#


(modes in card0-HDMI1-A-1 is empty)

[fh1105]

By the way: amazing support, @davidb2111! Thank you very much!!

[davidb2111]

Hi @fh1105

Seems edid does not report modes. Could you force the mode within /boot/recalbox-user-config.txt.

hdmi_group=1
hdmi_mode=X

where X should be:

• 16 for 1080p
• 4 for 720p
• 1 for VGA mode (640x480, as a fallback)

Once started, if still no display, try adding this setting:

hdmi_ignore_edid=0xa5000080

Hope this help.

[davidb2111]

@fh1105
Also, do you know the resolution of your TV?

[fh1105]

Hello!

Just a brief update, as I solved it by simply removing everything from my GPIO ports, and wiring my arcade buttons to a

Zero Delay Arcade USB Encoder

– which then connects to the RPi's USB ports.

All good now! Thank you, and keep it up!
Fabian