Page 17 of 18

Re: minisatip binaries

Posted: Wed Jul 01, 2020 11:02 pm
by cata
Yeah feel free to change it in adapter.h and create a pull request

Re: minisatip binaries

Posted: Mon Jul 20, 2020 6:28 am
by cata
Did you manage to test it, does it work ?

Re: minisatip binaries

Posted: Sun Aug 30, 2020 5:34 pm
by suppenkasper
Hi Cata,

It's been a long time. My Arm32 DCube is based on OpenATV 6.3. So I don't know if you could provide also binaries for this device. - I also noticed when I install minisatip the receiver doesn't shutdown anymore. It can just be rebooted. When I delete minisatip the error stays and it just appears after a fresh reflash of the receiver...

Could you also please refer or explain how to use DiseqC 1.1 (I have a bigger setup with 13 LNB's), so it's a bit of a big pitty just to be able to use one position. Even the minisatip config with DiseqC 1.0 doesn't work with my devices. I also tried this on an Octagon SF8008 (armv7l-based Hislicon-Quad-Core Box).

Re: minisatip binaries

Posted: Sat Sep 05, 2020 7:09 pm
by cata
The latest version of openatv (6.4) has the latest minisatip binaries. You can of course try the ones from the forum.

if you want just diseqc 1.1 use: -d 0:0-1
In that case src=13 will map to lnb 13 ... If you have both a diseqc 1.1 + diseqc 1.0 then the things are more complex.

About shutdown issue: if you try to run: killall minisatip , does the minisatip die?

Re: minisatip binaries

Posted: Tue Jun 08, 2021 11:03 am
by Validate
Why do you build binaries for ARM without CI?

[06 13:00:22.471 main]: minisatip version v1.1.5-76e53d1, compiled in May 31 2021 06:32:22, with s2api version: 050B
[08/06 13:00:22.471 main]: Built with dvbcsa
[08/06 13:00:22.471 main]: Built without CI
[08/06 13:00:22.471 main]: Built with dvbapi
[08/06 13:00:22.471 main]: Built without AES (OpenSSL)
[08/06 13:00:22.471 main]: Built with tables processing
[08/06 13:00:22.471 main]: Built with pmt processing
[08/06 13:00:22.471 main]: Built with satip client
[08/06 13:00:22.471 main]: Built with linux dvb client
[08/06 13:00:22.471 main]: Built with backtrace
[08/06 13:00:22.471 main]: Built without netceiver
[08/06 13:00:22.471 main]: Built without ddci
[08/06 13:00:22.471 main]: Built without t2mi

Re: minisatip binaries

Posted: Wed Jun 09, 2021 2:05 am
by cata
The arm version is for enigma boxes for which CI does not work.

If you are running on a SBC minisatip can be compiled from source code with CI support.

Re: minisatip binaries

Posted: Wed Jun 09, 2021 11:16 am
by Validate
cata wrote: Wed Jun 09, 2021 2:05 am The arm version is for enigma boxes for which CI does not work.

If you are running on a SBC minisatip can be compiled from source code with CI support.
Actually Enigma2 is exactly where I wanted to run it (Dreambox 920), because enigma itself can't extend ci+ slot for more than 1 channel at a time, unlike minisatip.
Why CI doesn't work there?

Re: minisatip binaries

Posted: Wed Jun 09, 2021 4:28 pm
by cata
The driver is different than the one present in Linux. There is also an alternative of using enigma2 for communication with the CAM:

Ser this for more details: viewtopic.php?f=5&t=670

Re: minisatip binaries

Posted: Wed Jun 09, 2021 7:29 pm
by Validate
cata wrote: Wed Jun 09, 2021 4:28 pm The driver is different than the one present in Linux. There is also an alternative of using enigma2 for communication with the CAM:

Ser this for more details: viewtopic.php?f=5&t=670
Do you refer to standalone mode or to OpenATV image, which will provide CI access? That topic doesn't touch CI question.
When I run minisatip on my box, I stop enigma2 process. But the problem I can't find binary with CI support compiled and I can't compile it myself.

./configure --enable-static --host=arm-linux-gnueabi --enable-enigma --enable-dvbca --disable-satipc --disable-axe
make

Code: Select all

make[1]: Entering directory '/home/neolo/minisatip_arm/src'
gcc -Wall -Wno-switch -ggdb -fPIC   -DDISABLE_SATIPCLIENT -DDISABLE_NETCVCLIENT -DDISABLE_DDCI -DDISABLE_T2MI -DENIGMA -o ../minisatip  ../build/minisatip.o  ../build/socketworks.o  ../build/stream.o  ../build/adapter.o  ../build/utils.o  ../build/aes.o  ../build/csa.o  ../build/dvbapi.o  ../build/ca.o  ../build/pmt.o  ../build/tables.o  ../build/dvb.o -lpthread -lrt -l:libcrypto.a -l:libdvbcsa.a -l:libdvben50221.a -l:libdvbapi.a -l:libucsi.a -ldl
/usr/bin/ld: cannot find -l:libdvbcsa.a
collect2: error: ld returned 1 exit status
Makefile:153: recipe for target '../minisatip' failed
make[1]: *** [../minisatip] Error 1
make[1]: Leaving directory '/home/neolo/minisatip_arm/src'
Makefile:11: recipe for target 'minisatip' failed
make: *** [minisatip] Error 2

Re: minisatip binaries

Posted: Fri Sep 17, 2021 12:52 pm
by suppenkasper
cata wrote: Sat Sep 05, 2020 7:09 pm The latest version of openatv (6.4) has the latest minisatip binaries. You can of course try the ones from the forum.

if you want just diseqc 1.1 use: -d 0:0-1
In that case src=13 will map to lnb 13 ... If you have both a diseqc 1.1 + diseqc 1.0 then the things are more complex.

About shutdown issue: if you try to run: killall minisatip , does the minisatip die?
Hey cata,

thanks for your answers. As I said, I need of course maximum complex circumstances... :(

I have DiseqC 1.1 16in1 switch (which uses actually 13 inputs) and behind LNB1 on DiseqC 1.1 I have a bigger 17/12 Multiswitch which uses 4 Satellites with DiseqC 1.0. - So in Enigma2 I know what I have to edit and works on all 16 satellite positions fine, but not with minisatip (unfortunately) or SatPI in newer OpenATV images... - Do you think support will be better within the next time to share tuners over network with diffrent platforms like TVH and other SatIP-Clients? I also have a bunch of USB Sat-cards like Technisat USB CI, which is also a mess with drivers under linux. My idea was to use my orange PI-Server with USB-Satcard, but also this doesn't work... Just DVB-S works on that device: https://www.linuxtv.org/wiki/index.php/ ... SB_2_HD_CI

I did this as it was described, but still no luck with DVB-S2 and for sure not with DVB-S2X unfortunately...

Maybe someone will adapt it there are some patches avaliable, but honestly can't understand why things don't get fixed anymore nowadays and linux gets more and more just unstable messy bugged code in every corner...