Posts by chewitt

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.

https://wiki.libreelec.tv/configuration/ir-remotes

but this assumes:

a) The IR hardware for the OrangePi board is supported in the Linux kernel

b) The TV remote sends IR signals in a format supported by the kernel

Reboot and repeat the process, but use only bluetoothctl to pair the device. There is a bug in the settings addon, but we are stuck with devs that do python coding who cannot replicate the problem and devs who can replicate the problem who cannot code in python.

Reports of "Stuck on Splash" almost always means "GPU not detected" .. the OS will be running fine, but no GPU means no GUI to overwrite the Splash screen. Search for a "LibreELEC" device on the network and access the Logs folder over SMB to generate a zip with the system logs that can be viewed or shared for clues on the problem. If the laptop has multiple GPUs it's best to disable one in BIOS; the Intel GPU should be better supported than the nVidia one. You can also try a current nightly from https://test.libreelec.tv to see if that's any different.

#!/bin/bash

deskpi_daemon=deskpilite
deskpi_lite_svc=/storage/.config/system.d/$deskpi_daemon.service

# remove old service file
if [ -e $deskpi_lite_svc ]; then
    sudo rm -f $deskpi_lite_svc
fi

# adding dtoverlay to enable dwc2 on host mode.
mount -o remount,rw /flash
sed -i '/dtoverlay=dwc2*/d' /flash/config.txt 
sed -i '$a\dtoverlay=dwc2,dr_mode=host' /flash/config.txt 

# install safe cut off power daemon.
mkdir -p /storage/deskpi
cd /storage/deskpi

# copy python script to /storage/deskpi
wget https://github.com/DeskPi-Team/deskpi_v1/raw/main/drivers/python/fan_control.py
wget https://github.com/DeskPi-Team/deskpi_v1/raw/main/drivers/python/safe_shutdown.py
wget https://github.com/DeskPi-Team/deskpi_v1/raw/main/drivers/python/safecutoffpower.py

# send signal to MCU before system shuting down.
echo "[Unit]" > $deskpi_lite_svc
echo "Description=DeskPi Lite Service" >> $deskpi_lite_svc
echo "Conflicts=reboot.target" >> $deskpi_lite_svc
echo "Before=halt.target shutdown.target poweroff.target" >> $deskpi_lite_svc
echo "DefaultDependencies=no" >> $deskpi_lite_svc
echo "StartLimitIntervalSec=60" >> $deskpi_lite_svc
echo "StartLimitBurst=5" >> $deskpi_lite_svc

echo "[Service]" >> $deskpi_lite_svc
echo "RootDirectory=/" >> $deskpi_lite_svc
echo "User=root" >> $deskpi_lite_svc
echo "Type=simple" >> $deskpi_lite_svc
echo "ExecStart=/usr/bin/python3 /storage/deskpi/safe_shutdown.py &" >> $deskpi_lite_svc
echo "RemainAfterExit=yes" >> $deskpi_lite_svc
echo "Restart=on-failure" >> $deskpi_lite_svc
echo "RestartSec=30" >> $deskpi_lite_svc

echo "[Install]" >> $deskpi_lite_svc
echo "WantedBy=multi-user.target" >> $deskpi_lite_svc

chown root:root $deskpi_lite_svc
chmod 644 $deskpi_lite_svc

systemctl daemon-reload
systemctl enable $deskpi_daemon.service
systemctl restart $deskpi_daemon.service

^ that's the install script adapted for LE quirks and locations .. no idea if it works or not.

If the external drive has a Linux filesystem (EXT4, XFS, BTRFS, etc. - not NTFS/exFAT) it's probably just easier to modify cmdline.txt and use disk=/dev/sda1 so that /storage (and thus /storage/.kodi/userdata/Thumbnails) is entirely on the USB drive.

Quote from jorgealdojr

I can do that if given directions..

You will fail in the task because the drivers for Silicon Village WiFi chipsets are designed for (at best) Linux 4.9 era Android kernels and will not compile against the modern-era kernels that LE10/11 use. The changes needed are not cosmetic nip/tuck .. it's more like a lung replacement (lots of crypto differences).

Seeking works well for H264 but other codecs need further development. LibreComputer are likely to sponsor some development work to improve things, but there's no specific schedule at the moment. Until then, things are what they are.