/etc/rc_maps.cfg and /usr/lib/udev/rc_keymaps/libreelec_multi.toml
Uh, no, LE 9.2.6 doesn't use toml files.
The wiki page describes the setup and files used in LE 9.x, master / LE 10 uses a newer ir-keytable version which uses toml files by default (the old files without toml extension are still supported though). The new toml format isn't documented on the wiki yet as it'd just confuse LE 9.x users for now, this will follow at some later point when we release LE 10.
so long,
Hias
The output looks fine and if you still have MCE Keyboard buttons mapped to menu/exit the output is expected - ir-keytable shows you that the MCE Keyboard protocol mce_kbd is supported but not enabled.
The MCE Remote (rc-6 protocol) usually has "Back" and "(DVD) Menu" buttons that map to exit/back and (context)menu in kodi. Just use these and stay away from MCE keyboard in the harmony configuration software.
BTW you can find more info on the wiki Infra-Red Remotes - LibreELEC.wiki and if you search the forum for mce_kbd you'll find info how to get MCE keyboard working - but that's rather tedious and not really needed in your case, MCE Remote should have everything you need/want and will work OOTB.
so long,
Hias
It's best to avoid the "MCE Keyboard", this is a really awkward protocol that's working poorly. Just stick to the Microsoft mediacenter (MCE) remote protocol, this is what you want to use ("Microsoft Windows Media Center SE" sounds like that might be fine, though I'm not really familiar with the harmony remotes)
so long,
Hias
Yes, LibreELEC switched to ir-keytable but lirc is still there for now if you really want/need to use it. See the wiki for more details Infra-Red Remotes - LibreELEC.wiki
Your dmesg doesn't show any sign of the gpio-ir driver being loaded, so check config.txt if you have any typos in there.
dtoverlay=gpio-ir, is all you need then you should get the following lines in dmesg (note that I use GPIO 5, so your lines may look a bit different)
xbmc:~ # dmesg | grep gpio_ir
[ 4.257079] rc rc0: gpio_ir_recv as /devices/platform/ir-receiver@5/rc/rc0
[ 4.257233] rc rc0: lirc_dev: driver gpio_ir_recv registered at minor = 0, raw IR receiver, no transmitter
[ 4.257353] input: gpio_ir_recv as /devices/platform/ir-receiver@5/rc/rc0/input1so long,
Hias
hdmi_enable_4kp60=1 is the correct setting. Also remove all other hdmi options you added and make sure you've enabled "Ultra HD deep colour" in your TV's settings (usually that setting is separate for each HDMI port, and it might be called slightly differently on your TV).
so long,
Hias
Both will work fine, choose whatever suits you best.
so long,
Hias
LibreELEC is using udevil to auto-mount external drives.
In addition to udevil that'a a udev rule to determine which drives/partitions to auto-mount, a systemd service template to perform the mounting/unmounting and the udevil config file (which defines filesystem types, options etc).
All config files are here in our repo: LibreELEC.tv/packages/sysutils/udevil at master · LibreELEC/LibreELEC.tv · GitHub
so long,
Hias
This is a known issue on 1GB RPi4s, it's a bit short on memory.
Try adding cma=64M at the end of /flash/cmdline.txt, see here for more info: RPI4 on Libreelec 9.1.502 thumbnail/pictures problems
so long,
Hias
Your initial problem was not with the total size of your SSD, but that older OpenELEC/LibreELEC versions created a rather small boot partition (/flash on the filesystem) which now became too small. Re-installing current LE (wiping your previous partitions) will fix that.
Current LibreELEC will work fine even on an 8GB SSD/SD-card/HDD, although I'd really recommend going for 32GB (or more) to have some spare room for larger movie libraries. If you want to store media files on your SSD/HDD/... you'll need a lot more space, of course.
so long,
Hias
You already got the answer to your (identical) question on the kodi forum: Updating for codecs?
Yes, RPi4 will decode h265.
If your receiver doesn't support E-AC3 simply don't enable E-AC3 passthrough in audio settings (it's disabled by default).
so long,
Hias
This is a known issue with Kodi Matrix/gbm. The milestone for fixing this has recently been moved to the next kodi version (20). See [GBM] add ability to screenshot with video plane by lrusak · Pull Request #18741 · xbmc/xbmc · GitHub
so long,
Hias
Correct. FKMS was basically a stop-gap to transition to standard linux drivers, all development is now focussed on KMS. 10-bit output, 4k etc will be added at some point but we don't have any ETA.
so long,
Hias
This is normal, 4k isn't supported by the RPi4 KMS driver yet, this still needs to be implemented.
so long,
Hias
Most devices use the kernel default of 128k (CONFIG_LOG_BUF_SHIFT=17), not sure why Generic is set to 64k. Would be best if you created a PR and change it to 17, too
hias@delle:~/private/libreelec/libreelec-git$ git grep CONFIG_LOG_BUF_SHIFT
projects/Allwinner/linux/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Allwinner/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Amlogic/linux/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=18
projects/Generic/linux/linux.x86_64.conf:CONFIG_LOG_BUF_SHIFT=16
projects/NXP/devices/iMX6/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=18
projects/Qualcomm/devices/Dragonboard/linux/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=14
projects/RPi/devices/RPi/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/RPi/devices/RPi2/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/RPi/devices/RPi4/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Rockchip/devices/RK3288/linux/default/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Rockchip/devices/RK3328/linux/default/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Rockchip/devices/RK3399/linux/default/linux.aarch64.conf:CONFIG_LOG_BUF_SHIFT=17
projects/Samsung/linux/linux.arm.conf:CONFIG_LOG_BUF_SHIFT=17so long,
Hias
Yes, that should work fine. An MCE USB receiver (the HP branded ones you can find cheaply on ebay work very well) or switching to an RPi4 (which uses a "real" USB controller) are other alternatives to the ones mentioned on the wiki.
so long,
Hias
No problem at all, this isn't too obvious.
As a rule of thumb: it's best to forget everything you learned about or find on search engines on the legacy style of video configuration/setup on RPi (i.e. hdmi... settings in config.txt)
With the switch to the KMS video driver we now use the same methods to configure video as eg Intel/AMD or all other ARM/... platforms use.
so long,
Hias
This is normal - tvservice uses the legacy functions which aren't relevant for master builds anymore (we still kept the legacy programs for testing ATM).
Use eg modetest to find out what displays are connected and what resolutions are supported.
so long,
Hias