Posts by chewitt

Connect the HDMI cable to the port nearest the USB-C power connector, then reboot. Fixed?

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.

The tether is intentionally simple with on/off options so I think you will need to fiddle with iptables to block traffic.

Last official release supporting Meson6 hardware was 9.0.2 and you will need to use Ubuntu 16.04 or 18.04 to build the image.

https://wiki.libreelec.tv/development-1/…cs#dependencies has info on package dependencies

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_UDF_FS=m
# end of CD-ROM/DVD Filesystems

^ We set those options in kernel defconfig. I'm not sure what BD-ROM needs, if different. Does the drive/disc work in a general purpose distro like Ubuntu or Fedora?

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.

Note that the Chrome addon only exists for Generic x86_64 images. You won't find it for any ARM SoC devices.

Quote from flystar

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.

Have you disabled password auth (enabled key-only auth) in settings?

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

noggin Capacity in our build environment is reduced currently (one server offline) so frequency of builds is not "nightly" at the moment.

GUI apps are just a wrapper on "dd" so have a go with that from Terminal.app?

Old (out of date ciphers) PuTTY version?

I've submitted a backport, so if we spin another 10.x release is should be included.

Have a read here: https://wiki.libreelec.tv/development-1/build-basics

It's hard to comment without seeing a UART boot log from the board (if you have one, please share it) but if the older image works, use it and then update via the .tar file in /storage/.update as normal. I've clean installed both N2 and N2+ recently without any issues, so I'm fairly sure there are no issues with the image. You do need the boot switch to the right? If petitboot is active (switch to the left) it will not boot, as HK are not interested to support modern u-boot with it.

Quote from noggin

Interesting - where is the best place to offer feedback on this, and help ?

I've pinged you some options in PM. It would be good to have your eyeballs on the text!