No 2160 on Pi4 through Sony 4K Receiver

  • First of all, I want to say thanks to all the good people that contribute to the Libreelec, I have really appreciated your work :D


    My problem is that I'm trying to get 4K to work trough my Sony STR-DN 1040 receiver, it is connected as following PI4 -- STR-DN1040 -- Samsung UE58 MU6125. This setup gives me only 1080p, I tried to go into "settings/system/display and changed the resolution to 3840x2160p and 4096x2160p but that gives me an black screen,

    If I connect the Pi4 directly to the TV it has no problem showing 4k videos, or changing the resolution on the gui to 2160p.


    Coreelec on an S905W (x96 mini) has no problem displaying 4k (30hz) through my receiver, so that makes me believe this is related to either Libreelec, or the kernel that Librelec uses on Pi4 (using Libreelec 9.1.501 Kernel 4.19.66)


    I have tried to 2 different micro hdmi cables, ( a third one is on is way from Ebay)


    Now that if I check with: tvservice -m DMT it gives an output of "mode 4: 640x480 @ 60Hz 4:3, clock:25MHz progressive" : tvservice -m CVT gives me an "invalide group"


    Summary: All cables is 4K certified ( a third one is on its way, to rule out an old one, and and an not so trusted one (micro hdmi)

    : 4K works trough receiver with an Android S905w box running Coreelec

    : Yes The pi4 is connected to an 4K input on my receiver (did try BD, Video1, and Game)

    : Did try with CONFIG_HDMI_B.O.O.S.T but no difference ( does it work on pi4? )


    I would be thankful if someone could direct me in the right direction, or have some tips on this problem :D









    Edited 2 times, last by OffLoad ().

  • awiouy

    Approved the thread.
  • There are 67 1-star reviews for this receiver on Amazon. Most are for HDMI issues.


    Have you tried running Coreelec on the Pi4 ?

  • There are 67 1-star reviews for this receiver on Amazon. Most are for HDMI issues.


    Have you tried running Coreelec on the Pi4 ?

    Thanks blueribb but, I dont think this is related to the same HDMI issues. Coreelec is for AMlogic devices, not for Pi4, so no :D


    I did istall the latest nightly 9.80-nightly-20190928-019132b and now the screen stays on when I switch to 2160p, but the TV is not changing resolution from 1080p to2160, resulting in an very blown up picture there I only can see the 1/4 of the gui, (upper left part)


    Did SSH into the Pi, to see if the Pi could see the TV, and by running "tvservice -n" it reported back "device name=SNY-SAMSUNG" So the Pi can "see" the TV.

    I will do some more testing, but hopefully I'm not the only one with this issue.


    This is the modes that currently is reported back by tvservice.


    # tvservice -m CEA

    Group CEA has 18 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

    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

    mode 93: 3840x2160 @ 24Hz 16:9, clock:297MHz progressive

    mode 94: 3840x2160 @ 25Hz 16:9, clock:297MHz progressive

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

    mode 98: 4096x2160 @ 24Hz unknown AR, clock:297MHz progressive

    Edited once, last by OffLoad ().

  • Please test with LibreELEC 9.2 beta 1 and make sure you have hdmi_enable_4kp60=1 in config.txt and enabled "Ultra HDMI Deep Colour" (or whatever the option to enable 4:4:4 chroma is named) on your TV/receiver.


    4kp50/60 is disabled by default on RPi4 (as it needs higher internal clocking and increases temperature) and it only supports 4:4:4 output (not 4:2:0), which is often disabled on TVs.


    so long,


    Hias

  • Yes - 2160p50 and 2160p59.94/60 support on some AVRs and TVs is limited to 4:2:0 which is a format the Pi 4 doesn't support (4:2:0 is only an HDMI standard for 2160p50 and above)


    Your Pi 4B will output RGB (which is the same bandwidth as 4:4:4) 8-bit at 2160p50 and above - not all AVRs and TVs support this.


    (4:2:0 8-bit support for 2160p50 and above was added to the HDMI 2.0 spec so that HDMI 1.4b hardware could be used to carry a 2160p50 and above signal - as the bandwidth just squeaks into HDMI 1.4b hardware limits. This was a way for manufacturers to 'upgrade' existing hardware that was HDMI 1.4b only to support HDMI 2.0. Just. However 4:2:0 is the only HDMI output spec that requires both horizontal AND vertical chroma subsampling - and the Pi doesn't support vertical subsampling - only horizontal - AIUI)

  • Hi. I will return to 9.2 beta 1, and hdmi_enable_4kp60=1 was enabled in config.txt, but 4KP60 its really not my goal, I'm happy with 25/30hz

    UHD is enabled on the TV.


    Yes - 2160p50 and 2160p59.94/60 support on some AVRs and TVs is limited to 4:2:0 which is a format the Pi 4 doesn't support (4:2:0 is only an HDMI standard for 2160p50 and above)


    Your Pi 4B will output RGB (which is the same bandwidth as 4:4:4) 8-bit at 2160p50 and above - not all AVRs and TVs support this.


    (4:2:0 8-bit support for 2160p50 and above was added to the HDMI 2.0 spec so that HDMI 1.4b hardware could be used to carry a 2160p50 and above signal - as the bandwidth just squeaks into HDMI 1.4b hardware limits. This was a way for manufacturers to 'upgrade' existing hardware that was HDMI 1.4b only to support HDMI 2.0. Just. However 4:2:0 is the only HDMI output spec that requires both horizontal AND vertical chroma subsampling - and the Pi doesn't support vertical subsampling - only horizontal - AIUI)


    This is what the receiver supports, I have no idea what the TV supports thou, but 4k is working if I connect the Pi4 directly to the TV.

    Edited once, last by OffLoad ().

  • OK, you can drop hdmi_enable_4kp60=1 from config.txt, 4kp50/60 isn't supported by the receiver (at 4:4:4 RGB). But 4kp24-30 should work according to the specs you posted. Puzzling.


    Could you test this build: libreelec-rpi4.arm-9.1-devel-20190928101045-ea02c4d.img.gz


    This is current LibreELEC 9.2 development tree plus latest 4.19 kernel and firmware (about what's to become the next 9.2 release).


    so long,


    Hias

  • It looks like the OP should DISABLE 4kp60 in config.txt as the receiver specs confirm that it only supports 4:2:0 video at 2160p50 and above which the Pi doesn't output (at least currently - and probably won't)


    If 4KP60 output is disabled in config.txt the Pi will output up to a max 4K30 output - which the receiver should be compatible with.


    What happens if you run the Pi with 4Kp60 disabled?

  • Installed the developer build, but no difference . hdmi_enable_4kp60=1 is also removed from config.txt, so no alteration in the config.txt for the moment.

    This is the supported formats for the TV Samsung 58" MU6125

    UHD is set to "ON"

    So, as you can see, both the receiver, and the tv supports RGB 4:4:4 8 Bit, so something weird going on here :)


    I'm going to load up an card with an Buster image, to see if I can get any 2160p to work in Buster.


    So far, thanks for your help :)

  • Update:

    Did try Buster, but no picture on 2160p, so went back to Libreelec developer build.

    My third micro HDMI cable hasn't arrived yet, so I went out an bought an Micro HDMI to HDMI adapter, to test with an HDMI cable that I know is working through the receiver to my TV, but still an black screen with "No Signal" appears when I switch to 2160p.


    So I SSH into the Libreelec, an ran a few tvservice test, just to see if I could figure out something, and to my suprise, when running "tvservice -M" to monitor the HDMI when I switched to 2160p the Pi4 is loosing HDMI connection.


    [I] HDMI in HDMI mode


    [I] HDMI cable is unplugged. Display 2


    [I] HDMI is attached


    [I] HDMI cable is unplugged. Display 2


    [I] HDMI is attached


    [I] HDMI cable is unplugged. Display 2


    [I] HDMI is attached


    [I] HDMI cable is unplugged. Display 2


    [I] HDMI is attached


    I'm running the HDMI adapter with an 50cm (tested to work on 4K) HDMI cable from the Pi4 to the receiver, and 1.5m (also tested to work with 4K) to the TV.


    Tried “config_hdmi_b.oost=9” in config.txt, but still no 2160p picture ?( Same message from "tvservice -M" HDMI cable is unplugged. Display 2


    Just to verify that the cables work, I disconnected the Pi, and connected the X96 Mini with the same cables, except the Micro HDMI adapter.


    2160p YcbCr 444 8bit 24/25/30hz works

    2160p YcbCr 422 10bit 24/25/30hz works

    2160p YcbCr 422 8bit 24/25/30hz works

    2160p RGB 8bit 24/25/30hz works


    So can we rule out any problem with the cables, receiver, and TV after this?


    I'm starting to think that the HDMI signal from the Pi is to weak (not sure if the receiver amplify the signal)




    Edited once, last by OffLoad ().

  • OffLoad could you try installing raspbian on an sdcard, and use the display configuration tool to switch to 4kp30.

    Does that have the same problem? If so can you also try with hdmi connected to other hdmi port

    (this doesn't work with kodi, but should with raspbian).


    Does 4kp24 work?


    I'm suspecting that the cable is borderline (I know it has worked on another device, but it could be just on the edge of being usable at 4kp30).

    But to begin with see if we can rule out a kodi/LE issue.

  • @popcornmix

    Already tried Raspian Buster, the option for 2160p is in the screen configuration , but when I select 2160p the TV blanks out, with "No Signal" This happens on HDMI 0 and 1. 4kp24 don't work, no 2160P resolutions, just black screen, and bumps back to 1080p.

    So I'm suspecting this is not an Libreelec problem at all, but possible an too weak HDMI signal from the Pi, or the cables (tested 3 different cables)

    Unfortunately there in no option for the Pi4 to ramp up the signal according to the config.txt wiki,


    I will try to switch out the cable from the TV to the receiver, to see if it helps. But it looks like I'm heading over to the raspberry pi forum, to see if someone there have an clue, if no one here could have an solution to this problem ;)

    Will report back in this thread if I can resolve this :thumbup:

    Edited once, last by OffLoad ().

  • The Pi4 has a known issue with HDMI CEC and Samsung TV's. This sounds like another Pi4 HDMI issue that affects some AVR's. If you had an older Raspberry Pi to test, that would eliminate Libreelec and your Sony AVR as the problem.

  • As it's showing same symptoms with raspbian, then it might be worth creating an issue here:

    Issues · raspberrypi/firmware · GitHub


    where the right people should see it.

    Thanks for the link, I'll gonna make an post there :thumbup:

    Just gonna do some more testing with some new HDMI cables, to make sure that is not the problem.

    The Pi4 has a known issue with HDMI CEC and Samsung TV's. This sounds like another Pi4 HDMI issue that affects some AVR's. If you had an older Raspberry Pi to test, that would eliminate Libreelec and your Sony AVR as the problem.

    I haven't had any CEC issues with the Pi4 on my setup.

    I have been running Pi3 on the same AVR, and TV without problem, but Pi3 only outputs up to 1080p, but the case here is that I want 2160p30 to be displayed from the Pi4, if I can't make it do that, it will be more useful for other stuff, 8)