[vdr] VDR with S2API (update)
Klaus Schmidinger
Klaus.Schmidinger at cadsoft.de
Sun Dec 14 13:01:55 CET 2008
On 13.12.2008 22:34, Oleg Roitburd wrote:
> 2008/12/13 Klaus Schmidinger <Klaus.Schmidinger at cadsoft.de>:
>> On 07.12.2008 14:41, Alex Betis wrote:
>>> On Sun, Dec 7, 2008 at 3:06 PM, Klaus Schmidinger
>>> <Klaus.Schmidinger at cadsoft.de <mailto:Klaus.Schmidinger at cadsoft.de>> wrote:
>>>
>>> On 07.12.2008 13:21, Klaus Schmidinger wrote:
>>> > Attached is an updated version of the patch to make VDR use
>>> > the S2API. Dominik Strasser reported that he got log entries like
>>> >
>>> > Dec 6 18:39:02 VDR vdr: [4102] ERROR: frontend 0: Das Argument
>>> ist ungültig
>>> > Dec 6 18:39:02 VDR kernel: DVB: adapter 0 frontend 1935763502
>>> symbol rate 0 out of range (451875..7230000)
>>> >
>>> > and I now also get
>>> >
>>> > Dec 7 13:03:26 vdr2 vdr: [3441] ERROR: frontend 0: Invalid argument
>>> > Dec 7 13:03:26 vdr2 kernel: DVB: adapter 0 frontend 0 symbol
>>> rate 0 out of range (5000000..45000000)
>>> >
>>> > when trying to tune to a DVB-S2 channel.
>>> >
>>> > The attached patch logs the value put into the DTV_SYMBOL_RATE slot,
>>> > and it appears to be fine. Why the value falls back to 0 when tuning
>>> > is currently totally unclear (as is the large frontend value in
>>> Dominik's
>>> > case).
>>> >
>>> > Any help in debugging this would be appreciated.
>>>
>>> Some more info: apparently the problem only happens if a DVB-S2 card
>>> (a TT-budget S2 3200 in my case) is (attempted to be) tuned to a DVB-S2
>>> channel after the driver has been freshly loaded. Once the card has
>>> been tuned to a DVB-S channel, subsequent tuning to DVB-S2 channels
>>> works fine.
>>>
>>> That scenario works fine with scan-s2 utility.
>> I just wanted to download the dvb-apps from linuxtv.org, but apparently
>> all those repositories are gone, http://linuxtv.org/hg/dvb-apps is empty.
>>
>> Any idea where to get the scan-s2 source now?
>
> http://mercurial.intuxication.org/hg/scan-s2/
When I run scan-s2 with an initial tuning file that contains only a DVB-S2
transponder (Astra 19.2E)
S 11362000 H 22000000 2/3
and change scan.c so that it first tunes to DVB-S2, as in
/* set up list of delivery systems*/
//fe_delivery_system_t delset[]={SYS_DVBS,SYS_DVBS2};
fe_delivery_system_t delset[]={SYS_DVBS2,SYS_DVBS};
I get this with a freshly loaded driver:
===============================================================================
API major 5, minor 0
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning /home/kls/vdr/scan-s2-c728a0055904/dvb-s/Astra-19.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S2 11362000 H 22000000 2/3 AUTO AUTO
initial transponder DVB-S 11362000 H 22000000 2/3 AUTO AUTO
----------------------------------> Using DVB-S2
>>> tune to: 11362:hS1C23:S0.0W:22000:
DVB-S IF freq is 1612000
FE_SET_PROPERTY TUNE failed: Invalid argument
>>> tune to: 11362:hS1C23:S0.0W:22000:
DVB-S IF freq is 1612000
FE_SET_PROPERTY TUNE failed: Invalid argument
----------------------------------> Using DVB-S
>>> tune to: 11362:hS0C23:S0.0W:22000:
DVB-S IF freq is 1612000
WARNING: >>> tuning failed!!!
>>> tune to: 11362:hS0C23:S0.0W:22000: (tuning failed)
DVB-S IF freq is 1612000
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
===============================================================================
If I run scan-s2 again, I get
===============================================================================
API major 5, minor 0
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning /home/kls/vdr/scan-s2-c728a0055904/dvb-s/Astra-19.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S2 11362000 H 22000000 2/3 AUTO AUTO
initial transponder DVB-S 11362000 H 22000000 2/3 AUTO AUTO
----------------------------------> Using DVB-S2
>>> tune to: 11362:hS1C23:S0.0W:22000:
DVB-S IF freq is 1612000
>>> parse_section, section number 0 out of 0...!
0x03F3 0x2B70: pmt_pid 0x0000 ZDFvision -- arte HD (running)
0x03F3 0x2B7A: pmt_pid 0x0000 IRT -- Simul SD (running)
0x03F3 0x2B84: pmt_pid 0x0000 IRT -- Simul HD (running)
>>> parse_section, section number 0 out of 0...!
service_id = 0x0
service_id = 0x2B70
pmt_pid = 0x1838
service_id = 0x2B7A
pmt_pid = 0x189C
service_id = 0x2B84
pmt_pid = 0x1900
>>> parse_section, section number 0 out of 0...!
VIDEO : PID 0x1842
AUDIO : PID 0x184D
AUDIO : PID 0x184E
TELETEXT : PID 0x1856
>>> parse_section, section number 0 out of 0...!
VIDEO : PID 0x18A6
AUDIO : PID 0x18B0
>>> parse_section, section number 0 out of 0...!
VIDEO : PID 0x190A
AUDIO : PID 0x1914
>>> parse_section, section number 0 out of 1...!
Network Name 'ASTRA'
>>> parse_section, section number 1 out of 1...!
dumping lists (3 services)
arte HD;ZDFvision:11361:hS1C23M5O35:S19.2E:22000:6210:6221=ger,6222=fra:6230:0:11120:1:1011:0
Simul SD;IRT:11361:hS1C23M5O35:S19.2E:22000:6310:6320=ger:0:0:11130:1:1011:0
Simul HD;IRT:11361:hS1C23M5O35:S19.2E:22000:6410:6420=ger:0:0:11140:1:1011:0
Done.
===============================================================================
So apparently not even scan-s2 is able to tune directly to a DVB-S2
transponder without first tuning to a DVB-S transponder.
Can anybody else confirm this, or am I doing something wrong?
Klaus
More information about the vdr
mailing list