Posts by chewitt

Quote from DJB628

any suggestions.

I suggest you tell us what hardware you have. If not we have a 1:16 chance of guessing the correct tar file you need.

pavuucek The OS updates cross-arch on the same hardware without issues, but binary addons might cause some warning/failure messages until they update to newer versions. So first boot after the main upgrade might have issues, but leave it a couple of minutes for secondary updates to happen and then all should be fine again. I'd recommend making a backup though .. in case things go south for some unforeseen reason.

The pvr.hts "failure to connect" warning is normal when there is no local tvheadend sever and you didn't configure the client to point to a server yet, but everything else half-visible in the screenshots just looks like a screwed up install; and considering it's an untested/unsupported platform that doesn't surprise me. There's a load of OpenGL related warnings .. maybe more. If you want a cheap HTPC device go purchase a Raspberry Pi for $30 and do things properly (seriously..)

"it works for me" .. i.e. the mirror is up and browsing libreelec.mirror.digitalpacific.com.au returns a file listing.

Please do not post the same question to multiple places in the forum. Once is enough. Be patient.

You installed the TVH client (pvr.hts) and it cannot connect to the local host (127.0.0.1). Did you install the TVH server addon?

Also be aware that the vmware image is not supported for production use (only test/dev work) and probably hasn't ever been tested in vmware player (only ESXi, Fusion, Workstation which staff have). YMMV.

Most of the work kszaq did was ported to our main repo before he retired so should be present in the current alpha images. There might be a few bits missing; if true I have no idea what they are. You'll also find quite a few packaging differences between K17 and K18 so if trying to 'backport' those to his repo codebase you'll also hit challenges. As there's no clear "this is the correct approach" .. just have a crack and see what fails

S912 devices tend to run hotter than S905 devices and "not shortcut shall be avoided" in the pursuit of profit. So check thermal temps are within a sensible range, and if not, crack the box open to make sure there's a heatsink and it's fixed properly.

Was the OE install "updated" to LE or have you done clean install? .. If it was an update; stop Kodi and rename /storage/.kodi to /storage/.oldkodi and then restart Kodi. You'll get a clean/empty install (which is easily reverted by renaming folders again) to test with. We see OE installs with so much accumulated cruft and odd settings that sometimes a spring-clean resolves things.

LE 8.2.4 was 99.9% for RPi (adding support for the 3B+) and 8.2.5 was 99% to update Pi firmware to solve some issues found (for 3B+). If you have number OCD and desperately need to see 8.2.5 on-screen; edit config/version to show that.

LE assumes booted hardware has a single GPU, and while multi-GPU configurations are not technically impossible multi-GPU-vendor configs are going to be challenging. You also need to understand the vmware image is shipped as a dev/test tool and nobody on staff has ever tested/proven things like GPU passthrough. If it happens to work that's nice. If it doesn't (which IMHO is likely) there is no bug .. it's not a use-case we support. Sorry if that sounds a bit harsh, but we don't want to set incorrect expectations for vmware support.

Напишите на Русском языке и мы переведём через Google

No. It uses a MediaTek MT8653 SoC which is not supported (and no plans to support).

The laptop will be 1080p max so you need to upgrade both 'HTPC' and AVR.

1. Most (not all, but most) LE images have a VNC *server* addon available. 2. Teamviewer (client) does not speak VNC so it cannot connect to a VNC server on an LE box, you would need to connect via TeamViewer to a Win/Mac desktop (with a VNC client installed) with network access to the VNC server on the HTPC. Performance of 2x remote viewing tools on-top of each other probably sucks. 3. If you have network access to the HTPC with VNC server installed you can connect directly using a VNC client.

NB: If you use VNC to remote view the Kodi GUI performance will be accessible for basic admin tasks. Don't expect to watch movies. Even if it does half work it's nothing something we have any interest in supporting.

To update:

a) After some basic investigation we found that swrast currently has hard requirements for X11, and our long-term plan (LE10) will see us drop all support for X11 (AMD and Intel move from X11/GL to a KMS/GBM + VAAPI (GLES) back end, and nVidia is probably discontinued) so we're not interested in pursuing that option much further.

b) No visible changes in Libhybris status, and this direction is still firmly seen as a hack by LE staff and Kodi staff.

c) The mesa driver is now capable of rendering on T860 hardware (used with the RK3399 boards and very similar to T820) in addition to T760 (used on RK3268) but the corresponding kernel driver is still at the earliest stages of being written. Great momentum building but a mountain of code to climb before we have anything useable.

In summary.. don't hold your breath for S912 mainline support.

Amlogic chose not to license the Mali T820 drivers for Linux. For alternative options read: Amlogic open source VPU decoder released .. and Dolby Vision is a proprietary (requires commercial licensing) standard so for the foreseeable future it's unlikely that anything running Linux will support it.

Post moved to the Amlogic section of the forum as it's an S905D device.