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.
Posts by chewitt
-
-
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.
-
Now i ordered a RP5 and installed nightly Build but the same issues like on the RP4. i have downloaded the recommended test files from here https://kodi.wiki/view/Samples and nothing is really working.
Do you want to play files from a library of test media or watch movies?
If you want a device that plays maximum test media, including HDR10+/DolbyVision/AV1 it's probably a new-ish Android or high-end Windows device that natively supports HDCP and more codecs than an RPi5. There are few devices that can do that under Linux and none of them are supported by this distro which focusses on the upstream Linux kernel not downstream vendor/BSP kernels.
If you want to watch movies: 99% of the 4K media files in my library are 8-bit/10-bit HEVC, and some are HDR/HDR10/HLG (or have compatible fall-back to those static HDR formats) and almost all are 23.976fps (a handful might be 30fps) and 100% of them play nicely on an RPi5.
-
You now seem to be recommending a clean install and restore backup not cloning which is what I want to do
In my experience users fixate on "cloning" as the solution when there are easier and faster approaches. I'd guess that 75% of users seeking a cloning solution simply want to boot their system from a new card, and backing up the current install and restoring it to a clean install on the same LE version achieves this. The other 25% want to create a second LE instance with the same setup as the first, and the same backup and restore to same-version clean install achieves this too. True cloning is a pain in the rear as SD cards and USB sticks might have the same marketing size (128GB) but can have different sector counts due the nuances of manufacturing memory devices, which is a problem if making a bit-for-bit copy where the target device has a lower sector count (is smaller) than the source device. Cloning from smaller to larger devices doesn't have that problem so usually works fine.
-
https://pine64.com/product/rockpr…oth-5-0-module/ says this is a Cypress (aka Broadcom) CYW43455 SDIO module so the fix is probably to use the correct firwmare/nvram files for the module. If there is no board specific file provided the kernel driver will look for default files and use them, but the current ones we package are sourced from some Amlogic boards and might not give great results.
Pine64 probably have the correct brcmfmac43455-sdio.bin/brcmfmac43455-sdio.txt files to use in distro images and you can override the ones we provide by creating /storage/.config/firmware/brcm/brcmfmac43455-sdio.(bin/txt) locally and rebooting.
-
The GeForce 6100 is a firm no as it requires a "no longer supported" nVidia driver version that isn't compatible with the version of Xorg we use (for at least 4-5 years). Support probably stops around LE 8.0. I've no clue about the AMD card but if the Generic Legacy (Xorg) version doesn't work, it's likely a similar story. You can try older releases from https://archive.libreelec.tv/ but beyond a point you'll hit issues with TLS certificates and add-ons that aren't compatible.
NB: Someone's unused RPi3B will greatly outperform both cards and is likely better for the planet in electricity use terms.
