Posts by chewitt

    I need wetek internal dvb tuner supports on Kodi with python 3. Are there any images can you recommend to me?

    You need an image with the Amlogic 3.14 kernel for tuners support, and Matrix for Python3 support, and AFAIK the CE images that support Matrix and Python3 are all using the Amlogic 4.9 kernel, which because it was "reworked" by Amlogic for GXL and newer devices has some breakage for GXBB (S905) hardware like the WP2. It's the classic problem with vendor-hacked BSP codebases; they don't need to consider backwards compatibility when supporting the next generation. NB: I don't pay attention to CE images though so I'm not sure how accurate that info is (better to ask them, not me). LE official images stopped at 9.0.2 (K17) although there are community created images equivalent to 9.2 available here in the forums, but once you go to K19/K20 and Python3 the kernels go upstream where the tuner drivers are missing.

    chewitt thanks. I worked LibreELEC-AMLGX.arm-10.80.0-box from sd. And installed tvheadend. But not show dvb adapter. I need crazycat driver. Where can I download?

    I don't enable the crazycat drivers in the image because I'm almost always running a kernel that's too new for them to be supported, so USB devices that have upstream kernel support are the only ones that will work. There is also no support for the internal DVB cards in the WP2; the tuner and demo drivers exist (out of tree) but someone needs to write a new V4L2 demux driver before those can be used, and I'm not aware of any one working on that.

    esrefasaf You can write the LE "box" image to an SD card, edit the name of dtb to use in uEnv.ini, and then boot the box. It is not currently possible to install mainline kernel LE images to the eMMC storage. In the long term I'd like to fix that with an image that run mainliine u-boot from eMMC (completely erasing/replacing the vendor u-boot code) but that still needs development and a eureka moment.

    NB: The images in my LE share may have an issue with hardware decoding at the moment, and I'm not able to investigate it properly until I get home after New Year, so you may find you can install/boot but not play much.

    Code
    2021-12-24 16:01:08.652 T:1346    ERROR <general>: Unable to load /storage/.kodi/addons/vfs.libarchive/vfs.libarchive.so.20.0.0, reason: libcrypto.so.1.1: cannot open shared object file: No such file or directory

    The claim of "the box doesn't boot" is false as the OS log shows the box boots and runs Kodi fine, but Kodi loads vfs.libarcive for OpenSSL 1.x and faults, causing Kodi to crash. Nightly images have bumped to OpenSSL 3.0 which includes a major (breaking) ABI change. All binary add-ons must be rebuilt and updated, and most are done and published; but we are still chasing some build issues in a few. Once those issues have been resolved an updated vfs.libarchive can be pushed; then it won't crash and cause problems. Until then, you can SSH into the box and delete /storage/.kodi/addons/vfs.libarchive to stop the crashing.

    There appears to be an issue with hardware decode in current nightly images; possibly fallout from the OpenSSL bump a few days algo which changed low-level compile options for a few things - everything else seems to work but decode simply never starts. I'm in the process of trying to revert my developmeent branch to an earlier state to confirm the origin of the problem. It's a bit annoying to have finally made progress on playback only for it to be immediately broken again, but that's life. Until this has been resolved anyone doing an install will need to use Kodi in software decode mode. NB: The images in my share are also affected.

    You can try dtech images which use LE 9.2 and might have more/better drivers included. I also have an experimental device-tree for the KI-pro in my LE11 images, although those images will not support the integrated tuner and I normally have the driver add-ons disabled to avoid breakage as I'm working on kernels that are ahead of LE master branch.

    NB: The general recommendation is to run tuners on a separate device (an old RPi should be fine) so you can run any OS/version that supports the drivers required. There is no single good solution normally due to the state of DVB support in all kernels.

    I'm just getting started. Do I need Ubuntu desktop or can I build from a server edition?

    There's no need for a Desktop version although it's often easier to work with(in) if the VM is on a laptop. If the build VM is on a remote device, minimal server images are fine and have lower overheads.

    The upstream kernel has support for the PCIe version of the RTL8125B adapter, but I'm not sure about USB. If it's supported it will either just work out of the box we can add the kernel config needed for that. If it requires and out-of-tree driver, you are welcome to self-compile an LE image with it included. If that's not your thing, we're sorry, but we have been refusing to add more crappy Realtek drivers to our images for about 2.5 years now and have no plan to go back on the decision. Including more of their shitty drivers in a distro like CE which never bumps kernel version isn't much drama. In LE where the kenel bumps frequently and Realtek drivers break with every bump .. the novelty of hunting down patches wears off (some time ago).

    NB: LE does not need "fastest" Ethernet speeds, although fast is never bad. We only need Ethenet to be "fast enough" and Gb is fast enough for 80GB disc rips, so it's not a high-demand topic. I've no idea about other 2.5Gb adapters, but we will have no issue enabling kernel config for any needed; under the same rules (in-kernel is good, out-of-tree is bad).