it seems impossible to unmount the /flash device because it is busy. Can it be the source of my problem ?
Our shutdown script waits for a while for running processes to exit gracefully, but there's a timer running and if the timeout value is reached it kills them and this ensures nothing is busy and the filesystem can be unmounted. It's more likely to be the BIOS on the device not responding properly to a power-state change; assuming it's an x86_64 device. What hardware is this?
"No WiFi" requires an explanation of what chip is inside the box before anyone can comment.
Nope, official updates are normally done using .tar files as those are faster to unpack/update from. The .img.gz also works but needs an extra step. Both have identical KERNEL/SYSTEM and .dtb files inside.
I did a little research on the HK forum and we need to construct a new device-tree overlay that adds nodes for the pcm5102 chip and audio card routing. Update to this file (again, it's been updated):
https://chewitt.libreelec.tv/testing/LibreELEC-AMLGX.aarch64-11.80.0.tar
Then run the following from the SSH console:
mount -o remount,rw /flash
cp /usr/share/bootloader/meson-gxbb-odroidc2-hifishield.dtb /flash/
sed -i 's/meson-gxbb-odroidc2/meson-gxbb-odroidc2-hifishield/g' /flash/extlinux.conf
mount -o remount,ro /flash
reboootThis should switch u-boot over to the hifishield device-tree file, and then we discover how accurate my blind guesswork was?
Please share URLs from "dmesg | paste" and "aplay -l | paste" and "aplay -L | paste" so we can see if anything happened.
To be clear, I'm not expecting audio output in Kodi yet, as I suspect audio mixer routing changes are required too.
The output of "pastekodi" includes the system log (dmesg) which is where we can see the drivers probe and load firmware (or not) which is more useful. Kodi debug logs don't contain any of that.
It's beest to report that kind of problem to the add-on author in the Kodi forums. It's not something we're responsible for (and thus not our area of expertise).
I've added the driver to this image: https://chewitt.libreelec.tv/testing/LibreE…h64-11.80.0.tar
I suspect the driver is only part of the puzzle though. I believe there are device-tree overlay and perhaps mixer changes too. One step at a time though.
EDIT: forgot to sync the image .. Give it 10 mins before downloading.
Martin threatening to do kernel work sounds awesome! If there is stuff to test I am happy to do it.
Martin pushed an updated kernel branch: https://github.com/xdarklight/lin…n-6.7-20231203/ - I'm not seeing anything obviously new in terms of commits, but it's an excuse to do a rebase for AMLGX sometime soon.
I'm with MatteN on leaving the fancy enhancements turned off (with my 65B7V) unless you like movies to look like camcorder footage. It does sound most like a software issue on the LG side though.
Worst case you could run Kodi natively: https://kodi.wiki/view/HOW-TO:Install_Kodi_for_webOS
If you can run CE from USB then you can run LE, but you will need to trigger the recovery boot process (same as installing CE for the first time) else the box is configured to look for CE boot files which are different to LE files. You'll need to repeat that each time you flip between the two OS.
abws update to https://test.libreelec.tv/12.0/Amlogic/o…droid-c2.img.gz (wget to the /storage/.update folder and reboot) and then update the repo again. We switched ARMv8 compatible boards to "aarch64" so "arm" add-ons are no longer being built and pushed to the repo - although there was a config error in the change so the AMLGX image remained on arm until last night. If you cross-grade to aarch64 the repo should exist.
Current LE images should boot from USB in addition to SD cards, but current LE images run kernels that don't have drivers for the i2c tuners found in Android boxes of that era (USB ones might work, but not i2c). Older LE images only support specific boxes (not yours) and CE hasn't supported GXL boards for some time either. In short.. 
I'm not sure what a Home Hub is? but if something is connected between the Pi and the TV, remove it and connect them direct to prove the connection works as expected without it. If it does, you can point fingers at the Hub device. If not, I would try a different HDMI socket on the LG as sometimes TVs are preconfigured for a certain content type on certain sockets. If that makes a difference: a) you have a workaround, b) you can point fingers at the TV firmware. LE does not otherwise send any HDMI content-type signalling that would cause the TV to detect/change something so there is nothing to adjust. The sole exception is when HDR media is being played, when we flag the Cinema (not Game) HDR profile. There is no equivalent flagging for non-HDR modes.
That output on the UART console means there is no bootloader on eMMC, which is a good thing as you can safely experiment with different GXL "board" images (see https://wiki.libreelec.tv/hardware/amlogic) on an SD card to see if anything boots. The (limited) GXL images we have are for VIM(1), Lafrite, LePotato. You can probably try the VIM2 GXM image too as GXM is a GXL derivative. If anything boots, let us know.
tomaszc Thanks for the tip-off. AMLGX images should have switched to aarch64 (not x86_64) bakck in October but something was missed. This should fix that when merged https://github.com/LibreELEC/actions/pull/71 .. I rarely use the official AMLGX releases (as I have my own) so hadn't noticed 
I've edited your post. If users want to install torrent clients on their HTPC the use-case is obvious and not something that we are keen to have discussed in detail in this forum.
Home > Add-ons / LibreELEC Add-ons / Audio decoders / SACD ISO support
IIRC this ^ also provides DSD file support to Kodi (so no need for MPD) though this is not referenced in the add-on info text. If you can confirm I'll send a change upstream to add mention of DSD to the add-on.
This is not currently possible using the LE11/LE12 Generic (GBM) releases as Kodi doesn't support 90º rotation with GBM. However if you run the Generic Legacy (X11) version I believe it will be supported.
Google research on "pcieport aer corrected error received" hints at power management on the NIC device, and a few forum posts and such recommendations adding "pcie_aspm=off" to kernel boot params in /flash/syslinux.cfg .. remount the partition rw using "mount -o remount,rw /flash" .. there are other options to perhaps experiment with once you start reading things.
