The update tar file includes md5 checksum files for SYSTEM and KERNEL (located in the target folder).
But the error you mentioned seems to happen on the storage partition so these checksum files won't help much.
Post the output URL of "pastekodi", ideally after you got such an error in dmesg, maybe we can sport something in the logs.
so long,
Hias
On RPi kernel command line parameters are set in /flash/cmdline.txt - note that everything has to be in a single line
I'm not aware of any general filesystem corruption issues on reboot, so I'd recommend testing with a different SD card. Also keep an eye on undervoltage messages in dmesg (and/or check throttled state with vcgencmd get_throttled).
so long,
Hias
Delete your .config/lircd.conf file - lirc will interfere with ir-keytable.
so long,
Hias
Then run "pastekodi -c > SOME_FILE_NAME" and upload the file here.
so long,
Hias
ix.io (which is used by pastekodi) sometimes has hiccups, just try running "pastekodi" again (or reboot and run all three commands again).
so long,
Hias
Hmm, that looks OK. Please run the following command and post the output:
udevadm control -l debug
udevadm trigger -s input -c add
pastekodiso long,
Hias
The file looks a bit weird (everything in one line), double-check it's fine and doesn't have windows line-endings or other stuff.
Also post the full output of ir-keytable -c -w .config/rc_keymaps/kodi
With a cut-down version it works fine here. After reboot:
LibreELEC:~ # cat .config/rc_keymaps/kodi
# table mecool, type: NEC
0x19 KEY_MUTE
0x17 KEY_VOLUMEDOWN
LibreELEC:~ # cat .config/rc_maps.cfg
* * kodi
LibreELEC:~ # ir-keytable -r
scancode 0x0017 = KEY_VOLUMEDOWN (0x72)
scancode 0x0019 = KEY_MUTE (0x71)
Enabled kernel protocols: lirc nec ``
so long,
Hias
Have you set the protocol in the keymap? Also did you use the old format or the new toml one? In the latter case you have to name the keymap file "kodi.toml".
Please post your keymap if you have problems.
so long,
Hias
Oh, that's really weird.
Thanks a lot for reporting back and telling us about the solution, and glad you got it working!
so long,
Hias
Sorry, no idea then. Since you get Dolby True HD flagged the RPi/kodi side looks fine.
Might be worth checking your AVR settings, maybe something is set up wrong (or there's some firmware bug in the AVR).
so long,
Hias
Can you test with the dolby trailers (eg Amaze Lossless Atmos) from here https://thedigitaltheater.com/dolby-trailers/
Amaze Lossless worked fine here, my LG 55C8 indicates Atmos with that file.
so long,
Hias
Did you enable True-HD passthrough in audio settings? It's off by default and you need to switch to advanced or expert level to see and change it.
For DD+ you would need to enable E-AC3 passthrough as well but I don't recommend that as it's buggy in kodi https://github.com/xbmc/xbmc/issues/19182
so long,
Hias
Please test with this RPi4 build and report back if it works
https://www.horus.com/~hias/tmp/libreelec/LibreELEC-RPi4.arm-10.0-devel-20220328220759-4d9d4e2.tar
H265 stuttering/lagging on RPi2/3 is to be expected as the old optimized code had to be dropped - see release notes.
so long,
Hias
I couldn't spot anything unusual in the logs.
BTW: when posting log always use the log upload function in LE settings (or "pastekodi" via ssh) as it'll include more info which could be relevant than just kodi.log
so long,
Hias
No need to, it's not even loaded.
The message is from the systemd service waiting for the serial device node of the bluetooth device, but this isn't created at all on RPi2.
The systemd service file could probably be improved to avoid this warning but we just picked that service file from RPiOS and it didn't bother me enough yet to create a local fix for it.
so long,
Hias
These are harmless, it's the bluetooth firmware loader service failing because RPi2 doesn't have BT. IIRC RPiOS shows the same warnings.
You can safely ignore these.
so long,
Hias
run "mount -o remount,rw /flash", the flash partition is mounted read-only by default
so long,
Hias
camelreef just wait a bit, I plan to update the RPi kernel after the issues from the clocking changes have been resolved
so long,
Hias