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.
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.
Flash two SD cards; one with LE, one with Lakka. If you want to boot Lakka .. swap cards.
The box image should work fairly well on WP2 except for DVB support (there is none) and some of the fancier bits like HDR to SDR conversion (also missing) and 3D support (which never really worked in the vendor kernel either). The only add-ons I'm aware of that continue to have issues with Kodi 19/20 and Python3 are pirate ones, and I think it's brilliant if those don't work.
failing that ill be going for the 4GB N2+ in hope some of the coreelec builds make their way into LE and it becomes very supported
LE has absolutely zero interest in resuming Amlogic vendor-kernel images, so that is 100% not going to happen. I'm reasonably sure that CE will continue to maintain their fork though.
I'd see if you can can simply copy the binary from the container to /storage and run from there. It's never guaranteed, but simple binaries without heavy runtime dependencies can often be copied over from e.g. Rasberry Pi OS to an LE install. If it works, use autostart.sh to add the binaries /storage/location to $PATH at boot time and you can avoid the complication of docker.
The current images in my share have not been tested (as I'm nowhere near LE boxes this week) but are rebuilt with Python 3.8 (reverting the 3.9 and 3.10 bumps in LE master branch).
Add-on crashes are probably some known problems with Python 3.9 that are affecting all development images at the moment. It's not specific to the AMLGX images (mine or nightly).
This overviews the process https://docs.rackspace.com/support/how-to…p-and-iptables/ but achieving something similar in LE would need a custom image with a number of extra pacakges baked in since you cannot install packages like Desktop Linux OS. However, I'd question the value of doing this. If you're hosting something and want to deny service to Russian/Byelorussian users; you're hosting things from the wrong OS in the first place (we would strongly advise against exposing LE to the internet, it is not designed for it). And if the use-case is blocking threats; any half-competent threat actor knows not to conduct business from IPs in their nation state (basic OpSec to avoid atttribution).
It's a while since I tested one but Cubox-i devices were booting and could handle H264 decoding last time I looked. The SoC has no support for HEVC so will need to software decode that format .. I doubt with good results. I have no time for testing anything right now but you can boot from an SD card and have a look at current test images and report back.
The OE forum link is dead for me .. I wasn't able to reacht the forum there for over a year now.
You're probably hitting the "flip done, timeout" problem. Update to LE10.0.2 and then run the RPi firmware update from LE settings.
I use a Flirc case in a semi-open space (small cabinet, behind a speaker-cloth screen) and play all kinds of media. I've not seen issues with RPi4 and cooling since the early pre-production boards which were toasty warm (and before the first flirc case samples shipped). I see no problems with HDR content either (no DV, but you won't get that on Allwinner either). I run a deliberately simple setup .. default skin, Gb Ethernet to a switch and all content on a Synology box in the Network because USB drives and cables everywhere are a pain in the arse. I have cables and AVR that will do 4K@60 but the only content I can find is test media so I don't bother enabling support and leave things in the default up-to 4K@30 mode. I avoide CEC as I have too many test boards hooked up and it's not reliable and missing things I care about. I have a simple BT remote which is good. RPi4 is the least drama device I own - I think minor changes to your setup solve most of the issues.
I'll let others chime in with advice on Allwinner and RK devices.
You might have downloaded an LE image from the LE website, but you definitely didn't download a Raspbian image. LE boot config is in /flash which needs to be remounted read-write to edit (mount -o remount,rw /flash). I've moved to the Allwinner section of the forum.
LE technical direction is to drop X11 and switch to GBM .. the same "run on the framebuffer" approach that we've used on RPi images for the last decade and also use (via V4L2) on all other ARM SoC platforms. This works great with Intel and AMD GPUs and is in the early infancy of working with nVidia after they recently capitulated on doing their own thing (which nobody adopted) and gained mesa support. To be clear, nVidia are slowly moving in the right direction, but there is still lots of missing stuff (NVDEC) and no guarantee that nVidia GPUs will have good/full support under GBM anytime soon.
Our master development branch currently still supports GBM *and* X11 image types (and Wayland, which is used with Lakka) but since GBM is our main technical direction that's the only one we auto-build and publish for testing https://test.libreelec.tv/ .. but you can self-build an X11 image or hunt around in this forum to see if anyone's sharing them you can test. Currently you will need an X11 image to get the right drivers etc. to use the card.
Again, the built-in Intel GPU on the motherboard will outperform the nVidia card for LE use. If you want the nVidia card for some other OS and use-case (Gaming, etc.) that's fine, but for LE use the nVidia card is just going to cause problems for you. Don't put a $1000 card on the shelf, sell it and use the $$ for something more meaningful.
Merged. Next nightly should have it included.
Any help what's going on?
No boot and debug Kodi logs = no interest in blindly guessing at your problem.
What is the build command for your odroid-c2 image ?
PROJECT=Amlogic DEVICE=AMLGX ARCH=arm UBOOT_SYSTEM=odroid-c2 make release
NB: Building aarch64 images should work, but we don't build aarch64 releases so there is no repo with aarch64 binary add-ons.
If you have integrated Intel graphics, use them. The GPU will perform better than the nVidia card.