Posts by HiassofT

Number one cause are broken SD cards, as I mentioned in post 2. They can go bad and there are lots of fakes around.

Powersupply issues can also cause all sorts of problems. A very short voltage dip is enough to make the CPU perform wrong calculations, affect memory content etc - if it happens at the "right" time it can also corrupt filesystems, of course.

Those things are quite easy to check, use another SD card and another (official) RPi power supply.

Actual DRAM memory issues are extremely rare - most of the time power supply and/or excessive overclocking were the cause of memory corruption. LE ships with "memtester", you can use it if you suspect RAM issues.

EDIT: and of course incorrect shutdown (i.e. just pulling the plug) is also well known to trash filesystems - but I hope the OP isn't doing that

so long,

Hias

RPi defaults to 8-bit RGB 4:4:4 (LE 10.0.2 will also do 8-bit YCC 4:4:4) and will switch to 10 or 12 bit RGB/YCC 4:4:4 (if available) or 12-bit YCC 4:2:2 (as a fallback) only when playing 10bit videos.

so long,

Hias

Certainly. If the signal is poor chances are high you don't get a connection - actually that's the number one cause for "no connection" issue (and the RPi's built-in wifi is known for struggling with poor signal conditions as it has only a tiny antenna).

so long,

Hias

This doesn't sound logical, nothing in LE will create a lircd.conf file. Either the SD card is bad or you have some script/addon/... installed that creates it.

I'm not quite sure why you want to disable eventlircd but if you really want to do it use "systemctl mask eventlircd".

so long,

Hias

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
pastekodi

so 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