mpv was included into addon being test tool: https://github.com/LibreELEC/LibreELEC.tv/pull/3256
mpv was removed from addon being test tool: https://github.com/LibreELEC/LibreELEC.tv/pull/3749
mpv was included into addon being test tool: https://github.com/LibreELEC/LibreELEC.tv/pull/3256
mpv was removed from addon being test tool: https://github.com/LibreELEC/LibreELEC.tv/pull/3749
Cherry picking two points. For general addon development questions you may get more feedback in Kodi forum.
Although it does say that there are modules available for use and pyserial is one of those modules but I don't know the addon id for it.
Following the usual naming conventions <import addon="script.module.pyserial"/> should work.
My addon needs to modify the /flash/config.txt file
IMO this requires some caution. E.g. check of supported HW, already modified config.txt...
From the UI there should be a deinstallation button.
Testing without owning the HW is not possible. Please try latest LE11 nightly and LE12 nightly from https://test.libreelec.tv/ . Maybe this is already fixed on updated systems.
To not alter your installation write the test image to an USB stick and type run at first boot.
After adding echo ".profile loaded" to your .profile is the string printed at login.
Which teminal program and ssh client do you use?
Kernel log for r8169:
kernel/git/stable/linux.git - Linux kernel stable tree
Deadlock in jumbo mode was introduced between 6.6 and 6.6.2 (our kernel bump on 2023-11-20). Only fixed in 6.6.5.
Try default 1500 MTU
Press F10 until volume is maximum in Kodi, increase volume on the TV to max too and try again.
The patch does only work for ARM devices. On X86_64 -ENODEV is returned instead of -EOPNOTSUPP when no HW is found.
a) SYSTEM is no initrd, delete the line (the squashfs image is loaded from boot= FS).
b) Consider loading KERNEL via HTTP URL, it's much faster than TFTP
c) Kernel NFS default to V3. If using a modern NFS V4 server add ,vers=4.2 to the NFS addresses.
Correction: since LE12 file system expansion on first boot is logged to /flash.
fsck on boot is logged to kernel and can be seen with dmesg|grep fsck:. Please note : in default configuration no check is forced as long the file system is clean.
After learning ssh access basics:
mkdir -p /storage/.config/system.d/[email protected]
nano /storage/.config/system.d/[email protected]/fsck.conf
paste the contents and save.
Additional UDEV rule may lead to race with udevil mount rule. Better extent the systemd udevil unit with a drop-in.
To fsck any ext4 file system (and only ext4 fs's) to mount create with path:
[Service]
ExecStartPre=-/usr/sbin/fsck -T -M -p -t ext4 %I
Edit: '-' added to ignore error codes
No. Only /flash and /storage is checked automatically.
Please post log urls of journalctl|paste via ssh for the working and not working case.