Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping
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 [EMAIL PROTECTED] 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 [EMAIL PROTECTED] 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 12152 7200 22105 7200 52081 7205 11760 7205 21608 7205 51578 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 12152 7201 22105 7201 52081 7205 11760 7205 21608 7205 51578 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
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 12152 7201 22105 7201 52081 7205 11760 7205 21608 7205 51578 It is very strange that using the 7205 changeset (all verbose) Zagros TV for instance and all other channels on transponder S 11727000 V 2750 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 2750 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 . S 10719000 V 2750 3/4 S 10723000 H 2990 3/4 S 10758000 V 2750 3/4 S 10775000 H 2800 3/4 S 10796000 V 2750 3/4 S 1083 H 000 3/4 S 10834000 V 2750 3/4 S 10853000 H 2750 3/4 S 10873000 V 2750 3/4 S 10892000 H 2750 3/4 S 10911000 V 2750 3/4 S 1093 H 2750 3/4 S 10949000 V 2750 3/4 S 10971000 H 2750 3/4 S 10992000 V 2750 2/3 S 11013000 H 2750 3/4 S 11034000 V 2750 3/4 S 11054000 H 2750 5/6 S 11075000 V 2750 3/4 S 11096000 H 2800 3/4 S 7000 V 2750 3/4 S 11137000 H 2750 3/4 S 11158000 V 2750 3/4 S 11179000 H 2750 3/4 S 1120 V 2750 5/6 S 11219000 H 2750 3/4 S 1124 V 2750 3/4 S 11258000 H 2750 2/3 S 11278000 V 2750 3/4 S 11296000 H 2750 3/4 S 11334000 H 2750 1/2 S 11355000 V 2750 3/4 S 11373000 H 19636000 2/3 S 11393000 V 2750 3/4 S 11411000 H 2750 5/6 S 11432000 V 2750 1/2 S 11449000 H 2750 2/3 S 1147 V 2750 5/6 S 11488000 H 2750 3/4 S 11523000 V 500 7/8 S 11526000 H 2750 3/4 S 11541000 V 2200 5/6 S 11566000 H 2750 3/4 S 11585000 V 2750 3/4 S 11604000 H 2750 5/6 S 11623000 V 2750 3/4 S 11642000 H 2750 3/4 S 11662000 V 2750 3/4 S 11681000 H 2750 3/4 S 11727000 V 2750 3/4 S 11747000 H 2750 3/4 S 11766000 V 2750 2/3 S 11785000 H 2750 3/4 S 11804000 V 2750 2/3 S 11823000 H 2750 3/4 S 11843000 V 2750 3/4 S 11862000 H 2750 3/4 S 11881000 V 2750 3/4 S 1190 H 2750 3/4 S 11919000 V 2750 2/3 S 11938000 H 2750 3/4 S 11958000 V 2750 3/4 S 11977000 H 2750 3/4 S 11996000 V 2750 2/3 S 12015000 H 2750 3/4 S 12034000 V 2750 3/4 S 12054000 H 2750 3/4 S 12073000 V 2750 3/4 S 12092000 H 2750 3/4 S 12111000 V 2750 3/4 S 12145000 H 000 3/4 S 12149000 V 2750 3/4 S 12169000 H 2750 3/4 S 12188000 V 2750 3/4 S
Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping
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 12152 7201 22105 7201 52081 7205 11760 7205 21608 7205 51578 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
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 7201.log.gz Description: GNU Zip compressed data 7205.log.gz Description: GNU Zip compressed data ___ 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
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
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
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
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
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
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
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
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
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
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
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
Re: [linux-dvb] TechniSat SkyStar HD: Problems scaning and zaping
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=[0x0400], Offset=[0xf334], Data=[0x444d4431] _stb0899_read_s2reg Device=[0xf3fc], Base address=[0x0400], Offset=[0xf33c], Data=[0x0001] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa2c], Data=[0x46454331] _stb0899_read_s2reg Device=[0xfafc], Base address=[0x0800], Offset=[0xfa34], Data=[0x0001] 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
Hi, On Sat, Feb 23, 2008 at 12:35:49PM +, 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
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
Artem Makhutov wrote: Hi, On Sat, Feb 23, 2008 at 12:35:49PM +, 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
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
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
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
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
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 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
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 scan.log.gz Description: GNU Zip compressed data ___ 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 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
