Honestly, no idea. I'll forward the Q to the kernel/u-boot maintainers for thoughts.
Posts by chewitt
-
-
-
vpeter nerd humour, referencing this: https://en.wikipedia.org/wiki/Somebody_…dams'_SEP_field
-
I don't think LibreElec will let you downgrade by default..
Incorrect. It will prevent you from changing the image type, e.g. trying to use RPi5 image on Generic, but it will not stop you from moving up or down within the same image type. As stated already, Kodi doesn't support downgrades (never has, and has no plan to change that) so whatever problems follow are self-inflicted. The nature of how LE is packaged prevents Kodi binary issues, but you will see problems with add-ons. And still this is taking more time that it would take to simply clean reinstall at the older version.
-
.. CE has a large SEP field errected around it -
Copy to /storage/.update and reboot. The updater can update from .tar files or .img/img.gz files.
-
The LE11 codebase is not going to have any more updates so the first thing to try will be updating to a current LE12 nightly to see if newer versions of everything magically solve the issue. If they do not, then (as suggested) we need debug/crash logs with errors in to provide some clues.
-
Poorly encoded media? .. what does mediainfo report for the file. How did you rip it?
-
It will work. You don't need to delete the add-on settings, only the add-on packages (and package cache).
Read: https://wiki.libreelec.tv/support/update .. you are "updating" to an older release.
-
NB: Kodi does not support downgrades; the core OS and Kodi itself will downgrade fine but add-ons (which will be updated to the newer version) do not magically downgrade themselves causing problems.
https://archive.libreelec.tv/archive/ <= So probably easier to just download the LE 9.2 installer, create new install media, and clean install at the older version.
-
-
This describes the BL1 (Silicon) to BL2 (Software) boot flow: https://docs.u-boot.org/en/latest/boar…/boot-flow.html
Once you get to BL2, what happens depends on what the software implements. Amlogic hacked in various recovery mechanisms to support common things that Android STB manufacturers want (and we abuse those to make the box run Linux). However those OEM box manufacturers sometimes tweak the code to suit their own purposes, or simply because they can, or because their developers were simply incompetent with strange ideas. As a result, while the general flow probably follows some common themes, there are enough exceptions seen "in the wild" that you shouldn't assume anything until you see UART logs and/or a dump of the u-boot env configuration.
If vendor u-boot is on eMMC in 99.999% of boxes it will be used. The contents of the u-boot environment (env) will then dictate what happens next. If the env has been modified through boot.scr or s905_autoscript methods it will look for Linux boot files (as dictated by what the boot scripts set) and this remains configured unless a reset is performed (restoring the original env for Android-only boot) or the recovery mode is triggered again; causing it to look for boot.scr or s905_autoscript which can (re)modify the env again.
Your box has an env modified by CE boot scripts to look-for and use CE boot files. Unless you trigger recovery again and tell it to use LE boot files; it continues to look for CE files and fails to find them as CE and LE boot media are (intentionally) different and since the kernels are now also rather different, the boot params may or may not be aligned.
Users frequently assume u-boot scripts are read on every boot and this is not true. Users also assume they can rename files and make it all work, and this is not completely true. Users also very-very-wrongly assume that I have any interest in CE or interest in triaging frankenbox configurations. Sorry to dissapoint..
-
You will need to enable hidden files and folders support before /storage/.update will be visible in the Kodi file manager. It's normally much easier to SSH into the box to run commands to copy files around, and if that sounds like rocket science, it's the kind of science that would be useful to learn; as much as we aim for a GUI experience if you want to start doing downgrades and backups it quickly turns into essential knowledge.
-
I'd recommend using using TVH 4.3 as 4.2 is effectively a dead codebase (no more fixes/changes will be made) and 4.2 is not upgradeable to 4.3 (and 4.4 in the mid-term future, at which point 4.2 will finally lose the 'stable' tag).
Tvheadend documentation is rather lacking .. in the project's to-do list, but it's a long list and there's some bigger items to fix before we get around to that whole heap of fun.
petediscrete or DeltaMikeCharlie .. any ideas?
p.s. There's also the Tvheadend forum: https://tvheadend.org
-
Add-on issues are rarely OS specific but you could prove that by testing the add-on under Kodi on RaspiOS instead of LE. If the issue exists there too you can focus on the Twitch add-on and log issues with the add-on devs via the support thread in the Kodi forums.
I'd also suggest using LE12 to see if anything is different. Development for LE and Kodi has been focussed on Kodi Omega for a while now and even if there's a bug found, the fix will go into LE12/Omega first.
-
Pinned for visibility..
-
I'll probably just add the script (with an edit to L20) and see what issues are unearthed.
-
The DXxxRenderers config probably has no effect as DX display drivers are a Windows thing. Enabling GL should be be the only config item to have impact, though I'm wondering if that truly means GL (only)? as GBM images are using GLES not GL (as shown by logs that heitbaum shared).
