Posts by chewitt

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.

Windows

I'd suggest using WinSCP to transfer files over SFTP (SSH) rather than SMB. It's marginally slower but for 5MB file who cares. If you get weird errors from that process there's probably something funky with the disk/filesystem and-or how it's mounted to investigate.

FWIW .. I don't see any issues with ordering changing with favourites (we use quite a few at home) .. the possible difference is that I use a shared SQL database on the back-end, so they are stored there not on local disk.

Best to file the bug with Kodi forums or GitHub with screenshots showing the issue

Note that if you enable SMB1 to SMB3 .. Samba will probably use SMB2 (default) not SMB3. I'm not sure that matters much - If it works, no need to fix things

LE's implementation was done by me to suit my use-case, which is remote access to home from whatever hotel I'm working from this week with all traffic tunnelled. If people have other use-cases; pull requests on GitHub that improve functionality without complex or onerous configuration are welcomed. Note that few people on staff use WireGuard and I have very little time for anything at the moment; so don't expect a particularly quick merge on the submission.

I'm personally liking Tailscale these days, as the setup is super-trivial (when there's a GUI) but packaging it into an add-on requires more time/effort than I currently have. I'd pay a bounty for someone to add it with a simple GUI to handle initial setup.

You can use the "disable SSH password authentication" option in the LE settings add-on, which has existed since ~2013.

aptalca ^ ping

Crash report available at /storage/.kodi/temp/kodi_crashlog_20220906055000.log

^ that's the only useful log that you can share.

There's probably different levels of sophistication you can do, but as a minimum you can share content from the 'server' box over SMB to the client device. Connect both to the same Gigabit Ethernet switch and Cat5 of better cables and playback (not streaming) over the LAN should be a breeze. If you will still watch content on the server box; install an SQL database (use Docker) and migrate the Library data there so you can maintain the watched/unwatched status between boxes. If you like pain, connect the client device over WiFi