Hello,
Recently I noticed that playing VP9 (HW) on a RK3399 Board (NanoPC-T4), I'm getting weird glitches while playback. It glicthes for few secs then video speeds up for those same few secs to catch up.
Here is the example of it:
Play from YouTube or locally, I get the same issue. VP9 (SW) plays smoothly though.
LibreELEC 10.0.2
Video Codec: ff-vp9-drm_prime (HW)
Kindly guide on this issue.
Regards~
Hello,
As the title is telling, my containers don't gracefully stop which is corrupting files. Mostly .db files go bad on every shutdown.
How can I fix this. How to gracefully stop all my containers before docker.service is stopped and fs is unmounted? I'm using many of LSIO ones and running them with docker-compose files.
Regards~
Edit 1: LE on RK3399.
Hello,
I'm using LE on my RK3399 based SBC called NanoPC-T4. I use another service which creates Metadata for for the library (TV Shows, Movies etc) and it works all good.
Now the problem I'm having is when I completely delete a TV Show or Movie folder and then do Clean Video Library, the entry is not being removed from the library (episodes are deleted for shows).
If the corresponding folder is deleted, its entry should be removed up cleaning library, but it doesn't work. Only way to remove the entry is to goto it and do Manage... > Remove from library.
I'm using "Local information only" and media & metadata is managed by Sonarr which then triggers Library Updates in LE.
Regards~
Edit 1: Forgot to mention, I'm using the AuraMOD AIO Skin and have created custom main menu items. If this info is needed.
Hello,
I'm using Docker on LE since version 18 on NanoPC-T4 (RK3399) where LE OS is running ARM64, but why is the Docker Add-on installed is using the ARM arch?
It pulls ARMv7 images, which caused errors with many containers that should be running on ARM64.
NanoPC-T4:~ # uname -a
Linux NanoPC-T4 5.10.47 #1 SMP Tue Aug 10 16:48:07 CEST 2021 aarch64 GNU/Linux
NanoPC-T4:~ # docker info
Client:
Debug Mode: false
Server:
Containers: 20
Running: 17
Paused: 0
Stopped: 3
Images: 21
Server Version: 19.03.15
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: journald
Cgroup Driver: systemd
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 8fba4e9a7d01810a393d5d25a3621dc101981175
runc version: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
init version:
Kernel Version: 5.10.47
Operating System: LibreELEC (official): 10.0.0
OSType: linux
Architecture: aarch64
CPUs: 6
Total Memory: 3.778GiB
Name: NanoPC-T4
ID: DTLH:RKKR:V54S:BNJK:LPAG:6KVA:5TVY:5VNT:GI5Q:HD54:R7VM:7CRD
Docker Root Dir: /var/media/Docker/root
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
NanoPC-T4:~ # docker version
Client:
Version: 19.03.15
API version: 1.40
Go version: go1.14.15
Git commit: 99e3ed89195c4e551e87aad1e7453b65456b03ad
Built: Thu Jul 15 16:45:05 UTC 2021
OS/Arch: linux/arm
Experimental: false
Server:
Engine:
Version: 19.03.15
API version: 1.40 (minimum version 1.12)
Go version: go1.14.15
Git commit: 99e3ed89195c4e551e87aad1e7453b65456b03ad
Built: Thu Jul 15 16:45:05 UTC 2021
OS/Arch: linux/arm
Experimental: false
containerd:
Version: 1.3.9
GitCommit: 8fba4e9a7d01810a393d5d25a3621dc101981175
runc:
Version: 1.0.0-rc93
GitCommit: 12644e614e25b05da6fd08a38ffa0cfe1903fdec
docker-init:
Version: 0.19.0
GitCommit:Running docker -version is showing linux/arm, where it should linux/arm64. How can this be fixed?
Regards~
/var/media is symlinked to /media
Yes, my /media/Docker is an removable external drive connected by USB. I wish the RK3399 had the install to eMMC on the official LE10 builds. Because putting Docker root on the sdcard is like decreasing its life.
Edit 1:
How can tell docker.service to start after usb storages are mounted? It should be After=xxx.mount
Hello,
I want to change docker default root directory which is set in '/storage/.kodi/userdata/addon_data/service.system.docker/config/docker.cfg'.
From:
/storage/.kodi/userdata/addon_data/service.system.docker/docker
To:
/media/Docker/root
But after doing so, there is something going wrong. When I install the Docker version of Portainer-ce, its docker-compose throws 'Invalid Plugin', 'Permissions denied' errors.
This doesn't happen with the default root location. Do I need to change something else as well or am I missing something?
Regards~
Hello,
Have anyone tested the newly released Stable Beta for T4 from Rockchip – LibreELEC
How are things looking in it?
Can anyone kindly tell me if the following things are working or not in the recent builds/images:
Regards~
This thread had links to a version for Kodi 18 that seemed stable on the NanoPC-T4. All of those links are now broken... What's the latest KODI 18 image that is recommended for use?
I use the RockPro64 image from here Rockchip – LibreELEC with dtb from balbes150 to enable BT, Ethernet & WiFi.
Display MoreHi Aciel,
I'm productively using the 4er Kernel Image (25102019).
There the EMBUARY Skin works error-free.
YouTube I'm not using on the NanoPC-T4, I'm triggering it directly from TV.
Greetings
Jerry
Can you check and tell me which versions of Skin Helper Service & Skin Helper Service Widget addons installed on your system.
These two addons are what preventing custom skins on my v19 system.
@JerryPenguin Are custom skins working under balbez150 Kodi 19 (Matrix) builds? e.g Aura from the official repo.
And also when using the YouTube Adon, the Watched Indicator Marks stay there when you browse videos or YT Playslists.
Can you kindly provide a link to your builds. Last link I had shows nothing now.
Hi there Aciel,
Thank you for your reply. I've taken a look but apparently there's no image by balbez150 especially to the RockPro64 board.
Anyway, I've seen a thread referring to a image developed to the NanoPC T4 board. Is this the one I'm supposed to use?
He builds same images for all the boards. Here https://yadi.sk/d/qgyvmkow5oqcha/kodi-19, get the Kernel 4 images as they are more stable.
After you burn the image to SDCard, you'll have to edit extlinux.conf on /flash ppartition and set the dtb according to which ever board you have. After your 1st time boot to LE, from there you can start the procedure to move to eMMC from within LE Configuration.
Mainline and Nightlies images of RK3399 doesn't support eMMC device block yet.
If you want the eMMC support then try images by balbes150
Omg, today I did an update on my T4 with Rock960 LE 20191031 image and it broke my system badly.
This new image is based on Kodi 19 Alpha 1 and a lot of adons are not supported on it.
Does anyone have older image based on last version of Kodi 18?
Tested NanoPC-T4 dtb from image 20190925 KODI-18 and:
Ethernet = Working
WiFi = Working
Bluetooth = Working
HDMI & Sound = Working, 1920x1080@60 (my TV max)
eMMC = Sorry, not using your image so can't test this out. JerryPenguin will comment on this.
How's 10bit HEVC & 10bit x264 performance on your images?
Edit 1: Day 2 of testing you dtb. Why do I think with your dtb, there is a 70% less caching issue on playback. JerryPenguin, can you test it too please
Hi Aciel,
does the Rock960 image also support EMMC incl. installation?
Official images don't show the eMMC device block at all. I want to run LE from the SDCard and leave eMMC for Android/Linux Distro so I can switch in-between them.
Can you please post your output of blkid
Add new image 20190925 KODI-18
I'll give your NanoPC-T4 dtb a test today and post the results with the official Rock960 image from test.libreelec.tv.
