chewitt maybe these files stay somewhere on the server and you could share?
I use my own images for testing, not nightlies, so I don't have old images anywhere and the current test server holds one or two days files and then deletes them. I also have no stability issues (within the normal range of what works/doesn't-work with the vdec) so your problems are probably a skin or some add-on not being happy about the recent Python 3.9 bump in master.
48Hz movies are certainly bad enough.
No TV panels have native modes at that refresh though, so you won't see it advertised via EDID or used, unless you forced it somehow and then the bad results are entirely your own problem.
Look at the overlays configuration in cmdline.txt for the LE 9.2.8 image and replicate that in boot params with the other distro. If the kernel versions match you can take our overlay files too. If they don't .. the sources for the overlays can be found in our repo and you'll have to compile them to match the kernel the other distro is using.
Amlogic G12B hardware (inc. VIM3) has working H264, working 8-bit VP9 and working but imperfect HEVC decoding in the LE codebase and no support for 10-bit media or encoding. I run zero testing with conventional desktop OS like Ubuntu so cannot speak for how well our patchset might work in browsers or with WebRTC applications.
https://github.com/LibreELEC/LibreELEC.tv/ <= all sources (URLs or patches) are clearly listed here. If you want proper support and assistance with the upstream codebase I'd suggest you reach out to the Amlogic kernel maintainers at Baylibre who authored most of the drivers - who would love someone to fund more man-hours of development time so they can add more functionality and finish/polish features.
The Slice DAC requires a device-tree overlay, but this is pre-configured in the LE 9.2.8 'Slice3' image, so what image are you trying to use?
The AMLMX image is more POC than usable. Most of the boot workflow is still rough/broken or being discovered (more u-boot archaeology needed) but if you know enough about LE boot processes and have UART cables attached then it's not too hard to bodge something and get something booted. S802/S805 should get Kodi up. S812 will boot but 8/10 boots will result in CPU stalls (disabling CPU cores to make it a single core device solves that so but there's been no Eureka moment yet). There's also no vdec at the current time. Otherwise Linux 5.17-rc4 boots and generally things sort of work. You're welcome to play around with the image, but don't expect too much.
Put me on the list for wanting tftp support.
Mainline u-boot already supports it (all the Amlogic boards in kernel-ci boot that way) so you should be able to write u-boot to SPI and boot the device (replacing petitboot). I have no personal experience with it so can't guide you, but it should be do-able.
emveepee I did some test boots from an SD card yesterday using the image in my web-share (5.17-rc4 and u-boot 2022.01) and it worked fine from a boot perspective. I'd recommend getting an emmc module; they're faster and more reliable than SD cards.
Τα ελληνικά σου είναι καλύτερα από τα δικά μου ελληνικά 
If there were changes, great work.
No changes in nightlies
Okay.. I dropped that from the USB-C addition patch. That patch is a placeholder at the moment as (according to Neil) there's a polarity issue not handled in the fusb302 code that prevents the driver from probing. It's greek to me, might mean more to you?
If media is scraped into a local library (sqlite) database you can query the database. If you Google sqlite3 and Kodi you will find queries on various forums and reddit that can give you the basics for exporting data. NB: It's easier to look in the GUI of course.
I'm assuming Janitor is an add-on? (never heard of it before). If yes, there is probably a user-support thread in the Kodi forums.
do i need to do a clean install of my box due to the above issue ?
You can update using the .tar file or clean install. Clean install is probably quickest.
I'm looking for ICC profile support and HDR to SDR mapping features.
I think Kodi and kernel have plumbing for ICC but the driver for tonemapping hasn't been written yet so that's not supported. Otherwise the image should work with the "box" image all S912 boxes are pretty similar.
I pushed an unclean set of images to the webserver by mistake where Kodi is built against python 3.8 but the OS has python 3.9 so Kodi fails to start. Those images have now been replaced with some corrected ones. The Python 3.9 change is fresh so I won't guarantee all add-ons have been published to the LE repo yet (the bump was in the last 24h). I have no interest in maintaining Matrix images as I have limited time for testing and Nexus better supports the Amlogic codebase.
I've test installed on a C2 and Ethernet works fine for me, see http://ix.io/3PBJ. The u-boot patch you found is still being included pstream, see https://github.com/chewitt/u-boot…ot.dtsi#L32-L36 - and the unknown boot command line is harmless, I'm not aware of any hardware issues with C2 other than the USB ports needing a hack to prevent the driver from autosuspending (which is in my kernel image).
I did a quick diff compare of the two Armbian patches and the first one you've linked is an early draft of Zero support based on a mix of the SEI510 and U200 device-trees. The second one looks like the final merged version which contains some differences to regulator naming and ensuring HDMI has power from boot.
G12A and G12B silicon has an mmc bug that requires a workaround/quirk, but that's in the g12-common dtsi so all devices will inherit it. The issue hits SDIO wifi in some older kernels but has been resolved upstream for a while now. See the history for drivers/mmc/host/meson-gx-mmc.c and note that I have some patches in my tree 5.16.y tree that are not upstream (the 270º patch is allegedly not needed but seems to benefit non-BCM modules like QCA9377).
NB: I have the impression that Armbian support for Amlogic isn't the best due to everyone on staff deliberately trying to look the other way and avoid the noise from unsupported "TV Box" users and board vendors not funding support. The net result seems to be a mixed bag of patches from various places and a generic defconfig. I respond to Q's when asked but I don't follow their development.
