[linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[NONAS EUAGGELOS]

Hello,

I have a Skystar HD. I use multiproto from here (checked it out yesterday):
http://jusst.de/hg/multiproto
It compiles fine, all needed modules are loaded automatically upon boot.
This is my dmesg:
saa7146: found saa7146 @ mem f88f2000 (revision 1, irq 21) (0x13c2,0x1019).
saa7146 (0): dma buffer size 192512
DVB: registering new adapter (TT-Budget S2-3200 PCI)
adapter has MAC addr = 00:d0:5c:67:dd:91
input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input3
stb0899_write_regs [0xf1b6]: 02
stb0899_write_regs [0xf1c2]: 00
stb0899_write_regs [0xf1c3]: 00
_stb0899_read_reg: Reg=[0xf000], data=82
stb0899_get_dev_id: ID reg=[0x82]
stb0899_get_dev_id: Device ID=[8], Release=[2]
_stb0899_read_s2reg Device=[0xf3fc], Base address=[0x00000400], Offset=[0xf334], Data=[0x444d4431]
_stb0899_read_s2reg Device=[0xf3fc], Base address=[0x00000400], Offset=[0xf33c], Data=[0x00000001]
stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1]
_stb0899_read_s2reg Device=[0xfafc], Base address=[0x00000800], Offset=[0xfa2c], Data=[0x46454331]
_stb0899_read_s2reg Device=[0xfafc], Base address=[0x00000800], Offset=[0xfa34], Data=[0x00000001]
stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1]
stb0899_attach: Attaching STB0899
stb6100_attach: Attaching STB6100
DVB: registering frontend 0 (STB0899 Multistandard)...

I use scan from here: 
http://jusst.de/manu/scan.tar.bz2
It does not compile, I use the binary I found in the archive.

I use szap2 from here:
http://www.free-x.de/vdr/patches/hdtv/szap2.tgz
It does compile.

My kernel is:
2.6.22-gentoo-r9

My problems are:
- When I scan the same transponder more than once, sometimes I get some services, sometimes I get no services.
- When I zap (with szap2) to a station more than once, sometimes I get a lock, sometimes I get no lock.
- I have also tried with vdr 1.4.7(old DVB API) and 1.5.14 (new dvb API). Both versions can tune to only one channel, the "Active" channel from previous vdr shutdown. When you change channel the signal is lost. I suppose it relates to the zap problem.

I would appreciate your help / suggestions.

Thank you very much.
Vagelis
 

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

Just replying to myself.

Nobody has the same problems that I have with Skystar HD? Can someone 
please explain the current status of the driver? Is this the expected 
behavior, or I am doing something wrong?

Thank you,
Vagelis

NONAS EUAGGELOS wrote:
> Hello,
>
> I have a Skystar HD. I use multiproto from here (checked it out yesterday):
> http://jusst.de/hg/multiproto
> It compiles fine, all needed modules are loaded automatically upon boot.
> This is my dmesg:
> saa7146: found saa7146 @ mem f88f2000 (revision 1, irq 21) (0x13c2,0x1019).
> saa7146 (0): dma buffer size 192512
> DVB: registering new adapter (TT-Budget S2-3200 PCI)
> adapter has MAC addr = 00:d0:5c:67:dd:91
> input: Budget-CI dvb ir receiver saa7146 (0) as /class/input/input3
> stb0899_write_regs [0xf1b6]: 02
> stb0899_write_regs [0xf1c2]: 00
> stb0899_write_regs [0xf1c3]: 00
> _stb0899_read_reg: Reg=[0xf000], data=82
> stb0899_get_dev_id: ID reg=[0x82]
> stb0899_get_dev_id: Device ID=[8], Release=[2]
> _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x00000400], Offset=[0xf334], Data=[0x444d4431]
> _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x00000400], Offset=[0xf33c], Data=[0x00000001]
> stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1]
> _stb0899_read_s2reg Device=[0xfafc], Base address=[0x00000800], Offset=[0xfa2c], Data=[0x46454331]
> _stb0899_read_s2reg Device=[0xfafc], Base address=[0x00000800], Offset=[0xfa34], Data=[0x00000001]
> stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1]
> stb0899_attach: Attaching STB0899
> stb6100_attach: Attaching STB6100
> DVB: registering frontend 0 (STB0899 Multistandard)...
>
> I use scan from here: 
> http://jusst.de/manu/scan.tar.bz2
> It does not compile, I use the binary I found in the archive.
>
> I use szap2 from here:
> http://www.free-x.de/vdr/patches/hdtv/szap2.tgz
> It does compile.
>
> My kernel is:
> 2.6.22-gentoo-r9
>
> My problems are:
> - When I scan the same transponder more than once, sometimes I get some services, sometimes I get no services.
> - When I zap (with szap2) to a station more than once, sometimes I get a lock, sometimes I get no lock.
> - I have also tried with vdr 1.4.7(old DVB API) and 1.5.14 (new dvb API). Both versions can tune to only one channel, the "Active" channel from previous vdr shutdown. When you change channel the signal is lost. I suppose it relates to the zap problem.
>
> I would appreciate your help / suggestions.
>
> Thank you very much.
> Vagelis
>  
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
> .
>
>   


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sat, Feb 23, 2008 at 12:35:49PM +0000, Vangelis Nonas wrote:
> > My problems are:
> > - When I scan the same transponder more than once, sometimes I get some services, sometimes I get no services.

I have never tried to scan with the SkyStar HD.

> > - When I zap (with szap2) to a station more than once, sometimes I get a lock, sometimes I get no lock.

I have the same problem. I was trying to tune to ProSieben 100 times today. And I got only 11 successful locks.
The signal strengt should be ok, as I have no problems to tune this
channel with other DVB-S cards...

Here is a little script to do such tests:
http://www.makhutov.org/downloads/dvb/tune.sh

You need this szap (http://abraham.manu.googlepages.com/szap.c) and this
patch (http://www.makhutov.org/downloads/dvb/szap.patch) to make the script work.

Has anyone any ideas why the tuning failes so often? Is it a problem of
szap or the driver itself? I heard, that this card works perfect with VDR for other users...

> > - I have also tried with vdr 1.4.7(old DVB API) and 1.5.14 (new dvb API). Both versions can tune to only one channel, the "Active" channel from previous vdr shutdown. When you change channel the signal is lost. I suppose it relates to the zap problem.

I have not tried out VDR with the SkyStar HD. I will run some tests
during the next week.

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sat, Feb 23, 2008 at 09:31:01PM +0300, Igor wrote:
> > > > - When I zap (with szap2) to a station more than once, sometimes I get a lock, sometimes I get no lock.
> > 
> > I have the same problem. I was trying to tune to ProSieben 100 times today. And I got only 11 successful locks.
> > The signal strengt should be ok, as I have no problems to tune this
> > channel with other DVB-S cards...
> 
> no anymore Prosiben (hd version) since last week :(
> http://www.lyngsat.com/hd/astra19.html

Yes, I know ... till 2010 ... :(

Now there is only one free DVB-S2 channel (Anixe HD)
on Astra 19.2 left :(

I was tuning the usual ProSieben.

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Artem Makhutov wrote:
> Hi,
> 
> On Sat, Feb 23, 2008 at 12:35:49PM +0000, Vangelis Nonas wrote:
>>> My problems are:
>>> - When I scan the same transponder more than once, sometimes I get some services, sometimes I get no services.
> 
> I have never tried to scan with the SkyStar HD.
> 
>>> - When I zap (with szap2) to a station more than once, sometimes I get a lock, sometimes I get no lock.
> 
> I have the same problem. I was trying to tune to ProSieben 100 times today. And I got only 11 successful locks.
> The signal strengt should be ok, as I have no problems to tune this
> channel with other DVB-S cards...
> 
> Here is a little script to do such tests:
> http://www.makhutov.org/downloads/dvb/tune.sh
> 
> You need this szap (http://abraham.manu.googlepages.com/szap.c) and this
> patch (http://www.makhutov.org/downloads/dvb/szap.patch) to make the script work.
> 
> Has anyone any ideas why the tuning failes so often? Is it a problem of
> szap or the driver itself? I heard, that this card works perfect with VDR for other users...


Can you guys please update from the multiproto tree and test again at
the earliest and give me your feedback ?

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sun, Feb 24, 2008 at 12:21:17AM +0400, Manu Abraham wrote:
> [...]
> Can you guys please update from the multiproto tree and test again at
> the earliest and give me your feedback ?

No, still the same:

Try: 50
Failes: 37
Tunes: 13

Maybe the problem is in the szap.c and not in the driver, as Reinhard
Nissl had no problems while tuning channels with VDR?

An other thing that I noticed is that only first tunes are successful.
I continued the same tuning test to 100, but I got no more successfull locks.
The last successfull lock was try 20:

Try: 100
Failes: 87
Tunes: 13

I am running a new test with a 15 seconds break after each tune now and
will mail you the results when the test finises.

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Artem Makhutov wrote:
> Hi,
> 
> On Sun, Feb 24, 2008 at 12:21:17AM +0400, Manu Abraham wrote:
>> [...]
>> Can you guys please update from the multiproto tree and test again at
>> the earliest and give me your feedback ?
> 
> No, still the same:
> 
> Try: 50
> Failes: 37
> Tunes: 13
> 
> Maybe the problem is in the szap.c and not in the driver, as Reinhard
> Nissl had no problems while tuning channels with VDR?
> 
> An other thing that I noticed is that only first tunes are successful.
> I continued the same tuning test to 100, but I got no more successfull locks.
> The last successfull lock was try 20:
> 
> Try: 100
> Failes: 87
> Tunes: 13
> 
> I am running a new test with a 15 seconds break after each tune now and
> will mail you the results when the test finises.

Are you sure that you got the top level 2 changes changeset 7204 and 7203
respectively ?

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
> Artem Makhutov wrote:
> >Hi,
> >
> >On Sun, Feb 24, 2008 at 12:21:17AM +0400, Manu Abraham wrote:
> >>[...]
> >>Can you guys please update from the multiproto tree and test again at
> >>the earliest and give me your feedback ?
> >
> >No, still the same:
> >
> >Try: 50
> >Failes: 37
> >Tunes: 13
> >
> >Maybe the problem is in the szap.c and not in the driver, as Reinhard
> >Nissl had no problems while tuning channels with VDR?
> >
> >An other thing that I noticed is that only first tunes are successful.
> >I continued the same tuning test to 100, but I got no more successfull 
> >locks.
> >The last successfull lock was try 20:
> >
> >Try: 100
> >Failes: 87
> >Tunes: 13
> >
> >I am running a new test with a 15 seconds break after each tune now and
> >will mail you the results when the test finises.
> 
> Are you sure that you got the top level 2 changes changeset 7204 and 7203
> respectively ?

Oh, I only got 7203. Will try with 7204 in a few minutes.

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
> > Are you sure that you got the top level 2 changes changeset 7204 and 7203
> > respectively ?
> 
> Oh, I only got 7203. Will try with 7204 in a few minutes.

Awesome! It fixed the problem:

Try: 100
Failes: 0
Tunes: 100

Great job!

Thanks, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Artem Makhutov wrote:
> Hi,
> 
> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>> Are you sure that you got the top level 2 changes changeset 7204 and 7203
>>> respectively ?
>> Oh, I only got 7203. Will try with 7204 in a few minutes.
> 
> Awesome! It fixed the problem:
> 
> Try: 100
> Failes: 0
> Tunes: 100
> 
> Great job!

Cool. :)

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Manu Abraham wrote:
> Artem Makhutov wrote:
>> Hi,
>>
>> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>>> Are you sure that you got the top level 2 changes changeset 7204 and 7203
>>>> respectively ?
>>> Oh, I only got 7203. Will try with 7204 in a few minutes.
>> Awesome! It fixed the problem:
>>
>> Try: 100
>> Failes: 0
>> Tunes: 100
>>
>> Great job!

Also, can you please do a benchmark in lock timings between changeset 
7205 and 7200 ?

The timing can be looked at by enabling the time stamps in the kernel 
config and
looking at timestamps in the logs for start - stop (FE_HAS_LOCK) between 
the 2
changesets.

Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

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

Thank you all for your help,

With the latest changeset I can tune channels correctly. I tried vdr and 
szap (from Manu).

I dont know how to undo the last changesets and go back to 7200. Please 
tell me how to do it and I'll get the timings.

I also tried to scan Hotbird and it seems that scanning is now 
consistent when you scan the same transponder more than once.

A full scan produced 1722 channels which is not bad, but it needs 
improvement. There are about 2200 channels I think.

I attach the log of the scan. It fails to scan certain transponders and 
I believe (not 100% sure, but I did some testing) that this is 
consistent across runs.

Regards
Vagelis



Manu Abraham wrote:
> Manu Abraham wrote:
>   
>> Artem Makhutov wrote:
>>     
>>> Hi,
>>>
>>> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>>>       
>>>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>>>         
>>>>> Are you sure that you got the top level 2 changes changeset 7204 and 7203
>>>>> respectively ?
>>>>>           
>>>> Oh, I only got 7203. Will try with 7204 in a few minutes.
>>>>         
>>> Awesome! It fixed the problem:
>>>
>>> Try: 100
>>> Failes: 0
>>> Tunes: 100
>>>
>>> Great job!
>>>       
>
> Also, can you please do a benchmark in lock timings between changeset 
> 7205 and 7200 ?
>
> The timing can be looked at by enabling the time stamps in the kernel 
> config and
> looking at timestamps in the logs for start - stop (FE_HAS_LOCK) between 
> the 2
> changesets.
>
> Regards,
> Manu
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
>
>   


[-- Attachment #2: scan.log.gz --]
[-- Type: application/x-gzip, Size: 25168 bytes --]

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Vangelis Nonas wrote:
> Thank you all for your help,
> 
> With the latest changeset I can tune channels correctly. I tried vdr and 
> szap (from Manu).
> 
> I dont know how to undo the last changesets and go back to 7200. Please 
> tell me how to do it and I'll get the timings.


clone the multiproto tree

from there, do a partial clone locally

hg clone -r 7200 multiproto multiproto_7200


> I also tried to scan Hotbird and it seems that scanning is now 
> consistent when you scan the same transponder more than once.
> 
> A full scan produced 1722 channels which is not bad, but it needs 
> improvement. There are about 2200 channels I think.

If you can provide a log with verbose=5 for the channels which it doesn't
scan it will be a bit more helpful. Will need the logs (/var/log/messages)
to debug this as well. The module parameters the same for both the
STB0899 and the STB6100

> I attach the log of the scan. It fails to scan certain transponders and 
> I believe (not 100% sure, but I did some testing) that this is 
> consistent across runs.

The log is just the output of the scan utility, will need the output from
the driver and a bit of thoughts.



Regards,
Manu

> Regards
> Vagelis
> 
> 
> 
> Manu Abraham wrote:
>> Manu Abraham wrote:
>>  
>>> Artem Makhutov wrote:
>>>    
>>>> Hi,
>>>>
>>>> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>>>>      
>>>>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>>>>        
>>>>>> Are you sure that you got the top level 2 changes changeset 7204 
>>>>>> and 7203
>>>>>> respectively ?
>>>>>>           
>>>>> Oh, I only got 7203. Will try with 7204 in a few minutes.
>>>>>         
>>>> Awesome! It fixed the problem:
>>>>
>>>> Try: 100
>>>> Failes: 0
>>>> Tunes: 100
>>>>
>>>> Great job!
>>>>       
>>
>> Also, can you please do a benchmark in lock timings between changeset 
>> 7205 and 7200 ?
>>
>> The timing can be looked at by enabling the time stamps in the kernel 
>> config and
>> looking at timestamps in the logs for start - stop (FE_HAS_LOCK) 
>> between the 2
>> changesets.
>>
>> Regards,
>> Manu
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>
>>
>>   
> 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

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

Hello,

I attach the timing logs for changsets 7205 and 7201. The funny thing is 
that when I use 7201 it does NOT have the problem with locking  when 
tuning, as it had before. I tried it 3 times, the third after a full 
shutdown of the pc and having removed the power for a couple on minutes. 
It is really strange.

Anyway, both logs were taken with these commands:

../szap/szap -c channels.conf -r "bbc world"
../szap/szap -c channels.conf -r "bbc prime"
../szap/szap -c channels.conf -r "filmnet1"

I'll check how scanning performs with 7201 and let you know

Regards
Vagelis


Manu Abraham wrote:
> Vangelis Nonas wrote:
>> Thank you all for your help,
>>
>> With the latest changeset I can tune channels correctly. I tried vdr 
>> and szap (from Manu).
>>
>> I dont know how to undo the last changesets and go back to 7200. 
>> Please tell me how to do it and I'll get the timings.
>
>
> clone the multiproto tree
>
> from there, do a partial clone locally
>
> hg clone -r 7200 multiproto multiproto_7200
>
>
>> I also tried to scan Hotbird and it seems that scanning is now 
>> consistent when you scan the same transponder more than once.
>>
>> A full scan produced 1722 channels which is not bad, but it needs 
>> improvement. There are about 2200 channels I think.
>
> If you can provide a log with verbose=5 for the channels which it doesn't
> scan it will be a bit more helpful. Will need the logs 
> (/var/log/messages)
> to debug this as well. The module parameters the same for both the
> STB0899 and the STB6100
>
>> I attach the log of the scan. It fails to scan certain transponders 
>> and I believe (not 100% sure, but I did some testing) that this is 
>> consistent across runs.
>
> The log is just the output of the scan utility, will need the output from
> the driver and a bit of thoughts.
>
>
>
> Regards,
> Manu
>
>> Regards
>> Vagelis
>>
>>
>>
>> Manu Abraham wrote:
>>> Manu Abraham wrote:
>>>  
>>>> Artem Makhutov wrote:
>>>>   
>>>>> Hi,
>>>>>
>>>>> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>>>>>     
>>>>>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>>>>>       
>>>>>>> Are you sure that you got the top level 2 changes changeset 7204 
>>>>>>> and 7203
>>>>>>> respectively ?
>>>>>>>           
>>>>>> Oh, I only got 7203. Will try with 7204 in a few minutes.
>>>>>>         
>>>>> Awesome! It fixed the problem:
>>>>>
>>>>> Try: 100
>>>>> Failes: 0
>>>>> Tunes: 100
>>>>>
>>>>> Great job!
>>>>>       
>>>
>>> Also, can you please do a benchmark in lock timings between 
>>> changeset 7205 and 7200 ?
>>>
>>> The timing can be looked at by enabling the time stamps in the 
>>> kernel config and
>>> looking at timestamps in the logs for start - stop (FE_HAS_LOCK) 
>>> between the 2
>>> changesets.
>>>
>>> Regards,
>>> Manu
>>>
>>> _______________________________________________
>>> linux-dvb mailing list
>>> linux-dvb@linuxtv.org
>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>
>>>
>>>   
>>
>
>
>


[-- Attachment #2: 7201.log.gz --]
[-- Type: application/x-gzip, Size: 17189 bytes --]

[-- Attachment #3: 7205.log.gz --]
[-- Type: application/x-gzip, Size: 11329 bytes --]

[-- Attachment #4: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

Hello,

I tried scanning with the 7201 changeset and I believe the results are 
better than the 7205 changeset. In the former case I get 2082 services 
on hotbird, in the latter 1722.

I'll shortly send kernel logs for a failing transponder during scan.

And something else:
When I give to scan the parameter -o vdr it will not output the results 
after a complete scan.


Regards
Vagelis


Vangelis Nonas wrote:
> Hello,
>
> I attach the timing logs for changsets 7205 and 7201. The funny thing 
> is that when I use 7201 it does NOT have the problem with locking  
> when tuning, as it had before. I tried it 3 times, the third after a 
> full shutdown of the pc and having removed the power for a couple on 
> minutes. It is really strange.
>
> Anyway, both logs were taken with these commands:
>
> ../szap/szap -c channels.conf -r "bbc world"
> ../szap/szap -c channels.conf -r "bbc prime"
> ../szap/szap -c channels.conf -r "filmnet1"
>
> I'll check how scanning performs with 7201 and let you know
>
> Regards
> Vagelis
>
>
> Manu Abraham wrote:
>> Vangelis Nonas wrote:
>>> Thank you all for your help,
>>>
>>> With the latest changeset I can tune channels correctly. I tried vdr 
>>> and szap (from Manu).
>>>
>>> I dont know how to undo the last changesets and go back to 7200. 
>>> Please tell me how to do it and I'll get the timings.
>>
>>
>> clone the multiproto tree
>>
>> from there, do a partial clone locally
>>
>> hg clone -r 7200 multiproto multiproto_7200
>>
>>
>>> I also tried to scan Hotbird and it seems that scanning is now 
>>> consistent when you scan the same transponder more than once.
>>>
>>> A full scan produced 1722 channels which is not bad, but it needs 
>>> improvement. There are about 2200 channels I think.
>>
>> If you can provide a log with verbose=5 for the channels which it 
>> doesn't
>> scan it will be a bit more helpful. Will need the logs 
>> (/var/log/messages)
>> to debug this as well. The module parameters the same for both the
>> STB0899 and the STB6100
>>
>>> I attach the log of the scan. It fails to scan certain transponders 
>>> and I believe (not 100% sure, but I did some testing) that this is 
>>> consistent across runs.
>>
>> The log is just the output of the scan utility, will need the output 
>> from
>> the driver and a bit of thoughts.
>>
>>
>>
>> Regards,
>> Manu
>>
>>> Regards
>>> Vagelis
>>>
>>>
>>>
>>> Manu Abraham wrote:
>>>> Manu Abraham wrote:
>>>>  
>>>>> Artem Makhutov wrote:
>>>>>  
>>>>>> Hi,
>>>>>>
>>>>>> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>>>>>>    
>>>>>>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>>>>>>      
>>>>>>>> Are you sure that you got the top level 2 changes changeset 
>>>>>>>> 7204 and 7203
>>>>>>>> respectively ?
>>>>>>>>           
>>>>>>> Oh, I only got 7203. Will try with 7204 in a few minutes.
>>>>>>>         
>>>>>> Awesome! It fixed the problem:
>>>>>>
>>>>>> Try: 100
>>>>>> Failes: 0
>>>>>> Tunes: 100
>>>>>>
>>>>>> Great job!
>>>>>>       
>>>>
>>>> Also, can you please do a benchmark in lock timings between 
>>>> changeset 7205 and 7200 ?
>>>>
>>>> The timing can be looked at by enabling the time stamps in the 
>>>> kernel config and
>>>> looking at timestamps in the logs for start - stop (FE_HAS_LOCK) 
>>>> between the 2
>>>> changesets.
>>>>
>>>> Regards,
>>>> Manu
>>>>
>>>> _______________________________________________
>>>> linux-dvb mailing list
>>>> linux-dvb@linuxtv.org
>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>
>>>>
>>>>   
>>>
>>
>>
>>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Vangelis Nonas wrote:
> Hello,
> 
> I tried scanning with the 7201 changeset and I believe the results are 
> better than the 7205 changeset. In the former case I get 2082 services 
> on hotbird, in the latter 1722.
>

Hmm.. Ok.

Can you please get 7205 and load the stb0899 and stb6100 modules with
verbose=2 or 5 as module parameters and see whether it makes any 
difference ?
(ie you see more of the services) ie check whether changing the module 
parameters
(verbosity level) makes any difference in the number of services found.

> I'll shortly send kernel logs for a failing transponder during scan.
> 
> And something else:
> When I give to scan the parameter -o vdr it will not output the results 
> after a complete scan.

Ok, this i had not added in, will look at this aspect.

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

Hello,

I scanned using 7205 changeset. With verbose=5, I get 1801 services. 
With verbose=2 I get 1725 services.

Using the 7201 changeset with verbose=5 I get 2082 services. I can check 
for verbose=2 and changeset 7201 if you think it is useful.

I have the "feeling" that 7201 behaves better. It is much faster also 
during scanning( I don't have measurements but I am pretty sure).

Should you need kernel logs for failing transponders either 7201 or 7205 
let me know.

Regards
Vagelis




Manu Abraham wrote:
> Vangelis Nonas wrote:
>> Hello,
>>
>> I tried scanning with the 7201 changeset and I believe the results 
>> are better than the 7205 changeset. In the former case I get 2082 
>> services on hotbird, in the latter 1722.
>>
>
> Hmm.. Ok.
>
> Can you please get 7205 and load the stb0899 and stb6100 modules with
> verbose=2 or 5 as module parameters and see whether it makes any 
> difference ?
> (ie you see more of the services) ie check whether changing the module 
> parameters
> (verbosity level) makes any difference in the number of services found.
>
>> I'll shortly send kernel logs for a failing transponder during scan.
>>
>> And something else:
>> When I give to scan the parameter -o vdr it will not output the 
>> results after a complete scan.
>
> Ok, this i had not added in, will look at this aspect.
>
> Regards,
> Manu
>
>
>


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Vangelis Nonas wrote:
> Hello,
> 
> I scanned using 7205 changeset. With verbose=5, I get 1801 services. 
> With verbose=2 I get 1725 services.
> 
> Using the 7201 changeset with verbose=5 I get 2082 services. I can check 
> for verbose=2 and changeset 7201 if you think it is useful.

It would be nice to see changeset 7201 with verbose=1 and 2, the results.

> I have the "feeling" that 7201 behaves better. It is much faster also 
> during scanning( I don't have measurements but I am pretty sure).

You can enable timestamps being output in printk's in the kernel config
to see the timestamps, with which you compare with the start - stop
events in the logs.

> Should you need kernel logs for failing transponders either 7201 or 7205 
> let me know.

Will need the logs for the failing transponders in 7205, to check for the
actual cause.


Regards,
Manu

> 
> Regards
> Vagelis
> 
> 
> 
> 
> Manu Abraham wrote:
>> Vangelis Nonas wrote:
>>> Hello,
>>>
>>> I tried scanning with the 7201 changeset and I believe the results 
>>> are better than the 7205 changeset. In the former case I get 2082 
>>> services on hotbird, in the latter 1722.
>>>
>>
>> Hmm.. Ok.
>>
>> Can you please get 7205 and load the stb0899 and stb6100 modules with
>> verbose=2 or 5 as module parameters and see whether it makes any 
>> difference ?
>> (ie you see more of the services) ie check whether changing the module 
>> parameters
>> (verbosity level) makes any difference in the number of services found.
>>
>>> I'll shortly send kernel logs for a failing transponder during scan.
>>>
>>> And something else:
>>> When I give to scan the parameter -o vdr it will not output the 
>>> results after a complete scan.
>>
>> Ok, this i had not added in, will look at this aspect.
>>
>> Regards,
>> Manu
>>
>>
>>
> 
> 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

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

Hello,

I have tested again changesets 7201 and 7205 with verbose 5, 2 and 1 
scanning 101 transponders on Hotbird (I attach my transponders file -- 
it is taken and adopted from ProgDvb).

Here are my statistics:

Changeset   Verbose  channels
--------------------------------
7201         1        2152
7201         2        2105
7201         5        2081
7205         1        1760
7205         2        1608
7205         5        1578


It is very strange that using the 7205 changeset (all verbose) Zagros TV 
for instance and all other channels on transponder
S 11727000 V 27500000 3/4
are NOT found.
But if you try and scan with a transponder file containing just a single 
line for the failing transponder it works correctly!!! (again 7205 
changeset and all verbose).

Moreover, I have noticed that when you scan a single transponder and you 
have placed only one entry in the transponders file, the program (scan) 
actually scans more than one, often many transponders. Is it normal? I 
thought scan only checks the transponders it finds in the file.

Anyway I attach the kernel log of scanning this transponder:
S 10758000 V 27500000 3/4
The transponder itself does not fail, but other transponders it "jumps 
to" fail. The log was taken with change set 7205 and verbose 5. It is 
1.5MB, I hope Manu got it at his private email.


Regards
Vagelis



Manu Abraham wrote:
> Vangelis Nonas wrote:
>> Hello,
>>
>> I scanned using 7205 changeset. With verbose=5, I get 1801 services. 
>> With verbose=2 I get 1725 services.
>>
>> Using the 7201 changeset with verbose=5 I get 2082 services. I can 
>> check for verbose=2 and changeset 7201 if you think it is useful.
>
> It would be nice to see changeset 7201 with verbose=1 and 2, the results.
>
>> I have the "feeling" that 7201 behaves better. It is much faster also 
>> during scanning( I don't have measurements but I am pretty sure).
>
> You can enable timestamps being output in printk's in the kernel config
> to see the timestamps, with which you compare with the start - stop
> events in the logs.
>
>> Should you need kernel logs for failing transponders either 7201 or 
>> 7205 let me know.
>
> Will need the logs for the failing transponders in 7205, to check for the
> actual cause.
>
>
> Regards,
> Manu
>
>>
>> Regards
>> Vagelis
>>
>>
>>
>>
>> Manu Abraham wrote:
>>> Vangelis Nonas wrote:
>>>> Hello,
>>>>
>>>> I tried scanning with the 7201 changeset and I believe the results 
>>>> are better than the 7205 changeset. In the former case I get 2082 
>>>> services on hotbird, in the latter 1722.
>>>>
>>>
>>> Hmm.. Ok.
>>>
>>> Can you please get 7205 and load the stb0899 and stb6100 modules with
>>> verbose=2 or 5 as module parameters and see whether it makes any 
>>> difference ?
>>> (ie you see more of the services) ie check whether changing the 
>>> module parameters
>>> (verbosity level) makes any difference in the number of services found.
>>>
>>>> I'll shortly send kernel logs for a failing transponder during scan.
>>>>
>>>> And something else:
>>>> When I give to scan the parameter -o vdr it will not output the 
>>>> results after a complete scan.
>>>
>>> Ok, this i had not added in, will look at this aspect.
>>>
>>> Regards,
>>> Manu
>>>
>>>
>>>
>>
>>
>
>
> .
>


[-- Attachment #2: Hotbird --]
[-- Type: text/plain, Size: 2623 bytes --]

S 10719000 V 27500000 3/4
S 10723000 H 29900000 3/4
S 10758000 V 27500000 3/4
S 10775000 H 28000000 3/4
S 10796000 V 27500000 3/4
S 10830000 H 3333000 3/4
S 10834000 V 27500000 3/4
S 10853000 H 27500000 3/4
S 10873000 V 27500000 3/4
S 10892000 H 27500000 3/4
S 10911000 V 27500000 3/4
S 10930000 H 27500000 3/4
S 10949000 V 27500000 3/4
S 10971000 H 27500000 3/4
S 10992000 V 27500000 2/3
S 11013000 H 27500000 3/4
S 11034000 V 27500000 3/4
S 11054000 H 27500000 5/6
S 11075000 V 27500000 3/4
S 11096000 H 28000000 3/4
S 11117000 V 27500000 3/4
S 11137000 H 27500000 3/4
S 11158000 V 27500000 3/4
S 11179000 H 27500000 3/4
S 11200000 V 27500000 5/6
S 11219000 H 27500000 3/4
S 11240000 V 27500000 3/4
S 11258000 H 27500000 2/3
S 11278000 V 27500000 3/4
S 11296000 H 27500000 3/4
S 11334000 H 27500000 1/2
S 11355000 V 27500000 3/4
S 11373000 H 19636000 2/3
S 11393000 V 27500000 3/4
S 11411000 H 27500000 5/6
S 11432000 V 27500000 1/2
S 11449000 H 27500000 2/3
S 11470000 V 27500000 5/6
S 11488000 H 27500000 3/4
S 11523000 V 5000000 7/8
S 11526000 H 27500000 3/4
S 11541000 V 22000000 5/6
S 11566000 H 27500000 3/4
S 11585000 V 27500000 3/4
S 11604000 H 27500000 5/6
S 11623000 V 27500000 3/4
S 11642000 H 27500000 3/4
S 11662000 V 27500000 3/4
S 11681000 H 27500000 3/4
S 11727000 V 27500000 3/4
S 11747000 H 27500000 3/4
S 11766000 V 27500000 2/3
S 11785000 H 27500000 3/4
S 11804000 V 27500000 2/3
S 11823000 H 27500000 3/4
S 11843000 V 27500000 3/4
S 11862000 H 27500000 3/4
S 11881000 V 27500000 3/4
S 11900000 H 27500000 3/4
S 11919000 V 27500000 2/3
S 11938000 H 27500000 3/4
S 11958000 V 27500000 3/4
S 11977000 H 27500000 3/4
S 11996000 V 27500000 2/3
S 12015000 H 27500000 3/4
S 12034000 V 27500000 3/4
S 12054000 H 27500000 3/4
S 12073000 V 27500000 3/4
S 12092000 H 27500000 3/4
S 12111000 V 27500000 3/4
S 12145000 H 3333000 3/4
S 12149000 V 27500000 3/4
S 12169000 H 27500000 3/4
S 12188000 V 27500000 3/4
S 12207000 H 27500000 3/4
S 12226000 V 27500000 3/4
S 12245000 H 27500000 3/4
S 12265000 V 27500000 2/3
S 12284000 H 27500000 3/4
S 12303000 V 27500000 3/4
S 12322000 H 27500000 3/4
S 12341000 V 27500000 3/4
S 12360000 H 27500000 3/4
S 12380000 V 27500000 3/4
S 12399000 H 27500000 3/4
S 12418000 V 27500000 3/4
S 12437000 H 27500000 3/4
S 12466000 V 27500000 3/4
S 12476000 H 27500000 3/4
S 12520000 V 27500000 3/4
S 12539000 H 27500000 3/4
S 12558000 V 27500000 3/4
S 12577000 H 27500000 3/4
S 12597000 V 27500000 3/4
S 12616000 H 27500000 3/4
S 12635000 V 27500000 3/4
S 12654000 H 27500000 3/4
S 12673000 V 27500000 3/4
S 12692000 H 27500000 3/4
S 12713000 V 27500000 3/4
S 12731000 H 27500000 3/4

[-- Attachment #3: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Vangelis Nonas wrote:
> Hello,
> 
> I have tested again changesets 7201 and 7205 with verbose 5, 2 and 1 
> scanning 101 transponders on Hotbird (I attach my transponders file -- 
> it is taken and adopted from ProgDvb).
> 
> Here are my statistics:
> 
> Changeset   Verbose  channels
> --------------------------------
> 7201         1        2152
> 7201         2        2105
> 7201         5        2081
> 7205         1        1760
> 7205         2        1608
> 7205         5        1578


Are you "really" sure that 7201 behaves better than others. I ask this, 
since
there was a bug in 7201 which caused many people not to have a LOCK, the
bugs which was fixed in 7203 and 7204. I am at a loss now, as to
understanding this strange phenomena, how a lock was achieved with no
communication to the tuner.

If it were 7200, i could have still believed, there was a possibility, 
but 7201
i am terribly confused.

Can you please verify whether you didn't get mixed up with the changeset
numbers or the logs that were produced ?


Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

Hello,

Here is the output of hg log|head -n 5 for two different directories 
(multiproto and multiproto_7200)

for multiproto:
changeset:   7205:9bdb997e38b5
tag:         tip
user:        Manu Abraham <manu@linuxtv.org>
date:        Sun Feb 24 02:10:56 2008 +0400
summary:     We can now reduce the debug levels, just need to look at 
errors only.

for multiproto_7200:
changeset:   7200:45eec532cefa
tag:         tip
parent:      7095:a577a5dbc93d
parent:      7199:0448e5a6d8a6
user:        Manu Abraham <manu@linuxtv.org>


So I guess I was referring to 7200 and not to 7201.
I am very positive about the results because I have tested it many 
times. It is just that it is 7200 instead of 7201.
So as a concluesion, 7200 behaves better than 7205. My corrected little 
table follows below just for clarification.

Changeset   Verbose  channels
--------------------------------
7200         1        2152
7200         2        2105
7200         5        2081
7205         1        1760
7205         2        1608
7205         5        1578


I apologise for the confusion, I may have caused.

Regards
Vagelis




Manu Abraham wrote:
> Vangelis Nonas wrote:
>> Hello,
>>
>> I have tested again changesets 7201 and 7205 with verbose 5, 2 and 1 
>> scanning 101 transponders on Hotbird (I attach my transponders file 
>> -- it is taken and adopted from ProgDvb).
>>
>> Here are my statistics:
>>
>> Changeset   Verbose  channels
>> --------------------------------
>> 7201         1        2152
>> 7201         2        2105
>> 7201         5        2081
>> 7205         1        1760
>> 7205         2        1608
>> 7205         5        1578
>
>
> Are you "really" sure that 7201 behaves better than others. I ask 
> this, since
> there was a bug in 7201 which caused many people not to have a LOCK, the
> bugs which was fixed in 7203 and 7204. I am at a loss now, as to
> understanding this strange phenomena, how a lock was achieved with no
> communication to the tuner.
>
> If it were 7200, i could have still believed, there was a possibility, 
> but 7201
> i am terribly confused.
>
> Can you please verify whether you didn't get mixed up with the changeset
> numbers or the logs that were produced ?
>
>
> Regards,
> Manu
>
>
> .
>


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Vangelis Nonas wrote:
> Hello,
> 
> Here is the output of hg log|head -n 5 for two different directories 
> (multiproto and multiproto_7200)
> 
> for multiproto:
> changeset:   7205:9bdb997e38b5
> tag:         tip
> user:        Manu Abraham <manu@linuxtv.org>
> date:        Sun Feb 24 02:10:56 2008 +0400
> summary:     We can now reduce the debug levels, just need to look at 
> errors only.
> 
> for multiproto_7200:
> changeset:   7200:45eec532cefa
> tag:         tip
> parent:      7095:a577a5dbc93d
> parent:      7199:0448e5a6d8a6
> user:        Manu Abraham <manu@linuxtv.org>
> 
> 
> So I guess I was referring to 7200 and not to 7201.
> I am very positive about the results because I have tested it many 
> times. It is just that it is 7200 instead of 7201.
> So as a concluesion, 7200 behaves better than 7205. My corrected little 
> table follows below just for clarification.


Ok, fine this is very much possible. Can other STB0899 users (all of them)
verify this result, such that i can revert back the changes ?


> 
> Changeset   Verbose  channels
> --------------------------------
> 7200         1        2152
> 7200         2        2105
> 7200         5        2081
> 7205         1        1760
> 7205         2        1608
> 7205         5        1578
> 
> 
> I apologise for the confusion, I may have caused.

No worries, don't apologise, this is all a part of the testing phase.


Thanks,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Oliver Bardenheier (obardenh)]

I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable,
many transponders not working.
I changed back to  45eec532cefa  and everything is working fine.

regards
Oliver

-----Original Message-----
From: linux-dvb-bounces@linuxtv.org
[mailto:linux-dvb-bounces@linuxtv.org] On Behalf Of Manu Abraham
Sent: Dienstag, 26. Februar 2008 22:45
To: linux-dvb@linuxtv.org
Subject: [linux-dvb] STB0899 users, please verify results was Re:
TechniSat SkyStar HD: Problems scaning and zaping

Vangelis Nonas wrote:
> Hello,
> 
> Here is the output of hg log|head -n 5 for two different directories 
> (multiproto and multiproto_7200)
> 
> for multiproto:
> changeset:   7205:9bdb997e38b5
> tag:         tip
> user:        Manu Abraham <manu@linuxtv.org>
> date:        Sun Feb 24 02:10:56 2008 +0400
> summary:     We can now reduce the debug levels, just need to look at 
> errors only.
> 
> for multiproto_7200:
> changeset:   7200:45eec532cefa
> tag:         tip
> parent:      7095:a577a5dbc93d
> parent:      7199:0448e5a6d8a6
> user:        Manu Abraham <manu@linuxtv.org>
> 
> 
> So I guess I was referring to 7200 and not to 7201.
> I am very positive about the results because I have tested it many 
> times. It is just that it is 7200 instead of 7201.
> So as a concluesion, 7200 behaves better than 7205. My corrected 
> little table follows below just for clarification.


Ok, fine this is very much possible. Can other STB0899 users (all of
them) verify this result, such that i can revert back the changes ?


> 
> Changeset   Verbose  channels
> --------------------------------
> 7200         1        2152
> 7200         2        2105
> 7200         5        2081
> 7205         1        1760
> 7205         2        1608
> 7205         5        1578
> 
> 
> I apologise for the confusion, I may have caused.

No worries, don't apologise, this is all a part of the testing phase.


Thanks,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Oliver Bardenheier (obardenh) wrote:
> I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable,
> many transponders not working.
> I changed back to  45eec532cefa  and everything is working fine.
> 


Thanks for the verification.


Regards,
Manu

> regards
> Oliver
> 
> -----Original Message-----
> From: linux-dvb-bounces@linuxtv.org
> [mailto:linux-dvb-bounces@linuxtv.org] On Behalf Of Manu Abraham
> Sent: Dienstag, 26. Februar 2008 22:45
> To: linux-dvb@linuxtv.org
> Subject: [linux-dvb] STB0899 users, please verify results was Re:
> TechniSat SkyStar HD: Problems scaning and zaping
> 
> Vangelis Nonas wrote:
>> Hello,
>>
>> Here is the output of hg log|head -n 5 for two different directories 
>> (multiproto and multiproto_7200)
>>
>> for multiproto:
>> changeset:   7205:9bdb997e38b5
>> tag:         tip
>> user:        Manu Abraham <manu@linuxtv.org>
>> date:        Sun Feb 24 02:10:56 2008 +0400
>> summary:     We can now reduce the debug levels, just need to look at 
>> errors only.
>>
>> for multiproto_7200:
>> changeset:   7200:45eec532cefa
>> tag:         tip
>> parent:      7095:a577a5dbc93d
>> parent:      7199:0448e5a6d8a6
>> user:        Manu Abraham <manu@linuxtv.org>
>>
>>
>> So I guess I was referring to 7200 and not to 7201.
>> I am very positive about the results because I have tested it many 
>> times. It is just that it is 7200 instead of 7201.
>> So as a concluesion, 7200 behaves better than 7205. My corrected 
>> little table follows below just for clarification.
> 
> 
> Ok, fine this is very much possible. Can other STB0899 users (all of
> them) verify this result, such that i can revert back the changes ?
> 
> 
>> Changeset   Verbose  channels
>> --------------------------------
>> 7200         1        2152
>> 7200         2        2105
>> 7200         5        2081
>> 7205         1        1760
>> 7205         2        1608
>> 7205         5        1578
>>
>>
>> I apologise for the confusion, I may have caused.
> 
> No worries, don't apologise, this is all a part of the testing phase.
> 
> 
> Thanks,
> Manu
> 
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Oliver Bardenheier (obardenh)]

 Seppo, You should use the group-mailer linux-dvb@linuxtv.org

regards
Oliver

-----Original Message-----
From: Seppo Ingalsuo [mailto:seppo.ingalsuo@iki.fi] 
Sent: Donnerstag, 28. Februar 2008 07:08
To: Oliver Bardenheier (obardenh)
Subject: Re: [linux-dvb] STB0899 users, please verify results was Re:
TechniSat SkyStar HD: Problems scaning and zaping

Oliver Bardenheier (obardenh) wrote:
> I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, 
> many transponders not working.
> I changed back to  45eec532cefa  and everything is working fine.
>   
I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to
see only BBC World from Astra 19.2E. Other channels I tried to zap to
didn't work. Also there seemed to be problems in driving reliably diseqc
positioner (that the old TT budget-s handled fine).

It was my first experience with brand new TT S2-3200 and vdr 1.5.16 with
Reinhard's H.264 patch set.

BR,
Seppo


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Seppo Ingalsuo]

Oliver Bardenheier (obardenh) wrote:
>  Seppo, You should use the group-mailer linux-dvb@linuxtv.org
>   
Sorry Olivier, I didn't mean to send you personal email!

I still have the same problem and I'm not familiar with various DVB 
driver sources discussed here (hg-tree, mantis). As I suppose I have the 
same issue as discussed in this thread, how do I retrieve an older 
version of the driver for TT S2-3200 that would work?

BR,
Seppo

> regards
> Oliver
>
> -----Original Message-----
> From: Seppo Ingalsuo [mailto:seppo.ingalsuo@iki.fi] 
> Sent: Donnerstag, 28. Februar 2008 07:08
> To: Oliver Bardenheier (obardenh)
> Subject: Re: [linux-dvb] STB0899 users, please verify results was Re:
> TechniSat SkyStar HD: Problems scaning and zaping
>
> Oliver Bardenheier (obardenh) wrote:
>   
>> I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable, 
>> many transponders not working.
>> I changed back to  45eec532cefa  and everything is working fine.
>>   
>>     
> I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to
> see only BBC World from Astra 19.2E. Other channels I tried to zap to
> didn't work. Also there seemed to be problems in driving reliably diseqc
> positioner (that the old TT budget-s handled fine).
>
> It was my first experience with brand new TT S2-3200 and vdr 1.5.16 with
> Reinhard's H.264 patch set.
>
> BR,
> Seppo
>
>   


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Oliver Bardenheier (obardenh)]

No problem,  :-)

You just check out the tree via the webpage:
http://jusst.de/hg/multiproto

then click on the needed changeset
http://jusst.de/hg/multiproto/rev/0448e5a6d8a6 

and download the bzip with the complete changeset
http://jusst.de/hg/multiproto/archive/0448e5a6d8a6.tar.bz2

The rest is routine....     :-)

Oliver


-----Original Message-----
From: linux-dvb-bounces@linuxtv.org
[mailto:linux-dvb-bounces@linuxtv.org] On Behalf Of Seppo Ingalsuo
Sent: Donnerstag, 28. Februar 2008 16:53
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] STB0899 users, please verify results was Re:
TechniSat SkyStar HD: Problems scaning and zaping

Oliver Bardenheier (obardenh) wrote:
>  Seppo, You should use the group-mailer linux-dvb@linuxtv.org
>   
Sorry Olivier, I didn't mean to send you personal email!

I still have the same problem and I'm not familiar with various DVB
driver sources discussed here (hg-tree, mantis). As I suppose I have the
same issue as discussed in this thread, how do I retrieve an older
version of the driver for TT S2-3200 that would work?

BR,
Seppo

> regards
> Oliver
>
> -----Original Message-----
> From: Seppo Ingalsuo [mailto:seppo.ingalsuo@iki.fi]
> Sent: Donnerstag, 28. Februar 2008 07:08
> To: Oliver Bardenheier (obardenh)
> Subject: Re: [linux-dvb] STB0899 users, please verify results was Re:
> TechniSat SkyStar HD: Problems scaning and zaping
>
> Oliver Bardenheier (obardenh) wrote:
>   
>> I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable,

>> many transponders not working.
>> I changed back to  45eec532cefa  and everything is working fine.
>>   
>>     
> I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to 
> see only BBC World from Astra 19.2E. Other channels I tried to zap to 
> didn't work. Also there seemed to be problems in driving reliably 
> diseqc positioner (that the old TT budget-s handled fine).
>
> It was my first experience with brand new TT S2-3200 and vdr 1.5.16 
> with Reinhard's H.264 patch set.
>
> BR,
> Seppo
>
>   


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Seppo Ingalsuo]

Oliver Bardenheier (obardenh) wrote:
> No problem,  :-)
>
> You just check out the tree via the webpage:
> http://jusst.de/hg/multiproto
>
> then click on the needed changeset
> http://jusst.de/hg/multiproto/rev/0448e5a6d8a6 
>
> and download the bzip with the complete changeset
> http://jusst.de/hg/multiproto/archive/0448e5a6d8a6.tar.bz2
>
> The rest is routine....     :-)
>   
Thanks! It works now (almost), zapping in Astra 19.2E works now very well.

... But diseqc positioner commands (GotoX from vdr rotor plugin) seem to 
not get through with 100% reliability. Changing to use diseqc.conf 
seemed to help a bit but I haven't been able to convince the motor to 
turn to 28.2E at all.

BR,
Seppo


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Vangelis Nonas]

Hello,

I think this page is very useful, because it explains the procedure 
quite well (also tells you about modified scan and zap):
http://www.linuxtv.org/wiki/index.php/Multiproto

Regards


Oliver Bardenheier (obardenh) wrote:
> No problem,  :-)
>
> You just check out the tree via the webpage:
> http://jusst.de/hg/multiproto
>
> then click on the needed changeset
> http://jusst.de/hg/multiproto/rev/0448e5a6d8a6 
>
> and download the bzip with the complete changeset
> http://jusst.de/hg/multiproto/archive/0448e5a6d8a6.tar.bz2
>
> The rest is routine....     :-)
>
> Oliver
>
>
> -----Original Message-----
> From: linux-dvb-bounces@linuxtv.org
> [mailto:linux-dvb-bounces@linuxtv.org] On Behalf Of Seppo Ingalsuo
> Sent: Donnerstag, 28. Februar 2008 16:53
> To: linux-dvb@linuxtv.org
> Subject: Re: [linux-dvb] STB0899 users, please verify results was Re:
> TechniSat SkyStar HD: Problems scaning and zaping
>
> Oliver Bardenheier (obardenh) wrote:
>   
>>  Seppo, You should use the group-mailer linux-dvb@linuxtv.org
>>   
>>     
> Sorry Olivier, I didn't mean to send you personal email!
>
> I still have the same problem and I'm not familiar with various DVB
> driver sources discussed here (hg-tree, mantis). As I suppose I have the
> same issue as discussed in this thread, how do I retrieve an older
> version of the driver for TT S2-3200 that would work?
>
> BR,
> Seppo
>
>   
>> regards
>> Oliver
>>
>> -----Original Message-----
>> From: Seppo Ingalsuo [mailto:seppo.ingalsuo@iki.fi]
>> Sent: Donnerstag, 28. Februar 2008 07:08
>> To: Oliver Bardenheier (obardenh)
>> Subject: Re: [linux-dvb] STB0899 users, please verify results was Re:
>> TechniSat SkyStar HD: Problems scaning and zaping
>>
>> Oliver Bardenheier (obardenh) wrote:
>>   
>>     
>>> I can confirm that current hg-tree breaks SkyStarHD. Mostly unusable,
>>>       
>
>   
>>> many transponders not working.
>>> I changed back to  45eec532cefa  and everything is working fine.
>>>   
>>>     
>>>       
>> I'm using multiproto-74c6c2ee613b grabbed yesterday and I was able to 
>> see only BBC World from Astra 19.2E. Other channels I tried to zap to 
>> didn't work. Also there seemed to be problems in driving reliably 
>> diseqc positioner (that the old TT budget-s handled fine).
>>
>> It was my first experience with brand new TT S2-3200 and vdr 1.5.16 
>> with Reinhard's H.264 patch set.
>>
>> BR,
>> Seppo
>>
>>   
>>     
>
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
>
>   


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] STB0899 users, please verify results was Re: TechniSat SkyStar HD: Problems scaning and zaping

[Seppo Ingalsuo]

Vangelis Nonas wrote:
> I think this page is very useful, because it explains the procedure 
> quite well (also tells you about modified scan and zap):
> http://www.linuxtv.org/wiki/index.php/Multiproto
Thanks for this as well! Modified scan & zap would have been next in my 
question list :^)

BR,
Seppo


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[P. van Gaans]

On 02/24/2008 06:56 PM, Vangelis Nonas wrote:
> Hello,
> 
> I tried scanning with the 7201 changeset and I believe the results are 
> better than the 7205 changeset. In the former case I get 2082 services 
> on hotbird, in the latter 1722.
> 
> I'll shortly send kernel logs for a failing transponder during scan.
> 
> And something else:
> When I give to scan the parameter -o vdr it will not output the results 
> after a complete scan.
> 
> 
> Regards
> Vagelis
> 
> 
> Vangelis Nonas wrote:
>> Hello,
>>
>> I attach the timing logs for changsets 7205 and 7201. The funny thing 
>> is that when I use 7201 it does NOT have the problem with locking  
>> when tuning, as it had before. I tried it 3 times, the third after a 
>> full shutdown of the pc and having removed the power for a couple on 
>> minutes. It is really strange.
>>
>> Anyway, both logs were taken with these commands:
>>
>> ../szap/szap -c channels.conf -r "bbc world"
>> ../szap/szap -c channels.conf -r "bbc prime"
>> ../szap/szap -c channels.conf -r "filmnet1"
>>
>> I'll check how scanning performs with 7201 and let you know
>>
>> Regards
>> Vagelis
>>
>>
>> Manu Abraham wrote:
>>> Vangelis Nonas wrote:
>>>> Thank you all for your help,
>>>>
>>>> With the latest changeset I can tune channels correctly. I tried vdr 
>>>> and szap (from Manu).
>>>>
>>>> I dont know how to undo the last changesets and go back to 7200. 
>>>> Please tell me how to do it and I'll get the timings.
>>>
>>> clone the multiproto tree
>>>
>>> from there, do a partial clone locally
>>>
>>> hg clone -r 7200 multiproto multiproto_7200
>>>
>>>
>>>> I also tried to scan Hotbird and it seems that scanning is now 
>>>> consistent when you scan the same transponder more than once.
>>>>
>>>> A full scan produced 1722 channels which is not bad, but it needs 
>>>> improvement. There are about 2200 channels I think.
>>> If you can provide a log with verbose=5 for the channels which it 
>>> doesn't
>>> scan it will be a bit more helpful. Will need the logs 
>>> (/var/log/messages)
>>> to debug this as well. The module parameters the same for both the
>>> STB0899 and the STB6100
>>>
>>>> I attach the log of the scan. It fails to scan certain transponders 
>>>> and I believe (not 100% sure, but I did some testing) that this is 
>>>> consistent across runs.
>>> The log is just the output of the scan utility, will need the output 
>>> from
>>> the driver and a bit of thoughts.
>>>
>>>
>>>
>>> Regards,
>>> Manu
>>>
>>>> Regards
>>>> Vagelis
>>>>
>>>>
>>>>
>>>> Manu Abraham wrote:
>>>>> Manu Abraham wrote:
>>>>>  
>>>>>> Artem Makhutov wrote:
>>>>>>  
>>>>>>> Hi,
>>>>>>>
>>>>>>> On Sat, Feb 23, 2008 at 10:32:58PM +0100, Artem Makhutov wrote:
>>>>>>>    
>>>>>>>> On Sun, Feb 24, 2008 at 01:29:31AM +0400, Manu Abraham wrote:
>>>>>>>>      
>>>>>>>>> Are you sure that you got the top level 2 changes changeset 
>>>>>>>>> 7204 and 7203
>>>>>>>>> respectively ?
>>>>>>>>>           
>>>>>>>> Oh, I only got 7203. Will try with 7204 in a few minutes.
>>>>>>>>         
>>>>>>> Awesome! It fixed the problem:
>>>>>>>
>>>>>>> Try: 100
>>>>>>> Failes: 0
>>>>>>> Tunes: 100
>>>>>>>
>>>>>>> Great job!
>>>>>>>       
>>>>> Also, can you please do a benchmark in lock timings between 
>>>>> changeset 7205 and 7200 ?
>>>>>
>>>>> The timing can be looked at by enabling the time stamps in the 
>>>>> kernel config and
>>>>> looking at timestamps in the logs for start - stop (FE_HAS_LOCK) 
>>>>> between the 2
>>>>> changesets.
>>>>>
>>>>> Regards,
>>>>> Manu
>>>>>
>>>>> _______________________________________________
>>>>> linux-dvb mailing list
>>>>> linux-dvb@linuxtv.org
>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>>>>>
>>>>>
>>>>>   
>>>
>>>
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> linux-dvb mailing list
>> linux-dvb@linuxtv.org
>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> 
> 
> _______________________________________________
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
> 

You might also want to try using transponderlists from joshyfun: 
http://joshyfun.peque.org/transponders/kaffeine.html. Network scanning 
does not give all channels in some cases.

On the Hotbird, I've got 1921 services, including encrypted radio and TV 
channels, but without data services. This is on a (well supported) 
Technotrend S-1500, so these should be all channels.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
> Also, can you please do a benchmark in lock timings between changeset 
> 7205 and 7200 ?

Do you mean changeset 7200 or 7204

> [...]

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Artem Makhutov wrote:
> Hi,
> 
> On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
>> Also, can you please do a benchmark in lock timings between changeset 
>> 7205 and 7200 ?
> 
> Do you mean changeset 7200 or 7204

yep. 7205 is head, but just a minor change.

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sun, Feb 24, 2008 at 05:52:39PM +0400, Manu Abraham wrote:
> Artem Makhutov wrote:
> >Hi,
> >
> >On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
> >>Also, can you please do a benchmark in lock timings between changeset 
> >>7205 and 7200 ?
> >
> >Do you mean changeset 7200 or 7204
> 
> yep. 7205 is head, but just a minor change.

I did the benchmark betweet 7205 and 7204.
The modules were loaded with no additional parameters.

Tuning time in 7204: ~0.83 seconds (min 0.81191 sec ; max 2.428967 sec)
Tuning time in 7205: ~0.26 seconds (min 0.24789 sec ; max 1.994216 sec)

You can get the logfiles of the tests here:
http://www.makhutov.org/downloads/dvb/logs/7204.log.gz
http://www.makhutov.org/downloads/dvb/logs/7205.log.gz

I made 60 tunes for 7204 and 45 tunes for 7205.

The first 20 tunes were made without any brake after each tune.
The next 20 tunes were made with a break of 15 seconds after each tune.
The next 20/5 tunes were made with a break of 2 minutes between each
tune.

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Artem Makhutov wrote:
> Hi,
> 
> On Sun, Feb 24, 2008 at 05:52:39PM +0400, Manu Abraham wrote:
>> Artem Makhutov wrote:
>>> Hi,
>>>
>>> On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
>>>> Also, can you please do a benchmark in lock timings between changeset 
>>>> 7205 and 7200 ?
>>> Do you mean changeset 7200 or 7204
>> yep. 7205 is head, but just a minor change.
> 
> I did the benchmark betweet 7205 and 7204.
> The modules were loaded with no additional parameters.
> 
> Tuning time in 7204: ~0.83 seconds (min 0.81191 sec ; max 2.428967 sec)
> Tuning time in 7205: ~0.26 seconds (min 0.24789 sec ; max 1.994216 sec)


Can you test the time between 7200 and 7204/7205.
(7201 - 7204 contains an optimization, compared to 7200 and hence
the need to check the results. So need to exclude 7201 and 7204)

Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Sun, Feb 24, 2008 at 11:23:02PM +0400, Manu Abraham wrote:
> Artem Makhutov wrote:
> >Hi,
> >
> >On Sun, Feb 24, 2008 at 05:52:39PM +0400, Manu Abraham wrote:
> >>Artem Makhutov wrote:
> >>>Hi,
> >>>
> >>>On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
> >>>>Also, can you please do a benchmark in lock timings between changeset 
> >>>>7205 and 7200 ?
> >>>Do you mean changeset 7200 or 7204
> >>yep. 7205 is head, but just a minor change.
> >
> >I did the benchmark betweet 7205 and 7204.
> >The modules were loaded with no additional parameters.
> >
> >Tuning time in 7204: ~0.83 seconds (min 0.81191 sec ; max 2.428967 sec)
> >Tuning time in 7205: ~0.26 seconds (min 0.24789 sec ; max 1.994216 sec)
> 
> 
> Can you test the time between 7200 and 7204/7205.
> (7201 - 7204 contains an optimization, compared to 7200 and hence
> the need to check the results. So need to exclude 7201 and 7204)

Ok, I got it. I was in the believe that the tuning will only work ~50 percent
successfull with rev 7200...)

Here are the results of the benchmarks with rev 7200:

A tune needs ~1 second.
Min: 0.829529 ; Max: 3.074599

The log file is available at:
http://www.makhutov.org/downloads/dvb/logs/7200.log.gz

So your optimizations works great ;)

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Manu Abraham]

Artem Makhutov wrote:
> Hi,
> 
> On Sun, Feb 24, 2008 at 05:52:39PM +0400, Manu Abraham wrote:
>> Artem Makhutov wrote:
>>> Hi,
>>>
>>> On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
>>>> Also, can you please do a benchmark in lock timings between changeset 
>>>> 7205 and 7200 ?
>>> Do you mean changeset 7200 or 7204
> 
> I did the benchmark betweet 7205 and 7204.
> The modules were loaded with no additional parameters.
> 
> Tuning time in 7204: ~0.83 seconds (min 0.81191 sec ; max 2.428967 sec)
> Tuning time in 7205: ~0.26 seconds (min 0.24789 sec ; max 1.994216 sec)
> 
> I have attached the logfiles of the tests.
> 
> I made 60 tunes for 7204 and 45 tunes for 7205.


 From the 7205 logs, it looks no lock failure at all. Is this too good 
to believe ?

but i do see that you have a lock loss case in 7204. is that 7204 and 7205
logs got interchanged ?


Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping

[Artem Makhutov]

Hi,

On Mon, Feb 25, 2008 at 12:27:27AM +0400, Manu Abraham wrote:
> Artem Makhutov wrote:
> >Hi,
> >
> >On Sun, Feb 24, 2008 at 05:52:39PM +0400, Manu Abraham wrote:
> >>Artem Makhutov wrote:
> >>>Hi,
> >>>
> >>>On Sun, Feb 24, 2008 at 02:18:52AM +0400, Manu Abraham wrote:
> >>>>Also, can you please do a benchmark in lock timings between changeset 
> >>>>7205 and 7200 ?
> >>>Do you mean changeset 7200 or 7204
> >
> >I did the benchmark betweet 7205 and 7204.
> >The modules were loaded with no additional parameters.
> >
> >Tuning time in 7204: ~0.83 seconds (min 0.81191 sec ; max 2.428967 sec)
> >Tuning time in 7205: ~0.26 seconds (min 0.24789 sec ; max 1.994216 sec)
> >
> >I have attached the logfiles of the tests.
> >
> >I made 60 tunes for 7204 and 45 tunes for 7205.
> 
> 
> From the 7205 logs, it looks no lock failure at all. Is this too good 
> to believe ?
>
> but i do see that you have a lock loss case in 7204. is that 7204 and 7205
> logs got interchanged ?

Oh, I haven't even seen that there was a lock loss. Since rev 7204 the
card tunes very reliable.

No, the logs between rev 7204 and 7205 got not interchanged.

Regards, Artem

-- 
Artem Makhutov
Unterort Str. 36
D-65760 Eschborn

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb