Posts by mglae

synologynas is likely a local hostname to be resolved.

Unfortunately resolving host names via nmblookup was dropped from kodi 20, now DNS lookups are finally used.

You can try to enable WS-Discovery via Settings->Services->SMB Client.

To avoid reinventing the wheel a link to the excellent Audio Quickstart Guide in Kodi Wiki should be enough.

Quote from titoasi

Do logs persist after reboot? Or they start loggin on each boot? Because then I don't see anything that caused the crash

There is almost never a reboot, only kodi is crashing. In this case you do see it in

Feb 24 16:10:19.617112 TitoasiRB kodi.sh[860]: Segmentation fault (core dumped)
Feb 24 16:10:34.647132 TitoasiRB kodi.sh[860]: Crash report available at /storage/.kodi/temp/kodi_crashlog_20230224161019.log
Feb 24 16:10:34.685475 TitoasiRB systemd[1]: kodi.service: Main process exited, code=exited, status=139/n/a
Feb 24 16:10:34.720498 TitoasiRB systemd[1]: kodi.service: Failed with result 'exit-code'.
Feb 24 16:10:34.720994 TitoasiRB systemd[1]: kodi.service: Consumed 20min 44.716s CPU time.
Feb 24 16:10:36.842051 TitoasiRB systemd[1]: kodi.service: Scheduled restart job, restart counter is at 1.
Feb 24 16:10:36.842767 TitoasiRB systemd[1]: Stopped kodi.service.
Feb 24 16:10:36.842817 TitoasiRB systemd[1]: kodi.service: Consumed 20min 44.716s CPU time.
Feb 24 16:10:36.863162 TitoasiRB systemd[1]: Starting kodi.service...
Feb 24 16:10:36.875145 TitoasiRB systemd[1]: Started kodi.service.

Pasting the Crash Logs via LE Settings Addon will give more information.

Maybe someone know what the burst of kodi.sh[864]: Failed to import fence to syncobj: -1 means.

With ssh you can use kodi-remote on the device.

It is ever possible to connect a (maybe cordless) keyboard.

AutoConnect is OK.

You can provide the usual pastekodi system log. Maybe someone gets an idia.

Quote from Glorious1

I'm still wondering why that change was needed for me when it wasn't for others.

You did not mention before you are using a case with fan and likely did install some software intercepting the power off path.

Quote from Glorious1

Only thing is, the case fan stays on, which I guess is expected because apparently the power to GPIO pins remains on as long as there is power connected to the Pi.

That is to be expected. The halt target only stops the CPU and nothing from the chip set.

You can use halt target instead of poweroff target:

ln -s /usr/lib/systemd/system/halt.target /storage/.config/system.d/poweroff.target
systemctl daemon-reload

There have been issues with the autoconnect status in the past, please check with:

grep AutoConnect /storage/.cache/connman/*/settings

"Still something missing to completely support your card."

I've no idea if there is currently an out of kernel tree driver required.

Do you use the recommended BIOS settings?

Quote from bobsmith

Thank you for your help, mglae, unfortunate I couldn't get your plugin to work

Congratulation, you found a Kodi bug . Installation from ZIP is failing when no repository is available.

To the RTL8821C issue:

Feb 14 00:24:54.424500 LibreELEC kernel: #PF: error_code(0x0000) - not-present page
Feb 14 00:24:54.424569 LibreELEC kernel: PGD 110000067 P4D 110000067 PUD 110224067 PMD 0 Feb 14 00:24:54.424585 LibreELEC kernel: Oops: 0000 [#1] SMP NOPT
Feb 14 00:24:54.424601 LibreELEC kernel: CPU: 2 PID: 460 Comm: systemd-udevd Tainted: P           O       6.1.11 #1
Feb 14 00:24:54.424613 LibreELEC kernel: Hardware name: HP HP Desktop M01-F0xxx/8643, BIOS F.31 03/29/2021
Feb 14 00:24:54.424623 LibreELEC kernel: RIP: 0010:rtw_pci_read32+0x16/0x20 [rtw88_pci]
Feb 14 00:24:54.424651 LibreELEC kernel: Code: 48 03 b7 a0 7a 00 00 48 89 e5 66 8b 06 5d e9 05 77 89 ee 90 f3 0f 1e fa 0f 1f 44 00 00 55 89 f6 48 03 b7 a0 7a 00 00 48 89 e5 <8b> 06 5d e9 e6 76 89 ee 66 90 f3 0f 1e fa 0f 1f 44 00 00 55 89 f6
[...]

Page fault when accessing the card, likely there is still something missing.

No idea.Is is installing successfully on my side.

To research network issues I've created a gbmshell addon temporary replacing kodi with a shell.

You can install the attached tools.gbmshell-1.0.0.0.zip addon from USB stick and export kodi, dmesg or journalcll logs the same way.

Our usual pastekodi tool can be used locally with pastekodi -c >/path(to/log

elonesna Yes, accepting the PW but failing afterwards is weird. Having no idea either.

elonesna The output of journalctl -u sshd might be helpful after a failed connect.

1. Extend the append line, don't create a new one
2. I had a typo, use i915.enable_fbc=1 i915.enable_guc=3 (I update my original post)

... or you can try the work around of https://github.com/LibreELEC/LibreELEC.tv/issues/7299

Maybe CPU is to recent.

Only idea is to test LE nightlys whenever the kernel is updated.