Can you also add this device /khadas-edge2/ in Build section on that Branch
No, because I don't have an edge2 board and don't need to waste CPU time bulding images for it that I won't use. Things are stlll a long way from the point where I have any interest in end-user testing.
balbes150 There is a DRM format/modifiers problem when Kodi (GBM) detects/uses a 10-bit GUI plane. This is an ugly hack to run Kodi under GBM (not Wayland): https://github.com/chewitt/LibreE…d49a27fd99c3bd4.
Only tested on RK3588 .. I didn't check much yet.
It appears to show some kind of online stream being played, but it's not a debug log so there's nothing useful to look at.
There are traces of pirate shitware in the logs. I lost interest at that point.
My hunch is that the 2nd HDMI is some sort of DP in disguise...
Most modern/cheaper Intel boxes derive HDMI from DP using an LSPCON chip as this multi-purpose (DP/HDMI) chipset is cheaper to implement than using dedicated DP and HDMI transceivers. LSPCON chips and their Windows oriented and buggy firmwares have been "the gift that keeps on giving" for problems since they first appeared in NUC devices about a decade ago.
I attach some logs
Pastebin (not attach) a proper Kodi debug log.
BTW: no control with the Samsung TV Remote Control is working only by USB-Keyboard
Support for HDMI-CEC is normal in Raspberry Pi and similar ARM SoC hardware boards, but it is rare to find it on x86_64 devices. You can check with the manufacturer, but I doubt the hardware supports it so no need to share logs.
Is LE installed to (and booting from) the internal drive or are you booting from a USB stick? - If booting from a USB stick are you using "run" or "live" mode? .. because "live" does not provide persistent storage so settings will be intentionally wiped/reset on reboot.
NB: Kodi is a GUI driven app. Connecting it to a TV/monitor for 2 mins to configure things as you need them to be is usually easier than trying to shortcut things from the console.
Let's go back a few steps. What hardware are you trying to boot, and how are you booting it?
mglae That's a solution to a different problem. There are Rockchip vendor tools that allow you to flash an [Android ROM] image direct to eMMC using a USB cable, but they use proprietary packging so our "dd" based ".img" format cannot be used with them.
I'm not aware of any tools to convert our img to the format used with vendor flashing tools. You can remount the boot partition with mount -o remount,rw /flash to edit extlinux.conf, but we are using u-boot that supports boot=UUID and extlinux.conf is using UUID so that should work as long as you don't have SD/USB media created from the same image attached (as those will also match the same UUIDs). You shouldn't need to change the conf.
I need to use LE12 , is there any solution to fix this problem?
You either continue using the LE13 image, or self-build an LE12 image with a current/newer kernel that supports the GPU.
You can disable auto-update.
Which is irrelevant as my builds are dev builds that do not support auto-updating.
I've set one via the UI and I've no idea where it's been stored; but not in cleartext in guisettings.xml so I'd guess it's somewhere in the MySQL DB that my install uses, and right now I don't have the option to go poking around in DB tables to check. However, if it can be set via guisettings.xml the format is probably be the same as the webserver username, so crib that and experiment. If no difference, revert the change and no harm is done.
There are no config.txt or cmdline.txt options to disable video output. You can disable the entire DRM connector, but that disables audio too as audio capabilities are derived from EDID/ELD data that depend on an active connector.
Selecting passthrough audio does not disable video for an HDMI port; hence that is not documented.
Did you attempt the force_turbo and core_freq config.txt changes as popcornmix suggested?
When you enable the webserver in the UI, a webserver password must be set first, else it will not enable.
Third option is to use one of your images, since they do contain the driver. But that means using a dev version of le, and very frequent updates.
Even if we bump Kodi versions and that contains an API bump that requires an add-on version increment, the existing "dev" image will remain working in 99% of cases. You're the person who dictates how often updates are done.
The standard thing to try with CEC issues is "turn off and disconnect everything, go have a cup of tea or wait a while, then reconnect and power it all back on again" .. but if that doesn't resolve the issue I wouldn't expect any development against that codebase.
