Posts by HiassofT

Set the GUI resolution in display settings to 1920x1080 and configure the whitelist - see https://wiki.libreelec.tv/configuration/4k-hdr

so long,

Hias

Quote from D4rk-M4tt3r

No error messages, commands seem to work as execute, but this doesn't fix the issue:

Note that you have to reboot after "getedid delete", otherwise the old edid will still be used. "getedid delete" followed by "getedid create" without reboot in between is a no-op.

so long,

Hias

Quote from ian_j

If I backup my originals of the files you linked to and I get major issues can I just copy over my originals again?

Yes, this will work

so long,

Hias

Scratch that, CONFIG_SND_SE6X would be the wrong driver, so recompiling won't help. The problem is that the Serenade III isn't supported (only the Serenade).

so long,

Hias

This specific soundcard isn't supported in LE (or most other linux distributions).

There's a driver for it in linux https://github.com/torvalds/linux…/se6x.c#L44-L45 but it conflicts with all other Oxygen and Virtuoso soundcards https://github.com/torvalds/linux…onfig#L825-L827

Hence we and other Linux distros can't enable it - but you could build LE yourself, with CONFIG_SND_OXYGEN and CONFIG_SND_VIRTUOSO disabled in projects/Generic/linux/linux.x86_64.conf and CONFIG_SND_SE6X enabled instead.

so long,

Hias

Post a full log when it happens again, using the latest LE12 nightly build (ssh in, run "pastekodi" and post the URL). It could be anything from a connection problem to power supply issue or something else - hopefully the log will give more info.

so long,

Hias

Quote from HarryH

If you currently doesn‘t have a dtoverlay=hifiberry … line in your config it seems that the overlay was instead loaded from the HAT EEPROM. Please keep in mind, that in future kernel versions it could be possible that this overlay in the HAT EEPROM will be outdated. Then you will need a matching dtoverlay line for your hifiberry.

RPi folks recommend to store the name of the overlay in the eeprom, not the actual overlay itself, to avoid kernel version issues.

Unfortunately Hifiberry did the latter (and OFC the overlays became incompatible with RPi5) but fortunately this could be fixed up with hat_map entries (see commit https://github.com/raspberrypi/li…fdda902104650b3) so the hifiberry cards should work fine now without any config.txt trickery.

so long,

Hias

Please test with RPiOS and the latest rpi-update kernel. If it doesn't work either create an issue on the RPi kernel github https://github.com/raspberrypi/linux/issues

BTW: the hifiberry-dacplushd overlay doesn't seem to have a "slave" option and the "slave" option of the hifiberry-dacplus overlay won't work on RPi5 so there are now two separate overlays for the (non-HD) DAC+, hifiberry-dacplus-std and hifiberry-dacplus-pro

so long,

Hias

Use the other HDMI port on your RPi5 (HDMI 0 / HDMI-A-1), CEC only works on this port ATM

so long,

Hias

Quote from Veda

And I do see the thunderbolt icon at the power up, but it does not seem to be present after that.

That's because the thunderbolt won't show up with the new graphics stack (i.e. while LE is running) so there won't be any visual notification in case of undervoltage or over-temperature, undervoltage is currently only logged to the kernel/system logs.

so long,

Hias

Thanks for reporting back and glad you got it working!

so long,

Hias

Veda BTW: your RPi is running on fumes, it would be a good idea to replace the power supply (the official one is highly recommended) as otherwise you may run into unexplainable occasional issues.

RPi throttled=0x50005
...
Feb 27 18:26:05.050964 LibreELEC kernel: hwmon hwmon0: Undervoltage detected!

so long,

Hias

Yes, there are a couple of options:

The easy one is to throw in some money and buy an HDFury Dr HDMI or VRROOM, then you can easily adjust the EDID via it's web interface (or app). Those devices aren't exactly cheap but I really like my VRROOM and it can do a ton of more stuff as well (I mainly use it to debug issues though).

You can also dump the EDID and then edit it eg with the AW EDID Editor https://www.analogway.com/emea/products/…aw-edid-editor/ - either dump the EDID of the TV and add the additional audio formats of your AVR or dump the EDID of your AVR and fix-up/add the HDR modes of the TV (the former should be easier).

Or you could simply replace the EDID with some default one that about matches your TV/AVR - HDFury has a nice EDID collection on their website https://hdfury.com/tools/HDfury_EDID_collection.zip (most edids are in the "Vertex EDID Tables" folder).

Either way, first ssh in and run getedid create - this will save the current EDID(s) to /storage/.config/firmware/edid/ and install them permanently. It'll print the names of the connected HDMI ports (usually HDMI-A-1) and you should now have edid-HDMI-X-Y.bin (eg edid-HDMI-A-1.bin) files in the .config/firmware/edid folder.

Copy that file over to your PC, edit it and copy it back or just replace it with some generic EDID (make sure you don't change the name!) and then run create-edid-cpio to also update the early-stage EDID file with the one in the .config/firmware/edid folder (repeat that if you need or want to change the edid).

If you later want to completely get rid of the EDID override simply run getedid delete

so long,

Hias

Your AVR (or maybe your TV) doesn't report support for HDR in the EDID - Kodi Omega now checks for that and will only output HDR if it's actually supported by the TV.

Try connecting the RPi directly to the TV and test if that works. If yes, the AVR is the culprit, if no it's the TV and you may have to adjust some settings on your AVR (or TV).

Make sure you power off the RPi before changing the cabling as kodi will only check the display capabilities on startup.

You can also verify the display capabilities with edid-decode /sys/class/drm/card0-HDMI-A-1/edid , you should see both a "Colorimetry Data Block" and a "HDR Static Metadata Data Block" like that:

 Colorimetry Data Block:
   BT2020YCC
   BT2020RGB
 HDR Static Metadata Data Block:
   Electro optical transfer functions:
     Traditional gamma - SDR luminance range
     SMPTE ST2084
     Hybrid Log-Gamma
   Supported static metadata descriptors:
     Static metadata type 1

Kodi will also show that info in it's log (the "display-info" lines), but your log doesn't contain any HDR info and none of the colorimetries are supported, so it seems the AVR only sends an empty colorimetry block and no HDR metadata block at all.

so long,

Hias

The fix is in our latest nightly build: https://test.libreelec.tv/12.0/RPi/RPi4/…-dd2ecfa.img.gz

morfikcould you please test it?

so long,

Hias

Nightly build with the fix is here: https://test.libreelec.tv/12.0/RPi/RPi4/…-dd2ecfa.img.gz

mokkurkalve could you please test it?

so long,

Hias

Yes. The issue has been fixed now in the RPi kernel https://github.com/raspberrypi/linux/pull/6110 and I'll add that to LE in the next few days.

so long,

Hias

You have to make sure that the voltage stays well above 4.8V all the time.

If it drops below about 4.65V you'll see the undervoltage errors in the log, but USB devices and other stuff running from +5V may already started to work erratically at voltage above that - the minimum spec for USB and other +5V devices is typically 4.75V min.

See also the power supply section of the official RPi documentation https://www.raspberrypi.com/documentation/…ml#power-supply

Note that the current draw / power consumption is highly dynamic and you'll get issues if the voltage drop lasts for a few milliseconds or shorter. Also note that lots of power supplies don't cope well with those dynamic loads, it's essential that they have very fast regulation.

You have to hook up a scope to +5V/GND at the RPi PCB to check that, using a multimeter is useless as it's way too slow.

so long,

Hias