Posts by mglae
-
-
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:
Codemkdir -p /storage/.config/system.d/[email protected] nano /storage/.config/system.d/[email protected]/fsck.confpaste 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:
Code: /storage/.config/system.d/[email protected]/fsck.conf[Service] ExecStartPre=-/usr/sbin/fsck -T -M -p -t ext4 %IEdit: '-' 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.
-
[BUG] Kodi doesn't show up on AMD Generic with LE 11.0.3 (Regression) · Issue #8013 · LibreELEC/LibreELEC.tvDescribe the bug When using an AMD CPU with integrated GPU there is a major regression from LE Generic 11.0.1 to 11.0.3 => LE is starting and print version at…github.com
-
For remote DB the local mariadb should have no effect. If kodi does not connect while network is up (you are connected via ssh) this is likely something different.
For complete debug logging insert
to your advancedsettings.xml and activate Database Component Logging in Kodi settings.
Reboot. When Kodi is hanging execute pastekodi via ssh and post the URL.
-
But would any network issue cause the inability to access the database on localhost?
"localhost" configuration is special. As a mariadb/mysqld feature it is using the unix socket. But Kodi's mariadb-connector-c defaults to /tmp/mysql.sock whereas the mariadb addon is configured to /run/mariadb/mysql.sock.
TL;DR: Unless it is fixed use 127.0.0.1 instead.
-
logan893 The /storage partition is full. Size expansion is broken in "run" mode of 11.0.3 so only 32 MiBytes are availabl.
Please enlarge the second partition of the stick with a tool like gparted.
-
chewitt We only do check the boot= and disk= partitions. There is no fsck support in udevil.
-
Seeing it with VNSI too.
Fixed with updating kodi again
-
-
Seem to be a ION issue with the NVIDIA-legacy driver. If you don't find a functioning work around via WEB search I'm afraid you have to continue to use LE10.