[question] new stable version planned?

[9000h]

Hi @perexg, do you plan a new stable version with the current minisatip git? CU 9000h

[Jalle19]

I built the latest minisatip for myself, will see how it runs and report back. I can post binaries if it seems to work okay.

[9000h]

Hi, don't worry, if needed I can do it by myself. CU

[flotux2]

Could someone please provide the firmware with latest minisatip included?

[Jalle19]

@flotux2 try this one: https://mega.nz/file/fA9kxYRD#FKE_Hj9pzKHR8wY4SmReolA2GOFD5UMoRcLdZfMhU3Q

It's built on top of this patch: https://github.com/catalinii/minisatip/pull/764

[flotux2]

@Jalle19 thanks alot! Do you notice any difference (hopefully positive) between this new version and the last official one?

[flotux2]

With version satip-axe-202009161311-15 minisatip7 cannot be started. I can see countless entries like the following when executing logread:

Jan 1 12:01:20 (none) local0.notice root: minisatip7 exited 127, restarting

dmesg doesn't show any strange message.

With version satip-axe-201810211549-15.fw I never had these problems.

My hardware is: GSS.box DSI 400

Any idea why that happens?

[Jalle19]

My build only has minisatip, there is no minisatip7 or minisatip8. Make sure you update your /etc/sysconfig files too to reflect this.

Do you notice any difference (hopefully positive) between this new version and the last official one?

I haven't noticed any negative issues at least, and the web interface has some more details. minisatip is regularly maintained so it's always a good thing to be able to use the latest version.

[Jalle19]

Actually, I forgot to mention that I successfully use https://github.com/catalinii/minisatip/pull/736 now, it wasn't possible with the previous build.

[posixx]

@Jalle19 i installed your build, made sure only minisatip was enabled in config file:

MINISATIP="yes" MINISATIP_OPTS=""

It appears minisatip is running:

Jan 1 12:00:00 (none) syslog.info syslogd started: BusyBox v1.26.2 Jan 1 12:00:00 (none) local0.notice root: AXE drivers load start Jan 1 12:00:01 (none) local0.notice root: AXE drivers load finish Jan 1 12:00:01 (none) daemon.info init: starting pid 718, tty '': '/etc/init.d/network' Jan 1 12:00:01 (none) daemon.info init: starting pid 719, tty '': '/etc/init.d/ntpd' Jan 1 12:00:01 (none) daemon.info init: starting pid 720, tty '': '/etc/init.d/nfsd' Jan 1 12:00:01 (none) daemon.info init: starting pid 721, tty '': '/etc/init.d/satip' Jan 1 12:00:01 (none) daemon.info init: starting pid 722, tty '': '/etc/init.d/telnetd' Jan 1 12:00:01 (none) daemon.info init: starting pid 723, tty '': '/etc/init.d/dropbear' Jan 1 12:00:01 (none) daemon.info init: starting pid 724, tty '': '/etc/init.d/inetd' Jan 1 12:00:01 (none) daemon.info init: starting pid 725, tty '': '/etc/init.d/crond' Jan 1 12:00:01 (none) daemon.info init: starting pid 727, tty '': '/etc/init.d/oscamd' Jan 1 12:00:01 (none) daemon.info init: starting pid 728, tty '': '/etc/init.d/customd' Jan 1 12:00:01 (none) daemon.err udhcpc[718]: started, v1.26.2 Jan 1 12:00:01 (none) local0.notice root: DHCP deconfig Jan 1 12:00:01 (none) authpriv.warn dropbear[723]: Failed loading /etc/dropbear/dropbear_dss_host_key Jan 1 12:00:01 (none) authpriv.warn dropbear[723]: Failed loading /etc/dropbear/dropbear_ecdsa_host_key Jan 1 12:00:01 (none) cron.info crond[725]: crond (busybox 1.26.2) started, log level 8 Jan 1 12:00:01 (none) authpriv.info dropbear[723]: Not backgrounding Jan 1 12:00:02 (none) local0.notice root: Setting STV6210 gain to 8 Jan 1 12:00:02 (none) daemon.warn mountd[720]: Kernel does not have pseudo root support. Jan 1 12:00:02 (none) daemon.warn mountd[720]: NFS v4 mounts will be disabled unless fsid=0 Jan 1 12:00:02 (none) daemon.warn mountd[720]: is specfied in /etc/exports file. Jan 1 12:00:02 (none) daemon.notice mountd[720]: Version 1.3.3 starting Jan 1 12:00:02 (none) daemon.err udhcpc[718]: sending discover Jan 1 12:00:05 (none) daemon.err udhcpc[718]: sending discover Jan 1 12:00:08 (none) daemon.err udhcpc[718]: sending discover Jan 1 12:00:11 (none) local0.notice root: DHCP leasefail Jan 1 12:00:31 (none) daemon.err udhcpc[718]: sending discover Jan 1 12:00:32 (none) daemon.err udhcpc[718]: sending select for 192.168.50.162 Jan 1 12:00:32 (none) daemon.err udhcpc[718]: lease of 192.168.50.162 obtained, lease time 7200 Jan 1 12:00:32 (none) local0.notice root: DHCP bound ('192.168.50.162' '' 'netmask 255.255.255.0' | '192.168.50.254' '192.168.50.250') replacing '' Jan 1 12:00:32 (none) daemon.notice minisatip[984]: minisatip version 1.0.3-abba905, compiled in Sep 16 2020 12:49:14, with s2api version: 0501 Jan 1 12:00:32 (none) daemon.notice minisatip[984]: Initializing with 4 devices Sep 30 06:55:41 (none) cron.err crond[725]: time disparity of 3022255 minutes detected Sep 30 06:56:33 (none) auth.info login[987]: root login on 'pts/0' Sep 30 07:55:13 (none) daemon.err udhcpc[718]: sending renew Sep 30 07:55:13 (none) daemon.err udhcpc[718]: lease of 192.168.50.162 obtained, lease time 7200 Sep 30 07:55:13 (none) local0.notice root: DHCP renew ('192.168.50.162' '' 'netmask 255.255.255.0' | '192.168.50.254' '192.168.50.250') replacing '192.168.50.162' Sep 30 07:57:50 (none) auth.info login[1026]: root login on 'pts/0'

But my TVHeadend is not discovering the tuners. It worked when i ran the stock firmware of my Digibit R1.

An i doing something wrong here?

EDIT: after cold boot Digibit R1 and restart of TVHeadend i see the adapters listed, FIXED

[posixx]

hmm after restarting TVHeadend the minisatip adapters are lost again.. something is wrong here..

EDIT AGAIN: Found it: needed to disable igmp-snooping for the interfaces of TVH and Digibit. SOLVED

[Jalle19]

Yes, this has nothing to do with this new firmware version.

[flotux2]

My build only has minisatip, there is no minisatip7 or minisatip8. Make sure you update your /etc/sysconfig files too to reflect this.

Ok, I will change my sysconfig accordingly and will test again.

Btw: do you have any plans to fork maybe this repository and create new builds with the latest minisatip version on a regular basis? That would be really awesome. perexg seems to have given up further development.

[perexg]

My build only has minisatip, there is no minisatip7 or minisatip8. Make sure you update your /etc/sysconfig files too to reflect this.

Ok, I will change my sysconfig accordingly and will test again.

Btw: do you have any plans to fork maybe this repository and create new builds with the latest minisatip version on a regular basis? That would be really awesome. perexg seems to have given up further development.

Not really, but the current minisatip covers all my requirements and the new versions are usually slower. I'll try to do some updates this month.

[flotux2]

I changed my settings in /etc/sysconfig/config to:

MINISATIP="yes"
MINISATIP_OPTS=""

I cannot view any channel with DVBViewer or an Android SAP>IP client.

dmesg shows the following entries:

@@@@@@@@@@@@ fe_open 0
@@@@@@@@@@@@ fe_open 1
@@@@@@@@@@@@ fe_open 2
@@@@@@@@@@@@ fe_open 3
Unaligned userspace access in "minisatip" pid=1028 pc=0x004251b8 ins=0x0826
Unaligned userspace access in "minisatip" pid=1028 pc=0x004251b8 ins=0x0826
Unaligned userspace access in "minisatip" pid=1028 pc=0x004251b8 ins=0x0826
Unaligned userspace access in "minisatip" pid=1028 pc=0x004251c8 ins=0x1811
[dms-ts] stream stop ok
[dms-ts] stream stop ok
[dms-ts] stream stop ok
[dms-ts] stream stop ok
@@@@@@@@@@@@ fe_open 0
[dms-ts] stream stop ok
[dms-ts] stream stop ok

[Jalle19]

Please ask for generic help with minisatip somewhere else, you are most likely missing relevant options since your MINISATIP_OPTS is empty.

[flotux2]

Please ask for generic help with minisatip somewhere else, you are most likely missing relevant options since your MINISATIP_OPTS is empty.

A valid statement I would say. With version 0.7 of your latest build from 2018 I also had no additional options and it worked without problemlos. So I will use that version.

[Jalle19]

Okay. I guess I'll have to try the latest build myself.

[Jalle19]

I upgraded both my boxes to my latest build and it works fine. I'll try to get an actual release made with change log and everything, uploaded to GitHub.

[estimadarocha]

waiting for it!

[Jalle19]

https://github.com/Jalle19/satip-axe/releases/tag/build16 here it is!

[flotux2]

@Jalle19: with you latest build I get on my Grundig GSS.BOX still these error messages and no channel works. :-(

Unaligned userspace access in "minisatip" pid=1028 pc=0x004251b8 ins=0x0826

[Jalle19]

It didn't work before either?

[Jalle19]

No idea why you're getting "Unaligned userspace access" but it's surely a minisatip bug, not a bug in these builds in general.

[flotux2]

It only worked with the minisatip 0.7 builds of perexg. Your builds with the 1.x versions of minisatip never worked on my Grund hardware.

[Jalle19]

Okay. Sorry to hear that, unfortunately I don't have the time nor skills to debug these kinds of issues. My main motivation behind getting new builds out were because I need them myself.

[Jalle19]

Since minisatip doesn't seem to crash for you (judging by your earlier dmesg log snippet) the problem is likely that the default options have changed, and since you're not specifying any options (MINISATIP_OPTS="") your at the mercy of whatever the defaults are.

I suggest opening an issue here instead: https://github.com/catalinii/minisatip/issues

[PsikoBlock]

Same problem as @flotux2 with MINISATIP_OPTS=-Q.

@@@@@@@@@@@@ fe_open 0
Unaligned userspace access in "minisatip" pid=970 pc=0x0041f2ec ins=0x0826 (repeated 10 times)
Unaligned userspace access in "minisatip" pid=970 pc=0x0041f2f6 ins=0x2812
Unaligned userspace access in "minisatip" pid=970 pc=0x0041f2fc ins=0x1811

(everything repeated for fe_open 1, 2 and 3)

On the older build (201910081156-16) I'm getting (again 4 times)

Unaligned userspace access in "minisatip" pid=971 pc=0x00429f52 ins=0x2872
Unaligned userspace access in "minisatip" pid=971 pc=0x00429f56 ins=0x1811

however it works fine.

My guess is it has to do with opening the adapters, as there are 4 of them. Sadly I don't have that much time for debugging either, but am definitely willing to try out new fixes :)

[Jalle19]

So everything is working despite those log messages?

[PsikoBlock]

On the old build, yes. On your new build, streams are not working.

[CJanne]

https://github.com/Jalle19/satip-axe/releases/tag/build16 here it is!

DVBViewer won't work! I use a simple Unicable config. MINISATIP_OPTS="-j 0:0-1210,1:1-1420,2:2-1680,3:3-2040"

HTTP stream works (Webinterface) RTSP stream don't work (webinterface)