problem setting up DVB-S2 muxes in version 3.2.18~g40a8920

Martin Hermannsen

Hello,

I got some problems while setting up tvheadend on my Synology DS412+ NAS. I installed the package from Synocommunity (version 3.2.18~g40a8920).

I attached the SkyTV Ultimate DVB-S/S2 USB-Stick from Sundtek. Supported mediaclient is working fine and can tune DVB-S/S2 streams without problems.

In tvheadend, I choose DVB network for Astra 19.2E and it found 104 muxes, also those DVB-S2 muxes but the quality is shown as No Signal. So I've tried to add such a mux manual but I cannot choose the delivery_system SYS_DVBS2 (I can't choose anything) and the constellation is fixed configured to QPSK (instead of PSK_8).

http://hermannsen.net/addmux.png

Here's the config of my DVB adapter:

{ "type": "DVB-S", "displayname": "Sundtek DVB-S/S2 (III)", "autodiscovery": 1, "idlescan": 1, "idleclose": 0, "skip_checksubscr": 0, "sidtochan": 0, "qmon": 0, "dump_muxes": 0, "poweroff": 0, "nitoid": 0, "diseqc_version": 0, "extrapriority": 0, "skip_initialscan": 0, "disable_pmt_monitor": 0 }

What could be the reason I can't receive any DVB-S transport stream?

Another guy uses this stick with tvheadend 2.11 and can configure the delivery_system and constellation. Why is this function missing in my version?

Markus Rechberger (Sundtek)

it also works with 3.2.18 (amd64)

http://support.sundtek.com/index.php/topic,1200.msg8548.html#msg8548

only difference is it's 3.2.18-gfaee94b

Syno is also using 64bit so there shouldn't be any difference, maybe your overall configuration is not okay.
Try to delete the tvheadend configuration and start over.

Martin Hermannsen

Thanks for your reply.

I already deleted my configuration and installation several times. But without success.

When I try to choose the delivery_system, I got the following debug output:

Jan 31 21:21:09 HTTP: 192.168.178.36: /dvb/feopts/delsys/_dev_dvb_adapter0_Sundtek_DVB_S_S2__III_ -- 400

This path does not exist in my system. Maybe the tvheadend package from Synocommunity ist somehow misconfigured?

Timo Kosig

Martin,

I am having exactly the same issue with exactly the same configuration (DS-412+ with 3.2.18 SynoCommunity package).

I have also tried to delete my configuration but this doesn't solve the problem.

I can suggest that I may not have had this problem before the SynoCommunity package was switched to compile with a 64 bit toolchain.

I'm willing to investigate this further if anyone has an idea how to get to the source of the problem.
I've already looked at the source of the code responsible as Adam mentioned here: https://tvheadend.org/issues/1624. Maybe TVHeadend can be built to add more debug information? Is there any debug log function that could be called from within the code?

Adam Sutton

Guys, as this is only being reported on synology builds (something we dont support officially) you're going to have to do the debugging yourselves or contact the package maintainer. Though I'm happy to try and provide some basic guidance.

I'd also strongly suggest using either master or release/3.4 branches as 3.2 will no longer be getting support.

Adam

Timo Kosig

Adam,

thanks for your reply. I'm planning to file a bug report with spksrc about this issue but as there are quite a few different architectures used by the different Synology Diskstation models I don't think the maintainer will have a DiskStation to debug this problem (as far as I can tell it only seems to be an issue on cedarview architecture systems, see https://github.com/SynoCommunity/spksrc/wiki/Architecture-per-Synology-model).

I'm a software developer myself and would be quite happy to try to figure this out if you can provide some basic guidance as how you'd approach the issue. My first line of inquiry would be to try and add some debug log statements to the extjs_dvb_feopts() method before every return statement that returns 400. So I would at least know why the method returns 400.

In terms of switching to master or release/3.4 branches - I think it has been suggested to the package maintainer. AFAIK he intends to wait for the next official stable release of TVHeadend and what might be another problem is that the Synology cross-compiling toolchain only has GCC 4.2.0 or 4.2.1. Synology will wait for DSM 5.0 until they change the GCC version.

I guess I'm correctly assuming that the master or release/3.4 branches would need GCC > 4.3 to compile?

Timo

Timo Kosig

After some research I have noticed that this is defined in the kernel headers of the 64bit toolchain which is used to build the TVHeadend binary:

#define DVB_API_VERSION 3 #define DVB_API_VERSION_MINOR 1

Would this explain why there's no delivery system available?

It's quite weird: the 64bit toolchain defines DVB_API_VERSION to 3.1 while the 32 bit toolchain defines DVB_API_VERSION to 5.4.

Adam Sutton

That is indeed the problem. S2 will not work prior to DVBv5.

Though interestingly that does indicate a bug for non S2 muxes, since the way the code is written that won't currently work.

Adam

Adam Sutton

http://pastebin.com/Xa3138uD this might allow you to add S muxes, but I'm really not sure (I've no way to test it).

Also I'd guess that your build system is quite broken as its quite probable that the kernel itself has been built with v5 support, but that the toolchain has been provided with out of date kernel headers. I think we've seen this before with synology. There is probably some way to check this, but I'm not sure.

Adam

Timo Kosig

Adam,

thanks for your feedback and the patch. I will try this tonight.

I also think that this is a problem which is caused by a mismatch of the kernel headers in the toolchain published by Synology and the actual kernel which is running on my DiskStation:

uname -a Linux DiskStation 3.2.30 #3202 SMP Fri Mar 1 01:04:10 CST 2013 x86_64 GNU/Linux synology_cedarview_412+

I've also filed a report with spksrc (https://github.com/SynoCommunity/spksrc/issues/468) about the issue, I hope that the maintainer will either switch back to the x86 toolchain (which defines DVB_API_VERSION to 5.4) for my architecture or that we can bring this up with Synology (although I don't have high hopes that they will fix this anytime soon...).

Adam Sutton

It's worth trying though, I'm pretty sure that it was synology that not so long ago was misreporting as DVBv3 and I think that was probably the 3.2 toolchain, so they may have already fixed there. Though my memory may just be failing me and it was another NAS provider!

Adam

Timo Kosig

Thanks for the encouragement, I've actually written to Synology describing the issue. I'll update this thread with their answer.

I've tried compiling TVHeadend with your patch but I'm afraid it failed with an error not finding SYS_UNDEFINED.

I've now tried option number two and I've managed to compile TVHeadend with the 32 bit toolchain. I've forced installed the 32bit Sundtek driver and things are working beautifully now. I can add muxes again, DVB-S and S2, PSK-8 is available to select as well.

Got a serviceprobe currently running, it's already found a load of HD channels which were missing.

The spksrc maintainer has also noticed my report, I guess he'll wait for Synology's answer before taking any further action.

Timo Kosig

I'm actually attaching the compiled package (it's for DSM 4.2 & cedarview architecture) so that others may benefit from it.

You can install force the Sundtek installer to install the 32bit driver by executing


./sundtek_netinst.sh -system 32bit

Markus Rechberger (Sundtek)

Timo Kosig wrote:
> Thanks for the encouragement, I've actually written to Synology describing the issue. I'll update this thread with their answer.
>
> I've tried compiling TVHeadend with your patch but I'm afraid it failed with an error not finding SYS_UNDEFINED.
>
> I've now tried option number two and I've managed to compile TVHeadend with the 32 bit toolchain. I've forced installed the 32bit Sundtek driver and things are working beautifully now. I can add muxes again, DVB-S and S2, PSK-8 is available to select as well.
>
> Got a serviceprobe currently running, it's already found a load of HD channels which were missing.
>

> The spksrc maintainer has also noticed my report, I guess he'll wait for Synology's answer before taking any further action.

I wonder why you would like to contact Synology for that?

Just use those header files:
http://git.linuxtv.org/linux-2.6.git/blob_plain/HEAD:/include/uapi/linux/dvb/version.h

http://git.linuxtv.org/linux-2.6.git/blob_plain/HEAD:/include/uapi/linux/dvb/frontend.h

replace the ones which come with the synology package and recompile, the API is backward compatible so you don't have to fear any problems.

Currently we support the latest API Version 5.6

Timo Kosig

I contacted Synology because the kernel headers supplied by them actually don't match the kernel which runs on my Diskstation (which is compiled with support for DVB API 5).

I'll have a try compiling a 64 bit version with those files.

I've already tried copying the dvb headers from the 32 bit version of the toolchain to the 64 bit version of the toolchain but that resulted in a compilation error.

Markus Rechberger (Sundtek)

Can you paste the errors?

Timo Kosig

I've just tried with the two files which you specified and I was able to successfully compile TVHeadend. Something must've gone wrong when I tried it yesterday with the headers from the 32 bit toolchain.

I will try if the compiled 64 bit TVHeadend works as expected once the serviceprobe is done.

Thanks again, really looking forward to get this sorted out properly.

Timo Kosig

Okay I managed to compile a 64bit TVHeadend against the exchanged headers. Works as expected.

Here's the compiled package for cedarview architecture Diskstations running DSM 4.2.

Michiel Roelofs

Anybody able to compile that for x86 based NAS such as 411+II?
Many thanks