Splashscreen images not displaying | omxiv erroring out

QuestionMark

Raspberry Pi 4 Model B
RetroPie 4.7.1 built from Raspberry Pi Imager v1.5 on macOS

Splashscreen images don't display, while splashscreen videos do.
Digging around a bit, I was able to pinpoint omxiv as the point of failure. I've tried using the binary with several of the splashscreen png images, but I get an error:

$ cd /opt/retropie/supplementary/omxiv
$ ./omxiv --once -t 12 -b --layer 1000 /home/pi/RetroPie/splashscreens/retropie-extra/akasol-smoked.png

> assertion failure:ilclient.c:747:ilclient_change_component_state():error == OMX_ErrorNone
> Aborted

I rebuilt the binary by following the directions in the repo's README.md. When I ran the new binary I got the same error.

I searched the web for what the error could mean and was taken to this website. I'm having trouble understanding what this all means though.

What should my next course of action be?

mitu

@questionmark said in Splashscreen images not displaying | omxiv erroring out:

What should my next course of action be?

Can you post your /boot/config.txt file ? Does this happen for any splashscreen image file ?

QuestionMark

@mitu It's the same for all splashscreen images.

/boot/config.txt :

# For more options and information see
# http://rpf.io/configtxt
# Some settings may impact device functionality. See link above for details

# uncomment if you get no picture on HDMI for a default "safe" mode
#hdmi_safe=1

# uncomment this if your display has a black border of unused pixels visible
# and your display can output without overscan
disable_overscan=0

# uncomment the following to adjust overscan. Use positive numbers if console
# goes off screen, and negative if there is too much border
#overscan_left=16
#overscan_right=16
#overscan_top=16
#overscan_bottom=16

# uncomment to force a console size. By default it will be display's size minus
# overscan.
#framebuffer_width=1280
#framebuffer_height=720

# uncomment if hdmi display is not detected and composite is being output
#hdmi_force_hotplug=1

# uncomment to force a specific HDMI mode (this will force VGA)
#hdmi_group=2
#hdmi_mode=85

# uncomment to force a HDMI mode rather than DVI. This can make audio work in
# DMT (computer monitor) modes
#hdmi_drive=2

# uncomment to increase signal to HDMI, if you have interference, blanking, or
# no display
#config_hdmi_boost=4

# uncomment for composite PAL
#sdtv_mode=2

#uncomment to overclock the arm. 700 MHz is the default.
#arm_freq=800

# Uncomment some or all of these to enable the optional hardware interfaces
#dtparam=i2c_arm=on
#dtparam=i2s=on
#dtparam=spi=on

# Uncomment this to enable infrared communication.
#dtoverlay=gpio-ir,gpio_pin=17
#dtoverlay=gpio-ir-tx,gpio_pin=18

# Additional overlays and parameters are documented /boot/overlays/README

# Enable audio (loads snd_bcm2835)
dtparam=audio=on

[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2

[all]
#dtoverlay=vc4-fkms-v3d
#overscan_scale=1

While I'm at it, is this where I would put settings like runahead?
Sorry if that's a dumb question, I'm very new to all of this.

mitu

Add at the end of the /boot/config.txt:

gpu_mem=128

and retry.

While I'm at it, is this where I would put settings like runahead?

No, that's a RetroArch (emulator) configuration option, while /boot/config.txt is used only by the RPI bootloader.
To modify the runahead settings, modify one of the retroarch.cfg files - see https://retropie.org.uk/docs/RetroArch-Configuration/#config-hierarchy. You may wish to add this configuration on a per-system basis or per-game basis, since each emulator/game may have different requirements. See https://retropie.org.uk/docs/Input-Lag/#run-ahead for configuration details.

QuestionMark

@mitu Adding gpu_mem=128 to the config allowed me to view all of the official retropie splashscreens exept for retropie-2015.png and retropie-default.png (I am on a 16:9 monitor, so I'm a little confused).

I tested the first 100 "extra" splashscreens and 44 of them didn't work.

Would further increasing the value of gpu_mem help?

Also I was reading the docs and found:

On the Raspberry Pi 4 the 3D component of the GPU has its own memory management unit (MMU), and does not use memory from the gpu_mem allocation. Instead memory is allocated dynamically within Linux. Increasing this amount can harm emulation performance.

So will this cause performance to dip?

mitu

@questionmark said in Splashscreen images not displaying | omxiv erroring out:

So will this cause performance to dip?

No, it will not.