Posts by mglae

Boot log is acceptable. Only if you continue using emby you have to add the "large_dir" feature.

Crash is when closing joysticks. I don't know if there are gaming improvements in LE12 nightlies but you can try LE13 to see if this is fixed in Kodi 22

Still no boot log, please reboot and create a log soon.

For a more detailed crash log please do

touch ~/.config/debug.enhanced

from ssh.

Jul 27 08:18:20.241021 LibreELEC kernel: EXT4-fs warning (device mmcblk0p2): ext4_dx_add_entry:2597: Directory (ino: 4888268) index full, reach max htree level :2
Jul 27 08:18:20.241057 LibreELEC kernel: EXT4-fs warning (device mmcblk0p2): ext4_dx_add_entry:2601: Large directory feature is not enabled on this filesystem

a) The emby server is spamming the log (and restarting). Follow this guide to enable the "large_dir" feature on /dev/mmcblk0p2

Jul 27 08:16:36.913108 LibreELEC kodi.sh[2461964]: Segmentation fault (core dumped)
Jul 27 08:16:40.690713 LibreELEC kodi.sh[2461964]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20250727081636.log

b) Usually there is no reboot. Kodi is restarted after a crash log was generated.

When the emby issue is solved reproduce the issue again and create a crash log URL hopefully including the boot logs.

Old AMD/ATI GPU failed to decode. Disable VAAPI acceleration in Kodi settings and test if your CPU is fast enough.

a) When having build issues use a docker environment from below tools/docker.

b) Maybe a simple screensaver like Dim or Black can reduce the idle load.

c) smartredraw is known to cause rendering errors. I don't know if there are improvements in Kodi 22 of LE13.

cepamoi22 Thanks for the info, I'm afraid it is years ago I test this (and this on the only existing X11 version - as Da Flex already suggested).

Setting the default refresh rate to 24Hz (and allow frame rate switching) may help too but but the system feels slower.

Thanks, but please see this thread.

In the meantime the mentioned fix is included in current kernel versions and can be tested with latest LE13 nightlies.

Kodi is still using a render loop (with screen refresh rate) therefore some unexpected high load is seen.

You can experiment with dirty regions and/or smartredraw but that may result in render errors.

Neither XML nor Linux question, but how kodi behave.

You have to use

<setting id="services.webserver">true</setting>

without the default="true" attribute.

guisettings.xml is owned by kodi. To force a specific option it is recommended to create an advancedsettings.xml entry.

Usually you can still use kodi-remote via ssh to control the UI.

If not removing default="true" the value is always reset to the default.

You can change an .IMG on any linux system.

As root do:

mkdir -p /tmp/mnt
losetup -fP --show ".IMG file name" 
# note "/dev/loopX" device
mount -o loop,rw /dev/loopXp1 /tmp/mnt/
# change anything below /tmp/mnt/
umount /tmp/mnt
losetup -d /dev/loopX

chewitt Please change the device in line #4 to nvme1n1p1 to address the created partition.

mandaragit1222 It's no regression to create a file system on the whole disk, just continue using it.

If you do prefer an UI configure LE Service addon's Update tab to manual updates from Custom URL https://test.libreelec.tv, channel libreelec-13.0 and update to latest nightly.

A quick search show: Timers Addon

In short: No. (Not without serious hacking)

Rename one file system if you need to to connect them both. This can be done on a different system with a GUI supporting the operation.

Not fixed yet.

When testing with LE11 Generic-Legacy nano shows the same issue.

There is no lib visible in the image, ncurses is linked statically.

1. Please keep in mind this is an English forum.
2. nano: in the meantime we do use wchar ncurses but forgot to enable utf8 support.
3. vi - like other busybox applets - lack utf8 support.
4. With installing System Tools Addon you can use vim supporting utf8.

Intel AX210 cards are well supported on notebooks.

Trying one of the inexpensive AX210 PCE-E to M.2 wifi cards should work OOTB.