Posts by chewitt

You can change/overwrite it in the LE settings add-on.

Core boxes are long out of stock but vendors normally have some support spares and I made it clear anything they unearth in the back of a cupboard will be fine for my/our needs. Hardkernel also posted a C1+ when they shipped a C4 sample so now I have a couple of Meson 8 things to play with over the summer.

u-boot/firefly-rk3399_defconfig at master · u-boot/u-boot · GitHub

^ find the correct defconfig for ROC-RK3399-PC and check CONFIG_DEFAULT_FDT_FILE

Connection configuration data is stored in /storage/.cache/connman/ but you should change configs through connman (connmanctl) as it manages those files and will probably overwrite any changes that you make. If you do want to manually edit, stop connman.service first, edit, then restart. You'll discover that SSID and passphrase data are base64 encoded so you cannot simply type new details in.

WeTek posted me a Core box the other day and have share their u-boot sources so I can start to look at what might be required to support the boxes again in the future. There's still a lot of work to be done for Meson8 support though, so it will be a lower priority thing to track.

Possibly an issue with newer GCC host binaries. I'd suggest building 9.0 images on Ubuntu 16.04 or 18.04 (looks like 20.04 in the screenshot).

The skin creator would need to add our icon and conditional shortcut the same way that it's done for the default Estuary skin (not hard to do) but the add-on can also be accessed from Add-ons > Program Add-ons on the Home screen menu.

1. Correct, it changes the behaviour of firmware which results in more power draw (which increases heat).

3. "mount -o remount/rw /flash" will remove the ro block on the boot partition. It and /storage are the only persistent writeable areas of the filesystem, as everything is inside a squashfs compressed file SYSTEM that's expanded on each boot, or the KERNEL file.

We don't use /etc/fstab which is why it's blank and you cannot edit or override the file. It only exists because some other Linux plumbing looks for it and craps out when it doesn't (even if the file is blank). We use udevil for mounting and it's possible to override our default udev rules if you want to (use a file with the same name in /storage/udev.rules.d). I guess when all the upstream sources adopt noatime we'll acquire the same change. Until then, we'll stick to the accepted defaults.

LE currently implements exFAT via FUSE which runs in userspace and so is rather slow. In the near-term future LE10 will probably bump to newer kernels which now have the new/official Microsoft exFAT driver implemented (Linux 5.7 IIRC) so the driver runs in-kernel and should be an order of magnitude faster to use; performance should be on-par with other in-kernel drivers like the VFAT drivers we use for FAT16/FAT32.

ConnMan checks ipv4.connman.net on boot to see if it's online or not. If the network is online Kodi will then start and numerous Kodi add-ons will check for updates by making a request to a Kodi URL which will redirect to a mirror hosted by one of 30+ independent mirror sites. Kodi uses mirrorbits which will geolocate your IP and recommend a server near to you, but you have no control over which one. The LE settings add-on will also start and check our infra for updates. This request is fulfilled by our infrastructure but if you choose to update the request will be redirected to one of our mirror sites and mirrorbrain will redirect you - and you have no control over which one. Individual add-ons that you install may also check for stuff.

Both LE and Kodi devs are quite security conscious, but we're also a simple client OS designed for watching TV so security is a deliberate and measured compromise around ease-of-use and we're not attempting to be the most seure device possible (as that OS is a pain in the arse for noob users to work with). TL/DR; If you don't trust LE/Kodi .. place it in a separate VLAN on youor network and implement firewall rules to prevent it reaching other devices.

Martin's branches are here: Branches · xdarklight/linux · GitHub .. note the amount of "WIP" items and don't get too excited

Put the device on a static DHCP reservation so you can SSH in after booting and share logs to see why the screen is black.

You can enable "disable password auth" after installing private SSH keys (stops unauthorised access to the console where passwd can be run). You can put a PIN on the LE settings add-on to stop people accessing the add-on to change the password from the GUI.

LE 9.0.2 is the latest official release. After this point we have abandoned all work on the legacy Amlogic 3.14 kernel and refocussed on mainline Linux support for LE10 (based on Kodi v19 which is still in a pre-Alpha state). This has some rough edges on playback but it otherwise in fairly good shape on Linux 5.6 .. I'm overdue to push a bump to Linux 5.7rcX to the master branch.

Current test images are in Index of / .. use the AMLGX 'box' image from an SD card.

NB: Kodi will always show under 1GB free because some RAM is reserved for system use (drivers and such) .. 775MB sounds about right/normal.

There's a mailing list on [email protected] but traffic is super low and I already pinged the main connman developer who worked with me on adding the initial wireguard support to connman (he wrote code, I tested it - my use-case is limited though).

If you need to control start sequencing use a system.d service, you have a lot more control over when things happen.

You might ask the author to submit the add-on to our repo?