Create a bootloader recovery SD card using the Raspberry Pi imager https://www.raspberrypi.com/software/ - use a spare SD card and choose the desired bootloader (SD/USB/net boot) in the operating systens -> misc utilities section.
Hard to tell what went wrong when you updated, this is the first report of a failed bootloader update that I have seen.
so long,
Hias
If you are on LE11.0.6 then that is the most recent release you'll get from rpi-eeprom-update -a - the EEPROM firmware files are included in the image so they'll be whatever was current at release time.
Use LE12 nightlies or the LE12 beta (which should be likely released today or tomorrow) to get newer EEPROM or write the latest EEPROM release from https://github.com/raspberrypi/rpi-eeprom/releases here to a spare SD card to manually update the EEPROM to some desired version.
Another option is to download a RPi5 pieeprom file from here https://github.com/raspberrypi/rp…r/firmware-2712 and then run rpi-eeprom-update -f pieeprom-YYYY-MM-DD.bin
so long,
Hias
RPi5 with 4GB RAM or if you want to save a few bucks RPi4 with 4GB.
so long,
Hias
Please test with LE12, it contains VC-1 playback optimizations and lots (but not all) VC-1 files should play fine on RPi4.
so long,
Hias
An easy workaround is to boot your RPi with the LG monitor connected, then ssh in and run "getedid create".
Then your RPi4 will "think" it's always connected to the LG monitor and ignore the broken EDID of your SABA TV.
so long,
Hias
lircd is ancient legacy and nowadays isn't started unless you really want to use it and manually create a lircd.conf file in /storage/.config
LE only use the modern ir-keytable way to handle IR remotes (and eventlircd to route the buttonpresses to kodi - that's another story though) for quite a while now so you won't see lircd running on any LE installation - unless you manually created the lircd.conf file
so long,
Hias
Da Flex sorry, but Zygmunt is correct here. With an underspecced cable you'll get signal drop outs (down to no signal at all) but you should see 4kp60 listed in settings.
Missing modes is usually caused by software/EDID issues, i.e. the AVR or TV isn't advertising the correct modes or the RPi4 hasn't been configured to 4kp60 in config.txt and thus won't use the mode, even if the TV/AVR advertises that capability.
so long,
Hias
Did you enable "Ultra HD Deep Colour" in your TV's HDMI port settings? If not then the PC will likely use 4:2:0 to output 4kp60 and RPi4 will be limited to 4kp30 as it doesn't support 4:2:0.
Please post the output of "edid-decode /sys/class/drm/card1-HDMI-A-1/edid" and "kmsprint -m"
so long,
Hias
USB boot should be enabled by default in the bootloader config, so just make sure you are using the latest bootloader eeprom version.
BTW: the latest LE12 nightly images now also support updating the bootloader eeprom in LE settings, like on RPi4.
so long,
Hias
TBH I never tried that but one thing for sure: the whole soundcard/soundconfig handling in LE is an utter mess dating back to ancient OpenELEC days.
Completely nuking it and replacing it with the current ALSA default config/state handling (like any current linux distro does) has been on my TODO list for quite a while now but unfortunately I didn't find the spare time to actually do that.
So any help in that area is highly appreciated, just open a PR.
so long,
Hias
Thanks for the report, I could reproduce it here - it also happens on RPi4 when using software deinterlace.
A workaround (dropping the problematic "fences" kodi changes) should be in nightlies soon
so long,
Hias
Thanks a lot for reporting back, it's very good to know the fix helped!
so long,
Hias
Yes:
/*!
* the path to use for the Linux CEC device
*/
#define CEC_LINUX_PATH "/dev/cec0"so long,
Hias
FYI: the builds have just finished and the 20240215 nightly with the fix is available:
https://test.libreelec.tv/12.0/RPi/RPi5/LibreELEC-RPi5.aarch64-12.0-nightly-20240215-540999d.img.gz
so long,
Hias
Wait about 20h before you try the latest LE12 nightly from here https://test.libreelec.tv/12.0/RPi/RPi5/
New images are currently being built and they include a fix for the "no display" issue on a KDL-46Z5500 - see bug report here https://forums.raspberrypi.com/viewtopic.php?p=2190093#p2190093
so long,
Hias
The Raspberry Pi DAC+ and DAC Pro (formerly IQaudio DAC+/Pro) come with a 3.5mm jack and cost about 20-25 bucks.
so long,
Hias
Very likely it's the well known USB3 / 2.4GHz interference issue
https://www.usb.org/sites/default/files/327216.pdf
Simple solution is to use an extension lead for the wireless dongle so you can put it 0.5-1m away from the USB3 leads/devices
so long,
Hias
No, that's all we've got. I recommend asking on the RPi forum https://forums.raspberrypi.com/
so long,
Hias