Posts by chewitt

For kicks, can you update the 17.5 system to a currently LE12 nightly and see what happens?

#!/bin/bash

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

do_install(){
  # create the persistent firmware dir
  mkdir -p "/storage/.config/firmware/edid"

  # capture the raw edid file
  if [ ! -e /storage/.config/firmware/edid/edid.bin ]; then
    cat "/sys/class/drm/card0-HDMI-A-1/edid" > "/storage/.config/firmware/edid/edid.bin"
  else
    echo "info: using existing edid.bin"
  fi

  # create the cpio file
  mkdir -p "/storage/cpio/lib/firmware/edid"
  cp "/storage/.config/firmware/edid/edid.bin" "/storage/cpio/lib/firmware/edid/"
  cd "/storage/cpio" || echo "error: cannot find /storage/cpio .. exiting!" && exit 1
  find . -print | cpio -ov -H newc > "/storage/.config/firmware/edid/edid.cpio"

  # mount /flash rw
  mount -o remount,rw /flash

  # copy the cpio file
  cp "/storage/.config/firmware/edid/edid.cpio" "/flash/edid.cpio"

  # cleanup cpio dir
  rm -rf "/storage/cpio"

  # determine boot method and set params
  if [ -f "/flash/extlinux/extlinux.conf" ]; then
    FILE="/flash/extlinux/extlinux.conf"
    if grep -q "initrd=/edid.cpio" "${FILE}" ; then
      echo "error: ${FILE} already contains edid.cpio, aborting!"
      exit 1
    else
      cp "${FILE}" "${FILE}.backup"
      sed -i "/ APPEND/s/$/ drm.edid_firmware=edid\/edid.bin video=HDMI-A-1:D/" "${FILE}"
      echo "info: edid setup complete!"
      exit 0
    fi
  else
    FILE="/flash/uEnv.ini"
    if grep -q "initrd=/edid.cpio" "${FILE}" ; then
      echo "error: ${FILE} already contains edid.cpio info .. aborting!"
      exit 1
    else
      cp "${FILE}" "${FILE}.backup"
      sed -i "/ bootargs/s/$/ drm.edid_firmware=edid\/edid.bin video=HDMI-A-1:D/" "${FILE}"
      echo "info: edid setup complete!"
      exit 0
    fi
  fi
}

do_cleanup(){
  rm "/storage/.config/firmware/edid/edid.bin"
  rm "/storage/.config/firmware/edid/edid.cpio"
  mount -o remount,rw /flash
  rm "/flash/edid.cpio"
  if [ -f "/flash/extlinux/extlinux.conf" ]; then
    FILE="/flash/extlinux/extlinux.conf"
  else
    FILE="/flash/uEnv.ini"
  fi
  cp "${FILE}.backup" "${FILE}"
  mount -o remount,ro /flash
}

do_usage(){
  echo "usage: getedid {create|delete}"
  exit 0
}

case $1 in
  create)
    do_install
    ;;
  delete)
    do_cleanup
    ;;
  *)
    do_usage
    ;;
esac

exit

I created ^ that some time ago to replicate the "edid-create" process for other boards (which never seemed to quite work) but it's not something that I was able to test easily so it hasn't been upstreamed.

Copy to /storage, make it executable, then run "./script.sh create" and see what happens.

There is no ISO image and LE cannot run from an ISO image (so you can stop looking for one). If you want to install to spare space on an existing disk this can be done, but it's not a supported configuration so you won't find nice HOWTO guides and instructions for setting something up. Grub will work fine (we don't care what bootloader is used) if you configure the boot entry correctly; see contents of syslinux.cfg for ideas. LE requires two partitions; one for boot files (512MB) and one for persistant storage (8-16GB min) assuming media is stored somewhere else.

I have a hunch Ubuntu/Fedora are using OpenGL (via Wayland) while LE/Generic is using OpenGLES, and thus the difference being seen is due to differences in GL vs GLES capabilities (and thus not technically a bug) but I'm not 100% sure.

Quote from elliottmc

you will probably get a much better experience if you use a NAS for storage

You have wrongly included "probably" in that statement

Use snapshots or clone the disk for experiments. Are you mapping the GPU in the VM or using the vmare GPU?

Read: https://wiki.libreelec.tv/hardware/amlogic#install2internal

In the absence of UART logs that show what actually happens during boot it's impossible to comment.

It's possible if you compile a custom image with a different busybox configuration. Otherwise, no. The better option to remove complexity is using SSH key authentication; then no passwords are prompted-for.

The "Generic" image switched from Xorg to GBM graphics but IIRC the vmware GPU in the OVA should support that. However if the host GPU has been mapped through to the VM this will 100% fail on nVidia cards as there is no support for them without Xorg.

NB: I've been told the virtual hardware version of the OVA needs bumping for Workstation 17.5 (and likely other recent versions) but that something which can be tweaked locally.

popcornmix any ideas?

There are no "central management of multiple devices" apps, but if you describe how you want to control them (and why) and what they are to be used for, there are probably things that can be done. LE and Kodi have options for access, scripting and automation.

It already does: https://github.com/LibreELEC/Libr…_autoscript.src

The only time I've seen stability issues like you describe is when trying (and failing) to use a 5V phone charger that only provided 1.5-2.0A to an RPi4 board. RPi5 needs a minimum stable 5V/3A from the PSU, and that increases to 5V/5A once you start to attach USB drives and other kinds of peripherals.

The first step in triage is to update to a current LE12 nightly release to see if newer versions of everything have already resolved the issue. Nightlies are quite stable, we're about to issue the first release in a short beta run.

If you follow the Kodi forum support thread and read some of the GitHub issue tickets; some rework is needed (and being done) and when that's completed an update will be pushed through Kodi repos. Until then manual updates are needed.

Quote from keesijp60

Can I install the amlogic builds above 10 into internal?

On a random S905W box, not supported, and no plans to ever change that.

Quote from homerojs2006

Would RP5 + NAS be OK?

It works fine for me (RPi5 + Synology NAS) with SMB shares and a Netgear GBit switch. I don't run anything exotic.

You need to invoke recovery boot again so it searches for bootscripts that tell it to load LE boot files else it will be looking for CE boot files which are different (names) and not found; hence you end up attempting to load Android.