Re : Re : [linux-dvb] Re : Technotrend Budget S2-3200 Digital artefacts on HDchannels

[Manu <eallaud@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 3593 bytes --]

Le 05.02.2009 19:50:18, Manu Abraham a écrit :
> Manu wrote:
> > Le 02.02.2009 18:43:33, Chris Silva a écrit :
> >> On Tue, Jan 27, 2009 at 9:13 PM, Manu Abraham 
> >> <abraham.manu@gmail.com>
> >> wrote:
> >>> Alex Betis wrote:
> >>>> On Tue, Jan 27, 2009 at 9:56 PM, Manu Abraham
> >> <abraham.manu@gmail.com>wrote:
> >>>>>> Hmm OK, but is there by any chance a fix for those issues
> >> somewhere or
> >>>>>> in the pipe at least? I am willing to test (as I already
> >> offered), I
> >>>>>> can compile the drivers, spread printk or whatever else is 
> >> needed
> >> to
> >>>>>> get useful reports. Let me know if I can help sort this
> problem.
> >> BTW in
> >>>>>> my case it is DVB-S2 30000 SR and FEC 5/6.
> >>>>> It was quite not appreciable on my part to provide a fix or
> reply
> >> in
> >>>>> time nor spend much time on it earlier, but that said i was
> quite
> >>>>> stuck up with some other things.
> >>>>>
> >>>>> Can you please pull a copy of the multiproto tree
> >>>>> http://jusst.de/hg/multiproto or the v4l-dvb tree from
> >>>>> http://jusst.de/hg/v4l-dvb
> >>>>>
> >>>>> and apply the following patch and comment what your result is ?
> >>>>> Before applying please do check whether you still have the 
> >> issues.
> >>>> Manu,
> >>>> I've tried to increase those timers long ago when played around
> >> with my card
> >>>> (Twinhan 1041) and scan utility.
> >>>> I must say that I've concentrated mostly on DVB-S channels that
> >> wasn't
> >>>> always locking.
> >>>> I didn't notice much improvements. The thing that did help was
> >> increasing
> >>>> the resolution of scan zigzags.
> >>> With regards to the zig-zag, one bug is fixed in the v4l-dvb 
> tree.
> >>> Most likely you haven't tried that change.
> >>>
> >>>> I've sent a patch on that ML and people were happy with the
> >> results.
> >>> I did look at your patch, but that was completely against the 
> >> tuning
> >>> algorithm.
> >>>
> >>> [..]
> >>>
> >>>> I believe DVB-S2 lock suffer from the same problem, but in that
> >> case the
> >>>> zigzag is done in the chip and not in the driver.
> >>> Along with the patch i sent, does the attached patch help you in
> >>> anyway (This works out for DVB-S2 only)?
> >>>
> >> Manu,
> >>
> >> I've tried both multiproto branches you indicated above, *with* 
> and
> >> *without* the patches you sent to the ML (fix_iterations.patch and
> >> increase timeout.patch) on this thread.
> >> Sadly, same behavior as S2API V4L-DVB current branch. No lock on 
> >> 30000
> >> 3/4 channels. It achieves a 0.5 second jittery sound but no image.
> It
> >> seems the driver is struggling to correctly lock on that channel,
> but
> >> doesn't get there in time... Or maybe the hardware... Dunno...
> 
> Can you please send me a complete trace with the stb6100 and stb0899
> modules loaded with verbose=5 for the 30MSPS transponder what you
> are trying ? One simple szap would be enough (no scan please) based
> on the http://jusst.de/hg/v4l-dvb tree.
> 
> Before you start testing, start clean from a cold boot after a
> powerdown. This makes it a bit more easier identify things.

OK I did just that with latest multiproto on a 11495 MHz trnaposnder, 
DVB-S2, 30MS/s, FEC 5/6 which works using the provider's STB . I put 
the log in attachement. You will observe a lock is acquired really 
briefly and then nothing. Obtained using:
szap2 -t 2
I hope this can give you some data. Let me know if you need more info 
(like putting some more printksin the source).
Bye
Manu

[-- Attachment #2: szap-dvbs2-nolock.txt.bz2 --]
[-- Type: application/x-bzip, Size: 9856 bytes --]