Posts by rkershenbaum

    I think you should try that. We have reports on the forum that different HDMI ports act differently. Usually the first HDMI port of the TV is the most capable one.

    This led me to the solution. See above.

    Only downside is that the AVR's OSD doesn't display on the TV, since it's connected to the unused (except for ARC) port on the TV.

    So it would be slightly preferable to go back to the original setup, with he Pi connected through the AVR -- if I can get 4k60hz that way. I'll try it with the new HDMI 2.0-certified cables when they arrive.

    Ok...My AVR is plugged into HDMI port 2 on the TV -- the ARC port. I plugged the Pi into HDMI port 1, and the TV detected it as a "PC". But I was able to go into the "Source" menu on the TV and change the type to "Home Theater System". That allowed me to keep the calibration settings that I want. That setting appears to persist across a boot or power cycle of the Pi. So all good so far.

    However, Kodi still doesn't show the 2160x3480 60 Hz option in the Whitelist settings -- only 30 Hz. That may be due to the cable I'm using. (It's pretty new, but I'm not sure it's HDMI 2.0 certified.) I'll try again with the HDMI 2.0-certified cable that I have on order. It should be here in about 10 days.


    Problem solved -- I think!

    I enabled "Input Signal Plus" on both ports in the TV settings, and rebooted the Pi. Now it goes to 2160X3480 60Hz in Kodi.

    So, the solution is:

    1. Connect the Pi's HDMI port directly to HDMI port 1 on the TV.
    2. Connect the AVR to HDMI port 2 (ARC port) on the TV and enable ARC on the AVR and TV.
    3. After the TV detects the Pi as "PC", open the "Source" menu on the TV and change the type to "Home Theater System".
    4. Reboot the Pi and add 2160x3480 60Hz to the Whitelist in Kodi.

    Thanks again for all the input! You guys are the best!

    Maybe this dirty hack is the only option:

    https://eu.community.samsung.com/t5/tv/turn-off…ut/td-p/7626071

    Do you have already checked, if you maybe can disable the auto detection and preset/force the mode to "Standard" (non PC mode) of the HDMI port before you connect the HDMI cable? Some Samsung TVs are said to have this option.

    Good thought. But the port doesn't even appear in the "Source" menu until a device is plugged into it. So I don't see any way to set the port to "Standard".

    Apparently, they've tried to make these TVs idiot-proof, but that comes with restrictions.

    ARC is only necessary for the connection TV -> AVR/soundbar, to provide the sound from TV back to the sound system via HDMI. So reserve that port for your AVR, if it also supports ARC. Your RPi doesn't use that kind of connection, so you could use another HDMI as well.

    That makes sense. To switch to a different device (e.g. Bluray player) we'd need to switch both the TV and AVR inputs. We could probably live with that, since we do it only rarely.

    The bigger problem is that the TV detects the Pi as a "PC" when it's directly connected. I've found TV calibration settings that greatly improve the picture quality, but those aren't available in "PC mode". I haven't found a way around that.

    Only one port on my TV uses ARC, so I'd need to use that port if I connect the Pi directly. Also, the TV detects it as a "PC" and restricts the calibration options I can use. There may be a way to circumvent that, but I haven't found it. (Anyone with a Samsung TV know?)

    I'll try new cables first, when they arrive, and report back.

    In the meantime, I found the recommended settings in the LibreELEC Wiki, and applied them:

    https://wiki.libreelec.tv/configuration/4k-hdr

    Most of my content is 1080p, so that's what the Pi is now sending to the TV, and the TV is doing the 4k upscaling. I don't even know if I have any 4k 60hz content. So all is good for now (but I do want to see what happens with the new 4k-certified cables).

    Thanks to everyone for the comments and suggestions!

    I think the whitelist is loading HDMI modes from the current display, but the older EDID is still in use. Probably your AVR is old, and has a problem with 4K modes.

    Could be. The receiver is, I think, a 2014 model. However, the specs say:

    This model will support HDMI 2.0 connectivity. It supports 4K Ultra HD 50 Hz/60 Hz signal pass-through to output motion-smooth high definition videos.

    It also supports RGB, YCbCr 4:4:4, YCbCr 4:2:2 as well as YCbCr 4:2:0 video signal for more vibrant and lifelike images.

    I was beating my head against a wall trying to get my system to go to 4k 60hz mode -- but I finally found a solution (I think).

    I'm running a Rpi5 with LibreELEC 12.1. Its HDMI port connects to a Yamaha RX-A740 receiver, which in turn connects to HDMI Port 2 on my Samsung UN75TU7000 TV. That port has "Input Signal Plus" enabled. The TV correctly detects the receiver on that port. However, the Kodi settings did not offer any 4K refresh rate higher than 30hz. Same in the Kodi Whitelist settings -- no 3480x2160 refresh rate above 30hz shown. I have the TV in "Movie" mode (with additional tweaks), which yields the best picture quality.

    Today, I connected the Rpi5 HDMI port directly to the TV's HDMI Port 2. Immediately, the TV detected it as a "PC". When I opened the TV settings, the only modes offered were "Entertainment" and "Graphic" -- but I want "Movie" mode. Going back to Kodi, though, I now saw the 60hz option available -- so I whitelisted it and changed the refresh rate.

    Then, I reconnected the Pi through the receiver, as per normal. The refresh rate stayed at 60hz, even across a boot. It disappeared as an option in the Whitelist settings, but that doesn't seem to have mattered. (Unless Kodi is showing 60hz, but really using 30hz....?)

    Hope this helps someone in the same situation.

    This is not specifically related to the USB wired Ethernet driver problems, since it also occurs with the built-in wired and wireless interfaces (without a USB network interface installed). But I also opened a ticket on the UI hang issue here:

    [BUG] After manually switching network interfaces, UI hangs for several minutes · Issue #8669 · LibreELEC/LibreELEC.tv
    Describe the bug After manually switching network interfaces, the LE user interface hangs for about three minutes How to reproduce Steps to reproduce the…
    github.com

    I know this isn't the highest priority problem, but just to keep it in the queue, I opened a ticket here:

    [BUG] LE12 on Rpi5 - RTL8153-based USB3.0 to wired ethernet adapter doesn't come up across a boot · Issue #8648 · LibreELEC/LibreELEC.tv
    Describe the bug RTL8153-based USB3.0 to wired ethernet adapter doesn't come up across a boot. It does not appear in Settings/LibreELEC/ Connections.…
    github.com

    Update: I still have a RTL8153 adapter, so I tested it on an Rpi5 with unmodified LE 11.0.6 and with the LE 12 nightly-20240222-96ea547.

    On the official LE 11 instance, the RTL8153 adapter came up automatically across boots and worked as expected.

    On the LE 12 nightly, it required unplugging and replugging to come up following each reboot. Howver, unlike the AX88179 adapters, it did retain its settings (connect-automatically=off, static IP address, etc.) across a boot.

    So the failure of the RTL8153 adapter to activate automatically across boots seems to have been introduced in LE 12. (I can live with this, since I don't use it all the time.)


    As expected, the AX88179 adapter didn't activate on either unmodified LE 11 or unmodified LE 12, even after unplugging and replugging.

    Unless I've screwed something up again (which is always possible), the Rpi4 and Rpi5 seem to behave differently. On the Rpi4, the eth1 interface comes up automatically after a boot or power cycle -- but loses its settings. On the Rpi5, the interface does not appear after booting, but will appear after unplugging and replugging the adapter, or after issuing "ifconfig eth1 up".

    Ok...playing around with this some more...

    I can get the eth1 interface to come alive after a reboot by unplugging it and plugging it back in. However, it loses all its settings, and defaults back to "connect automatically" and "dhcp". I want to use manual static IP addresses on both interfaces, and I want the eth1 interface to not connect automatically. When I want to use it, I will disable the eth0 instance, and enable the eth1 instance. (As I've mentioned, this results in a 1-5 minute UI hang.)

    This is progress, though....