You've probably built it on x64 workstation.
Their build system doesn't support cross-compiling, you have to build it on RPi4 running either PiOS or Ubuntu, 32bit because LibreElec still only supports 32bit userspace programs.
This is exactly what I’ve done. I’ll build it from a spare pi4 then.
Built for libreelec, installed.... Wont start.
LibreELEC:~ # ./libreelec.pkg.sh
INFO: ArgonOne Daemon self extracting installer
INFO: Checking installer ... OK
INFO: Starting installer
INFO: Verify package list ... FOUND!
INFO: Extracting files ... OK
INFO: Verify contents ...OK
INFO: Installing
search /flash/config.txt for overlay ... FOUND
Job for argononed.service failed because the control process exited with error code.
See "systemctl status argononed.service" and "journalctl -xeu argononed.service" for details.
Oct 04 14:26:27 LibreELEC systemd[1]: Starting argononed.service...
Oct 04 14:26:27 LibreELEC (rgononed)[1017]: argononed.service: Failed to execute /storage/sbin/argononed: Exec format error
Oct 04 14:26:27 LibreELEC (rgononed)[1017]: argononed.service: Failed at step EXEC spawning /storage/sbin/argononed: Exec format error
× argononed.service - Argon One Fan and Button Daemon Service
Loaded: loaded (/storage/.config/system.d/argononed.service; enabled; preset: disabled)
Active: failed (Result: exit-code) since Wed 2023-10-04 14:29:57 BST; 49s ago
Process: 1242 ExecStart=/storage/sbin/argononed (code=exited, status=203/EXEC)
CPU: 1ms
Oct 04 14:29:57 LibreELEC systemd[1]: argononed.service: Scheduled restart job, restart counter is at 5.
Oct 04 14:29:57 LibreELEC systemd[1]: Stopped argononed.service.
Oct 04 14:29:57 LibreELEC systemd[1]: argononed.service: Start request repeated too quickly.
Oct 04 14:29:57 LibreELEC systemd[1]: argononed.service: Failed with result 'exit-code'.
Oct 04 14:29:57 LibreELEC systemd[1]: Failed to start argononed.service.
Display MoreThe ones that we tested and confirmed to work are the following devices:
S922X:
Minix U22X-J
Ugoos AM6BS905X4:
Homatics R4
Dune Homatics R4
Nokia 8010RockTek G2
On S905X4 P7 FEL+MEL only work through libdovi and P8.1 conversion.
On the S922X we have P7 FEL support, but MEL doesn't currently work correctly.
Best overall?
Display MoreIt's obvious that having HDR10 support is better than not having HDR10 support at all.
And yes, the differences between HDR10 content and Dolby Vision content is a lot more nuanced than the difference between SDR and HDR.
But it doesn't mean that there's no discernible difference. I admit that most people, in most cases will not be able to tell the two formats apart (given say the same equipment and 2 versions of the same source material, one DV and the other HDR10). But again, it doesn't mean that there's no difference. In some cases there are noticeable improvements in DV content due to it being a dynamic metadata format.
Having DV support is often a matter of principle for people, who are (or at least consider themselves to be) videophiles. And no, being a videophile doesn't mean you have to buy expensive media players.
Adding DV support is non-trivial. It required a lot of work for us to get it working on CE on devices that have a DV enabled SoC.
But it's possible to have it on a Linux based device, albeit not on x86 and mainline kernel.
With all the above said, I think that none of the Pi boards support DV due to the licensing issue mentioned previously. Please correct me if I'm wrong on this.
Could you recommend some hardware for CE so I could try some DV content?
Ive been running LE on a Pi4 8GB for ages. Its excellent. I pre ordered a Pi5 8GB so can't wait to see if it increases the menu/UI performance.
DV is encumbered by licensing and closed-source code needed to make things work. Kodi supports it on selected Android hardware like the nVidia shield and Firestick where the chip vendor paid-to-play and embedded the necessary stuff in the Android display pipeline; and support for DV is simply exposed to Kodi as a capability via the Android MediaCodec API.
None of the above happens on general purpose Linux or distros like LE because none of the moving parts are open-source and aside from a few scattered bits of boot and wireless firmware everyone middle-fingers closed source blobs and nobody will pay the licensing fees. The one possible exception you might look into is the latest OSMC Vero 5? box which is basically taking the Amlogic Android-Linux kernel (with all the needed codec support built-in) and perverting it for Linux/Kodi use. Go read the small print though; because I haven't and I'm only assuming it has support for DV media (but it likely does).
Thanks, this is what I thought anyway.
My experience with LE on the Pi4 has been so good with standard HDR10 content, I am struggling to feel like I might be missing out by not being able to play DV content. I always ensure my media is HDR10.
Am I really missing anything with DV compared to HDR10?
A license fee has to be payed for Dolby Vision, so Kodi will never support it.
Except Kodi does in v21 on Android no?
I guess you mean LibreElec on x86?
I’ve been a long time user of LE on a Pi4 and the experience has been excellent. 4K HDR10 with pass through of any audio stream, what more could I want?
I have one minor niggle that probably shouldn’t even be a niggle…. I’ve just got a new 77” Sony Bravia XR which supports Dolby Vision. Obviously no DV on a Pi, so I started researching other hardware options for Kodi on hardware that does support DV.
Which basically means Android…. I have used a firestick 4K max and Nvidia shield Pro but neither of them hold a candle to the Pi4 running LE.
So long story short…. Is the pi4 as good as it gets currently for Kodi on LE? I have a pi5 on pre order but literally the ONLY thing missing here is DV support.
Thanks
Original link broken, and the thread is just a wash with various modifications and fixes which do or don't work.
Not exactly what I'm looking for!
Thanks
Hi there,
I don't even think I need it as the passive cooling with the Argon One is so good.... But does anyone have an idiots foolproof guide to getting fan control working with LibreELEC in 2023?
Theres a mix of info about bodged modified scripts, a build your own daemon and various things out there..... But nothing clear and easy.
Anyone care to share?
Im not using FTP over SSH, FTPS is fine.
I have actually resolved the problem just this minute. FTPS:// is for implicit TLS, whereas FTP:// with an auth=tls flag at the end is for explicit TLS.
Please see here:
LibCurl FTPS is attempting to use SSLv3 and failing connections
Just stumbled across this.
https://everything.curl.dev/ftp/ftps
I wonder if this is what is happening. My FTP server is configured for Explicit TLS rather than Implicit (since its deprecated in filezilla server) and that CURL doc says the correct way to handle Explicit FTPS is to use ftp:// and NOT ftps://, but then to add the "--ssl-reqd" flag on the curl command.
I guess that flag can't be added to the URL in KODI? How about adding |AUTH=tls instead? So ftp://user:pass@http://ftp.myftp.com/Movies|AUTH=tls
Full log:
Sorry forgot to add, I am running kodi 19.4 under libreelec 10.0.2.
I am trying to make an FTPS connection to a server of mine running filezilla server. Its set to require explicit FTPS (min TLS v1.2) and has a public wildcard certificate (issued by major public CA). This configuration is tested working from various FTPS clients at different locations. Should probably say that I'm a network/infrastructure guy and configure servers/networks/certificates all day long. The FTPS server is good.
However adding an FTPS connection within the Kodi interface does not work. It cannot make a connection. Upon investigation heres what the client kodi logs and the filezilla server logs show. IP's/Domains changed for privacy of course.
KODI LOG:
2022-04-25 07:31:29.882 T:1002 DEBUG <general>: CurlFile::Open(0xff8e0700) ftps://USERNAME:[email protected]:21/
2022-04-25 07:31:29.882 T:1002 DEBUG <general>: easy_acquire - Created session to ftps://FTP.MYSERVERHERE.COM
2022-04-25 07:31:30.097 T:1002 DEBUG <general>: Curl::Debug - TEXT: Trying 1.1.1.1:21...
2022-04-25 07:31:30.127 T:1002 DEBUG <general>: Curl::Debug - TEXT: Connected to FTP.MYSERVERHERE.COM (1.1.1.1) port 21 (#0)
2022-04-25 07:31:30.143 T:1002 DEBUG <general>: Curl::Debug - TEXT: successfully set certificate verify locations:
2022-04-25 07:31:30.143 T:1002 DEBUG <general>: Curl::Debug - TEXT: CAfile: /run/libreelec/cacert.pem
2022-04-25 07:31:30.143 T:1002 DEBUG <general>: Curl::Debug - TEXT: CApath: none
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_OUT:
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - TEXT: TLSv1.3 (OUT), TLS handshake, Client hello (1):
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_OUT:
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_OUT: e▒▒▒▒@}
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_OUT: ▒
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_OUT:
2022-04-25 07:31:30.144 T:1002 INFO <general>: Skipped 2 duplicate messages..
2022-04-25 07:31:30.144 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_OUT:
2022-04-25 07:31:30.157 T:1002 DEBUG <general>: Curl::Debug - SSL_DATA_IN: 220-F
2022-04-25 07:31:30.157 T:1002 DEBUG <general>: Curl::Debug - TEXT: error:1408F10B:SSL routines:ssl3_get_record:wrong version number
2022-04-25 07:31:30.157 T:1002 DEBUG <general>: Curl::Debug - TEXT: Closing connection 0
2022-04-25 07:31:30.159 T:1002 ERROR <general>: CCurlFile::FillBuffer - Failed: SSL connect error(35)
2022-04-25 07:31:30.159 T:1002 ERROR <general>: CCurlFile::Open failed with code 0 for ftps://USERNAME:[email protected]:21/:
2022-04-25 07:31:30.159 T:1002 ERROR <general>: GetDirectory - Error getting ftps://USERNAME:[email protected]:21/
SERVER LOG:
2022-04-25T06:36:26.058Z !! [FTP Session 1 5.5.5.5] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted.
2022-04-25T06:36:26.058Z !! [FTP Server] Session 1 ended with error from source 0. Reason: ECONNABORTED - Connection aborted.
2022-04-25T06:36:31.789Z !! [FTP Session 2 5.5.5.5] Control channel closed with error from source 1. Reason: EINVAL - Invalid argument passed.
2022-04-25T06:36:31.790Z !! [FTP Server] Session 2 ended with error from source 0. Reason: EINVAL - Invalid argument passed.
2022-04-25T06:36:38.577Z !! [FTP Session 3 5.5.5.5] Control channel closed with error from source 0. Reason: ECONNABORTED - Connection aborted.
2022-04-25T06:36:38.577Z !! [FTP Server] Session 3 ended with error from source 0. Reason: ECONNABORTED - Connection aborted.
2022-04-25T06:36:40.889Z !! [FTP Session 4 5.5.5.5] Control channel closed with error from source 1. Reason: EINVAL - Invalid argument passed.
2022-04-25T06:36:40.889Z !! [FTP Server] Session 4 ended with error from source 0. Reason: EINVAL - Invalid argument passed.This is the line of concern:
TEXT: error:1408F10B:SSL routines:ssl3_get_record:wrong version numberFrom my research, it appears this Curl FTPS library is having a hard time dealing with TLS 1.2 or above and actually looks like its trying to use SSLv3, which of course will fail.
Any ideas?
This is perfect thanks.
Hi there,
Is there a log file or way to get a list of all files which have failed to be matched using my chosen metadata provider? I notice I have more files in my movies directory than I do movies in my media library. I believe some items may not have been matched and I'd like a list of items so I can rename appropriately?
Thanks