[linux-dvb] Technisat DVB-S2 Skystar HD

Manu Abraham abraham.manu at gmail.com
Sat Oct 6 22:04:10 CEST 2007


Artem Makhutov wrote:
> Hi,
> 
> On Fri, Oct 05, 2007 at 01:30:53AM +0400, Manu Abraham wrote:
>> Manu Abraham wrote:
>>> Can you please get the log for (with STB0899 and STB6100 with verbose=5)
>>>
>>> a) 3 Mhz
>>>
>>> 1) a complete cycle with a LOCK, including where it calls track.
>>> 2) 3 complete cycles where it fails to LOCK, including where it calls track.
>>>
>>> b) 10 Mhz
>>>
>>> 1) a complete cycle with a LOCK, including where it calls track.
>>> 2) 3 complete cycles where it fails to LOCK, including where it calls track.
>>>
>>> with both DVB-S and DVB-S2 modes, for the same frequency for each.
>>>
>>> Please be careful as not to mix up the logs.
>>>
>> What's up ? 
>>
>> Haven't heard after this. 
>>
>> Btw, can you do a fresh clone and try again ? Have applied the fixes to the tree, 
>> just leave the 3 MHz to 10 MHz Search range change. I have added in a fix, 
>> which affects the Timing Recovery Loop, which was wrongly calculated, ie for 
>> a different master Clock.
>>
>> Can you please check whether you see any specific change for you in there ?
> 
> I have attached the logfiles.
> 
> Sometimes I was not able to get a DVB-S2 LOCK at all.
> DVB-S worked well, but DVB-S2 did not worked.
> After rebooting the computer DVB-S2 started to work too.
> 
> The files *-DVB-S2-FAIL1 and *-DVB-S2-FAIL2 were made while I could not get a DVB-S2 lock at all.
> 
> The file 3MHz-DVB-S2-FAIL3.log.gz was made while I was able to tune
> DVB-S2 from time to time.
> 
> I also was not able to tune to a DVB-S2 channel with 10 MHz, but I don't
> have the log. DVB-S2 works quite well with 10MHz, I was not able to
> reproduce this a 2nd time.

Oct  6 16:02:31 tvbox stb0899_set_delsys: Delivery System -- DVB-S
Oct  6 16:02:31 tvbox _stb0899_read_reg: Reg=[0xf533], data=00
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf533]: 08
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf548]: b1
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf549]: 40
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf54a]: 42
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf54b]: 12
Oct  6 16:02:31 tvbox _stb0899_read_reg: Reg=[0xff11], data=00
Oct  6 16:02:31 tvbox stb0899_write_regs [0xff11]: 80
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf1c2]: 7c 07
Oct  6 16:02:31 tvbox stb0899_set_mclk: state->config=d4873750
Oct  6 16:02:31 tvbox stb0899_set_mclk: mdiv=21
Oct  6 16:02:31 tvbox stb0899_write_regs [0xf1b3]: 15
Oct  6 16:02:31 tvbox _stb0899_read_reg: Reg=[0xf1b3], data=15
Oct  6 16:02:31 tvbox stb0899_get_mclk: div=21, mclk=99000000
Oct  6 16:02:31 tvbox stb0899_set_mclk: MasterCLOCK=99000000
Oct  6 16:02:31 tvbox stb0899_search: DVB-S delivery system

[..]

Sampling Rate calculated @ 99 Mhz, sampling @ 99 Mhz

Oct  6 16:02:50 tvbox _stb0899_read_reg: Reg=[0xf50d], data=40
Oct  6 16:02:51 tvbox stb0899_read_status: Delivery system DVB-S/DSS
Oct  6 16:02:51 tvbox _stb0899_read_reg: Reg=[0xf50d], data=40
Oct  6 16:02:52 tvbox stb0899_read_status: Delivery system DVB-S/DSS
Oct  6 16:02:52 tvbox _stb0899_read_reg: Reg=[0xf50d], data=40
Oct  6 16:02:53 tvbox stb0899_read_status: Delivery system DVB-S/DSS
Oct  6 16:02:53 tvbox _stb0899_read_reg: Reg=[0xf50d], data=40
Oct  6 16:03:01 tvbox _stb0899_read_reg: Reg=[0xf12a], data=5c
Oct  6 16:03:01 tvbox stb0899_sleep: Going to Sleep .. (Really tired .. :-))


Alpha, Beta values calculated for sampling rate @ 99 MHz, but it doesn't 
appreciate Fs @ 99 MHz for some reason, but appreciates 90 MHz better. 
(Sounds a bit strange, not sure whether the calculation is wrong) 

The same issue was passed on by Julian, Marco and Reinhard as well.
(Same behaviour for the entire range of cards)

All pointing to just one aspect. Though not sure exactly why, I have reverted 
this offending changeset. Will try to get more information as to why, but for
now, rather than waiting for the right answer let's proceed in the direction
that which assumes things to be correct.

Can you please try a fresh clone from the tree and retry with 
SearchRange=3MHz alone with logs, just one case alone ? But please see 
whether you get anymore failures.

Thanks for putting in efforts, in the right direction.

Thanks,
Manu



More information about the linux-dvb mailing list