Librelec 9.2.1 on rpi4 with Samsung television - no signal

micj1420 · March 17, 2020 at 7:54 AM

Hello

I have just installed a new Raspberry PI 4 with the last LibreElec version 9.2.1 in order to move from my olg RaspBerry Pi 3B.

Everything was wroking fine with the previous hardware. When connecting the rpi4 on a monitor with HDMI port using the same cable, I get the image and the sound.

My environment:

Raspberry pi 4 Model B Rev 1.1
Television: Samsung QE55Q82RALXXN

I tried to find some answer using the search but what I found (see below) didn't change anything:

Code

hdmi_enable_4kp60=1

Can someone point me to the right direction?

**Klojum** · March 17, 2020 at 8:38 AM Official Post

Quote from micj1420

When connecting the rpi4 on a monitor with HDMI port using the same cable

How did you manage that? The RPi3 has a HDMI port, the RPi4 has a micro-HDMI port.

Perhaps your adapter cable is having a compatibility issue?

PadreMartini · March 17, 2020 at 8:47 AM

I had a similar problem getting no signal through my AV Amp, and managed to solve it with this.

Try ssh-ing in while it's connected to the Samsung and then input

Code

tvservice --explicit "CEA 16 HDMI"

**Da Flex** · March 17, 2020 at 10:12 AM Official Post

Quote from PadreMartini
Code
tvservice --explicit "CEA 16 HDMI"

If this screen mode works, then you can make it permanent by adding this lines to config.txt:

Code

hdmi_ignore_edid=0xa5000080
framebuffer_width=1920
framebuffer_height=1080
hdmi_force_hotplug=1
hdmi_group=1
hdmi_mode=16

Remove this, because 4K / 60Hz content is not in common use, and it can cause trouble:

Code

hdmi_enable_4kp60=1

micj1420 · March 17, 2020 at 2:20 PM

Quote from Klojum

How did you manage that? The RPi3 has a HDMI port, the RPi4 has a micro-HDMI port.

Perhaps your adapter cable is having a compatibility issue?

If it's working on a monitor having a HDMI port, I might suppose that the same cable can be used with a television.

**Da Flex** · March 17, 2020 at 3:45 PM Official Post

The HDMI cable has to fulfill HDMI 2.0 or 2.1 standard to work on 4K devices. If your monitor is not 4K, then it's not a proof of complete function. On a 4K device, data transfer will speed up.

Any results when using the described setting at config.txt? It's a proved solution for many problematic TV's.

micj1420 · March 17, 2020 at 10:24 PM

Doesn't work. The cable is the original one (Official Raspberry Pi MicroHDMI Cable) sold by The Pi Hut.

Without modification of the config.txt:

LibreELEC:~ # tvservice -l

1 attached device(s), display ID's are :

Display Number 2, type HDMI 0

LibreELEC:~ # tvservice -m CEA

Group CEA has 4 modes:

mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive

mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive

mode 95: 3840x2160 @ 30Hz 16:9, clock:297MHz progressive

mode 97: 3840x2160 @ 60Hz 16:9, clock:594MHz progressive

LibreELEC:~ # tvservice -m DMT

Group DMT has 1 modes:

(prefer) mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive

With modification of the config.txt:

LibreELEC:~ # tvservice -l

1 attached device(s), display ID's are :

Display Number 2, type HDMI 0

LibreELEC:~ # tvservice -m CEA

Group CEA has 14 modes:

mode 1: 640x480 @ 60Hz 4:3, clock:25MHz progressive

mode 2: 720x480 @ 60Hz 4:3, clock:27MHz progressive

mode 3: 720x480 @ 60Hz 16:9, clock:27MHz progressive

mode 4: 1280x720 @ 60Hz 16:9, clock:74MHz progressive

mode 5: 1920x1080 @ 60Hz 16:9, clock:74MHz interlaced

(prefer) mode 16: 1920x1080 @ 60Hz 16:9, clock:148MHz progressive

mode 17: 720x576 @ 50Hz 4:3, clock:27MHz progressive

mode 18: 720x576 @ 50Hz 16:9, clock:27MHz progressive

(native) mode 19: 1280x720 @ 50Hz 16:9, clock:74MHz progressive

mode 20: 1920x1080 @ 50Hz 16:9, clock:74MHz interlaced

mode 31: 1920x1080 @ 50Hz 16:9, clock:148MHz progressive

mode 32: 1920x1080 @ 24Hz 16:9, clock:74MHz progressive

mode 33: 1920x1080 @ 25Hz 16:9, clock:74MHz progressive

mode 34: 1920x1080 @ 30Hz 16:9, clock:74MHz progressive

LibreELEC:~ # tvservice -m DMT

Group DMT has 19 modes:

mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive

mode 5: 640x480 @ 72Hz 4:3, clock:31MHz progressive

mode 6: 640x480 @ 75Hz 4:3, clock:31MHz progressive

mode 8: 800x600 @ 56Hz 4:3, clock:36MHz progressive

mode 9: 800x600 @ 60Hz 4:3, clock:40MHz progressive

mode 10: 800x600 @ 72Hz 4:3, clock:50MHz progressive

mode 11: 800x600 @ 75Hz 4:3, clock:49MHz progressive

mode 16: 1024x768 @ 60Hz 4:3, clock:65MHz progressive

mode 17: 1024x768 @ 70Hz 4:3, clock:75MHz progressive

mode 18: 1024x768 @ 75Hz 4:3, clock:78MHz progressive

mode 21: 1152x864 @ 75Hz 4:3, clock:108MHz progressive

mode 28: 1280x800 @ 60Hz 16:10, clock:83MHz progressive

mode 32: 1280x960 @ 60Hz 4:3, clock:108MHz progressive

mode 35: 1280x1024 @ 60Hz 5:4, clock:108MHz progressive

mode 36: 1280x1024 @ 75Hz 5:4, clock:135MHz progressive

mode 47: 1440x900 @ 60Hz 16:10, clock:106MHz progressive

mode 48: 1440x900 @ 75Hz 16:10, clock:136MHz progressive

mode 51: 1600x1200 @ 60Hz 4:3, clock:162MHz progressive

mode 58: 1680x1050 @ 60Hz 16:10, clock:146MHz progressive

**chewitt** · March 18, 2020 at 2:19 AM Official Post

Are you using the HDMI port nearest to the power connector (good idea) or the other one (not such a good idea) ?

micj1420 · March 18, 2020 at 4:14 AM

Quote from chewitt

Are you using the HDMI port nearest to the power connector (good idea) or the other one (not such a good idea) ?

I used the right one (port nearest to the power connector)

**Da Flex** · March 18, 2020 at 8:25 AM Official Post

Quote from micj1420

Doesn't work. The cable is the original one (Official Raspberry Pi MicroHDMI Cable) sold by The Pi Hut.

I wouldn't count on that "official" cable too much (source).

Your TV seems to be a new one, so it shouldn't be on the list of problematic old TV's (which need a workaround at config.txt).

I would buy another microHDMI cable (2.0 or 2.1 standard), and remove the workaround at config.txt.

The list of provided screen modes looks OK, I think the cable is just too slow to deliver them.

micj1420 · March 18, 2020 at 1:06 PM

Quote from Da Flex

I wouldn't count on that "official" cable too much (source).

Your TV seems to be a new one, so it shouldn't be on the list of problematic old TV's (which need a workaround at config.txt).

I would buy another microHDMI cable (2.0 or 2.1 standard), and remove the workaround at config.txt.

The list of provided screen modes looks OK, I think the cable is just too slow to deliver them.

It's a brand-new Samsung .... I just ordered a new cable from Amazon ... expect to get it tomorrow if Covid-19 allows.

Librelec 9.2.1 on rpi4 with Samsung television - no signal

Similar Threads

Hyperion addon does not work with inputstream.adaptive (Netflix etc.) with Pi4