The NTP pool being set to de.pool.ntp.org suggests you've configured some things in the settings add-on. Can I ask you to take a spare SD card and do a clean install (don't set anything for NTP, etc.) then check the files again. I'd like to ensure this is a repeatable problem with the default configurations we have.
Posts by chewitt
-
-
Had a typepo.
^ It seems to be a recurring issue
-
I know that upgrade from 9.x to 11 wasn't supported and clean install was required but is it also the case with every future update like recently released 11.0.1? My 11.0.0 won't autoupgrade to 11.0.1?
It was undesirable to direct update from 9 > 10/11 due to the Python 2 > 3 changes in Kodi which break add-ons. There is/was no issue with updating from 10 > 11 and in the future from 10/11 > 12. At the moment auto-update requires something to be manually set on the back-end infra else the OS doesn't prompt and we (staff) frequently forget to set it giving the incorrect appearance of it being broken (the process is, but not the code). We plant to move that logic client-side in LE12 to eliminate the forgetful humans from the process. I enabled auto-update for 11.0.0 > 11.0.1 yesterday for those who didn't already bump.
-
If you think copy/pasting a URL is complicated ..
-
In the absence of any technical data to prove what you played (and whether that format is supported) .. we can only make blind guesses
-
Code
video=HDMI-A-1:1920x1080M@60Add ^ that to the line of kernel boot params in syslinux.cfg and it should force output on the HDMI connection instead of the LVDS? connection to the internal screen.
-
What's the content of "cat /storage/.cache/timezone" ??
-
Submit an enhancement request to the add-on maintainer(s) via the Kodi forum support thread for the add-on.
-
Any ideas on what I could try ?
Sharing debug log-files, else all we see is another user expecting us to divine the problem using magic and we'll go find someone else to help.
-
can someone make the generic to a img file? impossible to get 11.0.1 online to use the tar file
Did you think of looking in the same folder to see what other files are there?
-
As per release notes; the AMLGX image is not perfect and will not be for all users. I'm not too interested in bug reports because I know the hardware decoders have bugs, there is nothing I can do about that, and comparisons with CE are meaningless since the codebase has 0% kernel and driver code in common.
-
Code
HDR format: Dolby Vision, Version 1.0, dvhe.08.06, BL+RPU, HDR10 compatible / SMPTE ST 2094 App 4, Version 1, HDR10+ Profile A compatibleDolby Vision = No
HDR10+ = No
HDR10 = Yes
HDR = Yes
TL/DR; ^ the static formats are supported, the dynamic and proprietary ones are not. I'll also caveat that right now LE/Kodi (on Linux) have reached the "HDR support v1.0" milestone, and maybe v1.5 on RPi4 which has more plumbing for colourspace and bit-depth wired up. HDR support still needs more things in the Linux kernel to be agreed upon, and should hopefully improve with related planned changes for Kodi Omega (v21).
-
Code
video=Composite-1:720x480@60ie <= NTSC video=Composite-1:720x576@50ie <= PAL^ add one of those those to boot params in cmdline.txt; notice that PAL gives higher resolution than NTSC so if the TV supports it, use PAL.
LE11 will have better compatibility with add-ons. LE 9 is starting to show age now.
-
I've enabled auto-update earlier so you should be prompted now too..
-
Go into the LE settings add-on, change to manual update, select 11.0.1, then later (after download/reboot) switch back to auto again. No need to reinstall between minor version bumps.
-
Here are two test images for RPi4 and Generic (GBM) that contain connman/iwd with latest patches/changes (HEAD):
https://chewitt.libreelec.tv/testing/LibreELEC-RPi4.arm-11.0.1.tar
https://chewitt.libreelec.tv/testing/LibreELEC-Generic.x86_64-11.0.1.tar
If others can confirm things are resolved we'll get the changes submitted and merged.
-
Could it be possible to create a Generic-legacy image for Virtual machines also?
No. The current image is created solely to facilitate internal dev/test work in vmware workstation/fusion and is not formally supported (and not on other hypervisors) so we have no desire to create more versions. If it happens to run anywhere else it's a coincidence, and if it breaks (and it does, because staff are not using it often) then we have no promise of fixing things.
-
At the moment there are still some add-ons and Kodi Omega plumbing bits that are not aarch64 compatible so we are deliberately omitting the config needed to permit successful crossgrade from arm to aarch64 images; and based on how future testing goes we might decide to not allow that anyway. As such the update from arm to aarch64 is being correctly rejected. If you make a clean install, the aarch64 images should run fine; albeit Kodi Omega is a pre-Alpha codebase right now.
