There is no HDMI output when TV turns on later than LibreELEC

elonesna · December 6, 2020 at 10:29 AM

If my TV is off when LibreELEC starts up then there is no HDMI signal when I turn on the TV.

I have not been able to solve the problem, only assign a key on the remote control to restart the mini PC with the TV on.

Does anyone know how to solve this problem other than restarting the mini PC with the TV on?

Notes:

- Mini PC with Intel i5-5257U hardware (and with Iris Graphics 6100) and two HDMI outputs.

- LibreELEC stable 9.2.6 running 24/7 as a server with daily scheduled restart. Running services: SSH, SFTP, SAMBA (read-only services), FTP, TigerVNC, tvheadend, zerotier-one, syncthing, oscam, portainer, and docker.

**Klojum** · December 6, 2020 at 10:48 AM Official Post

Quote from elonesna

I have not been able to solve the problem

Turn on the TV first, then the RPi... LibreELEC needs to do a HDMI-handshake, which isn't possible when the TV is off.

Also, read here: "No signal" on TV with Raspberry Pi 4, after LibreELEC logo.

elonesna · December 6, 2020 at 11:39 AM

Quote from Klojum

Turn on the TV first, then the RPi... LibreELEC needs to do a HDMI-handshake, which isn't possible when the TV is off.
Also, read here: "No signal" on TV with Raspberry Pi 4, after LibreELEC logo.

"Turn on the TV first" - Not possible, the PC works 24/7. It is a TV server (tvheadend), multimedia server (Samba and FTP) and automatic smartphones backup server (syncthing) for my house and the houses of my relatives (zerotier-one). It reboot at dawn when all the TVs are off.

"then the RPi ..." - It is not an RPi, it is an x86-64 PC, the solutions in the link do not work.

Note.- When the LibreELEC server starts up with the TV turned off, a VNC session (tigerVNC) can be started but always in "virtual screen" 1024x768p60Hz mode and no other resolution can be chosen. When the TV is on and LibreELEC is working fine, then multiple resolutions can be chosen. I manage all LibreELEC and CoreELEC devices from my smartphone. With CoreELEC and ARM Amlogic processors as a server I never had any problems.

Code

When LibreELEC started with TV off:

LibreELEC:/etc/X11 # xrandr -q
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
HDMI1 disconnected primary (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)


When LibreELEC started with TV off and after TV is started:

LibreELEC:/etc/X11 # xrandr -q
Screen 0: minimum 8 x 8, current 1024 x 768, maximum 32767 x 32767
HDMI1 connected primary (normal left inverted right x axis y axis)
1920x1080     60.00 +  50.00    59.94    30.00    25.00    24.00    29.97    23.98
1920x1080i    60.00    50.00    59.94
1280x1024     60.02
1360x768      60.02
1152x864      59.97
1280x720      60.00    50.00    59.94
1024x768      60.00
800x600       60.32
720x576       50.00
720x576i      50.00
720x480       60.00    59.94
640x480       60.00    59.94
720x400       70.08
HDMI2 disconnected (normal left inverted right x axis y axis)
VIRTUAL1 disconnected (normal left inverted right x axis y axis)

Display More

The command

Code

/usr/bin/xrandr --output HDMI1 --mode 1920x1080 --rate 25

works inside SSH but not inside crontab.

elonesna · December 7, 2020 at 12:47 AM

Solved

During the LibreELEC installation I used the HDMI2 port of the PC. LibreELEC configured itself to boot on this port. A few days later I switched to the HDMI1 port and thereafter LibreELEC was unable to activate the TV when it was turned on later than LibreELEC.

Conclusion: LibreELEC configures itself to turn on the TV during the installation process.

More informationfor for x86_64 processors here EDID - LibreELEC.wiki.

**chewitt** · December 7, 2020 at 2:22 AM Official Post

Quote from elonesna

Conclusion: LibreELEC configures itself to turn on the TV during the installation process.

The conclusion is wrong. LE does not turn on the TV, but Kodi stores the active video output interface in /storage/.kodi/userdata/guisettings.xml so if you install with HDMI2 and then change the interface to HDMI1 this invalidates the stored configuration.

ghtester · December 7, 2020 at 5:16 PM

Well as far as I can remember, I started having this issue as well after upgrading to LE 9.2.6 (even I did not change the HDMI port).

In my case I am turning on/off the display by relay (through GPIO pin on my RPi 4B) and there was a python script switching the relay ON after LE startup. It was working fine in previous LE versions but now it's too late to 'handshake' with display booting at the same time so the display did not receive HDMI signal anymore.

I have solved it through config.txt - putting there a command for setting the appropriate GPIO pin earlier so the display is ready before Kodi starts. This works fine.