Posts by chewitt

I'd understand if the WeTek Core didn't work; the last image we published was LE 8.2.5 and this is dated so some add-ons might have issues and not work now. However, if you also see the same on a completely different OS platform it would suggest something in your network or upstream from you (but what, is anyone's guess). In either case .. share debug logs. Maybe we see something you don't.

Scrapers have been a challenge in recent times due to the upstream websites changing their terms/conditions and becoming companies with commercial models. It's forced change on the Kodi ecosystem, but forccing millions of users (or Kodi itself) into a paid-for service was never an option, so it is (or it's been) what it is.

I use "Tubed" .. it's much faster, and also supports the same API keys the other add-on uses.

Write the image to an SD card and boot the RPi4.

ps. This is an English language forum. Please post Spanish and English (Google translate) texts.

Quote from Lior.parsi

Any suggestions?

Post in the Lakka/Libretro forum?

LE 10.0 added lvm2, luks (dm-crypt, veracrypt), mdraid, ext4 encryption <= sky42 images are focussed on encrypted drive support but as a result have all the bits you need for RAID. He doesn't build an image for RPi2/3 devices yet (likely as we have not released LE10 for RPi3 officially, but the sources are public so you could do that yourself (or ask nicely).

RPi3 works fine with LE10 with the following exceptions: hardware deinterlace which is still being implemented, 3D which may be done in time but not in the short term, and software optimisation for HEVC playback which is unlikely to ever be reimplemented.

The Nest requires signed firmware and you don't have Google's signing keys, so you can build kernel, u-boot and everything needed, but you will not be able to reimage it to run what you built. There are lots of cheap S905X2 devices with better connectivity and factory boot firmware that is easily persuaded to run modern Linux. If you also want to run upstream u-boot (on Amlogic hardware) you need the signing FIPs for Amlogic boot firmware. This is simple with SBC devices which will provide full sources. It is less simple with tvbox devices which often use cheap bottom bin (lower quality) RAM chips which need tweaked RAM timing data to work; which means you typically need the specific boot FIPs (tweaked for the batch of RAM used) to get successful boot.

Amlogic GXBB has 8-bit internal and 8-bit output regardless of media content. GXL is internally 10-bit but outputs 8-bit. GXM is the first SoC that can handle a full 10-bit pipeline but now software comes in; the upstream kernel will currently only output 8-bit (some plumbing is missing) where the vendor kernel can do 10-bit, and it's the same for newer G12A, G12B and SM1 hardware. GXM (Midgard) uses "Amlogic" framebuffer compression to reduce the internal bandwidth needed with 4K media. G12A and newer (Bifrost) devices use "ARM" framebuffer compression (similar but different). Onto this you overlay all the RGB/YUV colourspace stuff that/s involved with SDR/HDR; the upstream kernel has cleaner and better organiseed plumbing for this but is further behind the vendor kernel which has horrible plumbing and lots of preset defaults but will mostly end up at the right combination of frequently neeeded settings.

I'll pass the observation that the best way to solve issues with TVDB is .. making edits to TVDB. If you ensure content (re)scrapes correctly it helps you; and anyone else trying to use it.

The poster Q is probably best asked in Kodi forums.

Your post is confusing. However:

a) If the skin works on Matrix, it works on Matrix. If you manually upgrade from Leia to Matrix you still end up on Matrix. There is no reason why you cannot remove the Leia version of the skin (reverting to Estuary) and then update and install the Matrix version and start using it.

b) If you backup a Leia install and then do a clean Matrix install and restore the 'Leia' backup you pollute the Matrix install with Leia stuff. You will need to a selective restore of only the things that don't cause conflicts (e.g. add-ons).

c) LE is packaged with the entire OS in two files: KERNEL and SYSTEM. This means you cannot update "Just Kodi" because our OS packaging dictates that you update everything at the same time .. but if you are self-compiling you can update to an image that contains only whatever Kodi change you want to make. If you are thinking to use the Leia OS base that you customised but with "Kodi Matrix" .. it's not impossible but nobody around here is likely to spend a month on forum posts to explain how, so you either know how, or it's best not to ask.

RPi4 (2GB) is not the cheapest device or best spec, but the quality of software support wins hands-down, which translates to less time fiddilng with the board and more time watching movies. Allwinner and Rockchip support continues to improve but I couldn't name a specific device that I'd personally recommend.

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).

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.

Quote from mega-samu

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.