You can clone the embedded Estuary skin folder to /storage/.kodi/addons then modify addon.xml to change the name so it doesn't clash with the embedded version, then mod as you like.
You're also welcome to experiment with webmin via docker, but LE is not a derivative of any other distro and our layout is rather non-standard which normally trips up tools that expect conventional Debian/Fedora packaging.
You can't for two reasons:
a) There is no package manager to install packages like webmin
b) The userspace filesystem is decompressed from SYSTEM on each boot, and is read-only
It's possible to install the Docker add-on and the pull a webmin container, but webmin is going to assume a standard Linux distro with a normal filesystem layout where everything is read-write, so you'll find most (all?) features are non-functional.
Why do you think you need webmin?
Change 'echo disabled > /sys$devpath/power/wakeup' to 'echo XHCI >> /proc/acpi/wakeup' and try again.
I dug out one of my boxes. It was already installed with a working LE 11.0 install, but I updated using the latest LE13 image in my test share and the update overwrites/replaces all the boot files, and it rebooted fine afterwards.
The boxes I have are still running the original pre-production boot firmware as I'm not an O2 customer (or in CZ) so the boxes have never been been updated. Yours probably has been, and may also be a newer hardware iteration; although I believe the only change made over time was a different WiFi/BT module, that won't prevent boot, and if Armbian boots the box can boot LE.
You probably need to do a 'toothpick' reset to ensure u-boot searches/finds and loads LE boot scripts from the SD card. These define what boot files to use, and LE uses different files to Armbian.
The refresh rate is not clear in the PVR stream so Kodi needs to start playback to detect it and then switch to the correct rate.
I would try configuring the resolution whitelist like this https://wiki.libreelec.tv/configuration/4k-hdr
I would also define the PVR fallback refresh rate to 59.94Hz as this appears to be what the streams are using. Right now Kodi tries to play at 25Hz and then switches. I'm wondering if this setting defines the initial rate that Kodi attempts? (not guaranteed, I'm not familiar with the setting or how it works in code). If not, setting the desktop refresh rate to 59.94 (not 60.00) might work better.
Have a play and experiment.
If you read the code you'll find that in lots of scenarios Kodi tests for capabilities and makes code-path decisions based on whether something succeeds (is supported) or fails (is not supported). Both 'errors' are normal and harmless.
# SPDX-License-Identifier: GPL-2.0-or-later
# Copyright (C) 2009-2014 Stephan Raue ([email protected])
# Copyright (C) 2019-present Team LibreELEC (https://libreelec.tv)
ACTION!="add|change", GOTO="end"
DRIVER=="ehci-pci|xhci_hcd", RUN+="/usr/bin/sh -c 'echo disabled > /sys$devpath/power/wakeup'"
LABEL="end"Create that ^ as /storage/.config/udev.rules.d/30-disable-wakeup.rules but ensure you do this via SSH/nano to ensure unix line endings are used (as Windows endings will not work). You can stop/disable and then delete the systemd service file.
Working?
imhotep Please remove "debugging" from boot params as this does not add anything useful and floods the log. Then update to this image: https://chewitt.libreelec.tv/testing/LibreE…h64-12.80.2.tar and run the following commands (share the URL's generated):
cat /sys/kernel/debug/devices_deferred | paste
journalctl | paste
Thx.
There are plans for RK3588 support: https://github.com/LibreELEC/LibreELEC.tv/pull/7864 but Kwiboo doesn't appear to be in a hurry to get things merged. It's taken forever for HDMI support to get upstream and most codecs are still missing, although most boards can software decode a wide range of media.
Share the contents of the /storage/.config/system.d/xhci.service file you created.
Create the custom systemd service as /storage/.config/system.d/xhci.service
Enable with systemctl enable /storage/.config/system.d/xhci.service
Start with systemctl start /storage/.config/system.d/xhci.service
Then check for errors. If you need to make changes and edit the file, run systemctl daemon-reload after the changes.
Aside from the odd /storage location, systemd things work the same as most other distros.
Guessing at the solution wastes time and sucks, so it would help if you posted info on the commands that work to disable it, and other links that helped you arrive at that solution.
You will be able to update to the main LE13 release when it comes, although (as with the original poster) if the board needs Linux 6.14 to support the NIC and the release image is using Linux 6.12 (the current plan) that will cause problems. I'm going to start an internal discussion about moving the Generic image to a newer kernel, but it's a group decision, so not guaranteed.
It's normally faster to backup and restore than clone as less data is being moved, and you avoid issues with disk/filesystems being different sizes.
Kodi binary add-ons might be small but are still built using the LE buildsystem, which 100% does not support compile on Windows.
Are some more likely to be stable than others, due to some development cycle or similar, or is it random?
The devil is in the details of what specifically changed on a day-to-day basis. We tend to queue anything majorly distruptive for the start of the release cycle but in recent years even those have been quite smooth. For context, the family daily-driver RPi5 has been running dangerously unstable sounding "pre-alpha" K22 images for more than a year now without any drama. Hopefully K22 will start lurching towards release soon.
<?xml version="1.0" encoding="utf-8" ?>
<advancedsettings version="1.0">
<loglevel hide="false">1</loglevel>
</advancedsettings>That ^ content will enable debug logging without the OSD.
The current log is /storage/.kodi/temp/kodi.log and previous log is kodi.old.log, there are kodi crashlog(s) in the same folder. The current and previous log are rotated with each reboot so they are persistent but not preserved. Crashlogs are preserved.
You cannot build LE images natively on Windows and since an older Ubuntu release (16.04/18.04) is required to build older LE images it's not possible to use WSL either. Virtual machines are the only option.