imforumman and others affected by the issue:
The workaround is now included in official LE10 nightly builds (starting with today's 20220610 build)
Add vc4.force_hotplug=3 to /flash/cmdline.txt to activate the workaround on both HDMI ports.
Also please try with 1 and 2 instead of 3 to activate it only on the first or second HDMI port and report back which values work for you.
so long,
Hias
The logs show you plugged in the HDMI cable to the wrong HDMI port (HDMI1 instead of HDMI0), please try the other one.
so long,
Hias
Start by providing logs, our crystal balls are all still on repair.
ssh in, run pastekodi and modetest | pastebinit and post the URLs you got.
so long,
Hias
Yes, you can use the SD card in the other RPi.
so long,
Hias
I've uploaded RPi4 builds with the latest version of popcornmix's patch https://github.com/raspberrypi/linux/pull/5052
LE10: https://www.horus.com/~hias/tmp/libr…054-eb85a9e.tar
LE11: https://www.horus.com/~hias/tmp/libr…608-bbb7ee2.tar
Please test with vc4.force_hotplug=3 added to the end of cmdline.txt and report back if this works.
The value 3 forces HDMI hotplug on both HDMI ports, you can also use 1 to force it only on the first HDMI port or 2 for only the second one.
so long,
Hias
You can just plug in ethernet after a wifi issue, it should connect automatically. Ethernet takes precedence over wifi so if you have ethernet plugged in wifi won't be tried at all.
so long,
Hias
hmm, that log looks like you freshly booted with ethernet cable plugged in - I don't see any failed wifi connection attempts here
so long,
Hias
Just run "pastekodi" and post the URL you got. We can't provide any more help if you don't provide full, unredacted logs.
so long,
Hias
No, by "pastekodi" logs I meant "pastekodi" logs 
dmesg doesn't help much, pastekodi includes journal (which might give some clue) and other useful info
so long,
Hias
Can your grab logs after a wifi connect fail? Usual "pastekodi" log will do fine.
LE master recently switched from wpa_supplicant to iwd and I'm wondering if that might be related.
so long,
Hias
zcat should work fine, I've used it myself a lot of times to create fresh SD or USB media.
YMMV though, ISTR some people reported that their linux desktops doing media autodetect while writing the image interfered (didn't have that issue myself yet).
Regarding x86: when you first boot from a fresh USB media you get a choice of 3 modes: install, live and run - the latter will create a persistent storage partition on the USB drive so that's what you probably want to use.
so long,
Hias
Not sure what ventoy is but you can boot from an USB stick on x86.
Concerning RPi and your filesystem corruption issues I'd say the 10 bucks for a Sandisk 32GB SD card might be a really good investment and could save you a lot of time.
so long,
Hias
LE10.0.2 also runs fine on RPi02W, but it's not officially supported because of it's small RAM.
so long,
Hias
Can you test with LE10 on the RPi and with LE11 on the x86 laptop?
so long,
Hias
See https://github.com/xbmc/xbmc/pull/17921
Teletext has known issues in kodi for a long time, the Kodi PR is now open for more than 2 years so I guess it should take at max 1-2 more years until it gets fixed
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
