Reply to thread

Message

<blockquote data-quote="deeptho" data-source="post: 1121377" data-attributes="member: 215446">pk008,first of all are you sure that the &quot; DVB-S2X TP with FEC 25/36 info is correct.Websotes are not always uptodate, so it is dangerous to rely on them for thistype of detailed information.In any case, the matype field provides info on&nbsp; streamtype (11= transport stream),multistream (1=single stream), ccm/acm (1=CCM),syncrhonisation&nbsp; (0=not active)null packet deletion (=0 none) rolffooff (10 = 0.20).So this is unrelated to FEC and type fof modulationFEC and such are gotten form the modcode, which I cannot see in this report.The driver has no knowledge of FEC_25/36. All of this is based on some giant lookup tables, whichmay contain incorrect entries.&nbsp; I can fix if I know what is wrong.So if you can provide me with the correct modcode,&nbsp; I can proceed. I cannot receive this satellite myself.With some effort, you can get the modcode either fromthe neumo-blindscan program (by adpating it to add a DTV_MODCODE call in getinfo)or from the the driver debugging information.Accessing the debug log requires a few steps1. configure your system (e.g., rsyslog) so that it actually logs kernel debug messagesFor example, in rsylsogd, you need to add the following line to /etc/rsyslog.confkern.debug&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp;&nbsp; /var/log/debugyou need to restart bysystemctl restart rsyslog2. activate extra debug messages: as root:echo 1 &gt;&nbsp; /sys/module/stid135/parameters/stid135_verbose/var/log/debug will then start to log lines withGOT MODCODE followed by the number.Or you could get the modcode&nbsp; from some other program (maybe on windows)Note that I did not write these drivers. I just fixed them where needed and then adapted what was missing.It is a huge piece of software&nbsp; with many weird pieces of code (and bugs).</blockquote>

[QUOTE="deeptho, post: 1121377, member: 215446"] pk008, first of all are you sure that the " DVB-S2X TP with FEC 25/36 info is correct. Websotes are not always uptodate, so it is dangerous to rely on them for this type of detailed information. In any case, the matype field provides info on streamtype (11= transport stream), multistream (1=single stream), ccm/acm (1=CCM), syncrhonisation (0=not active) null packet deletion (=0 none) rolffooff (10 = 0.20). So this is unrelated to FEC and type fof modulation FEC and such are gotten form the modcode, which I cannot see in this report. The driver has no knowledge of FEC_25/36. All of this is based on some giant lookup tables, which may contain incorrect entries. I can fix if I know what is wrong. So if you can provide me with the correct modcode, I can proceed. I cannot receive this satellite myself. With some effort, you can get the modcode either from the neumo-blindscan program (by adpating it to add a DTV_MODCODE call in getinfo) or from the the driver debugging information. Accessing the debug log requires a few steps 1. configure your system (e.g., rsyslog) so that it actually logs kernel debug messages For example, in rsylsogd, you need to add the following line to /etc/rsyslog.conf kern.debug /var/log/debug you need to restart by systemctl restart rsyslog 2. activate extra debug messages: as root: echo 1 > /sys/module/stid135/parameters/stid135_verbose /var/log/debug will then start to log lines with GOT MODCODE followed by the number. Or you could get the modcode from some other program (maybe on windows) Note that I did not write these drivers. I just fixed them where needed and then adapted what was missing. It is a huge piece of software with many weird pieces of code (and bugs). [/QUOTE]

Verification