Experiment with a current LE11 nightly from https://test.libreelec.tv/ .. these images have a much newer kernel with more GPU support. Are things now working?
Posts by chewitt
- 
					
 - 
					
https://wiki.libreelec.tv/configuration/edid#generic-x86_64 <= read up .. RPi4 under GBM/V4L2 is basically the same as any other Linux DRM device now, e.g. Intel.
 - 
					
You may/probably need to trigger recovery mode via the button on the underside of the box (toothpick method) as the boot scripts changed.
 - 
					
noggin the RPi4 SoC is basically an RPi3B+ with faster clock speed and an extra IP block for 4K HEVC, so 3D works on RPi4 under the older LE9.2 codebase as nothing really changed, but support needs to be reworked for the newer GBM/V4L2 pipeline.
 - 
					
RPi4 was designed to run way hotter than most people are mentally prepared to run their devices. Remember when it first launched and the average temps were over 65ºC?
 - 
					
Discussion on torrenting media is NOT welcome in this forum. Your post was deleted.
 - 
					
PANiCnz this is the RK section of the forum so RPi4 status isn't helpful.
RK3399 should have working HEVC for some time.
 - 
					
I have fuzzy memory that that the boot files/layout is different and thus you cannot update from LE 8.2.5 to LE10/LE11 images and it needs to be a clean install. As I'm the closest to a maintainer the iMX6 images have (and I didn't touch a Cubox-i in the last 6-months) I'd strongly suggest you test boot from an SD card first.
 - 
					
Can I install an older version of Libreelec on Pi 400 that will allow me to play 3d videos? Thanks.
It's a software issue, not hardware. You might be able to run the older LE9.2 image (which supports 3D). I have fuzzy memeory there may be newer iterations of the 400 that need firmware newer than what's shipped in the 9.2 image. I could be confusing it with RPi Zero2 though? (easiest way is to image an SD card and test).
 - 
					
The Kodi add-on provides MPD binaries. Those binaries can be run outside of Kodi too.
 - 
					
Correct (AMLGX). The box image supports vendor u-boot. The WP2 image boots maintline u-boot but requires you to erase the emmc (to clear vendor u-boot) first. I have a backup of the factory image that can always been restored if you want to test that https://www.dropbox.com/s/tw6bg3kipc8t…wp2.img.gz?dl=0 but it's not necessary.
 - 
					
I'm in Dubai which means despite it reaching 50ºC outside in mid-summer the RPi4 is used in an air-conditioned environment, albeit stuffed in a semi-open cupboard (five sides closed, one side open behind speaker-cloth) where temps are somewhat higher than the ambient 24-25ºC of the apartment. It's personal preference, but I don't want to hear the spin up/down of fans during a movie.
 - 
					
I use the flirc case with an RPi4. I would never recommend anything with a fan for HTPC use.
 - 
					
If the drive will be used exclusively with LE, ext4 would be preferred. If you need to move it between LE and Windows, exFAT or NTFS are the only options. LE11 should be using the upstream NTFS drivers now (not FUSE) which should make NTFS a lot faster.
 - 
					
rubbo There are no LE10 images but you can use the LE11 nightly or from my share here: https://chewitt.libreelec.tv/testing/ .. NanoPi-K2 is the one GXBB device that I don't have so it's untested from a boot perspective (but should work the same as any other GXBB board). Feedback is welcome.
 - 
					
You can run commands via connmanctl, e.g. "connmanctl tether wifi on" (and off) which is easier than dbus commands. Note that if you drive the feature from connmanctl the GUI on/off switches will not reflect the status correctly (but you prob. don't care about that).
 - 
					
It's a while since I booted WP2 from vendor u-boot but worst case you might need to trigger recovery mode as the u-boot bootscripts in the box image are a little different to ones used with the legacy kernel. There's no dtb renaming or such needed.
 - 
					
How do I do that with a black screen? I'd love to share the info. Is SSH enabled by default?
It's not enabled by default. You can add "ssh" to kernel boot params in cmdline.txt and this forces the SSH daemon to start at boot.