How do I get the latest eeprom update?
And what is different between the LE 12 nightly instead of LE 11.0.6 ?
"rpi-eeprom-update -a" .. then reboot, and the main difference is another 18+ months of Kodi development, and a newer RPi kernel and drivers. We will be forking the release branch soon; nightlies are stable (except for the name).
LE repo > Virtual Filesystems > Archive Support .. it was moved to a binary add-on some Kodi releases ago
The next issue will be that some of the subs providers have moved to a freemium/subscription model .. and that's not something we can really guide anyone on.
The last line contains the clue .. that's the Hub u-boot binary not the WP2 one. I'll see if I can regenerate the WP2 one (needs some setup as those files were last built on some other machine).
Nice. I'll add the module change to the next kernel defconfig bump that I push.
There are no errors from the IPTV add-ons repo. So as told already in the other thread: If it reports no add-ons, you need to discuss that with the people who created that repo (which is not LE and not Team Kodi, so not our problem to solve).
would those files be located somewhere else by any chance that I can download?
You can probably find ssv driver garbage in the CE repo. It's not on any of our file shares.
It works here 
The issue with BIOS selection is both drives are permanently connected so you have to enter the BIOS boot menu to switch, whereas with a removable SD card device it can be preferred over the HDD only when connected. The SSD will give a decent I/O performance advantage unless it's a rubbish one. So really you need to configure a bootloader capable of working with both OS.
Where should I open the PR? Here, I assume?
Correct.
what is the next upgrade I can do? I want to install Xenon
Some other distro, please.
The project does not support dual-boot configurations; it's always a complete pain in the rear to setup and future Windows updates are likely to break whatever fragile arrangement you come up with. There are some threads in the forum which describe the seqence of fiddling that worked for some other users if you search for them, but I wouldn't expect too much sympathy or help from staff, as we're all volunteers giving up free time and we prefer fun stuff on Linux not purgatory on Windows 
2024-02-27 08:12:23.466 T:553 INFO <general>: Starting Kodi (19.5 (19.5.0) Git:19.5-Matrix). Platform: Linux ARM 32-bit
2024-02-27 08:12:23.466 T:553 INFO <general>: Using Release Kodi x32
2024-02-27 08:12:23.466 T:553 INFO <general>: Kodi compiled 2023-01-07 by GCC 10.2.0 for Linux ARM 32-bit version 5.10.110 (330350)
2024-02-27 08:12:23.466 T:553 INFO <general>: Running on BCM2835 with LibreELEC (official): 10.0.4, kernel: Linux ARM 32-bit version 5.10.110
2024-02-27 08:12:23.466 T:553 INFO <general>: FFmpeg version/source: 4.3.2-KodiThe non-working file plays fine here, but RPi5 doesn't support H264 H/W decode and ffmpeg is software decoding the file. Please retest with a current LE12 nightly and run "pastekodi" and share the URL.
Was the drive formatted (anything would be good) before trying to install?
Perhaps try booting from an Ubuntu USB and use 'dd' to directly write the LE image to the 1TB drive, then interrupt boot and type "run" to run from USB (or in your case HDD) instead of starting the installer.
Honestly no idea, the best place to ask would be the Kodi forum support thread: https://forum.kodi.tv/showthread.php?tid=193014
I don't think it's possible (without extending Kodi to track tasks and generate responses on status requests) but the better/best place to ask the Q is the Kodi forum where Kodi devs might have other ideas; it's not something specific to LibreELEC.
projects/Allwinner/linux/linux.aarch64.conf:CONFIG_VXLAN=m
projects/Allwinner/linux/linux.arm.conf:CONFIG_VXLAN=m
projects/Amlogic/linux/linux.aarch64.conf:# CONFIG_VXLAN is not set
projects/Generic/linux/linux.x86_64.conf:CONFIG_VXLAN=m
projects/NXP/devices/iMX6/linux/linux.arm.conf:CONFIG_VXLAN=m
projects/NXP/devices/iMX8/linux/linux.aarch64.conf:CONFIG_VXLAN=m
projects/Qualcomm/devices/Dragonboard/linux/linux.aarch64.conf:CONFIG_VXLAN=m
projects/RPi/devices/RPi/linux/linux.arm.conf:# CONFIG_VXLAN is not set
projects/RPi/devices/RPi2/linux/linux.arm.conf:CONFIG_VXLAN=m
projects/RPi/devices/RPi4/linux/linux.aarch64.conf:CONFIG_VXLAN=m
projects/RPi/devices/RPi5/linux/linux.aarch64.conf:CONFIG_VXLAN=m
projects/Rockchip/devices/RK3288/linux/default/linux.arm.conf:CONFIG_VXLAN=m
projects/Rockchip/devices/RK3328/linux/default/linux.aarch64.conf:CONFIG_VXLAN=m
projects/Rockchip/devices/RK3399/linux/default/linux.aarch64.conf:CONFIG_VXLAN=m
projects/Samsung/linux/linux.arm.conf:CONFIG_VXLAN=mIt looks like Amlogic (and RPi 0/1) are the only kernels we ship that don't have VXLAN support enabled. That can be changed.
If you can share samples and share debug logs that demonstrate the problem we can investigate. No promises on fixes.
You need to ask the question to the operators of the IPTV add-on repo, it is nothing to do with LE or Team Kodi.