We will **pause further testing until a newer kernel (e.g. 6.8+) explicitly introduces framebuffer export improvements, writeback support, or enhanced plane access.**
LE13 (nightlies) are using Linux 6.12.x (LTS) for some time already and if you need to go even newer RPi devs have Linux 6.14 and 6.15 branches in their GitHub repo.
To boot LE you need:
a) Bootloader installed to the disk. Can be syslinux or Grub2 or whatever you are using for the multi-boot; with a configuration file somewhere (as defined by the needs of that bootloader) that creates an LE item and tells it where the KERNEL and SYSTEM files are to be found.
b) Boot files partition containing KERNEL and SYSTEM. Can be VFAT or EXT4 and 512MB or 1GB sized.
c) Storage partition. Must be EXT4 and whatever size you like for your needs. No files required as the OS will populate anything it needs on /storage on first boot.
The complicated bit is A and we don't support multi-boot setups because it's a pain in the rear to figure out what's needed and then support the resulting mess and inevitable deletion of Windows + Music Collection + Photo's of kids that happens when things aren't done right. When we say not supported we mean "we are not even remotely interested in touching that problem" so you really do need to go figure out that bit for yourself.
As far as I can see the ID's of the device are mapped to the right drivers and those have probed and loaded.
I don't have anything to suggest, other than emailing the linux-asoc mailing list.
The GBM/V4L2 video pipeline is completely different to the previous method used with RPi boards so the approach also needs to be different and zero-copy rendering brings inherent problems for the ambilight use-case. The same issue also exists with Allwinner, Amlogic, and Rockchip devices that use the same DRM framework in the same way.
lrusak did some initial work on screenshot support a couple of years ago: https://github.com/xbmc/xbmc/pull/18741 but IIRC this had a problem level of impact on rendering and the effort stalled. It might be acceptable to resurrenct that for the kind of ad-hoc screenshot usage but IIRC it's the wrong approach for 60fps video.
Our advice is (and has been since LE10) that people wanting to use Ambilight should use an HDMI grabber device. It's not as cheap as past methods, but it's simple and works everywhere.
The error message itself is misleading and wireless being wireless there's a large number of potential variables including poor signal which RPi boards are inherently prone to. Over time things seem to have generally improved though, and you're the first person flagging an issue in this forumn for some time.
LE13 nightlies are running newer kernels and lots of other bits. Perhaps make a test install on a spare SD card and see if that helps.
Edit project/Generic/linux/linux.x86_64.conf and search for CONFIG_ASUS_WMI .. change it from unset to CONFIG_ASUS_WMI=m and then add CONFIG_ASUS_NB_WMI=m underneath it, save/exit and then rebuild the image with the change. There's really no need to use make menuconfig.
Sector by sector cloning is (literally) a waste of time. It's faster to copy data in the source filesystem to a target filesystem than to copy the entire filesystem. It also ensures you don't need to fix the incorrect partition/filesystem geometry data that you cloned.
Not going to be implemented by LE because we are not RPi kernel developers.
Needs https://github.com/LibreELEC/LibreELEC.tv/pull/7864 to be merged as a basic step. Also needs upstream kernel developers to finish writing all the drivers because AFAIK that SoC type is still missing a ton of things. If you've been using it for a while already I assume you are either using some kind of vendor kernel (which we won't use on principe) or it's a desktop distro release missing a bunch of media functionality.
ideally by extracting the ISO file to its own partition (as recommended for Google TV)
Good luck with that. We don't ship an ISO image; never have and never will.
I would find it better if I create 2 empty partitions and copiedthe required files from the ISO into them
Assuming you mean the .img file (not .iso) then you are thinking in the right direction. No need to clone anything. Just copy KERNEL and SYSTEM to a dedicated LE boot partition and create whatever bootloader entries are required for whatever bootloader you are using; crib the general content from syslinux.cfg. Note that the boot partition can be VFAT or EXT4 but the /storage partition MUST be EXT4 to support Linux permissions. Also note that we do not provide support for multi-boot configurations.
Maybe consider using the last working nvidia drivers that works perfectly from 20250412 570.133.07 ?
The path of progress is FORWARDS, not backwards, so no.
Note that you are using a pre-alpha nightly image. If you expect stability you are using the wrong release.
I think someone spotted the issue: https://github.com/LibreELEC/LibreELEC.tv/pull/10082
Would it be possible to enable support for at least `drmModeGetResources()` on `/dev/dri/card0`?
No idea. Go ask the Raspberry Pi kernel developers responsible for DRM support in the kernel. We don't write that stuff.
I've never used it (and no idea how to use it) but the "hid_mapper" binary is in the system-tools bundle in the LE add-on repo.
nvidia rtx a2000 12gb version
nVidia support is currently broken in LE13 nightlies and might take a while to fix as nobody on staff has anything to-hand that can run the offending 570.xx drivers: we have been telling users to avoid nVidia GPU purchases for years and it seems we have heeded our own advice. It probably needs a motivated user to figure out the issue and send a fix. If the card is also supported by the older 550.xx driver you can use older nightlies.
dtech has an LE 9.2.8.x image which should be usable, although these days the majority of Leia add-ons are becoming outdated, but for local media it can extend the life of things.
How would one go about updating the jellyfin server to the latest version?
Someone submits a pull request to the libreelec-12.0 branch in GitHub bumping the version and updating the SHA256 hash, then the request is merged and gets automatically built overnight and pushed to our repo.
Mostly bumping gets done by staff, but anyone can submit the change.
Have 2 movies in 1080i@25 resolution
Then Kodi playing at 50fps is correct, because Kodi only outputs progressive, so it must render each interlaced (half) frame as a full progressive frame and you need 50 frames to account for 25 interlaced frames.
I lose frames at 50 refresh rate
I normally recommend people re-rip from the original media when the encoding is bad, but you've stolen a movie off the internet that's been ripped into a lossy interlaced format. I guess that made sense to the original pirate that created and shared it.
The only issue I can see is that you're expecting a lossy pirate rip to be high quality 
It should have been built/distributed for all architectures.
