[RPi5] No Display After Reboot

Quote from slim0287

I've done a clean install on my RPI5. It works great in terms of installing addons, setting up wireguard, and watching programs. However when I either reboot the Pi or I turn the TV off, the Pi no longer outputs an HMDI signal. I can log in remotely and head /sys/class/drm/*/status shows me the HDMI is connected however there is no signal, as reported by the TV. I've tried systemctl restart kodi and getedid create but they don't help, I've tried different TVs, different HDMI cables, and plugging into the other HDMI port on the Pi but nothing helps.

Andy advice?

Try the force hotplug option.

Quote from slim0287

However, I have no display output so I cannot use the GUI as you suggest in step 1 for enabling the debug log mode.

Create an advancedsettings.xml file, and set log level to value 1. Then you're logging permanently, and invisible for GUI.

This appears to be the same issue I've experienced with my RPi5 as well. A reboot and no signal at HDMI. I suspect it's more of a TV brand/age HDMI issue than the RPi5 but curious to see what he comes up with.

Just curious here what brand/model of TV are you using with your Rpi5?

Is your faulty RPI5 in a case. If so remove it and test it again.

Quote from slim0287

I admit I ought to have tried swapping ports sooner but cie la vie!

Create new EDID: Click!

I had no idea the order in which devices were powered might be an issue. If I understand correctly the RPi5 system will record all necessary EDID info on it's 1st run and save in a permanent file for future boots?

Quote from Reddirt

I had no idea the order in which devices were powered might be an issue. If I understand correctly the RPi5 system will record all necessary EDID info on it's 1st run and save in a permanent file for future boots?

No, it‘s not saved automatically. The command „getedit create“ is the manual process for that, and „getedit delete“ the counterpart.

Explanation:

Since some LE versions, its more important that:

1. the EDID informations are available
2. the EDID information must be correct

Normally the HDMI handshake should be initialized during boot of the RPi. This happens dynamically with every boot process. At this time it‘s important that the HDMI chain is working and not disturbed. Disturbing is possible with bad manufactured/not certified HDMI cables, Micro-HDMI adapter, other HDMI devices …

For example you should ensure, that you switch on the RPi as the last one if your cabling looks like this:
RPi5 -> AVR -> TV

The ideal sequential order to power-on is that:

1. TV (provides EDID data for screen size/frequencies + supported sound channels/formats)
2. AVR (passthrough and/or provides additional EDID data)
3. RPi5

If the AVR is powered-off, the RPi5 can‘t get the EDID information. Some newer AVRs are able to passthrough the EDID information if they are in standby. But there also exists TV, that only provide this information if the TV is switched on.

To get a more robust system against the different power-on scenarios, it‘s possible to grab the EDID data one-time and save it in to the file system with the „getedit create“ command. After that the kernel/KODI will use this saved information at the next boot instead of the dynamical available EDID information. But this implies, that this file must match to your current hardware constellation. On this way it also possible to fake some information, if the extracted EDID block is incomplete or something like that.
If you afterwards make some (conflicting to the EDID file) changes on your hardware/device firmware, then you must update or delete the EDID file again.

Thanks for the detailed explanation. That explains why we sometimes have issues with HDMI connected devices. Also good to know I could create a file to work around the auto config although I understand why it's done this way.

I used ssh and followed the link from DaFlex to create an EDID file. 1st time ever I rebooted my RPI5 on our old Sony with no issues whatsoever. You're the man D and thanks. Also kudos to Harry for a quick education on the how and why of EDID. Since this old Sony is the only TV with a RPI5 issue it's likely an aged TV firmware issue and nothing to do with LE.

vc4.force_hotplug is incompatible with 4kp60 which you are using as GUI resolution so this is expected.

I recommend setting the GUI resolution to 1920x1080 and setting up the whitelist as described in the wiki https://wiki.libreelec.tv/configuration/4k-hdr

Also please drop vc4.force_hotplug from cmdline.txt and make sure you use a proper cable/connection which signals hotplug properly as otherwise you'll have the same issue whenever switching inputs or TV on/off while the RPi switched to 4kp60 during video playback.

so long,

Hias