Chase the vendor for the correct ROM image to restore the box, or their u-boot sources (which are GPLv2 .. but good luck with that) or keep experimenting with u-boot(s) from ROM images (as you've been doing, from SD card).
Posts by chewitt
-
-
We haven't published add-ons for the LE11 codebase yet, so there is no repo to connect to.
-
Not possible. The device has a Hisilicon Hi3798mV100 SoC chip which has zero upstream Linux kernel support (only an ancient Linux 3.18 vendor kernel) and a GPU with zero mesa GL/GLES support.
-
There is an "RK3328" device in our buildsystem, but no "3328" device, so add-on requests are doing exactly what you coded, which is wrong.
-
The u-boot you found only partially works. It looks to be compatible with the RAM, but there is some form of chip detection going on (from the error) so it's probably been created for another type of GXL device, e.g. S905X not S905W. The one good thing is .. you are experimenting from an SD card. Keep doing this, because if you flash the wrong u-boot to eMMC it becomes a major pain to recover the box (not impossible, but complicated).
The only mainline u-boot(s) that I have pre-compiled are here: Index of /testing/u-boot/ .. vim/lafrite/lepotato are all GXL devices (S905X, S905X) but the mainline sources don't really have device detection like vendor sources so from SD card they will either work or fail cleanly.
-
Also now Armbian supports this Rockchip: CSC Armbian for RK3318/RK3328 TV box boards - Rockchip CPU Boxes - Armbian forum
From a forum post in that thread you linked: [15:00:37.296] OS: Linux, 4.4.213-rockchip64, #5 SMP Fri Apr 16 17:25:31 UTC 2021, aarch64
This means the Armbian image is using the Rockchip 4.4 vendor kernel. LE has no interest in that kernel. I'll let others comment on whether there is any usable mainline kernel support.
-
Either you rebranded the distro name to something other than "LibreELEC" or (more likely) you haven't overriden the URL for accessing the add-on server, so it will fall back to looking for a project/device combo that genuinely doesn't exist on our server: LE has never shipped an "RK322x" device so we have never built add-ons for that image. You'll need to link to something binary compatible.
-
Do a force refresh on the LE repo. The add-ons are there.
-
Nothing stops you from booting from an SD card and storing media on a NAS drive or USB disk.
-
Panfrost is awesome!
.. (drops mic) -
It is possible to install the WC image to emmc, but I honestly forget how this is done or what the special image filenames are, and WeTek staff are no longer present/active in the forums; so should you attempt it and anything goes wrong please don't ask for help
-
I excluded 1080p @ 25/29.97/30 because with "double rates" allowed Kodi will switch to 1080p @ 50/59.94/60 instead and this also allows Kodi to better handle interlaced content: Kodi ONLY outputs progressive so to handle 1080i @ 25 (PAL) you need 2x progressive frames to render each 1x interlaced frame. This works at 50Hz, and drops 50% of frames at 25Hz. You can also whitelist 720p (and SD) modes if you want, but Kodi handles 1080p scaling well (as well as most TVs) so it's not normally needed. In the case of 4K media most TVs handle 1080p > 4K scaling better than Kodi, and the Kodi GUI is much snappier for navigation at 1080p (as 1/4 the data is being processed) so it's better to leave Kodi desktop resolution at 1080p (TV scales to 4K native panel resolution) and use the whitelist so Kodi switches to 4K modes only when actually needed for (hardware decoded) playback.
-
Connman (Connetion Manager) manages connections, so it also manages Ethernet. This commit connman/connman.git - Connection Manager might help you understand more about how the current feature works. The change it implements is not in current shipping LE, but will come next time Connman cuts a release and we bump to it. If you are into self-building LE images it's pretty trivial to bump to the latest commit for testing.
-
Each Kodi version bump necessitates some rework from add-on authors, which creates an opportunity to fiddle and change things, and K18 > K19 included the Python2 > Python3 change which almost certainly mandated some rework. So where, say, the Krypton and the Leia versions of the add-on are probably quite similar, the Leia and Matrix versions are very likely to have bigger changes. The author is key..
-
Sony STR-DN1050 has HDMI ports. Use them!
-
I suggest you flag the issue to the add-on author via the Kodi forum thread.
-
-
The problem is the clock is not being (re)set via NTP at startup, so the system clock falls back to a default value (glibc version release date) which is before the validity start-time of the TLS certificates used on the add-on repo servers (the S in HTTPS). As a result your system sees the webserver certs as invalid and the connection fails.
The connection manager in LE defaults to pool.ntp.org servers, so either access to these is being blocked (some ISPs do this) or there is something odd in your network (perhaps DHCP from the router sets the NTP server with a null value). Either way.. this is the problem you need to solve. As long as the ISP is not blocking port 123 (NTP) you should be able to find/set other NTP servers in the LE settings addon; then reboot to effect the change. If the ISP is blocking the port, they probably provide their own NTP server, or you will need to have a local in-network time source (NAS box, Active Directory server, etc.) or invest in an RTC chip/hat for the RPi4 so that you can manually set the clock and persist the time value over reboots.
NB: Kodi regional settings are irrelevant to this problem. It's the system clock value that matters.
