Add these lines to the end of /flash/config.txt - see here for details https://wiki.libreelec.tv/configuration/config_txt
CPU isn't the bottleneck in HD 60 FPS H264 decoding, core and h264 are the important blocks involved there.
so long,
Hias
Add these lines to the end of /flash/config.txt - see here for details https://wiki.libreelec.tv/configuration/config_txt
CPU isn't the bottleneck in HD 60 FPS H264 decoding, core and h264 are the important blocks involved there.
so long,
Hias
ssh in, run "pastekodi" and "pastecrash" and post the URLs you got.
so long,
Hias
In case you didn't do it already: run "getedid delete"and reboot - otherwise any changes to your TV settings or subsequent "getedid create" commands won't have any effect, the edid from your TV on the very first "getedid create" call will still be used.
so long,
Hias
Do you still have lircd.conf around? If yes, this is expected. You can either use lircd or ir-keytable but not both at the same time.
so long,
Hias
You can use eg systemd.unit=multi-user.target - see https://www.freedesktop.org/software/syste…l#systemd.unit=
so long,
Hias
Concerning SD cards: I've got rather mixed results with Kingston and rather poor results with Transcend in the past (also on portable audio recorders, cameras and phones) so I tend to avoid them.
One of those cards even bricked my parents' Marantz audio recorder, it's update process didn't verify firmware checksums and missed that a few blocks of the firmware file were corrupt (all 0xff). Card went to the bin but it took me a long time to unbrick the audio recorder.
I'm almost exclusively using Sandisk Extreme 32GB cards on RPis since a few years and didn't have any issues with those yet.
so long,
Hias
QuoteLE ships with "memtester", you can use it if you suspect RAM issues.
Stop kodi ("systemctl stop kodi") and all other programs you don't need to make as much free RAM available as possible, then check with "free" how much free memory you got and run memtester, specifying a bit less memory. eg if you want to check 600MB run
so long,
Hias
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
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