"No signal" on TV with Raspberry Pi 4, after LibreELEC logo.

kdrone · August 27, 2019 at 9:59 PM

I just installed the OS several times, on my own and via NOOBS, always with the same result.

After the LibreELEC logo, my TV says "NO SIGNAL", and nothing happens.

Can't access SSH.

What's going on? Is it a bad Kodi config?

And yes, I have the HDMI cable plugged on HDMI 0 (near the USB-C port)

[edit] I just manged to open an SSH on the machine, it seems to be working, but it isn't displaying anything. What do I do at this point and why did this happen?

[edit 2] tvservice reposrts this:

state 0xa [HDMI CUSTOM RGB full unknown AR], 1920x1200 @ 59.00Hz, progressive

Clearly my display does not support 1920x1200, but why is this set at this resolution when I never configured it to be this way, and how can I change this via terminal or some other way? I need it to be 1080P

[edit 3] I added hdmi_force=1 to the config.txt file, tvservice -m CEA says only mode 16 is enabled, and none for DMT, and still, the system boots and then goes into 1920x1200 @ 59Hz mode!! edid.dat follows:

Code

HDMI:EDID version 1.3, 1 extensions, screen size 115x65 cm
HDMI:EDID features - videodef 0x80 !standby !suspend active off; colour encoding:RGB444|YCbCr422; sRGB is not default colourspace; preferred format is native; does not support GTF
HDMI:EDID found monitor name descriptor tag 0xfc
HDMI:EDID monitor name is EP-HDMI-RX
HDMI:EDID found monitor range descriptor tag 0xfd
HDMI:EDID monitor range offsets: V min=0, V max=0, H min=0, H max=0
HDMI:EDID monitor range: vertical is 59-61 Hz, horizontal is 15-46 kHz, max pixel clock is 80 MHz
HDMI:EDID monitor range does not support GTF
HDMI:EDID found preferred CEA detail timing format: 1280x720p @ 60 Hz (4)
HDMI:EDID found CEA detail timing format: 720x480p @ 60 Hz (2)
HDMI:EDID established timing I/II bytes are 21 08 00
HDMI:EDID found DMT format: code 4, 640x480p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 9, 800x600p @ 60 Hz in established timing I/II
HDMI:EDID found DMT format: code 16, 1024x768p @ 60 Hz in established timing I/II
HDMI:EDID standard timings block x 8: 0x0101 0101 0101 0101 0101 0101 0101 0101 
HDMI:EDID parsing v3 CEA extension 0
HDMI:EDID monitor support - underscan IT formats:no, basic audio:yes, yuv444:yes, yuv422:yes, #native DTD:1
HDMI:EDID found CEA detail timing format: 1920x1080p @ 60 Hz (16)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 60 Hz (5)
HDMI:EDID found CEA detail timing format: 1280x720p @ 50 Hz (19)
HDMI:EDID found CEA detail timing format: 1920x1080i @ 50 Hz (20)
HDMI:EDID found CEA detail timing format: 720x576p @ 50 Hz (17)
HDMI:EDID found CEA format: code 4, 1280x720p @ 60Hz (native)
HDMI:EDID found CEA format: code 19, 1280x720p @ 50Hz 
HDMI:EDID found CEA format: code 5, 1920x1080i @ 60Hz 
HDMI:EDID found CEA format: code 20, 1920x1080i @ 50Hz 
HDMI:EDID found CEA format: code 16, 1920x1080p @ 60Hz 
HDMI:EDID found CEA format: code 2, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 3, 720x480p @ 60Hz 
HDMI:EDID found CEA format: code 17, 720x576p @ 50Hz 
HDMI:EDID found CEA format: code 18, 720x576p @ 50Hz 
HDMI:EDID found CEA format: code 1, 640x480p @ 60Hz 
HDMI:EDID found audio format 6 channels AC3, sample rate: 32|44|48 kHz, bitrate: 640 kbps
HDMI:EDID found audio format 7 channels DTS, sample rate: 44|48 kHz, bitrate: 1536 kbps
HDMI:EDID found HDMI VSDB length 7
HDMI:EDID HDMI VSDB has physical address 1.0.0.0
HDMI:EDID HDMI VSDB supports AI:yes, dual link DVI:no
HDMI:EDID HDMI VSDB deep colour support - 48-bit:no 36-bit:no 30-bit:no DC_yuv444:no
HDMI:EDID HDMI VSDB max TMDS clock 150 MHz
HDMI:EDID HDMI VSDB has no latency information
HDMI:Warning EDID must support pcm or no audio
HDMI:EDID filtering formats with pixel clock unlimited MHz or h. blanking unlimited
HDMI:EDID best score mode initialised to CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 0)
HDMI:EDID best score mode is now CEA (1) 640x480p @ 60 Hz with pixel clock 25 MHz (score 61864)
HDMI:EDID best score mode is now CEA (2) 720x480p @ 60 Hz with pixel clock 27 MHz (score 4566472)
HDMI:EDID CEA mode (3) 720x480p @ 60 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID best score mode is now CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz (score 5190888)
HDMI:EDID DMT mode (4) 640x480p @ 60 Hz with pixel clock 25 MHz has a score of 18432
HDMI:EDID CEA mode (5) 1920x1080i @ 60 Hz with pixel clock 74 MHz has a score of 3773832
HDMI:EDID DMT mode (9) 800x600p @ 60 Hz with pixel clock 40 MHz has a score of 28800
HDMI:EDID CEA mode (16) 1920x1080p @ 60 Hz with pixel clock 148 MHz has a score of 4273832
HDMI:EDID DMT mode (16) 1024x768p @ 60 Hz with pixel clock 65 MHz has a score of 47185
HDMI:EDID CEA mode (17) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 2066472
HDMI:EDID CEA mode (18) 720x576p @ 50 Hz with pixel clock 27 MHz has a score of 66472
HDMI:EDID CEA mode (19) 1280x720p @ 50 Hz with pixel clock 74 MHz has a score of 3117160
HDMI:EDID CEA mode (20) 1920x1080i @ 50 Hz with pixel clock 74 MHz has a score of 2732360
HDMI0:EDID preferred mode remained as CEA (4) 1280x720p @ 60 Hz with pixel clock 74 MHz
HDMI:EDID has HDMI support and audio support
edidparser exited with code 0

Display More

kdrone · August 27, 2019 at 11:32 PM

I don't understand why Kodi was set to display its GUI at 1900x1200 but I also couldn't find how to change it on guisettings.xml

What I did is

- SSH into the Raspberry Pi

- type tvservice -m CEA to find a supported mode

- type tvservice --explicit "CEA 16 HDMI"

This made Kodi display and then I had to go to system settings and change resolution to 1080P. Problem solved, but I just wasted a whole day trying to figure all of this out

Mario77 · August 28, 2019 at 1:35 AM

Try to edit guisettings.xml

ssh

Code

systemctl stop kodi.service

edit line 321 in /storage/.kodi/userdata/guisettings.xml to 1920x1080@60hz

Code

<setting id="videoscreen.screenmode">0192001080060.00000pstd</setting>

ssh

Code

systemctl start kodi.service

Not tested but should work....take a guisettings.xml backup just in case.

HypnoToad · August 28, 2019 at 3:26 AM

I have 2 rasp pi 4's. 2GB and 4GB

The 4gb one has issues with the same micro hdmi cable I have used to setup both of them.

The color test screen will come up, but then if it's moved slightly the main OS doesn't load with it's default resolution, as if the cable has been unplugged while it was loading.

I don't get this connection issue with the 2GB model, I can also move it around without any connection issues.

The OS's I am using are libreelec pi 4 build and raspbian, and it all seems like a hardware disconnection and not a software one. Because if I can get it into a good position I can use the device just fine.

I am afraid that I may have accidentally broken something when I've treated this device in particular with great care because it was the first one I got.

Your issue seems on the surface much like mine where the hdmi is not detecting the cable being plugged in. If you move it around do you get any artifacts or images, you might have to do what I am planning on doing and looking into other micro hdmi adaptors

kdrone · August 28, 2019 at 1:29 PM

Quote from Mario77
Try to edit guisettings.xml
Code
<setting id="videoscreen.screenmode">0192001080060.00000pstd</setting>

Thanks that would have been helpful when I was trying to access that file, videoscreen.screenmode was empty. T%hat should be another way to do it.

My way though gives an immediate image on Kodi so you can then use the GUI to change settings.

For some reason the RPi 4 was detecting my display as 1920x1200 capable, I now excluded that resolution from the whitelist just to be safe. I think this board still needs some bugs ironed out.

Quote from HypnoToad

Your issue seems on the surface much like mine where the hdmi is not detecting the cable being plugged in. If you move it around do you get any artifacts or images, you might have to do what I am planning on doing and looking into other micro hdmi adaptors

No it was a software issue, the screen was going off after Kodi was launched, as I explained.

I get no artifacts or anything, and if I was you I wouldn't be wiggling that around, you probably did damage the port.

bluenote · December 21, 2019 at 2:22 AM

Quote from Mario77
Try to edit guisettings.xml

ssh
Code
systemctl stop kodi.service
edit line 321 in /storage/.kodi/userdata/guisettings.xml to 1920x1080@60hz
Code
<setting id="videoscreen.screenmode">0192001080060.00000pstd</setting>
ssh
Code
systemctl start kodi.service
Not tested but should work....take a guisettings.xml backup just in case.

Thank you so much for this. I spent hours screwing around with this and what you wrote here fixed my problem. Thanks.