If you created the /run xorg.conf and restarted the service the journal log should show Xorg starting in debug mode, which will generate a load more output and it would be useful to see that.
I updated the image in the share (Xorg based) to include a couple of things .. but I'm making random guesses.
Not a debug log. Not a complete log. So hard to comment.
Are you using 4K "certified" cables? .. 4K 10-bit media (and often HD audio) combined will be pushing higher data rates on the HDMI cable and dropouts are a textbook symptom of a cable that can't sustain the required data rate.
Is this something I should be worried ?
No, all harmless.
LE doesn't use /etc/fstab although it exists because some tools check for its existence.
Are there any stray .mount files in /storage/.config/system.d ?
Section "Device"
Identifier "Nvidia card"
Driver "nouveau"
EndSectionIn the Xorg image, create /storage/.config/xorg.conf with ^
XORG_DEBUG="-logverbose 6 -verbose 6"Also create /run/libreelec/debug/xorg.conf with this ^ and then systemctl restart xorg.service to get debug output.
Also run journalctl -xe windowmanager.service to perhaps see more about what the failing dependency is?
Official:Forum rules/Banned add-ons - Official Kodi Wiki
If you want support, come back with a full clean Kodi debug log showing no pirate crapware installed.
Probably this https://github.com/LibreELEC/LibreELEC.tv/pull/9671
in which case grab the latest nightly from https://test.libreelec.tv/ .. both LE12 and LE13 nightlies have the fix.
Fresh image using OpenGL/Xorg: https://chewitt.libreelec.tv/testing/LibreE…-12.80.1.img.gz
If OpenGL ES vs. OpenGL wasn't the issue, I'm out of ideas.
What happens if you run umount /etc/issue ??
It's a 2.4GHz wireless (but not WiFi) device that pretends to be a keyboard then. It's most unusual to see issues with them as they are simply a keyboard device to the OS. Share the output of "lsusb -tv" and the URL from "pastekodi" please.
RPi5:~ # df
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs 4085920 16 4085904 0% /dev
tmpfs 1648976 17904 1631072 1% /run
/dev/nvme0n1p1 524008 154160 369848 29% /flash
/dev/loop0 139264 139264 0 100% /
/dev/nvme0n1p2 228336223 3052383 225279744 1% /storage
tmpfs 4122400 0 4122400 0% /dev/shm
tmpfs 4122400 16 4122384 0% /var
tmpfs 1024 0 1024 0% /run/credentials/systemd-journald.service
tmpfs 4122416 0 4122416 0% /tmpIt's not like that here (on this RPi, or any other device I'm using). Post evidence to support and explain what you're seeing.
Please add "ssh" to boot params so the daemon is forced to start on boot and you can access the console without using textmode, which also disables a bunch of stuff in the OS and probably prevents Kodi from running. Then "pastekodi" to get the system boot and current Kodi log or Kodi crash log, if any?
NB: I suspect OpenGL ES support for nv40 cards might be rather lacking, so I'll tweak the image to use OpenGL instead.
How is the remote working? .. IR sensor added to RPi board, CEC, BT, USB widget that pretends to be a keyboard?
Boot with the TV on, then SSH in and run getedid create to capture the EDID data from the HDMI connection to file and configure boot to use this so it thinks the TV is always on.
What have you set (or not set) in config.txt ??