Nope, because I forget where I looked now and the conclusion was "dead end" so there's no point in looking again. Unless you're some embedded systems porting guru (in which case you would already be getting on with it instead of asking questions) this really is a dead end.
Posts by chewitt
-
-
The first step is to throw away the HiSilicon box (as it has an unsupported SoC) and replace with something recent from Amlogic
-
Connect the RPi directly to the TV and see if the video issues are gone. If they do, the inline AVR is the problem.
-
Nothing comes with a BR drive so this is a DIY project, which means an Intel CPU base and currently there is no recommendation on the GPU to partner with. Intel continues to fluff the specs of its boxes; there is always something wrong/missing from the spec. nVidia is heading towards the landfill due to their continued insistence of following different standards to all the other vendors (we may have a fun choice to ditch support for them in the future). AMD appears to be in league with Intel. Even in the ARM space there are challenges; we are in the middle of rewriting Kodi-on-Linux graphics around V4L2 and currently none of the existing main players (Amlogic, Rockchip, etc.) have mainline kernels and the proper software support .. everything is still "work in progress" and it's too early to tell how things really play out.
So, as what you seek is a unicorn that doesn't exist, pick up a cheap SBC device that will tide you over for a year or so until the real-world catches up with the dream-world.
-
Did you enable "allow remote control via UPnP" in UPnP/DLNA settings?
-
Set the TV to "just scan" or similar instead of calibrating the screen.
-
It's normal. The install image contains two partitions; one 512MB for boot, one 32MB? that is reworked on first boot to fill 100% of the remaining space on the card.
-
It's in LE settings python code.
-
Disable SSH/Samba and don't install pirate add-ons, then your device is isolated from the network and there is no need to waste your time trying install anti-malware tools. Even if something generic did compromise a device it would need to be compiled specifically for LE with knowledge of our OS and it's major quirks (like all the normal install-to location being uncompressed from a read-only file on boot into a virtual filesystem).
-
It will be useful.
-
Lots of progress on RK generally but I'm not aware of anyone taking an interest in RK3229, only the better spec RK3328, RK3288 and RK3399.
-
There are two ways to achieve this. If you add 'ssh' to kernel boot params it is forced on permanently. You will find the GUI option to disable is then hidden because permanently means permanently. If you patch the default value in the LE settings add-on code you can change the default without compromising the ability to later turn it off, which is a good thing for security.
-
I don't know enough about pi firmware internals to make a proper comment, but I doubt the "lightning bolts" appear until things are booted, so power issues during boot itself may not be on-screen visible. Also, from past experience, iIf it smells like a power problem, it is probably a power problem.
-
Make sure you use the RPi2 image (RPi2/3) not the RPi (RPi0/1) image.
-
Look at the systemd mount example(s) in /storage/.config/system.d/ and create a boot-time mount for the NAS share, then configure TVH server to use the local mount point for that remote share, e.g. /storage/recordings.
-
it is possible to use ipsec vpn (freeswan, strongswan or libreswan) on a libreelec box (wetek)?
Not by default because we don't build the Linux kernel with ipsec config and we don't build connman with ipsec support - because ipsec is almost never used outside of corporate VPN environments so it's not a target for our 'domestic' user audience. If you understand the moving parts of an ipsec implementation it's probably not too hard to create a custom image with appropriate changes; but there are no guides or instructions on the topic so it's down to you to experiment and figure it out.
-
With LibreELEC you have root access by default, so you dont need 'sudo'
What is a solution???
^ well, that's the answer to the question. Just remove the 'sudo' prefix to commands you're trying to use.
-
8.2.3 auto update won't happen because it has not been enabled on the back end .. oversight on a team members part
