Posts by knedlyk

Yep, I used it for almost 2 years and then switched to ssh tunnel.

@cappsie New version is available which fixes this issue, take a look

@rewoz It looks like I have a temporary workaround. Finally my kodi stopped flickering. I did the following:

1. Decreased System->Display->Update Frequency from 60 Hz to 50 Hz

2. Set Player -> Allow using DRM PRIME decoder to No

It flickers on the beginning for a second and then runs almost without. At least with lower frequency....

Try it and give us some feedback.

Blueman, did you try suggested by Da Flex ? I have the same problem with Netflix.

I have the same problem on a Tanix TX6 board. I have to stop and then start the playback several times to stop the flickering. This only happens when watching Netflix (I don't have Amazon).

Thanks, it helped for me too!

I still don't understand. From previous answer I have understood that in case of TX6 Libreelec uses 64 bit kernel for aarch64 architecture and 32 bit userspace for running 32-bit widevine library needed fo netflix/amazon etc. Am I right?

Quote from jernej

Not sure what you want to know. It's only difference of building LE

I'm curious how to use widevine with pure aarch64 kernel and system. The purpose is very simple: I want to do the same for archlinuxarm TX6 project. They released 6.1 aarch64 kernel and uboot which run quite well on Tanix TX6. The only one problem that kodi can't run widevine with "Unsupported 64-bit userspace found. User needs 32-bit userspace on arm64".

Quote from jernej

Simple. While kernel is really 64-bit, userspace in 32-bit. In fact, widevine is the only reason why we release all ARM images with 32-bit userspace.

Ok, I understand. Where can I read more about this 32 bit userspace realization?

Quote from Da Flex

If your device has Google Chrome support, then Widevine library will be extracted from there. That's closed source code, but it works.

Mmm, not sure. I installed archlinuxarm on TX6 compiled against aarch64 architecture, but widevine library doesn't work with kodi. It says that it doesn't compatible. That is why I asked my question.

Can somebody explain, how the widevine work on libreelec on Tanix TX6? As far I know, there is no arm64/aarch64 support for widevine. Nevertheless, I see that kernel is for aarch64, but netflix works perfect with widevine installed via the inputstream Kodi plugin.

LibreELEC:~ # uname -a
Linux LibreELEC 5.10.146 #1 SMP PREEMPT Fri Oct 14 21:11:50 UTC 2022 aarch64 GNU/Linux

How it can be possible? What mechanism or tricks do you use?

Is openvfd module included in kernel for Tanix TX6 in development release?

Thanks to all. I managed to start WG server on my LibreElec. Nothing special. If someone is interested, I will post my configs.

Quote from chewitt

WG support is ultimately all about what's in the kernel (and WG is there) so there's techincally nothing that prevents LE being used to host a server, but there is no plumbing to facilitate that in the GUI or in ConnMan, which is client focussed (and no intent to add anything) so you'd have to self-create whatever scripts are needed to create interfaces and do things on boot, etc.

It is enough for me to know that no additional resources needed to start WG server.

For some reasons, I need to have Wireguard server working on my RPI with Libreelec. I tested WireGuard client and it appeared to work fine. What about WG server? Is it possible?

After a few days I managed to solve default route issue. Below there are my scripts with descriptions.

WG configuration:

/storage/.config/wireguard/wg0.conf

[Interface]
ListenPort = <port>
PrivateKey = <privkey>

[Peer]
PublicKey = <publkey>
AllowedIPs = 0.0.0.0/0
Endpoint = <endpoint hostname>:<port>

Wireguard startup script:

/storage/.config/wgconnect.sh

#!/bin/bash

ip link add dev wg0 type wireguard
ip address add dev wg0 10.0.0.2/24
wg setconf wg0 /storage/.config/wireguard/wg0.conf
ip link set up dev wg0

sleep 5

ip route flush 0.0.0.0/1
ip route flush 128.0.0.0/1
ip route add <first ip which should be routed> via 10.0.0.1
ip route add <second ip which should be routed> via 10.0.0.1
ip route add <third ip which should be routed> via 10.0.0.1

Stop Wireguard connection:

/storage/.config/wgdisconnect.sh

#!/bin/bash
ip link set down dev wg0

Systemd service:

/storage/.config/system.d/wireguard.service

[Unit]
Description=WireGuard VPN Service
After=network-online.target nss-lookup.target connman-vpn.service time-sync.target
Wants=network-online.target nss-lookup.target connman-vpn.service time-sync.target

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sleep 5

ExecStart=/storage/.config/wgconnect.sh
ExecStop=/storage/.config/wgdisconnect.sh

[Install]
WantedBy=multi-user.target

Then all traffic routes via default eth0 interface and several ip's via wg0. Routes look as follows:

$ ip route

default via 192.168.1.1 dev eth0 
10.0.0.0/24 dev wg0 scope link  src 10.0.0.2 
62.179.1.62 via 192.168.1.1 dev eth0 
62.179.1.63 via 192.168.1.1 dev eth0 
<first routed ip> via 10.0.0.1 dev wg0 
192.168.1.0/24 dev eth0 scope link  src 192.168.1.19 
192.168.1.1 dev eth0 scope link 
<second routed ip> via 10.0.0.1 dev wg0 
<third routed ip> via 10.0.0.1 dev wg0

At least, it works for me.