How and where can I fix that? The mini PC provides 2 HDMI ports. I tried both but no difference in behavior.
Connect your preferred HDMI setup. Then execute getedid delete, followed by getedid create on SSH terminal. Reboot.
Posts by Da Flex
-
-
Any more questions, or can I mark this thread as resolved?
-
I also wasn’t able to get the Digi+ Pro working on Raspbian.
Then it's not our fault. Ask at the HiFiBerry forum. Maybe the soldering trick also works for RPi5 (post #4), but we don't know.
-
I think HiassofT is right - it's very likely a hardware issue. Have a look at your Digi2 Pro board. If it has HW 2.1 printed, then you have to solder, or ask HiFiBerry for a replacement:
-
Take another microSD, install Raspberry Pi OS on it, and test Digi2 Pro with it. So we can figure out whether it's a general problem, or just an LE issue.
-
Unfortunately there is no way to change playback speed. You can only adjust the time difference between audio and video. If not already done, disable the "Sync Playback to Display" option.
-
Second line was like this and I keep it:
Codedtoverlay=hifiberry-digi-proPlease use my suggestion. This is what we support:
Config.txt | LibreELEC.wikiwiki.libreelec.tv -
Do you have these two lines at config.txt?
Codeforce_eeprom_read=0 dtoverlay=hifiberry-digiIf yes, and the issue remains, post a log...
Please provide a full debug log.How to post a log (wiki)1. Enable debugging in Settings>System Settings>Logging2. Restart Kodi3. Replicate the problem4. Generate a log URL (do not post/upload logs to the forum)
use "Settings > LibreELEC > System > Paste system logs" or run "pastekodi" over SSH, then post the URL link -
Here is a log file from streaming on a clean image of 13.0 20251117 nightly. Interestingly, the glitch is not present on this version.
Thanks, it has the same errors as seen at post #3, so my theory is wrong.
-
This could be the cause of the issue:
Code2025-11-01 10:48:10.479 T:1208 info <general>: CDVDVideoCodecDRMPRIME::Open - using decoder V4L2 mem2mem H.264 decoder wrapper 2025-11-01 10:48:10.479 T:1208 error <general>: ffmpeg[0x212e50a0]: [h264_v4l2m2m] Could not find a valid device 2025-11-01 10:48:10.479 T:1208 error <general>: ffmpeg[0x212e50a0]: [h264_v4l2m2m] can't configure decoder ... 2025-11-01 10:48:10.540 T:1214 error <general>: ffmpeg[0x209fd8f0]: [deinterlace_v4l2m2m] Could not find a valid device 2025-11-01 10:48:10.540 T:1214 error <general>: ffmpeg[0x209fd8f0]: [Parsed_deinterlace_v4l2m2m_0] Failed to configure output pad on Parsed_deinterlace_v4l2m2m_0 2025-11-01 10:48:10.540 T:1214 error <general>: CDVDVideoCodecDRMPRIME::FilterOpen - avfilter_graph_config: Invalid argument (-22) -
Always test with the latest LE release.
-
I have this 871129219935 grundig IR remote control...
What? Could you share a link?
-
Hm… I'm a bit reluctant to because my current setup works. Why do you think LE13 will help?
Updated drivers on newer Linux kernel.
PS:
Quote2025-11-12 19:50:07.762 T:1129 info <general>: load skin from: /storage/.kodi/addons/skin.xperience1080/ (version: 10.0.0)
Use the default skin to rule out any complications with a custom skin.
-
Should I move all those - besides the newly added <power> - to remote.xml instead?
Yes, basically just to keep remote and major device separated in config files.
-
Check your microSD for errors. You can do that from any Linux PC. You can also copy & paste among microSD cards that way.
-
Thanks, but I actually want to get the shutdown dialog when pressing the power button on my remote control. I just want to power-off when pressing the power-button on the computer.
That's why remote.xml exists as a separate option.
-
I thought Legacy was for NVidia cards?
Generally yes, but the old X11 can sometimes fix issues like this.
-
Same with Generic-Legacy?
