I have a hunch Ubuntu/Fedora are using OpenGL (via Wayland) while LE/Generic is using OpenGLES, and thus the difference being seen is due to differences in GL vs GLES capabilities (and thus not technically a bug) but I'm not 100% sure.
Posts by chewitt
-
-
you will probably get a much better experience if you use a NAS for storage
You have wrongly included "probably" in that statement
-
Use snapshots or clone the disk for experiments. Are you mapping the GPU in the VM or using the vmare GPU?
-
Read: https://wiki.libreelec.tv/hardware/amlogic#install2internal
In the absence of UART logs that show what actually happens during boot it's impossible to comment.
-
It's possible if you compile a custom image with a different busybox configuration. Otherwise, no. The better option to remove complexity is using SSH key authentication; then no passwords are prompted-for.
-
The "Generic" image switched from Xorg to GBM graphics but IIRC the vmware GPU in the OVA should support that. However if the host GPU has been mapped through to the VM this will 100% fail on nVidia cards as there is no support for them without Xorg.
NB: I've been told the virtual hardware version of the OVA needs bumping for Workstation 17.5 (and likely other recent versions) but that something which can be tweaked locally.
-
-
There are no "central management of multiple devices" apps, but if you describe how you want to control them (and why) and what they are to be used for, there are probably things that can be done. LE and Kodi have options for access, scripting and automation.
-
-
The only time I've seen stability issues like you describe is when trying (and failing) to use a 5V phone charger that only provided 1.5-2.0A to an RPi4 board. RPi5 needs a minimum stable 5V/3A from the PSU, and that increases to 5V/5A once you start to attach USB drives and other kinds of peripherals.
-
The first step in triage is to update to a current LE12 nightly release to see if newer versions of everything have already resolved the issue. Nightlies are quite stable, we're about to issue the first release in a short beta run.
-
If you follow the Kodi forum support thread and read some of the GitHub issue tickets; some rework is needed (and being done) and when that's completed an update will be pushed through Kodi repos. Until then manual updates are needed.
-
Can I install the amlogic builds above 10 into internal?
On a random S905W box, not supported, and no plans to ever change that.
-
Would RP5 + NAS be OK?
It works fine for me (RPi5 + Synology NAS) with SMB shares and a Netgear GBit switch. I don't run anything exotic.
-
You need to invoke recovery boot again so it searches for bootscripts that tell it to load LE boot files else it will be looking for CE boot files which are different (names) and not found; hence you end up attempting to load Android.
-
Speak to Lakka devs, they have a forum.
-
The LE docker add-on stores persistent data in the Kodi userdata/addon_data folder, and AFAIK the ls.io containers that are wrapped as Kodi binary add-ons do the same. The LE backup function includes /storage/.kodi so will capture our data.
If you installed other containers via "docker pull" their data will be stored based on their compose files or launch configs; which could be anywhere (on /storage) based on what you set. If not under the /storage/(.cache/.config/.kodi) folders it will not be backed up by the LE backup function. However that function is just a tar command, so you can always just backup what you need with tar and be good. The Kodi backup add-on (in the Kodi repo) does other things; you need to define what it backs-up.
The Docker add-on will update itself when moving between LE10 and LE11 and LE12. If you're using Docker on an ARM SoC device beware that LE12 (official beta shipping soon) moved most devices from "arm" to "aarch64" CPU architecture and this will require arm containers to be swapped for aarch64/arm64 equivalents. Intel x86_64 is not impacted.
-
my only real problem is that i cannot set a static ip adress. after reboot it is back to dhcp.
No idea what the issue is, but I avoid the need to configure static IPs on client devices by creating static DHCP reservations for the client device MAC address in the router. Then I can (re)install frequently (as I do lots of device testing) and the IP for the device is always the same.
