Posts by chewitt

"Long ago" probably means using the legacy video pipeline which means the hdmi_ tweaks in config.txt aren't relevant to the now-different video pipeline used in current LE releases.

LE 9.0.2 image is here: https://releases.libreelec.tv/LibreELEC-LePo…rm-9.0.2.img.gz

Once that's installed you can probably update to dtech release of LE 9.2.8 (search the forum for his release thread).

LE11 dev image with Kodi 20 and Linux 5.19 is here: https://chewitt.libreelec.tv/testing/LibreE…lepotato.img.gz

IIRC /storage/.kodi/userdata/favourites.xml ?? .. I don't think it's a DB file

Most monitoring tools have install scripts that assume sudo is needed and wrong path locations for LE, but as dependencies aren't complex the scripts can be adapted to run on LE without much effort. You can run more complicated things in Docker containers; but that's more for application stacks than simple things.

If you can point to an online location for the installer script someone can see what might be needed.

Just exclude the -w filename.pcap .. then it outputs to console

git clone https://github.com/LibreELEC/LibreELEC.tv.git
cd LibreELEC.tv
git checkout libreelec-10.0
PROJECT=RPi DEVICE=RPi2 ARCH=arm make image

^ If you don't change to the libreelec-10.0 branch you are building against master and the driver will need patches for Linux 5.19.y

https://chewitt.libreelec.tv/testing/88x2bu.ko <= module built against 5.10.110 kernel (current HEAD of libreelec-10 branch)

http://sprunge.us/LDOzia works for me (no PKG_DEPENDS_TARGET required).

tcpdump -G 300 -W 1 -w dumpfile.pcap -nnpi wlan0 arp

^ tcpdump's -G and -W options can be combined to do the same thing; meaning rotate the capture file after 300 seconds, write 1 file

It's impossible to advise without seeing the package.mk content

You can add "textmode" to kernel boot params in syslinux.conf .. this will boot the device to a text console (no GUI) so with a keyboard you can poke around to figure out if there's an issue with Ethernet and see what's being detected GPU wise.

Quote

Exception: Invalid package reference: dependency RTL88x2BU in package linux-drivers::PKG_DEPENDS_TARGET is not valid

So the PKG_DEPENDS_TARGET variable in the package.mk that you added is incorrect in some way.

LE's niche is (and will probably remain) users with offline media, DVB services, and limited streaming media. Anyone who's serious about the online streaming media world should look to run Kodi on Android (a box/stick with L1 widevine etc.) or perhaps an AppleTV device that are natively part of the walled garden ecosystems that all the streaming media services reside in. There simply aren't enough developers working on Kodi or LE or the time/money resources that would be needed to do anything different. Adding a browser isn't going to noticeably change that, and using VLC isn't going to happen when Kodi is essentially a big fancy wrapper around deeply embedded FFMpeg. At least FFMpeg and VLC share common roots.

Sure, the OS will run on the latest boards if the correct firmware is present, but the "as released" image does not contain that firmware and will not boot. Changing that that would require an LE 9.2.9 image that we have no plan to create or release as LE 10.x/11.x now have much better (more feature complete) hardware support for RPi4.

The challenge with all the 'external' DVB drivers is that the upstream sources are rarely updated to latest kernel quickly, and we are bumping to the latest kernel release frequently, which breaks the patches needed. As a result, we generally don't bother updating them until we reach the later stages of a beta cycle when we've locked on a specific kernel as our release target AND the upstream driver patchset is available. It would be nice to track things more closely and bump more frequently, but curating DVB patcsets is a miserable time consuming pain in the arse chore task, and devs generally (and understandably) find more fun things to spend their free time on.

If the LE image is on your Desktop and the filename is LibreELEC-RPi4.arm-10.0.2.img.gz:

dd if=~/Desktop/LibreELEC-RPi4.arm-10.0.2.img.gz of=/dev/diskX

See https://www.raspberrypi.com/documentation/…-pi-4-boot-flow

if [ "$(systemctl is-active reboot.target)" = "active" ]; then
  exit 0
fi

^ If reboot.target is active you are rebooting, and exit the script. Untested, but I think should work. An alternative would be to test whether shutdown.target is active and only then proceed.

You can do it, but not using our installer.

LE requires two partitions: one for /flash (boot files) and one for /storage (persistent data) and on x86_64 hardware you can use MSDOS or GPT partition schemes. The boot volume can be either vfat or ext4 but storage MUST be a linux filesystem type (ext4) else we cannot set secure SSH key permissions and you'll never be able to login to the device console.

If the current filesystem is a Linux format then you can use Gparted from e.g. an Ubuntu Live USB image to shrink/move the current partition to make space for the /boot volume (512MB is enough) and mount the existing partition as /storage. Install syslinux or GRUB to the boot partition with an extlinux.conf that sets boot=/dev/sda1 disk=/dev/sda2 etc. and then copy the KERNEL and SYSTEM files over, and on first boot we will (re)create the .kodi and .cache and .config folders that we need on /storage.

If the current filesystem is a Windows format then you need to create TWO partitions so that we can store Kodi data correctly etc. - the media partition will auto-mount and be usable. I'd create the /storage partition at 8GB .. it's normally enough for all the thumbs and other cruft that Kodi accumulates in use.