Project

General

Profile

Actions
Copy link

Bug #3433

closed

Transponder 11464 gets no scan

Added by Daniel Guenther over 9 years ago. Updated over 9 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DVB
Target version:
-
Start date:
2015-12-22
Due date:
% Done:

0%

Estimated time:
Found in version:
4.1-360~g0916e52-dirty
Affected Versions:

Description

Hi there,

I have a MOI Pro running with the following cards:

TurboSight TBS 62x1 DVBC frontend
TurboSight TBS 6982SE DVBS/S2 frontend

both with 2 tuners on.

I set up the cards with SATConfig "Universal LNB only" leaving the rest as default, activated both tuners and set up a network called "ASTRA".
Muxes will be recognized and most transponders get a scan, some of the have status FAIL.
The bad is that also the Transponder 11464 gets no scan and this one is carrying essential channels like "PRO7 HD" which I like to watch.

According to some guys on IRC channel i tried to play the mux, the result is:

015-12-22 11:33:27.278 mpegts: 11464H in SAT - tuning on DVB-S #1 2015-12-22 11:33:27.289 linuxdvb: DVB-S #1 - failed to tune [e=Invalid argument] 2015-12-22 11:33:29.000 mpegts: 11464H in SAT - tuning on DVB-S #0 2015-12-22 11:33:29.012 linuxdvb: DVB-S #0 - failed to tune [e=Invalid argument] 2015-12-22 11:33:34.000 subscription: 0201: No input source available for subscription "HTTP" to mux "11464H in SAT" 2015-12-22 11:33:34.001 webui: Couldn't start streaming /s

In dmesg I noticed the following:

[1634888.826863] SAA716x TBS 0000:06:00.0: DVB: adapter 2 frontend 0 frequency 864000 out of range (950000..2150000)

I have no idea why this wrong frequency is used there, other programs like w_scan are able to scan the transponder and generate a servicelist.

Actions
Copy link

Also available in: Atom PDF