Posts by Da Flex

Please check /storage/.cache/services/bluez.conf.

Feb 27 18:26:06.611084 LibreELEC systemd[1]: bluetooth-defaults.service was skipped because of an unmet condition check (ConditionPathExists=!/storage/.cache/services/bluez.conf).
Feb 27 18:26:06.630146 LibreELEC systemd[1]: Started bluetooth.service.
Feb 27 18:26:06.630668 LibreELEC systemd[1]: obex.service was skipped because of an unmet condition check (ConditionPathExists=/storage/.cache/services/obexd.conf).
Feb 27 18:26:06.631087 LibreELEC systemd[1]: Reached target bluetooth.target.
Feb 27 18:26:06.636231 LibreELEC (uetoothd)[596]: bluetooth.service: Referenced but unset environment variable evaluates to an empty string: BLUEZ_ARGS, BLUEZ_DEBUG
...
Sep 20 20:39:13.587846 LibreELEC bluetoothd[596]: profiles/audio/avdtp.c:avdtp_connect_cb() connect to 54:15:89:45:56:78: Connection refused (111)

Thanks. We need a complete log then...

Hmm, pretty much the same errors at both logs. I'm not familiar with NXP hardware. Search for cache settings (GUI or advancedsettings.xml), and increase values. Maybe the video needs too much cache with subtitles.

PS: Check whether the crash generates a kodi_crashlog_<TIMESTAMP>.log. If yes, upload it like here:

Post

RE: [x86-64] Unregistered exception handler message when booting

Workflow for kodi.old.log:

• install LE 12.0.1 Generic
• replicate the issue
• restart until LE boots successfully
• login by SSH
• cd .kodi/temp
• cat kodi.old.log | pastebinit
• post the resulting URL

Da Flex

September 11, 2024 at 1:41 AM

Update to LE 12.0.1. Older versions have an audio channel bug.

Quote from miguel.yarza

• If I play the .mkv file with integrated subtitles and DRM PRIME enabled => SIGSEGV crash.
• If I remove subtitles from the .mkv file with mkvmerge -o output.mkv --no-subtitles input.mkv and DRM PRIME enabled => video plays fine.

Then it's a bug at mkvmerge or DRM Prime. The DRM Prime error should be visible somewhere at kodi.log.

Maybe the AVR still remembers RPi4 somehow. Switch it off for a while.

Thanks. You can remove it from blacklist.conf again (use nano editor on SSH).

I'm running out of ideas, and gave our devs a ping. It could be similar to this, but not sure:

[SOLVED] iHD Hardware Video Acceleration Fails / Applications & Desktop Environments / Arch Linux Forums

After booting, login by SSH, run getedid create, and reboot.

Quote from hundrakg

Im happy so far with the 8.2.5, but would have been good to know why the 12.0.1 struggles?

with struggle I mean its choppy and jerky playback, sound is fine.

Quote from soder10

Rpi5 2 GB version has garbled UI output with this release.

Yep, and it was already fixed in nightly builds:

Thread

[RPi5 2GB] Not Rendering LE 12.0.1

With the keyboard I can navigate somewhere, by guessing how the interface will look like. But there was no chance to connect this thing to the network for debugging.

How to reproduce

Steps to reproduce the behavior:

1. Flashing microSD card with Raspberry Pi Imager(on mac) or LibreELEC USB-SD Creator(on Windows).
2. Plugging pi 5 to external monitor(with HDMI0), placing microSD card and power cable.
3. Waiting to finish resizing a volume with automatic rebooting after 15 secs.
4. See not fully rendered screen.

…

stalko

August 28, 2024 at 8:15 PM

chulygun Yes, that's the suggested workflow.

It must be an error in the Linux kernel, before LE starts logging.

The kodi.old.log has this part, which isn't at kodi.log:

2024-09-14 07:15:26.343 T:975     debug <general>: libva info: VA-API version 1.20.0
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Trying to open /usr/lib/dri/iHD_drv_video.so
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Found init function __vaDriverInit_1_20
2024-09-14 07:15:26.343 T:975     error <general>: libva error: /usr/lib/dri/iHD_drv_video.so init failed
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: va_openDriver() returns 1

After that the correct driver gets loaded in both logs:

2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Trying to open /usr/lib/dri/i965_drv_video.so
2024-09-14 07:15:26.343 T:975     debug <general>: libva info: Found init function __vaDriverInit_1_20
2024-09-14 07:15:26.344 T:975     debug <general>: libva info: va_openDriver() returns 0

Maybe it's worth to blacklist the iHD driver.

Quote from marialovesmatcha

Is there any way to capture a manual log? Or does the fact that no log is created mean that LE doesn't even manage to start...

kodi.old.log shows a successful boot sequence, so it's not helpful. Maybe a broken hardware part, which can't be initialized at boot sometimes. Hardware boot sequences are complex, so random results are possible.

You can search for dead hardware parts after successful boot (internal WiFi, Bluetooth etc.). I don't think it's an LE problem.