dispmanx_vncserver: main.c:605: main: Assertion `image' failed.

[estivalet]

got this in retropie 4.5 Any tips?

[hanzelpeter]

This assert means that it cannot allocate enough memory for display buffer. What is the resolution of display you want to show? And what RPI model is it? Some other program taking a lot of memory?

[estivalet]

no, I found the issue right now, the hdmi cable was loose on the raspberry PI and so I think it was not generating a signal for HDMI image

[jakubiakdev]

I have the same issue, but I don't have any monitors connected. Someone from kodi forums said that this application might help if there is no monitor but I don't know if it is true

[hanzelpeter]

Hello.

Could you please add first lines of output when program is run.

When it is something like Display size is 4 x 46446656

I saw this on some firmware version and I needed to change display ID from 0 to 8 in open dispmanx display. I also need to get rpi4 and check on it. There I need probably t o add display ID parameter.

[hanzelpeter]

Added -d option to specify dispmanx display ID. Headless I use 0, but 3 can be tried. Please pull and recompile if you wish.

[John-Duh]

Hello, I'm having the same issue I believe. Here's the error message: Open display[0]... Display is 4 x 1053349172 Rotate is 67108864 dispmanx_vncserver: main.c:669: main: Assertion `image' failed. Aborted

I tried adding -d option as mentioned in the help but this didn't change the output.

This is on a raspberry pi 4 running retropie

[jose1711]

Same thing on RPi3 running latest OSMC.

./dispmanx_vncserver  -d 0
Open display[0]...
Display is 4 x 1053650496
Rotate is 67108864
dispmanx_vncserver: main.c:669: main: Assertion `image' failed.
Aborted

Tested with -d set to 0, 2, 3 and 7 - always the same. Maybe it's related to this?

$ /opt/vc/bin/tvservice -o  
/opt/vc/bin/tvservice is not supported when using the vc4-kms-v3d driver.
Similar features are available with standard linux tools
such as modetest from libdrm-tests.

[hanzelpeter]

Hello.

I think this is related to vc4-kms-v3d. I also use raspi-config and use vc4-fkms-v3d driver.

[jose1711]

Thank you, you were right. Switching to fkms solved it. Maybe you could it add it to README.md?