Posts by chewitt

A1392 .. the second generation (square) ones. Prices for them seem to go up/down but there's usually someone offering one caked in dust (they clean up easily) and missing the easily replaces (figure-eight) power cable, and that one's the bargain. The first generation ones are always cheaper but I've had a few die on me over the years - the second generation are solid.

The last Apple A1rport Express I acquired from eBay was $12.

Converting 4K media to 1080p is handled in hardware but you still need to copy 4K images in memory and on cheap ARM boards (even well made ones like the RPi4) that doesn't come for free. If you play 4K media on a 4K panel (witth whitelist entries) there's no conversion involved. Scaling lower resolution content to 4K has a similar process but with the desktop size at 1080p Kodi will scale SD media to 1080p and output 1080p and the TV can internally handle the upscale to the 4K native panel resolution. You could also force Kodi to run at 4K desktop, but the TV will do a massively better and more efficient job at scaling 1080p to 4K than Kodi/RPi4 will. Low-power ARM boards are fantastic when everything is aligned and they can work to their strenghts. If you want something that can convert anything to anything .. start with a Core i7 NUC as you'll need the CPU grunt

Internal installation is not (and never will be) supported on cheap box devices using LE which is why we have never included that script in any of our official releases .. ergo you are not using one of our releases.

Also note that SSH in LE doesn't support a load of ancient/insecure ciphers. If you have a really old version of PuTTY it won't work. If you have a semi-recent version it will work.

I have default config.txt (no hdmi_enable_4kp60=1 or GPU increases) and a LG 4K TV with 23.976/24/50/59.94/60 Hz modes set for 1080p and 23.976/24/25/29.97/30 set for 4K and the desktop defaulted to 1080p. Apart from washed out HDR content (as no HDR support) I have no issues playing anything. I don't have any 4K60 media .. hence no need to force that config.

fbicknel is playing [email protected] media on a 1080p panel and RPi4 isn't optimised for that kind of thing (and won't be for aeons) so best option for him would be to re-rip that Movie in 1080p.

NB: The issue witth 25/29.97/30 modes is that Kodi always outputs progressive so interlaced media requires 50/59.94/60 so that each half-frame can be rendered as a full frame. There is no 4K interlaced media so this is only a 1080 thing.

At the end of the day not all media is ripped properly, not all TVs support all refresh rates, and RPi4 support under MMAL "is what it is" because it was a quick and dirty hack to ensure something worked at launch. The focus of all development is on GBM/V4L2 not MMAL.

NB: I'm booting the 1GB LaFrite fine with Linux 5.6-rc6 so there's no issue with the dtb size. LibreComputer pay Baylibre to upstream everything so I doubt there's anything missing from the upstream kernel apart from audio card stuff (will be done for Linux 5.8 probably).

It might be an issue with the CMA value in device-tree being too high. I force it to 896MB to facilitate 4K playback but this fails gracefully to 256MB on devices with under 2GB RAM. However, unless it accidentally works with the 512MB version of LaFritte I have no plans to support it. We have the same position with numerous 512MB Allwinner boards. Our experience with them (and older Raspberry Pi devices) is that 512MB is no longer enough for reliable Kodi use and our resources are limited so "pick your battles" applies.

Read: Configuring WireGuard in LibreELEC [LibreELEC.wiki]

# SPDX-License-Identifier: GPL-2.0
# Copyright (C) 2020-present Team LibreELEC (https://libreelec.tv)

PKG_NAME="mdadm"
PKG_VERSION="45c43276d02a32876c7e1f9f0d04580595141b3d"
PKG_SHA256="b4db5d84c43d92ae5b90ec6e547d461b405b8953b9c8ae5e41e692f62ea1d5d8"
PKG_ARCH="any"
PKG_LICENSE="LGPLv2"
PKG_SITE="https://raid.wiki.kernel.org/index.php/A_guide_to_mdadm"
PKG_URL="https://git.kernel.org/pub/scm/utils/mdadm/mdadm.git/snapshot/mdadm-$PKG_VERSION.tar.gz"
PKG_DEPENDS_TARGET="toolchain systemd"
PKG_LONGDESC="mdadm is a tool for managing Linux Software RAID arrays."
PKG_TOOLCHAIN="manual"

make_target(){
  make SYSCONFDIR=/storage/.config CC=$CC CWFLAGS=
}

make_install_target(){
  mkdir -p $INSTALL/usr/bin
    cp mdadm $INSTALL/usr/bin/mdadm

  mkdir -o $INSTALL/usr/lib/udev/rules.d
    cp udev-md-raid-creating.rules $INSTALL/usr/lib/udev/rules.d/01-md-raid-creating.rules
    cp udev-md-raid-arrays.rules $INSTALL/usr/lib/udev/rules.d/63-md-raid-arrays.rules
    cp udev-md-raid-assembly.rules $INSTALL/usr/lib/udev/rules.d/64-md-raid-assembly.rules
    cp udev-md-clustered-confirm-device.rules $INSTALL/usr/lib/udev/rules.d/69-md-clustered-confirm-device.rules
}

^ that seems to build under LE master, so probably builds under LE 9.2.x as well. You'll probably want to extend the package with a default conf that's copied to /storage/.config/mdadm.conf.sample etc. etc. .. lots of prior art for that in the build-system.

Two options depending on how ugly you like your script babies to be:

a) Create /storage/.config/autostart.sh and place some commands there; the script is executed at the start of userspace boot and is blocking but you can (background)& the commands and prefix with a sleep value to have something execute 10 seconds after boot (or whenever, you control the sleep value). This is the ugly kid.

b) Create a systemd .service file in /storage/.config/system.d to run commands or call a script; systemd gives you precise control of when the service is executed in the startup/boot workflow. This is the better way.

The screenshots show that you are running CE not LE so you're asking for support in the wrong forum. We have no knowledge of what userspace changes and hacks have been added to their codebase.

Is the content new media or old media that has succesfully been played many times before?. It's it's new media the issue most likely lies with the media and its encoding - software update might cure that. If it's old media .. could be hardware. Anything running LE 7.x has been around for a while.

Quote from donbrew

Be prepared for most of the addons to break. Seems that Python got upgraded AGAIN to something like 3.01 or something, so now Python 3.0 doesn't work. All of the recently updated to 3.0 addons are broken now (notably six is broken).

This is not relevant for LE 9.2.x releases which are entirely Python2 based. The Python3 changes only impact LE master (will be LE10 in the future).

HDR will not happen in LE 9.2.x .. the development that's required for it is focussed around the LE10 codebase.

C2 ships with a heatsink which is more than enough for S905 as it never gets particuarly hot - active cooling with fans will not be required unless using something that generates a ton of CPU load. I forget whether the 3.14 kernel supports thermal zones to do more, but if not I am in the midddle of sending a patch upstream to add thermal zones support to all Amlogic GXBB/GXL/GXM devices.

C2 also has GPIO pins which could be used to interact with external switches and such.. similar to a Raspberry Pi but not as well documented. AFAIK the C2 has no support for ACPI in hardware so not sure that's the direction to chase things in. LE does not package lmsensors but "cputemp" will give you the output from the single (CPU) temperature sensor on the boarad and you can always script around that.

The network-tools add-on bundles bwm-ng. That's #9 in that list.

I'd guess our release manager forgot to enable auto-update.