Posts by UNPi4

Hi,

I am using cyberghost with no problems (only username/password) and with the normal openvpn.service.

With installed telerising.script it is also working, but then I had to adjust the timing with systemd.

The same thing here.

I am only using simple IPTV watching TV-channels.

Starting with ca. 300 MB the memory-consumption can quickly grow by switching between the channels several times via remote control.

First the channels appear fast. Later more and more slower. The memory usage is then round about 500-600 MB.

The old channels are "not released".

If it's to slow I must restart kodi.

Hallo.

I just noticed a strange WLAN-connection-Problem:

1. If there is only 1 WLAN configured with the Passwort,

everything is working normal.

2. When a secound WLAN (available) is configured,

Libreelec starts switching between these 2 WLANs.

You can see it "Libreelec- connection".

Libreelec can not decided which one to use.

3. Libreelec doesn't remember the last choosen WLAN as

preferred connection. It is switching permanent

between the 2 available Accesspoints (in my case).

4. I must delete the Password for 1 Accesspoint to get the

other working.

5. Is there another solution ?

6. This problem exists in LE11 but also in LE10.

I think you are right. I tried to be careful, but there is sometimes a smal way to go.

I just noticed, that drmprime and direct-to-plane are working when I disable arm_boost=1 in the /flash/distroconfig.txt

Do I have an old pi4 which can not work with this standard-option?

Currently running:

Linux LibreELEC 5.15.56 #1 SMP Tue Aug 2 23:13:43 UTC 2022 aarch64 GNU/Linux

Checking it s. https://www.reddit.com/r/raspberry_pi…aspberry_pi_os/

with

od -An -tx1 /proc/device-tree/emmc2bus/dma-ranges

gives:

LibreELEC:~ # od -An -tx1 /proc/device-tree/emmc2bus/dma-ranges

00 00 00 00 c0 00 00 00 00 00 00 00 00 00 00 00

40 00 00 00

The "40" in the second line mean's that it is an older Chip?

May it be helpfull to allow the boost as an config-option in LibreElec if not all pi4 can work with it?

Thank's for reading.

Sorry, I have translated this text with Google ...

After testing various settings to create and install an executable version on a Rpi4 2GB, I have good ones
Experiences made with following settings:

1. With the used version inputstream.adaptive.so.19.0.1 I checked https://github.com/kodi-pvr/pvr.iptvsimple/issues/294 HTTP2 disabled. Maybe at some point that won't be necessary anymore. So the "401" Errors are gone.

/storage/.kodi/userdata/advancedsettings.xml:

 <advancedsettings> <network> <disablehttp2>true</disablehttp2> </network> </advancedsettings>

2. Since I had WiFi problems, I asked https://raspberrypi.stackexchange.com/questions/9660…e-off-permanent

set the powersave mode to OFF. With the Pi4, due to the described interactions between HDMI and WLAN masking the HDMI ports with copper foil (snail tape) is recommended. That has both increased reception and stability.

3. Following the notice at https://forum.kodi.tv/showthread.php?tid=343068 I have the DRM-PRIME decoding under Settings - Player completely deactivated (software and hardware). There I also switched the prime reender mode to EGL, since direct DMA use was also problematic. Also a general increase in memory split in /flash/config.txt to 256 MB brought no improvement.

4. The number of video buffers (default 3) under Settings - System - Video I reduced it to 2. All attempts to use 3 always have a short time to abort. It didn't matter whether with or without DRM-PRIME.

5. Since I'm using an openvpn connection and using the inputstream addon and AES-128-GCM problems, I adjusted the openvpn-config for Kodi 19.04 on AES-256-GCM (I removed the remote line):

client
dev tun 
proto udp 
auth-user-pass #PATH/pass.txt 
resolv retry infinite 
redirect-gateway def1 
persist key 
persist-tun 
nobind 
cipher AES-256-GCM 
ncp-disable 
auth SHA256 
ping 5 
ping exit 60
ping-timer-rem 
explicit-exit-notify 2 
script-security 2 
remote-cert-tls server 
route delay 5 
verb 4 

mssfix 

ca #PATH/ca.crt
cert #PATH/client.crt 
key #PATH/client.key 

for Kodi 20 Nexus Trial (Used: LibreELEC-RPi2.arm-11.0-nightly-20220727-fcc8f2f.img.gz) you can also use CHACHA20-POLY1305 for the data-channel, which means less work for the Pi despite AES-NEON (https://forums.raspberrypi.com/viewtopic.php?t=317075):

client
dev tun
proto udp 
auth-user-pass #PATH/pass.txt 
resolv retry infinite 
redirect-gateway def1 
persist key
persist-tun
nobind 
cipher AES-256-GCM 
#ncp-disable 
auth SHA256 
ping 5
ping exit 60 
ping-timer-rem
explicit-exit-notify 2 
script-security 2 
remote-cert-tls server 
route delay 5 
verb 4 

mssfix 

data-ciphers CHACHA20-POLY1305
data-ciphers-fallback AES-256-GCM 

ca #PATH/ca.crt 
cert #PATH/client.crt 
key #PATH/client.key

6. The Pi temperature is quickly around 70° C when the case is open. https://en.linuxteaching.com/article/raspberry_pi_throttling The Kodi 19.04 version is currently running stabey, the Nexus test version at least more stable than without the adjustments.
I added the openvpn option mssfix to fix problems with the packet size with DSL connections.
(Default value of 1450 allows IPv4 packets to be transmitted over a link with MTU 1473 or higher without IP level fragmentation)

Maybe this experience will be useful for someone.