Re: [linux-dvb] Terratec Cinergy DVB C PCI CI - CI working?
On 03/14/2008 11:35 PM, Karim 'Kasi Mir' Senoucci wrote: > Hello everyone, > I've got the Terratec Cinergy C PCI HD card with the CI extension and am > currently trying to get this to work with Mythbuntu 7.10. So far, I've > got a working TV signal and a more or less complete list of the Kabel > Deuttschland DVB-C channels. I can even watch the free-to-air channels > without any problems. > > The encrypted channels (of which there are legion) are another matter, > though. AS I wrote above, I have the CI addon, I have a AlphaCrypt CAM > capable of decoding the Cable encryption, plus I've got a keycard which > actually can decode about 100 channels. > > But still, MythTV doesn't decode any encrypted channels - which leads me > to my question: is the CI supported by Linux? As far a I can see, there > is no line containing CI oder CAM in any logfile written by the linux > system. > > Can anybody help me out here? Any help is appreciated; if you need more > input, just ask and I will try to provide the info. > > Greetings > Kasi Mir > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Did you get the latest v4l-dvb from http://linuxtv.org/repo/? If not, try that first. When you insert your CAM, you should be able to read some message with dmesg about the card having been initialized or having failed. You should also have a /dev/dvb/adapterN/ca0. Also check your CI cable. They fail quite often. P. ___ 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] DiSEqC trouble with TT S-1500
On 02/20/2008 08:24 PM, Remy Bohmer wrote: > Hello All, > > Maybe I have the answer: > I also had problems with switches and LNBs which did not want to work > properly. > Behind 1 receiver it worked properly, but behind another 2 different > DVB-S PCI cards, it just failed. I never suspected the LNB/Switch > setup, because it worked behind another receiver. > But, In the end it turned out that there was 1 LNB in my setup that > caused all the trouble, that LNB refused to cooperate with the > switches and other LNBs, when a DVB-S PCI card was used (both > Technisat Skystar 1CI, and TT-S1500). Once switched to this LNB, the > complete setup failed to work from that moment on. I could never > switch back to 1 of the previous LNBs, but the last (buggy) LNB still > worked if I switched back to it. > > So, my advice is to start with 1 LNB behind a switch, once it works, > add another one, check if both LNBs still works, if so, add another > LNB and so on. Maybe you end up, just like me, with 1 LNB that > destroys the complete behavior. > > So, my 3 TT-S1500s are properly working here now with MythTv and > DiseqC switches with 4 LNBs per card/switch. So, it _can_ work... > > > Good luck! > > > Kind Regards, > > Remy > > > > 2008/2/20, P. van Gaans <[EMAIL PROTECTED]>: >> On 02/20/2008 10:48 AM, Doru Marin wrote: >> > P. van Gaans wrote: >> >> On 02/18/2008 02:04 PM, Doru Marin wrote: >> >> >> >>> P. van Gaans wrote: >> >>> >> >>>> On 02/16/2008 01:20 AM, P. van Gaans wrote: >> >>>> >> >>>> >> >>>>> On 02/13/2008 09:21 PM, P. van Gaans wrote: >> >>>>> >> >>>>>> On 02/13/2008 03:01 PM, Doru Marin wrote: >> >>>>>> >> >>>>>>> Hi, >> >>>>>>> >> >>>>>>> Can you explain how you select those 4 positions ? DiSEqC >> >>>>>>> commands or tone/voltage changes ? >> >>>>>>> Also can you determine the input type of those positions (Hi/Low, >> >>>>>>> H/V, etc) ? A scenario to see when and why that happens, would be >> >>>>>>> more useful. >> >>>>>>> >> >>>>>>> P. van Gaans wrote: >> >>>>>>> >> >>>>>>>> Hi, >> >>>>>>>> >> >>>>>>>> I've got a Technotrend S-1500 (if it matters: I use it with >> >>>>>>>> Kaffeine 0.8.3). It works mostly fine, but there's a strange >> >>>>>>>> problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 >> >>>>>>>> euro), I can only switch without trouble to position 1 and 2. If >> >>>>>>>> I tune directly to position 3 it won't lock. >> >>>>>>>> >> >>>>>>>> However, if I first tune to a channel on position 1 or 2 and try >> >>>>>>>> a channel on position 3 after that, it will work. Position 4 >> >>>>>>>> however is completely unreachable. >> >>>>>>>> >> >>>>>>>> On a standalone receiver, there's no trouble with the same cable. >> >>>>>>>> >> >>>>>>>> Now Spaun is a really expensive and respected brand. So their >> >>>>>>>> switches possibly work in a different way, because a cheap >> >>>>>>>> Maximum 4/1 switch works perfectly with the S-1500. Position 1, >> >>>>>>>> 2, 3 and 4 all work perfectly. I also did some "dry testing" >> >>>>>>>> indoors and it looks like a 7 euro Satconn 4/1 switch would also >> >>>>>>>> work fine, but a 17 euro Axing SPU 41-02 probably won't. >> >>>>>>>> >> >>>>>>>> I'm guessing this could be solved in stv0299.c but I'm not much >> >>>>>>>> of an expert. I took a look at the code but I'm not really sure >> >>>>>>>> what to do. >> >>>>>>>> >> >>>>>>>> ___ >> >>>>>>>> linux-dvb mailing list >> >>>>>>>> linu
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/20/2008 10:48 AM, Doru Marin wrote: > P. van Gaans wrote: >> On 02/18/2008 02:04 PM, Doru Marin wrote: >> >>> P. van Gaans wrote: >>> >>>> On 02/16/2008 01:20 AM, P. van Gaans wrote: >>>> >>>> >>>>> On 02/13/2008 09:21 PM, P. van Gaans wrote: >>>>> >>>>>> On 02/13/2008 03:01 PM, Doru Marin wrote: >>>>>> >>>>>>> Hi, >>>>>>> >>>>>>> Can you explain how you select those 4 positions ? DiSEqC >>>>>>> commands or tone/voltage changes ? >>>>>>> Also can you determine the input type of those positions (Hi/Low, >>>>>>> H/V, etc) ? A scenario to see when and why that happens, would be >>>>>>> more useful. >>>>>>> >>>>>>> P. van Gaans wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> I've got a Technotrend S-1500 (if it matters: I use it with >>>>>>>> Kaffeine 0.8.3). It works mostly fine, but there's a strange >>>>>>>> problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 >>>>>>>> euro), I can only switch without trouble to position 1 and 2. If >>>>>>>> I tune directly to position 3 it won't lock. >>>>>>>> >>>>>>>> However, if I first tune to a channel on position 1 or 2 and try >>>>>>>> a channel on position 3 after that, it will work. Position 4 >>>>>>>> however is completely unreachable. >>>>>>>> >>>>>>>> On a standalone receiver, there's no trouble with the same cable. >>>>>>>> >>>>>>>> Now Spaun is a really expensive and respected brand. So their >>>>>>>> switches possibly work in a different way, because a cheap >>>>>>>> Maximum 4/1 switch works perfectly with the S-1500. Position 1, >>>>>>>> 2, 3 and 4 all work perfectly. I also did some "dry testing" >>>>>>>> indoors and it looks like a 7 euro Satconn 4/1 switch would also >>>>>>>> work fine, but a 17 euro Axing SPU 41-02 probably won't. >>>>>>>> >>>>>>>> I'm guessing this could be solved in stv0299.c but I'm not much >>>>>>>> of an expert. I took a look at the code but I'm not really sure >>>>>>>> what to do. >>>>>>>> >>>>>>>> ___ >>>>>>>> linux-dvb mailing list >>>>>>>> linux-dvb@linuxtv.org >>>>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>>>>>> >>>>>> I select them with Kaffeine. Hi/low and H/V doesn't matter. I >>>>>> tried upgrading to Kaffeine 0.8.5 but that doesn't make a >>>>>> difference. The "scan" application has the same issues. >>>>>> >>>>>> ___ >>>>>> linux-dvb mailing list >>>>>> linux-dvb@linuxtv.org >>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>>>> >>>>>> >>>>> Nobody any ideas? If not, does anybody have some idea what the >>>>> difference between position 1+2, pos 3 and pos 4 could be? I was >>>>> thinking 1 and 2 might be working because of toneburst, but I don't >>>>> think Kaffeine uses such a signal and that doesn't explain why pos >>>>> 3 works if first tuning to 1 or 2 and 4 doesn't work at all. >>>>> >>>>> >>>> I've figured out a bit more. If I tune directly to postion 3, I get pos >>>> 1. Whenever I tune to pos 4, I get pos 2. >>>> >>>> I'll also ask people from Kaffeine as I'm not sure if the problem is >>>> in the application, driver or somewhere else. >>>> >>>> ___ >>>> linux-dvb mailing list >>>> linux-dvb@linuxtv.org >>>> http://www.linuxtv.org/cgi-bin/mailman/l
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/18/2008 02:04 PM, Doru Marin wrote: > P. van Gaans wrote: >> On 02/16/2008 01:20 AM, P. van Gaans wrote: >> >>> On 02/13/2008 09:21 PM, P. van Gaans wrote: >>> >>>> On 02/13/2008 03:01 PM, Doru Marin wrote: >>>> >>>>> Hi, >>>>> >>>>> Can you explain how you select those 4 positions ? DiSEqC commands >>>>> or tone/voltage changes ? >>>>> Also can you determine the input type of those positions (Hi/Low, >>>>> H/V, etc) ? A scenario to see when and why that happens, would be >>>>> more useful. >>>>> >>>>> P. van Gaans wrote: >>>>> >>>>>> Hi, >>>>>> >>>>>> I've got a Technotrend S-1500 (if it matters: I use it with >>>>>> Kaffeine 0.8.3). It works mostly fine, but there's a strange >>>>>> problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 >>>>>> euro), I can only switch without trouble to position 1 and 2. If I >>>>>> tune directly to position 3 it won't lock. >>>>>> >>>>>> However, if I first tune to a channel on position 1 or 2 and try a >>>>>> channel on position 3 after that, it will work. Position 4 however >>>>>> is completely unreachable. >>>>>> >>>>>> On a standalone receiver, there's no trouble with the same cable. >>>>>> >>>>>> Now Spaun is a really expensive and respected brand. So their >>>>>> switches possibly work in a different way, because a cheap Maximum >>>>>> 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 >>>>>> all work perfectly. I also did some "dry testing" indoors and it >>>>>> looks like a 7 euro Satconn 4/1 switch would also work fine, but a >>>>>> 17 euro Axing SPU 41-02 probably won't. >>>>>> >>>>>> I'm guessing this could be solved in stv0299.c but I'm not much of >>>>>> an expert. I took a look at the code but I'm not really sure what >>>>>> to do. >>>>>> >>>>>> ___ >>>>>> linux-dvb mailing list >>>>>> linux-dvb@linuxtv.org >>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>>>> >>>> I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried >>>> upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The >>>> "scan" application has the same issues. >>>> >>>> ___ >>>> linux-dvb mailing list >>>> linux-dvb@linuxtv.org >>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>> >>>> >>> Nobody any ideas? If not, does anybody have some idea what the >>> difference between position 1+2, pos 3 and pos 4 could be? I was >>> thinking 1 and 2 might be working because of toneburst, but I don't >>> think Kaffeine uses such a signal and that doesn't explain why pos 3 >>> works if first tuning to 1 or 2 and 4 doesn't work at all. >>> >>> >> >> I've figured out a bit more. If I tune directly to postion 3, I get pos >> 1. Whenever I tune to pos 4, I get pos 2. >> >> I'll also ask people from Kaffeine as I'm not sure if the problem is >> in the application, driver or somewhere else. >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > Hi, > > Strange scenario. You're not saying anything about input types and the > switch type. Are you sure that are properly connected ? How the switch > inputs are marked and from where you got the input signals ? Please > elaborate, if you want a proper answer. > I suggest to play with 'scandvb' from dvb-apps package instead of > Kaffeine. Look into scanning results if the scanned channels match with > what you wished to have on those positions. > Hi, What do you mean with input type? Anyway, this is my config: Visiosat Bisat G3C for 19.2/28.2/23.5 + Triax 54cm for Hotbird 4 quad LNBs Spaun SAR 411F: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird Maximum 4/1: A = Astra 19.2 B = Astra 28.2/Eurobird1 C = Astra 23.5 D = Hotbird All works fine on a standalone so it is connected correctly. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/16/2008 01:20 AM, P. van Gaans wrote: > On 02/13/2008 09:21 PM, P. van Gaans wrote: >> On 02/13/2008 03:01 PM, Doru Marin wrote: >>> Hi, >>> >>> Can you explain how you select those 4 positions ? DiSEqC commands or >>> tone/voltage changes ? >>> Also can you determine the input type of those positions (Hi/Low, >>> H/V, etc) ? A scenario to see when and why that happens, would be >>> more useful. >>> >>> P. van Gaans wrote: >>>> Hi, >>>> >>>> I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine >>>> 0.8.3). It works mostly fine, but there's a strange problem. With my >>>> Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only >>>> switch without trouble to position 1 and 2. If I tune directly to >>>> position 3 it won't lock. >>>> >>>> However, if I first tune to a channel on position 1 or 2 and try a >>>> channel on position 3 after that, it will work. Position 4 however >>>> is completely unreachable. >>>> >>>> On a standalone receiver, there's no trouble with the same cable. >>>> >>>> Now Spaun is a really expensive and respected brand. So their >>>> switches possibly work in a different way, because a cheap Maximum >>>> 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 >>>> all work perfectly. I also did some "dry testing" indoors and it >>>> looks like a 7 euro Satconn 4/1 switch would also work fine, but a >>>> 17 euro Axing SPU 41-02 probably won't. >>>> >>>> I'm guessing this could be solved in stv0299.c but I'm not much of >>>> an expert. I took a look at the code but I'm not really sure what to >>>> do. >>>> >>>> ___ >>>> linux-dvb mailing list >>>> linux-dvb@linuxtv.org >>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>> >> >> I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried >> upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The >> "scan" application has the same issues. >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > > Nobody any ideas? If not, does anybody have some idea what the > difference between position 1+2, pos 3 and pos 4 could be? I was > thinking 1 and 2 might be working because of toneburst, but I don't > think Kaffeine uses such a signal and that doesn't explain why pos 3 > works if first tuning to 1 or 2 and 4 doesn't work at all. > I've figured out a bit more. If I tune directly to postion 3, I get pos 1. Whenever I tune to pos 4, I get pos 2. I'll also ask people from Kaffeine as I'm not sure if the problem is in the application, driver or somewhere else. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/13/2008 09:21 PM, P. van Gaans wrote: > On 02/13/2008 03:01 PM, Doru Marin wrote: >> Hi, >> >> Can you explain how you select those 4 positions ? DiSEqC commands or >> tone/voltage changes ? >> Also can you determine the input type of those positions (Hi/Low, H/V, >> etc) ? A scenario to see when and why that happens, would be more useful. >> >> P. van Gaans wrote: >>> Hi, >>> >>> I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine >>> 0.8.3). It works mostly fine, but there's a strange problem. With my >>> Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only >>> switch without trouble to position 1 and 2. If I tune directly to >>> position 3 it won't lock. >>> >>> However, if I first tune to a channel on position 1 or 2 and try a >>> channel on position 3 after that, it will work. Position 4 however is >>> completely unreachable. >>> >>> On a standalone receiver, there's no trouble with the same cable. >>> >>> Now Spaun is a really expensive and respected brand. So their switches >>> possibly work in a different way, because a cheap Maximum 4/1 switch >>> works perfectly with the S-1500. Position 1, 2, 3 and 4 all work >>> perfectly. I also did some "dry testing" indoors and it looks like a 7 >>> euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU >>> 41-02 probably won't. >>> >>> I'm guessing this could be solved in stv0299.c but I'm not much of an >>> expert. I took a look at the code but I'm not really sure what to do. >>> >>> ___ >>> linux-dvb mailing list >>> linux-dvb@linuxtv.org >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>> > > I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried > upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The > "scan" application has the same issues. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Nobody any ideas? If not, does anybody have some idea what the difference between position 1+2, pos 3 and pos 4 could be? I was thinking 1 and 2 might be working because of toneburst, but I don't think Kaffeine uses such a signal and that doesn't explain why pos 3 works if first tuning to 1 or 2 and 4 doesn't work at all. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DiSEqC trouble with TT S-1500
On 02/13/2008 03:01 PM, Doru Marin wrote: > Hi, > > Can you explain how you select those 4 positions ? DiSEqC commands or > tone/voltage changes ? > Also can you determine the input type of those positions (Hi/Low, H/V, > etc) ? A scenario to see when and why that happens, would be more useful. > > P. van Gaans wrote: >> Hi, >> >> I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine >> 0.8.3). It works mostly fine, but there's a strange problem. With my >> Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only >> switch without trouble to position 1 and 2. If I tune directly to >> position 3 it won't lock. >> >> However, if I first tune to a channel on position 1 or 2 and try a >> channel on position 3 after that, it will work. Position 4 however is >> completely unreachable. >> >> On a standalone receiver, there's no trouble with the same cable. >> >> Now Spaun is a really expensive and respected brand. So their switches >> possibly work in a different way, because a cheap Maximum 4/1 switch >> works perfectly with the S-1500. Position 1, 2, 3 and 4 all work >> perfectly. I also did some "dry testing" indoors and it looks like a 7 >> euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU >> 41-02 probably won't. >> >> I'm guessing this could be solved in stv0299.c but I'm not much of an >> expert. I took a look at the code but I'm not really sure what to do. >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > I select them with Kaffeine. Hi/low and H/V doesn't matter. I tried upgrading to Kaffeine 0.8.5 but that doesn't make a difference. The "scan" application has the same issues. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] DiSEqC trouble with TT S-1500
Hi, I've got a Technotrend S-1500 (if it matters: I use it with Kaffeine 0.8.3). It works mostly fine, but there's a strange problem. With my Spaun 4/1 DiSEqC switch (they cost approx 25-40 euro), I can only switch without trouble to position 1 and 2. If I tune directly to position 3 it won't lock. However, if I first tune to a channel on position 1 or 2 and try a channel on position 3 after that, it will work. Position 4 however is completely unreachable. On a standalone receiver, there's no trouble with the same cable. Now Spaun is a really expensive and respected brand. So their switches possibly work in a different way, because a cheap Maximum 4/1 switch works perfectly with the S-1500. Position 1, 2, 3 and 4 all work perfectly. I also did some "dry testing" indoors and it looks like a 7 euro Satconn 4/1 switch would also work fine, but a 17 euro Axing SPU 41-02 probably won't. I'm guessing this could be solved in stv0299.c but I'm not much of an expert. I took a look at the code but I'm not really sure what to do. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Software support for the "Technotrend TT-Budget S-1500"
On 01/22/2008 12:12 AM, Michael Finch wrote: > Hi All, > > I have noticed that there is significant support for the "Technotrend > TT-budget S1500" PCI card, which I am excited to see. > I have also noticed that there is very little support for the "Technotrend > TT-budget S1401" card. > > I am curious if the reason for the lack of support for the S-1401 card is > simply because nobody has gotten around to developing LINUX support for it or > if there is a good reason to go with the S-1500 card instead. I have a client > with a new project that requires using one of these cards (or something > similar). Is the S-1500 a better choice?Thanks,Mike Finch > [EMAIL PROTECTED] > _ > Climb to the top of the charts! Play the word scramble challenge with star > power. > http://club.live.com/star_shuffle.aspx?icid=starshuffle_wlmailtextlink_jan > > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb I have the S-1500 and it works perfect right out of the box. Supported since.. quite a while I believe. The difference between the two is the CI-connector for the optional budget-ci on the S-1500. I wanted to use a CAM so I got the S-1500 with budget-ci and extension cable. If you don't need a CI/CAM, you'll save some money by going for the S-1401. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Multiproto ???
On 01/16/2008 05:17 PM, Stephen Rowles wrote: >> The current BBC HD transmissions, prior to the official launch of Freesat >> are DVB-S, and broadcast From Astra 28.2E. There was some talk of a >> possible >> move to DVB-S2 at some time in the future, but I don't have a reference >> for >> this and haven't seen anything more about it in the last few months. >> >> AFAIK, all the current BBC HD transmissions are 1080i. > > Ouchy, > > I'll revise my hardware estimate then if they are 1080i I will need a > seriously quick processor, or the VAAPI project to get off the ground > quickly then :D > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > With an mplayer compiled half a year ago or so I can watch BBC HD recordings on my Athlon 64 X2 4200+ when using mplayer -lavdopts fast:skiploopfilter=all. It runs smooth and picture quality is only hurt a little bit (especially in very fast action scenes). Current BBC HD broadcast is DVB-S, probably because 1 transponder for 1 channel would be ridiculous. On the same transponder you also find BBC 1 CI and BBC 1 Cambridge. Video is h.264 1440*1080i. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Looking for a satellite signal finder tool
On 12/18/2007 06:12 PM, spectro wrote: > Is there a console dvb tool I can use as signal finder to tune my dish? > > So far I tried hacking dvbtune to print signal level once a second > while acquiring signal lock but it is not helping much. Googling > didn't find anything so I want to check before I get into some serious > hacking. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > What about femon or femonspeak? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S card swaps / giveaway
On 12/09/2007 10:00 PM, Matthew Bloch wrote: > Hello again, > > I've had two unsuccessful attempts at finding a Linux-supported DVB-S > card. I've bought two Technisat products: a Skystar USB Plus - except > the "Plus" model is completely different from the supported "Skystar > USB", and now a Skystar 2 TV PCI card, except I bought a revision 2.7V > which isn't supported either. > > I'd happily give either or both of these away to developers interested > in getting some drivers written; alternatively I could swap one of them > for a Linux-supported card if that interests anyone? > > Finally can anyone suggest a shop selling a compatible card who'll ship > to the UK? It's been an expensive uphill struggle so far :) > > Thanks, > Second half of august 2007 I bought a Technotrend S-1500 with CI from dvbshop.net, and it works for me. I recognize your experience, I once bought a Technisat AirStar DVB-T USB. Didn't work on Linux either. I'll take another look at that sometime.. P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-S card for 3.8 GHz frequency range?
On 12/07/2007 12:08 PM, Matthias Schwarzott wrote: > On Freitag, 7. Dezember 2007, Bernhard Rosenkraenzer wrote: >> Hi, >> >> I'm trying to record the Ethiopian Schoolnet DVB-S channels - >> unfortunately they seem to be broadcast at really weird frequencies >> (3.887 GHz, Symbol rate 2650) that none of the DVB-S cards I tried >> can handle (the cards I tried seem to be limited to the 10 GHz-12 GHz >> range). >> >> Is there any card (PCI preferred, but USB would be ok) that can >> receive DVB-S broadcasts at 3.887 GHz, or is there anything that could >> be used to shift the signal to a reasonable frequency? >> > Well normally the LNB shifts the frequency to a reasonable range that can be > carried on coax cables. It just seems that your LNB is no normal Ku band one. > So you must have have one with another local-oszilator frequency (C-Band?). > Wikipedia tells me: "A typical C-band satellite uses 3.7–4.2 GHz for > downlink." > Local oscillator: 5.15 GHz > > It should be enough to configure the software using the correct LO frequency. > Then you should be able to receive the channel. > > Matthias If he can in the first place. For KU-band, usually a small dish (40-120cm) is used. That's consumer (DTH, Direct To Home) stuff. With the C-band, you have usually have to start thinking 180cm and up, and a different (probably more expensive) LNB. In Kaffeine, you can configure a C-band LNB. I've never tried it, I don't have enough space to set up a dish for the C-band.. P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] CAM inserted/used reduces signal and SNR ?
On 11/18/2007 10:34 AM, Luc Brosens wrote: > Hi, > > side note : > the problems in my previous post "KNC1 TV-Station S, revision 0x1894, doesn't > tune", were related to the PCI-slots of the motherboard I used > rebuilt the machine around a new motherboard, both KNC1's are now recognized > and able to tune > lesson learnt : check the hardware before complaining about the software ... > > next step is accessing the scrambled signals > > as I said, the cards scan OK and using "szap" I can tune to them : > [EMAIL PROTECTED]:~> szap -a 1 -c channels.conf VT4 > reading channels from file 'channels.conf' > zapping to 795 'VT4': > sat 0, frequency = 12669 MHz V, symbolrate 2200, vpid = 0x03af, apid = > 0x039b sid = 0x31e5 > using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' > status 05 | signal 9ffb | snr 21f6 | ber ea08 | unc | > status 1f | signal d430 | snr dad3 | ber 0100 | unc | FE_HAS_LOCK > status 1f | signal d47e | snr dab5 | ber | unc | FE_HAS_LOCK > status 1f | signal d5b8 | snr dacd | ber | unc | FE_HAS_LOCK > status 1f | signal d458 | snr dac7 | ber | unc | FE_HAS_LOCK > status 1f | signal d5bc | snr daf7 | ber | unc | FE_HAS_LOCK > status 1f | signal d460 | snr da9a | ber | unc | FE_HAS_LOCK > status 1f | signal d47c | snr daac | ber | unc | FE_HAS_LOCK > status 1f | signal d46c | snr dac1 | ber | unc | FE_HAS_LOCK > status 1f | signal d465 | snr dabe | ber | unc | FE_HAS_LOCK > status 1f | signal d481 | snr dabb | ber | unc | FE_HAS_LOCK > status 1f | signal d46f | snr dab5 | ber | unc | FE_HAS_LOCK > status 1f | signal d43b | snr daa0 | ber | unc | FE_HAS_LOCK > status 1f | signal d468 | snr dabe | ber | unc | FE_HAS_LOCK > status 1f | signal d47e | snr daa6 | ber | unc | FE_HAS_LOCK > status 1f | signal d342 | snr dac1 | ber | unc | FE_HAS_LOCK > > [EMAIL PROTECTED]:~> szap -a 1 -c channels.conf VTM > reading channels from file 'channels.conf' > zapping to 793 'VTM': > sat 0, frequency = 12669 MHz V, symbolrate 2200, vpid = 0x03ad, apid = > 0x0399 sid = 0x31e3 > using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0' > status 1f | signal d404 | snr b772 | ber c000 | unc | FE_HAS_LOCK > status 1f | signal d479 | snr da8b | ber | unc | FE_HAS_LOCK > status 1f | signal d5b7 | snr daac | ber | unc | FE_HAS_LOCK > status 1f | signal d5b6 | snr da97 | ber | unc | FE_HAS_LOCK > status 1f | signal d47c | snr daa0 | ber | unc | FE_HAS_LOCK > status 1f | signal d5bb | snr da70 | ber | unc | FE_HAS_LOCK > status 1f | signal d342 | snr da97 | ber | unc | FE_HAS_LOCK > status 1f | signal d480 | snr daa6 | ber | unc | FE_HAS_LOCK > status 1f | signal d340 | snr da97 | ber | unc | FE_HAS_LOCK > status 1f | signal d481 | snr da40 | ber | unc | FE_HAS_LOCK > status 1f | signal d47e | snr da6a | ber | unc | FE_HAS_LOCK > status 1f | signal d340 | snr da6d | ber | unc | FE_HAS_LOCK > status 1f | signal d468 | snr da91 | ber | unc | FE_HAS_LOCK > > both VTM and VT4 are encrypted channels here, so no mpg-output at this time > > I have found one (1) encrypted channel that works using gnutv : > > [EMAIL PROTECTED]:~> gnutv -adapter 1 -channels channels.conf -out dvr VTM > Using frontend "ST STV0299 DVB-S", type DVB-S > status SCVYL | signal d47c | snr dac1 | ber ff00 | unc | > FE_HAS_LOCK > CAM Application type: 01 > CAM Application manufacturer: 0100 > CAM Manufacturer code: > CAM Menu string: CANALDIGITAAL > CAM supports the following ca system ids: > 0x0100 > Received new PMT - sending to CAM... > [EMAIL PROTECTED]:~> > > using mplayer, I have a clear picture > this proves to me that descrambling works > > but I have yet to find another channel that works, even on the same > transponder frequency none of the others work !? > > what's more, it looks like it's the CAM that's the cause of things : > > first, remove the CAM from the CI slot : > > [EMAIL PROTECTED]:~> gnutv -adapter 1 -channels channels.conf -out dvr VT4 > Using frontend "ST STV0299 DVB-S", type DVB-S > status SCVYL | signal d464 | snr da9a | ber a700 | unc | > FE_HAS_LOCK > > the lock is immediate > > insert the CAM, same command : > > [EMAIL PROTECTED]:~> gnutv -adapter 1 -channels channels.conf -out dvr VT4 > Using frontend "ST STV0299 DVB-S", type DVB-S > CAM Application type: 0140 | snr 83c1 | ber ff00 | unc | > CAM Application manufacturer: 0100 > CAM Manufacturer code: > CAM Menu string: CANALDIGITAAL > CAM supports the following ca system ids:e
Re: [linux-dvb] BBC Freesat in the UK and DVB-S2
On 11/03/2007 09:33 PM, Torgeir Veimo wrote: > > On 3 Nov 2007, at 20:18, P. van Gaans wrote: > >> BBC/ITV Freesat is DVB-S. BBC HD is also still available in DVB-S, but >> it's possible BBC HD will move to a DVB-S2 transponder in the future. >> It's hard to say if (or more likely: when) that will happen. BBC HD is >> h.264. >> >> Channel 4 and Five are still encrypted in Videoguard. Channel 4 will >> most likely go FTA soon, the future of Five is unclear. I think it's >> best to pick up those channels from DVB-T for now. > > > Do you know if the bitrate for similar channels on Freesat is higher > than it is on Freeview? > > > --Torgeir Veimo > [EMAIL PROTECTED] > > > Let's see if I can compare them.. The closest UK DVB-T transmitter is located in London, Crystal Palace, just over 300 kilometers away from my house. That's going to be a problem. P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] BBC Freesat in the UK and DVB-S2
On 11/03/2007 03:37 PM, Nicolas Will wrote: > Hello all, > > Now that my DVB-T setup is mostly clean and stable, it is probably time > to introduce some new stuff ;o) > > I really have 3 questions. > > In DVB-S in general, can I have one receiving card and 2 LNBs with a > DiSEqC switch (2 dishes on 2 different satellites)? > > Is the BBC Freesat in UK in DVB-S or in DVB-S2, especially regarding > eventual HD content? > > I think the PCI DVB-S cards are mostly well supported. It appears that > DVB-S2 is still up in the aire regarding Linux support. Any special > recommendations for PCI hardware? > > Thanks for your help and pointers. > > Nico > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > BBC/ITV Freesat is DVB-S. BBC HD is also still available in DVB-S, but it's possible BBC HD will move to a DVB-S2 transponder in the future. It's hard to say if (or more likely: when) that will happen. BBC HD is h.264. Channel 4 and Five are still encrypted in Videoguard. Channel 4 will most likely go FTA soon, the future of Five is unclear. I think it's best to pick up those channels from DVB-T for now. "In DVB-S in general, can I have one receiving card and 2 LNBs with a DiSEqC switch (2 dishes on 2 different satellites)?" Yes. For recommendations: I would prefer the Technotrend S-1500. The board design is a bit better compared to the KNC1, the CI cable can be replaced when broken (standard SCSI cable where KNC1 uses something I've never seen before) and it has a remote control. If you're going to use a CAM, stay away from Twinhan. If you just want some FTA-card, I'm not sure which one would be best. You could obviously save some money by not taking a CI if you're not planning on using a CAM anyway. For DVB-S2, Technotrend S2-3200 seems the safest choice, but AFAIK it doesn't run as smooth on Linux as, say, the S-1500. P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-C Plus CI/CAM not working
On 11/03/2007 05:10 PM, Rutger ter Borg wrote: > Dear Linux DVB developers, > > Last week I've purchased a KNC One TV-Station DVB-C Plus, including a > CineView and Alphacrypt CAM module. Unfortunately, I haven't been able to > get the decryption working. I've searched this list (and Google) for > solutions, have found similar reports, however none of the proposed fixes > helped. > > I have tried combinations of the following: > * (debian-) kernels 2.6.22-2, and 2.6.23-1 (latest) > * different PCI slots (to change the assigned IRQ) > * refitting the cable > > The following was successful: > * Tuning to channels using czap > > The following doesn't work: > * Enabling the CAM > > The system keeps looping over inserted/ejected messages if the CAM is > inserted: > > Nov 3 16:06:04 fraggle kernel: ACPI: PCI interrupt for device :00:08.0 > disabled > Nov 3 16:13:56 fraggle kernel: Linux video capture interface: v2.00 > Nov 3 16:13:56 fraggle kernel: saa7146: register extension 'budget_av'. > Nov 3 16:13:56 fraggle kernel: ACPI: PCI Interrupt :00:08.0[A] -> GSI > 19 (level, low) -> IRQ 19 > Nov 3 16:13:56 fraggle kernel: saa7146: found saa7146 @ mem > c21fce00 (revision 1, irq 19) (0x1894,0x0023). > Nov 3 16:13:56 fraggle kernel: saa7146 (0): dma buffer size 192512 > Nov 3 16:13:56 fraggle kernel: DVB: registering new adapter (KNC1 DVB-C > Plus MK3) > Nov 3 16:13:56 fraggle kernel: adapter failed MAC signature check > Nov 3 16:13:56 fraggle kernel: encoded MAC from EEPROM was > ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff:ff > Nov 3 16:13:56 fraggle kernel: saa7146_vv: saa7146 (0): registered device > video0 [v4l2] > Nov 3 16:13:56 fraggle kernel: KNC1-0: MAC addr = 00:09:d6:6d:88:7b > Nov 3 16:13:56 fraggle kernel: DVB: registering frontend 0 (Philips > TDA10023 DVB-C)... > Nov 3 16:13:56 fraggle kernel: budget-av: ci interface initialised. > Nov 3 16:13:56 fraggle kernel: budget-av: cam inserted A > Nov 3 16:13:56 fraggle kernel: budget-av: cam ejected 5 > Nov 3 16:14:00 fraggle kernel: budget-av: cam inserted A > Nov 3 16:14:00 fraggle kernel: budget-av: cam ejected 5 > ... > Nov 3 16:14:04 fraggle kernel: budget-av: cam inserted A > Nov 3 16:14:05 fraggle kernel: budget-av: cam ejected 5 > > , and this inserted/ejected loop keeps repeating. The messages stop when the > CAM is removed from the CI module. The system runs in 64 bit mode on an > AMD64. > > Given this, > * Is it more likely to be a driver problem, or a hardware problem? If it is > a driver problem, in which source file should I start looking? > * What cross-checks could I do next to determine the exact problem? > > Thanks in advance, > kind regards, > > Rutger ter Borg > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > I've seen that before. I can't garuantee my solution also works for you, but: check your CI cable (flatcable between your TV-station card and cineview). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT 1500 dvb-c with CI problem
On 10/17/2007 08:53 PM, Erik Badman wrote: > P. van Gaans skrev: >> On 10/17/2007 07:50 PM, Erik Badman wrote: >>> Hi >>> >>> I just bought a Technotrend 1500 dvb-c card with a ci addon and conax >>> cam. >>> >>> I can scan channels with dvbscan and use czap to view unencrypted >>> channels, but when i try to view a encrypted channel it doesnt work. >>> Czap seems to work but when i run mplayer /dev/dev/adapter0/dvr0 nothing >>> is played. I have tried kernel 2.6.23 and 4vl-dvb from cvs. >>> >>> When I try to scan channels in mythtv-setup it hangs at 3%. >>> >>> I tried Windows XP to check if there was a hardwareproblem but there it >>> works just fine. >>> >>> Is there anything I can try to get it to work? Anything information I >>> can provide to help find the error? >>> >>> Thanks, Erik >>> >>> ___ >>> linux-dvb mailing list >>> linux-dvb@linuxtv.org >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>> >> Do you have a ca0 in /dev/dvb/adapter0 (just ls to see the contents)? >> Maybe try Kaffeine? Get the latest v4l-dvb from hg? >> > Yes ca0 exists under /dev/dvb/adapter0. I have tried Kaffeine, > channelsearch works, but viewing channels doesnt work. > You can't even watch unencrypted channels in Kaffeine? If you can watch unencrypted channels, are you sure the encrypted channels are marked as being encrypted? If you start Kaffeine from a terminal, what error messages does Kaffeine output, if any? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT 1500 dvb-c with CI problem
On 10/17/2007 07:50 PM, Erik Badman wrote: > Hi > > I just bought a Technotrend 1500 dvb-c card with a ci addon and conax cam. > > I can scan channels with dvbscan and use czap to view unencrypted > channels, but when i try to view a encrypted channel it doesnt work. > Czap seems to work but when i run mplayer /dev/dev/adapter0/dvr0 nothing > is played. I have tried kernel 2.6.23 and 4vl-dvb from cvs. > > When I try to scan channels in mythtv-setup it hangs at 3%. > > I tried Windows XP to check if there was a hardwareproblem but there it > works just fine. > > Is there anything I can try to get it to work? Anything information I > can provide to help find the error? > > Thanks, Erik > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Do you have a ca0 in /dev/dvb/adapter0 (just ls to see the contents)? Maybe try Kaffeine? Get the latest v4l-dvb from hg? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Common interface on Technotrend S-1500 broken in v4l-dvb?
On 10/14/2007 07:54 PM, Oliver Endriss wrote:
> Oliver Endriss wrote:
>> P. van Gaans wrote:
>>> On 10/14/2007 12:11 AM, Oliver Endriss wrote:
>>>> P. van Gaans wrote:
>>>>> Today I was testing some stuff and downloaded and installed the newest
>>>>> v4l-dvb from hg. After a while I figured out that FTA channels on my TT
>>>>> S-1500 still worked, but the CAM would not respond. I checked all
>>>>> connections, re-inserted the CAM, reboot the computer but nothing would
>>>>> help. My CI daughterboard version is 1.1 and I bought this S-1500 end of
>>>>> august 2007. I use Ubuntu 7.04 with kernel 2.6.20-16-generic.
>>>>>
>>>>> After installing a somewhat older version of v4l-dvb I luckily had left
>>>>> on my harddisk, the common interface directly came back to life.
>>>> Could you please try to find out which changeset broke the code?
>>>>
>>>> If you have a current HG checkout, you can update the driver to a given
>>>> version using 'hg update '.
>>>>
>>>>> Maybe I just did something wrong somewhere, but would it be possible
>>>>> some big change was made to the way the S-1500 handles the CI that could
>>>>> have broken it?
>>>> It's probably a change in budget-ci.c or dvb_ca_en50221.c
>>>>
>>>> Just an educated guess:
>>>> Did http://linuxtv.org/hg/v4l-dvb/rev/b0a3a9b43d60
>>>> break the code? -> 'hg update 6279'
>>>>
>>>> CU
>>>> Oliver
>>>>
>>> 6279 does not compile.
>>>
>>> make -C /home/wn/v4l-dvb/v4l
>>> make[1]: Entering directory `/home/wn/v4l-dvb/v4l'
>>> perl scripts/make_config_compat.pl /lib/modules/2.6.20-16-generic/source
>>> ./.myconfig ./config-compat.h
>>> File not found:
>>> /lib/modules/2.6.20-16-generic/source/include/linux/netdevice.h at
>>> scripts/make_config_compat.pl line 15.
>>> make[1]: *** [config-compat.h] Error 2
>>> make[1]: Leaving directory `/home/wn/v4l-dvb/v4l'
>>> make: *** [all] Error 2
>>>
>>> After trying a bit I figured out 6266 does compile. Everything between
>>> 6279 and 6266 does not. I can tell you that with 6266, the common
>>> interface works, I hope that's enough info.
>> Now I have a confirmation from Marco Schluessler that changeset
>> http://linuxtv.org/hg/v4l-dvb/raw-rev/b0a3a9b43d60
>> broke CI support.
>>
>> For now simply revert this changeset.
>> Save http://linuxtv.org/hg/v4l-dvb/raw-rev/b0a3a9b43d60 to a file.
>> Then use 'patch -p1 -R < file' to revert the changeset.
>
> Marco sent me the attached patch which should fix the problem.
> Please test.
>
> CU
> Oliver
>
>
>
>
>
> - "while (!ca->wakeup)" breaks the CAM initialisation
>
> Signed-off-by: Marco Schluessler <[EMAIL PROTECTED]>
>
> diff -bur
> v4l-dvb-ea93c93f1547_orig/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c
> v4l-dvb-ea93c93f1547/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c
> ---
> v4l-dvb-ea93c93f1547_orig/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c
> 2007-10-14 13:19:25.0 +0200
> +++ v4l-dvb-ea93c93f1547/linux/drivers/media/dvb/dvb-core/dvb_ca_en50221.c
> 2007-10-14 18:37:15.0 +0200
> @@ -973,7 +973,7 @@
> /* main loop */
> while (!kthread_should_stop()) {
> /* sleep for a bit */
> - while (!ca->wakeup) {
> + if (!ca->wakeup) {
> set_current_state(TASK_INTERRUPTIBLE);
> schedule_timeout(ca->delay);
> if (kthread_should_stop())
>
>
>
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
I wanted to test it but just downloaded the latest v4l-dvb and see the
patch is already applied. Common interface works with latest v4l-dvb
(oct 16 2007).
P.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Common interface on Technotrend S-1500 broken in v4l-dvb?
On 10/14/2007 12:11 AM, Oliver Endriss wrote: > P. van Gaans wrote: >> Today I was testing some stuff and downloaded and installed the newest >> v4l-dvb from hg. After a while I figured out that FTA channels on my TT >> S-1500 still worked, but the CAM would not respond. I checked all >> connections, re-inserted the CAM, reboot the computer but nothing would >> help. My CI daughterboard version is 1.1 and I bought this S-1500 end of >> august 2007. I use Ubuntu 7.04 with kernel 2.6.20-16-generic. >> >> After installing a somewhat older version of v4l-dvb I luckily had left >> on my harddisk, the common interface directly came back to life. > > Could you please try to find out which changeset broke the code? > > If you have a current HG checkout, you can update the driver to a given > version using 'hg update '. > >> Maybe I just did something wrong somewhere, but would it be possible >> some big change was made to the way the S-1500 handles the CI that could >> have broken it? > > It's probably a change in budget-ci.c or dvb_ca_en50221.c > > Just an educated guess: > Did http://linuxtv.org/hg/v4l-dvb/rev/b0a3a9b43d60 > break the code? -> 'hg update 6279' > > CU > Oliver > 6279 does not compile. make -C /home/wn/v4l-dvb/v4l make[1]: Entering directory `/home/wn/v4l-dvb/v4l' perl scripts/make_config_compat.pl /lib/modules/2.6.20-16-generic/source ./.myconfig ./config-compat.h File not found: /lib/modules/2.6.20-16-generic/source/include/linux/netdevice.h at scripts/make_config_compat.pl line 15. make[1]: *** [config-compat.h] Error 2 make[1]: Leaving directory `/home/wn/v4l-dvb/v4l' make: *** [all] Error 2 After trying a bit I figured out 6266 does compile. Everything between 6279 and 6266 does not. I can tell you that with 6266, the common interface works, I hope that's enough info. P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Common interface on Technotrend S-1500 broken in v4l-dvb?
Today I was testing some stuff and downloaded and installed the newest v4l-dvb from hg. After a while I figured out that FTA channels on my TT S-1500 still worked, but the CAM would not respond. I checked all connections, re-inserted the CAM, reboot the computer but nothing would help. My CI daughterboard version is 1.1 and I bought this S-1500 end of august 2007. I use Ubuntu 7.04 with kernel 2.6.20-16-generic. After installing a somewhat older version of v4l-dvb I luckily had left on my harddisk, the common interface directly came back to life. Maybe I just did something wrong somewhere, but would it be possible some big change was made to the way the S-1500 handles the CI that could have broken it? P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [UK Specific] Ditch Sky!
On 10/02/2007 02:12 PM, Robert Longbottom wrote: > On Tue, October 2, 2007 12:49 pm, UxBoD wrote: >> Nope, don't have Sky+ and refuse to pay for it; hence looking at a MythTV >> installation. Okay, so I would need to replace my Sky dish with a >> different one that has dual LNBs. I presume that also means running a >> second coax cable aswell ? > > Yes, or just replace the LNB and keep the dish. I'm not sure if you need > a specific "sky" LNB for the sky dish because it isn't round, but I'd have > thought you could pick one up from somewhere (ebay maybe) or try asking in > somewhere like Maplins, I've overheard them giving reasonable advice on > satellite kit in my local branch. > > And yes, you need a second coax from the dish to your reciever. I'm not > sure if its possible to get round this using some kind of disecq switch, > but when I put my dish up, I figured running two wires wasn't much more > difficult than just running one. > > Robert. > >> Regards, >> >> --[ UxBoD ]-- >> // PGP Key: "curl -s https://www.splatnix.net/uxbod.asc | gpg --import" >> // Fingerprint: C759 8F52 1D17 B3C5 5854 36BD 1FB1 B02F 5DB5 687B >> // Keyserver: www.keyserver.net Key-ID: 0x5DB5687B >> // Phone: +44 845 869 2749 SIP Phone: [EMAIL PROTECTED] >> >> - Original Message - >> From: "Robert Longbottom" <[EMAIL PROTECTED]> >> To: linux-dvb@linuxtv.org >> Sent: Tuesday, October 2, 2007 12:43:14 PM (GMT) Europe/London >> Subject: Re: [linux-dvb] [UK Specific] Ditch Sky! >> >> On Tue, October 2, 2007 12:02 pm, UxBoD wrote: >>> Hi, >>> >>> I am looking to cancel our Sky contract and switch to FreeAirSat >>> services >>> ie. Just keep the Sky card but no contract. >>> >>> Have been looking around to find out the best DVB-S card to get, which >>> will also allow a CI too be connected aswell. >>> >>> The Technotrend S-2300 looks pretty good as a full featured card, and >>> has >>> a optional CI which will take two CAMs. This would allow me to have a >>> Setanta subscription for the Rugby etc. >>> >>> I intend to build a MythTV server with possibly two of these cards and >>> split the LNB feed so that I can record and watch different channels at >>> the same time. >> I can't comment on which DVB-S card is best, but I can say that you can't >> just split the LNB feed - you need a dual LNB. If you have Sky+ you >> should already have one of these. >> >> In fact it's slightly more complex than this - you could potentially >> record different channels from the same mux (there are up to 6 channels >> per mux I think), but there is currently no functionality in MythTv that >> allows for this. There is however some work in progess for MythTv that >> allows recording multiple channels from the same mux. >> >>> Will this card work okay with the 2.6 drivers and does my approach sound >>> reasonable ? >> Hope this helps, >> Robert. >> >> >> >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> >> >> -- >> This message has been scanned for viruses and >> dangerous content by MailScanner, and is >> believed to be clean. >> >> >> ___ >> 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 > I believe the Sky LNB (Philips IIRC) is indeed different. A standard LNB will probably work, but not optimal. One option is to replace the whole dish with a standard dish (Triax, Gibertini or other standard dish) so you can put a standard twin or quad LNB on it. For the CAM, the T-rex (or Dragon, pretty much the same as the T-rex) only works when you load firmware from the internet into it with a CAS interface or loadercard (you load the firmware on the loadercard with a Phoenix cardreader first). This firmware can't be downloaded from any "legal" site, you'll need to look in the darker areas of the internet (and I can and will not help you. :p). You can also get the Diablo CAM, same story. You still need to put your Sky card in an official Sky receiver every 4-6 weeks or so, because the T-rex/Diablo does not update the Sky card. There does not exist any CAM that supports the Sky card out of the box, neither does there exist any CAM that is capable of updating the Sky card. I believe some cardservers can update the card, but that's a whole different story. Good luck. I'd say your best option is to get rid of the Sky card and be happy with everything FTA. You may want to consider setting up a UHF antenna so you can get Freeview (if you're anywhere close to a transmitter), on Freeview you can get some channels FTA
Re: [linux-dvb] PowerCAM.Pro and AstonCrypt module
On 09/06/2007 04:21 PM, Guillaume Marçais wrote: > On 9/3/07, P. van Gaans <[EMAIL PROTECTED]> wrote: >> On 09/03/2007 04:57 PM, P. van Gaans wrote: >>> On 09/03/2007 03:58 PM, Guillaume Marçais wrote: >>>> I have a PowerCAM.Pro CAM module, attached to a TechnoTrend budget >>>> S1500, and it does not seem to work with linuxtv. When it is plugged >>>> in, I do not get anything, even scan returns only timeouts. If the >>>> common interface is unplugged, then scan returns over 1400 channels. >>>> So there seem to be some sort of an incompatibility. >>>> >>>> The CAM module that I should have come with the pack I bought is an >>>> AstonCrypt Dual. Does this CAM module work with linuxtv? >>>> >>>> Guillaume. >>>> >>>> OS: XUbuntu Feisty Fawn >>>> Provider: CanalSat >>>> >>>> ___ >>>> linux-dvb mailing list >>>> linux-dvb@linuxtv.org >>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>> >>> Check out http://linuxtv.org/wiki/index.php/TechnoTrend_TT-budget_S-1500 >>> and please update the article with new CAMs as it seems you have at >>> least one. But make sure your card works properly, does it work with the >>> Aston? >>> >>> ___ >>> linux-dvb mailing list >>> linux-dvb@linuxtv.org >>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>> >> Stupid me, forgot to ask.. What does dmesg say when you insert/eject >> your CAM and while it's in it? > > OK, sorry for the noise. Finally, the PowerCAM.Pro works fine. I guess > it was not plugged in properly or something. After taking it out and > putting it back in, it works, with no software modification. I can see > encrypted channels fine with kaffeine. Now if I could get MythTV to > work... But that's another story for another mailing list :) > > I can update the wiki page > http://linuxtv.org/wiki/index.php/TechnoTrend_TT-budget_S-1500. My > concern is I do not know what version of the CI is in the machine and > I do not have physical access to it. Can I tell from the logs/dmesg? > > Guillaume. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Probably not (at least I wouldn't know how). You could add a note about the powerCAM or make a new table for unknown CI versions. Btw, I personally haven't seen any difference in CAM compatibility between 1.0 and 1.1, I doubt there is any. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] PowerCAM.Pro and AstonCrypt module
On 09/03/2007 04:57 PM, P. van Gaans wrote: > On 09/03/2007 03:58 PM, Guillaume Marçais wrote: >> I have a PowerCAM.Pro CAM module, attached to a TechnoTrend budget >> S1500, and it does not seem to work with linuxtv. When it is plugged >> in, I do not get anything, even scan returns only timeouts. If the >> common interface is unplugged, then scan returns over 1400 channels. >> So there seem to be some sort of an incompatibility. >> >> The CAM module that I should have come with the pack I bought is an >> AstonCrypt Dual. Does this CAM module work with linuxtv? >> >> Guillaume. >> >> OS: XUbuntu Feisty Fawn >> Provider: CanalSat >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > > Check out http://linuxtv.org/wiki/index.php/TechnoTrend_TT-budget_S-1500 > and please update the article with new CAMs as it seems you have at > least one. But make sure your card works properly, does it work with the > Aston? > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Stupid me, forgot to ask.. What does dmesg say when you insert/eject your CAM and while it's in it? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] PowerCAM.Pro and AstonCrypt module
On 09/03/2007 03:58 PM, Guillaume Marçais wrote: > I have a PowerCAM.Pro CAM module, attached to a TechnoTrend budget > S1500, and it does not seem to work with linuxtv. When it is plugged > in, I do not get anything, even scan returns only timeouts. If the > common interface is unplugged, then scan returns over 1400 channels. > So there seem to be some sort of an incompatibility. > > The CAM module that I should have come with the pack I bought is an > AstonCrypt Dual. Does this CAM module work with linuxtv? > > Guillaume. > > OS: XUbuntu Feisty Fawn > Provider: CanalSat > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Check out http://linuxtv.org/wiki/index.php/TechnoTrend_TT-budget_S-1500 and please update the article with new CAMs as it seems you have at least one. But make sure your card works properly, does it work with the Aston? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] free channels not working on mux with crypted channels
On 08/30/2007 08:29 PM, Petri Jarvisalo wrote: > I never could imagine what a difference swapping pci slot would make. > Had to swap 2 times, 1st time it gave still some errors and last time fully > clear picture. > > Thanks to all, everything works now! > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Still you should check all the other channels you can receive. I had a similar problem, and although the problems on one channel were solved after swapping, problems started appearing on another channel after the swap. But you could be lucky, but I suggest checking it. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] free channels not working on mux with crypted channels
On 08/29/2007 02:35 PM, P. van Gaans wrote: > On 08/29/2007 02:20 PM, Petri Jarvisalo wrote: >> Ok, this far i know. >> >> 1: >> I asked on #kaffeine, when ever the problem is software based. >>- Wasn't. >> 2: >> I also had a chat on #linuxtv: >> - not problem with bad signal or cabling >> I also compiled latest v4l from snapshot. >> final statment: mailing list time. >> >> Card is Hauppauge DVB-C ver 2.1 (wintv?) with saa7146_vv (latest snapshot) >> So problem is what topic says, everything else works like a dream. >> >> not working (free) channel: >> [EMAIL PROTECTED]:~$ czap -c channels.conf MTV3 >> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' >> 10 MTV3:41800:INVERSION_AUTO:690:FEC_NONE:QAM_128:305:561:49 >> 10 MTV3: f 41800, s 690, i 2, fec 0, qam 4, v 0x131, a 0x231 >> status 00 | signal 7f7f | snr | ber 001517c4 | unc 0038 | >> status 1f | signal f0f0 | snr ebeb | ber 001517c4 | unc | >> FE_HAS_LOCK >> status 1f | signal | snr eaea | ber 001517c4 | unc | >> FE_HAS_LOCK >> status 1f | signal | snr eaea | ber 000d7b72 | unc | >> FE_HAS_LOCK >> >> encrypted channel (from same mux): >> [EMAIL PROTECTED]:~$ czap -c channels.conf "Subtv Juniori" >> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' >> 18 Subtv >> Juniori:41800:INVERSION_AUTO:690:FEC_NONE:QAM_128:517:610:257 >> 18 Subtv Juniori: f 41800, s 690, i 2, fec 0, qam 4, v 0x205, a >> 0x262 >> status 00 | signal 3e3e | snr | ber 037a | unc | >> status 1f | signal f7f7 | snr e3e3 | ber 037a | unc | >> FE_HAS_LOCK >> status 1f | signal | snr eaea | ber 037a | unc | >> FE_HAS_LOCK >> status 1f | signal | snr eaea | ber 000c0cce | unc | >> FE_HAS_LOCK >> >> working channel: >> [EMAIL PROTECTED]:~$ czap -c channels.conf "YLE TV1" >> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' >> 21 YLE TV1:16200:INVERSION_AUTO:690:FEC_NONE:QAM_128:512:650:17 >> 21 YLE TV1: f 16200, s 690, i 2, fec 0, qam 4, v 0x200, a 0x28a >> status 00 | signal 7878 | snr | ber 00054dbc | unc 007c | >> status 1f | signal f3f3 | snr ebeb | ber 00054dbc | unc | >> FE_HAS_LOCK >> status 1f | signal | snr ecec | ber 00054dbc | unc | >> FE_HAS_LOCK >> status 1f | signal | snr ecec | ber 0006c49e | unc | >> FE_HAS_LOCK >> status 1f | signal | snr ecec | ber 0006c49e | unc | >> FE_HAS_LOCK >> >> stream example on problematic channel, recorded from kaffeine: >> http://purkki.zapto.org/temp/%20Uutiset.m2t (patience it's only 512 adsl) >> >> Those problematic channels works fine on hardware digibox on same appartment. >> >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > > I notice the working channel is in the VHF range and the non-working in > the UHF-range. > > Did you try another PCI slot? > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Excuse me, both are in the VHF range. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] free channels not working on mux with crypted channels
On 08/29/2007 02:20 PM, Petri Jarvisalo wrote: > Ok, this far i know. > > 1: > I asked on #kaffeine, when ever the problem is software based. >- Wasn't. > 2: > I also had a chat on #linuxtv: > - not problem with bad signal or cabling > I also compiled latest v4l from snapshot. > final statment: mailing list time. > > Card is Hauppauge DVB-C ver 2.1 (wintv?) with saa7146_vv (latest snapshot) > So problem is what topic says, everything else works like a dream. > > not working (free) channel: > [EMAIL PROTECTED]:~$ czap -c channels.conf MTV3 > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > 10 MTV3:41800:INVERSION_AUTO:690:FEC_NONE:QAM_128:305:561:49 > 10 MTV3: f 41800, s 690, i 2, fec 0, qam 4, v 0x131, a 0x231 > status 00 | signal 7f7f | snr | ber 001517c4 | unc 0038 | > status 1f | signal f0f0 | snr ebeb | ber 001517c4 | unc | > FE_HAS_LOCK > status 1f | signal | snr eaea | ber 001517c4 | unc | > FE_HAS_LOCK > status 1f | signal | snr eaea | ber 000d7b72 | unc | > FE_HAS_LOCK > > encrypted channel (from same mux): > [EMAIL PROTECTED]:~$ czap -c channels.conf "Subtv Juniori" > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > 18 Subtv > Juniori:41800:INVERSION_AUTO:690:FEC_NONE:QAM_128:517:610:257 > 18 Subtv Juniori: f 41800, s 690, i 2, fec 0, qam 4, v 0x205, a > 0x262 > status 00 | signal 3e3e | snr | ber 037a | unc | > status 1f | signal f7f7 | snr e3e3 | ber 037a | unc | > FE_HAS_LOCK > status 1f | signal | snr eaea | ber 037a | unc | > FE_HAS_LOCK > status 1f | signal | snr eaea | ber 000c0cce | unc | > FE_HAS_LOCK > > working channel: > [EMAIL PROTECTED]:~$ czap -c channels.conf "YLE TV1" > using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0' > 21 YLE TV1:16200:INVERSION_AUTO:690:FEC_NONE:QAM_128:512:650:17 > 21 YLE TV1: f 16200, s 690, i 2, fec 0, qam 4, v 0x200, a 0x28a > status 00 | signal 7878 | snr | ber 00054dbc | unc 007c | > status 1f | signal f3f3 | snr ebeb | ber 00054dbc | unc | > FE_HAS_LOCK > status 1f | signal | snr ecec | ber 00054dbc | unc | > FE_HAS_LOCK > status 1f | signal | snr ecec | ber 0006c49e | unc | > FE_HAS_LOCK > status 1f | signal | snr ecec | ber 0006c49e | unc | > FE_HAS_LOCK > > stream example on problematic channel, recorded from kaffeine: > http://purkki.zapto.org/temp/%20Uutiset.m2t (patience it's only 512 adsl) > > Those problematic channels works fine on hardware digibox on same appartment. > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > I notice the working channel is in the VHF range and the non-working in the UHF-range. Did you try another PCI slot? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend S-1500 with CI: common interface is not detected
On 04/06/2007 09:09 PM, Will Tatam wrote: > I had similar issues with this board until i used the current > development tree of linux-dvb rather than a stock kernel. I could then > get apps like Myth to see I had a cam, but I never worked out know to > setup my dragon cam properly to work with my legal viewing card > > Will Tatam > > P. van Gaans wrote: >> I'll try to keep it short. I've got a TT S-1500 and the CAM can not be >> seen in /dev/dvb/adapter. It doesn't work either, no encrypted channel >> lights up. FTA channels do. However, on my KNC1 DVB-C with Cineview, >> there is a "ca0" in /dev/dvb/adapter and in Kaffeine I can watch >> encrypted channels. In dmesg I see info for the KNC1 card when >> ejecting/inserting CAMs, not a single line with info about the CI on the >> TT. >> >> I don't see in what other way I could possibly connect the TT budget CI >> to the card (the hardware). The CAM is not upside-down. The CAM was >> tested in another receiver and works. I have the latest v4l-dvb drivers. >> Ubuntu 6.10 Edgy. >> >> Any help is appreciated. >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Late reply, but I figured it out. The cable is OK. The v4l-dvb code is OK. The CI daughterboard is OK. I replaced the S-1500 card itself with a spankin' new S-1500 and the problems were gone. So my first Technotrend S-1500 is broken, at least it's CI-connector. I felt I should post the solution now that I solved it. And by the way, made a big update to the CAM tests at http://linuxtv.org/wiki/index.php/TechnoTrend_TT-budget_S-1500 ;). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Problem using mplayer.
On 08/28/2007 04:47 AM, kevin liu wrote: > Dear Nicola > Mplayer can give a perfect HDTV effects, but after a period of > time, it gives such complaints: > "" > Too many video packets in the buffer: (148 in 8421326 bytes). > Maybe you are playing a non-interleaved stream/file or the codec failed? > For AVI files, try to force non-interleaved mode with the -ni option. > A:69414.9 V:69410.6 A-V: 4.281 ct: 8.984 14445/14445 44% 0% 3.6% 130 0 > Too many video packets in the buffer: (148 in 8402931 bytes). > Maybe you are playing a non-interleaved stream/file or the codec failed? > For AVI files, try to force non-interleaved mode with the -ni option. > "" > What's the problem? > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Your system is probably too slow. If the video looks smooth, try running mplayer with the -framedrop option. What CPU do you have and are you trying to watch MPEG2 of MPEG4 AVC? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB Hardware question
On 08/23/2007 12:26 PM, Sid Boyce wrote: > Yesterday I was asked a question about DVB cards, "Are there different > cards needed for PAL and NTSC?", my friend wanted to know if he bought a > PC with a DVB card in the UK (PAL-I), whether the card would work in the > USA (NTSC). > I told him a different tuner is needed. Am I correct or is it dependent > on the manufacturer? What about DVB-S cards, would they be dependent on > the transponder frequencies of available satellites? > Suggested cards and any pertinent info. > Thanks and Regards > Sid. NTSC or PAL doesn't matter. Any DVB-T/S/C card from Europe can perfectly show PAL, NTSC, HDTV (MPEG2/h.264) or pretty much any other format as long as an (MPEG) decoder for the given format is available. In case of analog TV cards, most TV cards today support PAL, NTSC and SECAM all in one card. These can be used worldwide. The DVB-T/S/C cards will often not work in the USA. Not because of PAL/NTSC, but because the USA often uses ATSC. Check up with your local provider to find out if they use DVB or ATSC. I don't mind helping you, I only wonder why you post this to this list, because what does this have to do with Linux.. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] DVB-T Full Spectrum Frequencies Scan
On 08/22/2007 04:57 PM, Frederic CAND wrote: > Hi everyone, > > I'm having some troubles trying to perform a dvb-t frequencies scan > without a scan file. > Does anyone know if a software (or even an algorithm i could write in C) > exist to do so ? > My idea was to scan frequencies using all combinations of DTT > parameters. This is a first problem because it makes a lot of > possibilities. The second problem is that I don't know on which > frequency I should start my scanning, nor the step to use between to > frequencies. > > I thought to parse the Terrestrial Delivery System descriptor in the > NIT, but it appears that some countries do not fill correctly this > descriptor (particularly the "Frequency" field). So it's useless. > > I'm looking for a universal method that do not need a scan file to be > specified to automate everything. As STBs can do that i though that we > could do that programatically. > > If anyone has a clue, please help :'( > > Some time ago I made an "all-UHF" scanfile, but it was rejected because of the autoscan feature available with some DVB-T cards. However, far from all DVB-T cards support autoscan, and in that case you simply need all-UHF. But it was rejected anyway, because every card *should* support autoscan. But they don't. So you have a problem. Well anyway. If you want all-UHF, just ask and I'll look it up and send it to you. all-UHF only scans channel 21-69, it does not scan frequencies in between like channel 21,5 (21,5 would be 478Mhz). But in most countries such frequencies are not used anyway. For guard interval and other settings it uses "auto", supported by every card that I've tried. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 SNR goes/went bad
On 08/13/2007 10:31 PM, Manu Abraham wrote: > On 8/14/07, P. van Gaans <[EMAIL PROTECTED]> wrote: >> On 08/13/2007 09:55 PM, Manu Abraham wrote: >>>>> Can you describe the problem that you face ? other than low SNR ? ie >>>>> have you checked whether your cables are okay, Dish is aligned proper >>>>> etc etc ? It will help to avoid a lot of frustration later. :) >>>>> >>>>> >>>>> Manu >>>>> >>>> That's great! >>>> >>>> The problems I face: I have a lot of BER, measured with femon -h (with >>>> my patch applied for decimal readings). The sky is clear. Visiosat Bisat >>>> G3C dish. >>>> >>>> On ZDF on Astra 19,2 east (Astra 1), I see nothing (and I mean >>>> _nothing_) but green and purple blocks and loud aliens in my speakers >>>> constantly. BER is into 65000. >>>> >>>> On Omroep Brabant on Astra 1D at 23,5 east, I see some bits from the >>>> image but constantly lots of complete stripes with corrupted MPEG, and >>>> the audio is also bad. So this stream is also corrupt. BER into 65000. >>>> >>>> Now ZDF is one of the weakest transponders on 19,2 east and Astra 1D is >>>> old so doesn't perform optimal either. But this is not normal. >>>> >>>> On BBC One/Two/Three/Four on Astra 2D, and that beam is strong in my >>>> location, the picture is good most of the time, but once approx every >>>> minute a small visible corruption passes by. Just as long as it does >>>> _not_ start to rain, I can follow the program. BER into 65000. >>> >>> I understood your problem. >>> >>>> On the Dutch channels on Astra 1 at 19,2 east again, like Nederland 1 at >>>> 12515.25 H (Astra 1G) or RTL 5 at 12343.50 H (Astra 1H) the picture is >>>> perfect, and BER hoovers and shows 0, 256 or 512 (which is low). >>>> >>>> There are also values in between. n-tv on Astra 1 at 19,2 east shows >>>> around 17000-18000. Perfect picture. >>>> >>>> But.. When it starts to rain, the whole party is over. >>> >>> During rain, don't expect anything much with DVB-S >> With just a little normal rain, DVB-S should work fine. Only when >> there's hard rain and it's seriously cloudy you could expect the picture >> to actually fail with a properly set up dish. Overall DVB-S is very >> reliable. DVB-S is also used as a feed for many cable channels in The >> Netherlands, and they hardly ever fail. >> > > > By rain i meant, by the rain we have here, we don't receive any DVB-S. > Don't know how many cms of rain .. I don't know where you live. In The Netherlands, with a 64cm dish (which I have), only in heavy storm the signal isn't strong enough. Occasional rain is no problem here. > > >>>> So that's my problem. When I swap the KNC1 for my Technotrend S-1500, >>>> all the channels work, including ZDF, perfectly, and the BER is zero >>>> everywhere, even ZDF works with zero BER. There are many other channels >>>> that do not work but I couldn't possibly list them all, I don't think >>>> that would make sense anyway. And sure, there could be a little >>>> difference in tuner quality and stuff in favor of the Technotrend, but I >>>> really don't believe it would be that big for cards from the same price >>>> range. And it's not like Philips is a bad or cheap brand either. >>> >>> Though i am not saying it is bad, devices designed improperly leads to >>> bad results. However good the components are. We have examples, but >>> not stating that is the case here, but a possibility. >> Yes, that's true. >> >>> >>>> I'm actually not sure the SNR number in femon is low, I was really >>>> talking about Signal to Noise ratio - with all that corruption and >>>> horrible performance it has to be bad. >>>> >>>> On Windows, I can watch ZDF with the KNC1, but I see some "error" level >>>> in the Windows software, that "error" most likely means BER. But it's >>>> not much. Last time I checked anyway, it's been a while since I've seen >>>> Windows. >>> >>> If this is an overall problem that you see, then it has nothing to do >>> with the drivers. I thought in your case, the driver was misbehaving >> It's not an ove
Re: [linux-dvb] KNC1 SNR goes/went bad
On 08/13/2007 09:55 PM, Manu Abraham wrote: >>> Can you describe the problem that you face ? other than low SNR ? ie >>> have you checked whether your cables are okay, Dish is aligned proper >>> etc etc ? It will help to avoid a lot of frustration later. :) >>> >>> >>> Manu >>> >> That's great! >> >> The problems I face: I have a lot of BER, measured with femon -h (with >> my patch applied for decimal readings). The sky is clear. Visiosat Bisat >> G3C dish. >> >> On ZDF on Astra 19,2 east (Astra 1), I see nothing (and I mean >> _nothing_) but green and purple blocks and loud aliens in my speakers >> constantly. BER is into 65000. >> >> On Omroep Brabant on Astra 1D at 23,5 east, I see some bits from the >> image but constantly lots of complete stripes with corrupted MPEG, and >> the audio is also bad. So this stream is also corrupt. BER into 65000. >> >> Now ZDF is one of the weakest transponders on 19,2 east and Astra 1D is >> old so doesn't perform optimal either. But this is not normal. >> >> On BBC One/Two/Three/Four on Astra 2D, and that beam is strong in my >> location, the picture is good most of the time, but once approx every >> minute a small visible corruption passes by. Just as long as it does >> _not_ start to rain, I can follow the program. BER into 65000. > > > I understood your problem. > >> On the Dutch channels on Astra 1 at 19,2 east again, like Nederland 1 at >> 12515.25 H (Astra 1G) or RTL 5 at 12343.50 H (Astra 1H) the picture is >> perfect, and BER hoovers and shows 0, 256 or 512 (which is low). >> >> There are also values in between. n-tv on Astra 1 at 19,2 east shows >> around 17000-18000. Perfect picture. >> >> But.. When it starts to rain, the whole party is over. > > > During rain, don't expect anything much with DVB-S With just a little normal rain, DVB-S should work fine. Only when there's hard rain and it's seriously cloudy you could expect the picture to actually fail with a properly set up dish. Overall DVB-S is very reliable. DVB-S is also used as a feed for many cable channels in The Netherlands, and they hardly ever fail. > > >> So that's my problem. When I swap the KNC1 for my Technotrend S-1500, >> all the channels work, including ZDF, perfectly, and the BER is zero >> everywhere, even ZDF works with zero BER. There are many other channels >> that do not work but I couldn't possibly list them all, I don't think >> that would make sense anyway. And sure, there could be a little >> difference in tuner quality and stuff in favor of the Technotrend, but I >> really don't believe it would be that big for cards from the same price >> range. And it's not like Philips is a bad or cheap brand either. > > > Though i am not saying it is bad, devices designed improperly leads to > bad results. However good the components are. We have examples, but > not stating that is the case here, but a possibility. Yes, that's true. > > >> I'm actually not sure the SNR number in femon is low, I was really >> talking about Signal to Noise ratio - with all that corruption and >> horrible performance it has to be bad. >> >> On Windows, I can watch ZDF with the KNC1, but I see some "error" level >> in the Windows software, that "error" most likely means BER. But it's >> not much. Last time I checked anyway, it's been a while since I've seen >> Windows. > > > If this is an overall problem that you see, then it has nothing to do > with the drivers. I thought in your case, the driver was misbehaving It's not an overall problem, I only have this problem with the KNC1 card. > > The TT card you have behaves similarly ? The TT card performs fine, I still have to test it in somewhat harder rain, but the fact it shows ZDF perfectly without even BER is a huge difference. I also have a Vantage standalone receiver. I did test that one in rain, and ZDF would just keep going. > >> The problem seems to be getting worse, because some days/weeks ago I >> believe I had zero BER at the Dutch channels, and now it's around >> 256-512. But the weather, temperature and other stuff also varies, so >> it's always hard to say. > > > Maybe it has something to do with your dish alignment, LNB alignment > etc ? A LNB skew can cause a lot of errors to happen, eventhough the > dish is aligned correctly. > Trust me, I know stuff about alignment. I have re-aligned the dish 5 or 6 or more times and _every_ time the result did not fully satisfy me. I changed the height of the dish, how deep the LNB was into the holder, the skew, tried moving the LNB holder up and down (possible on my dish), I tried everything. Even swapped the LNB's, but that made no difference either. The last couple of times, I took my laptop up on the roof so I could VNC to my desktop and see the signal/BER instead of using the cheap satbeeper. Then I swapped the card for the Technotrend, and checked the status... Hey... No signal trouble? But OK.. The Common Interface on the S-1500 is totally not detected, dmesg
Re: [linux-dvb] TT S2-3200 stable, CI, go or no-go?
On 08/12/2007 11:02 AM, Manu Abraham wrote: > On 8/12/07, P. van Gaans <[EMAIL PROTECTED]> wrote: >> I know there have been some posts about the card - but I didn't see the >> questions asked I have. >> >> [story you can skip] >> The problem is this: currently I have a KNC1 DVB-S card + cineview CI. >> But it's breaking down, SNR appears to get worse by the day. Bad luck :'( > > > Can you please get your hardware details of this card you mention ? > Like which tuner, which PLL, which demod etc. The more detailed, the > better. Should I read out some of those specifications in software (if so, what software) or should I just get the card out and tell you all the numbers and stuff on it? It's not going that fast, but over the last weeks, reception really seems to be getting a little worse - and it's not the dish. Reception on Windows is much better, but still not what it should be. I don't know if the reception is going backwards on Windows as well (it's been a while since I opened the Windows). > > >> I also have a TT S-1500 with budget CI. I would use that, but the CI >> doesn't work for no reason! Bad luck again :'( > > > AFAIK, There is an experimental patch floating around which "seems to" > fix this issue. > Please test the patch and get back whether it fixes. you can search in > the archives for the S 1500 thread. Some people have reported > success. But that is just not enough to pull it in, since applying > that, could probably break others -- We need more testers, who get > back with valid results. I've found different patches. I tried the most recent, posted by Simon Baxter on 29/07/2007 01:06 AM, it would be written by Mark Anderson. When trying to patch, I see this: patching file drivers/media/dvb/dvb-core/dvb_ca_en50221.c Hunk #1 FAILED at 721. Hunk #2 FAILED at 757. 2 out of 2 hunks FAILED -- saving rejects to file drivers/media/dvb/dvb-core/dvb_ca_en50221.c.rej patching file drivers/media/common/saa7146_i2c.c Hunk #1 FAILED at 179. Hunk #2 FAILED at 195. Hunk #3 FAILED at 207. Hunk #4 FAILED at 250. 4 out of 4 hunks FAILED -- saving rejects to file drivers/media/common/saa7146_i2c.c.rej Do I have to try to apply them by hand? In cases like this, I prefer a complete file.. Thing is: the system really does not see the CI. dmesg says absolutely nothing, like the CI isn't there at all. No error, just totally nothing. I can physically disconnect the CI and report back exactly the same results. There is no ca0. > > >> I've got a Phoenix reader, I know someone will be going to suggest that >> - so I would put my smartcard in that - the Phoenix is OK, but it >> refuses to init the satellite smartcard (another smartcard for cable did >> work but that's worthless for me!) - how much bad luck can I have? >> [/story you can skip] >> >> So I have to buy a new card, and I feel it would be a waste to buy >> another DVB-S1 card nowadays. S2 cards are not really expensive anymore. >> >> So I would be perfectly happy with a TT S2-3200 that only works on >> DVB-S1 (stable!) for the moment and with a working CI. I can perfectly >> live with DVB-S2 support in the drivers being added at a later stage. >> > > > I guess by here, you would be pretty frustrated. Hardware > configuration as days pass by gets more and more complicated, not > simpler. Gone are the days of the simple hardware. > > Users need to have some amount of patience. The developers do this > mostly out of their free time. It is not that very simple to get > devices working properly. Users pressurizing the developers to release > early, brings in those half baked drivers, so a certain percentage of > the attributes go to the users as well. > > It is not easy, when a user comes with a patch for something stating, > well this fixes issue "x" whereas in reality the patch has got nothing > to do with "x". > > Moreover we have had just high noise levels alone rather than useful > talks, which hasd additional attributes for developments to crawl. > I don't want to pressurize you, that was not my intention. I know it's far from easy. I just had no idea where the current development was and wanted to know - when would anything for the S2-3200 come into hg, does the CI work, what's the stability ATM, I just had no idea. I just wanted to say I wouldn't need the S2 functionality yet. The latest files I have found appear to be from february, so I really had no idea. And I'd like to say thank you, because it really is a lot of work, and not easy. Thank you, all developers and people who send in patches/drivers. Your work really is appreciated. > >
[linux-dvb] TT S2-3200 stable, CI, go or no-go?
I know there have been some posts about the card - but I didn't see the questions asked I have. [story you can skip] The problem is this: currently I have a KNC1 DVB-S card + cineview CI. But it's breaking down, SNR appears to get worse by the day. Bad luck :'( I also have a TT S-1500 with budget CI. I would use that, but the CI doesn't work for no reason! Bad luck again :'( I've got a Phoenix reader, I know someone will be going to suggest that - so I would put my smartcard in that - the Phoenix is OK, but it refuses to init the satellite smartcard (another smartcard for cable did work but that's worthless for me!) - how much bad luck can I have? [/story you can skip] So I have to buy a new card, and I feel it would be a waste to buy another DVB-S1 card nowadays. S2 cards are not really expensive anymore. So I would be perfectly happy with a TT S2-3200 that only works on DVB-S1 (stable!) for the moment and with a working CI. I can perfectly live with DVB-S2 support in the drivers being added at a later stage. I have the feeling the answer is going to be "no", but I want to ask anyway.. Could I expect this from the S2-3200 at this stage, or really soon (weeks I mean)? And when will S2-3200 support be added to hg? Or do I have to look for another solution.. Tia, P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Dell Dimension E521 AVerMedia M779 DVBt Hybrid TV Tuner
greg wrote: > On Sun, 2007-07-29 at 11:28 +0200, Greg Tee wrote: > >>> 01:00.0 Multimedia video controller: Micronas Semiconductor Holding AG >>> Unknown device 0720 > >> Finally I found some new information: >> >> [11:23:29] === Device Information === >> [11:23:29] Capture filter friendlyname:M779 PCIe Audio/Video Capture 1 >> [11:23:29] Model Name: AVerMedia M779 >> [11:23:29] Transmission Interface: PCI Express >> [11:23:29] Supported Standards:PAL/SECAM/DVB-T >> [11:23:29] TV Tuner: XC3018 >> [11:23:29] Audio/Video Decoder:AVF4910A >> [11:23:29] Encoder:NEC61151 >> [11:23:29] Ditial TV Demodulator: ZL10353 >> [11:23:29] === Driver Version === >> [11:23:29] Bridge: 2.4.0.31 >> [11:23:29] Video Capture: 2.4.0.31 >> [11:23:29] Tuner: 2.4.0.31 >> [11:23:29] === Test Results === >> [11:23:29] Tuner Product ID: 3028 >> [11:23:29] Tuner Version: HW: 1.0 FW: 2.7 >> [11:23:29] AVDeocder Manufacture ID: 0xEC >> [11:23:29] Encoder Device Version: 2 >> [11:23:29] Demodulator Chip ID:0x14 >> [11:23:29] Get Device Information: [PASS] >> [11:23:29] TV Tuner: [PASS] >> [11:23:29] Audio/Video Decoder:[PASS] >> [11:23:29] Encoder:[PASS] >> [11:23:29] Digital TV Demodulator: [PASS] >> [11:23:29] --- Test End --- >> [11:23:29] > > Does this info help to get this (Dell) hardware supported? > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Xceive.. Forget it. There is code for that, even code for Linux, but it was released by Rechberger and he's not planning on getting it to v4l-dvb in any way. In his last mail he said something about a userspace driver.. I'm not sure how that'll have to integrate with v4l-dvb. I'd go look out for another TV-card right now. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] TT-3200 DVB-S2 Patch for Kernel 2.6.22
Ulrich wrote: > Hi, > > > I hope this is not the wrong place for the following kind of feedback: > > > `·.¸¸.·´¯`·.·´¯`· THANK YOU SO MUCH!!! <=== > > > And of course many thanks to Manu, Laasa and everyone who has > contributed to these drivers and utilities. > > I'm sorry, I can't help with testing right now, but I'm definitly buying > this DVB-S2-Card very soon. > > > I just wanted to let you know that I appreciate your efforts, and I'm > looking forward to enjoying HDTV on my Linux-machine. > > Keep up your good work! > > > Best wishes, > Ulrich > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > What HDTV do you expect to enjoy exactly? BBC HD doesn't require DVB-S2, most other channels use PAFF interlacing which isn't supported by libav yet (but there is active progress I believe). I'm looking for the TT-3200 as well, but I'm waiting for the driver to make it into v4l-dvb and be stable. Also I need a working CI, I don't know what the status on that is. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Recommended DVB-T CI Card?
[EMAIL PROTECTED] wrote: > Is there any DVB-T card with integrated or separate CI interface that > are fully supported and available in stores? > > Regards, > Fredrik Dahlberg > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > KNC1 TV-Station DVB-T+Cineview and Technotrend T-1500+Budget CI should both work. Technotrend available at dvbshop.net, KNC1 here and there on eBay maybe. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] PATCH: extra switch for zap (developers?)
Uwe Bugla wrote: > Am Freitag, 27. Juli 2007 04:27:59 schrieben Sie: >> P. van Gaans wrote: >>> Uwe Bugla wrote: >>>> Am Donnerstag, 19. Juli 2007 02:29:34 schrieben Sie: >>>>> Uwe Bugla wrote: >>>>>> Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans: >>>>>>> I don't call myself a programmer (I've never seen any C guide), but >>>>>>> somehow I figured out how to add an extra switch to tzap to make it >>>>>>> print the status in (human-readable) decimal instead of hex. It is >>>>>>> attached. It would be really nice if this would make it into the >>>>>>> dvb-apps on linuxtv.. >>>>>>> >>>>>>> Talking about that, could anybody tell me the minimal and maximal >>>>>>> and/or >>>>>>> possible values for status, signal, snr, ber and uncorrected? If I >>>>>>> would >>>>>>> know them I could try to make the numbers more human-readable (eg >>>>>>> signal >>>>>>> ranging from 0 to 99 or so). >>>>>> Could you please redo that: >>>>>> - in patch format (=only the additions) >>>>>> - equally for tzap, czap, szap and femon? >>>>>> >>>>>> Thus everybody could take advantage from that idea. >>>>>> Would be a pleasure for us all if you did! >>>>>> >>>>>> My idea for further enlargement (a quite old idea of mine): >>>>>> route the human readable numbers into a speech recognition engine >>>>>> (festival) to make them auditable and thus real usable for DVB-S dish >>>>>> tuning f. ex. >>>>>> >>>>>> Note: If the DVB-S dish is far away from the machine (card), auditable >>>>>> signals are necessary. >>>>>> >>>>>> ___ >>>>>> linux-dvb mailing list >>>>>> linux-dvb@linuxtv.org >>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>>> In patch format.. Oh please.. I have no idea how to produce that! I >>>>> installed xxdiff, it perfectly shows what I've changed but I don't see >>>>> an option to save it to a patch file! >>>>> >>>>> You're lucky I've got a satellite dish so I should also be able to >>>>> patch szap and femon. I'll also produce a patched version of czap but >>>>> my cable card is not installed ATM and I don't feel like doing so >>>>> (cable provider is crap) but I'll probably get someone else on this >>>>> list to test it. >>>>> >>>>> Please do not try to add the switch yourself without asking me if I'm >>>>> still working on it. Nobody needs double work. >>>>> >>>>> If somebody can tell me how to produce the so much wanted .diff files >>>>> I'll start working on it. >>>> A. Take the latest kernel patch (i. e. 2.6.21.1) as an example. >>>> B. format is as follows: >>>> --- a/(file to be changed) >>>> +++ b/(file to be changed) >>>> @@ -(starting line number),(total number of lines starting from the >>>> beginning line before the change) +(starting line number),(total >>>> number of lines starting from the beginning line after the change) >>>> (3 context lines starting with a space) >>>> (additions start with plus) >>>> (deletions start with minus) >>>> (3 context lines starting with a space) >>>> >>>> If this explanation still is too abstract, have a look at the example >>>> again. >>>> Don't forget to test the patch! >>>> No fuzz factors, no rejections please. >>>> For testing purposes keep the original file to be patched in a >>>> separate directory please. >>>> Now please give it a try - for sure you gonna make it! >>> I've got an idea of how the .diff is constructed, but I simply refuse to >>> write them by hand. I've bought a computer NOT to do any more boring >>> repetitive work ;-). >>> >>> diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily. >>> >>> Tzap was patched already. >>> Szap patched, compiles, tested and OK. >>> Czap patched, compiles without errors, untested
Re: [linux-dvb] PATCH: extra switch for zap (developers?)
P. van Gaans wrote: > Uwe Bugla wrote: >> Am Donnerstag, 19. Juli 2007 02:29:34 schrieben Sie: >>> Uwe Bugla wrote: >>>> Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans: >>>>> I don't call myself a programmer (I've never seen any C guide), but >>>>> somehow I figured out how to add an extra switch to tzap to make it >>>>> print the status in (human-readable) decimal instead of hex. It is >>>>> attached. It would be really nice if this would make it into the >>>>> dvb-apps on linuxtv.. >>>>> >>>>> Talking about that, could anybody tell me the minimal and maximal >>>>> and/or >>>>> possible values for status, signal, snr, ber and uncorrected? If I >>>>> would >>>>> know them I could try to make the numbers more human-readable (eg >>>>> signal >>>>> ranging from 0 to 99 or so). >>>> Could you please redo that: >>>> - in patch format (=only the additions) >>>> - equally for tzap, czap, szap and femon? >>>> >>>> Thus everybody could take advantage from that idea. >>>> Would be a pleasure for us all if you did! >>>> >>>> My idea for further enlargement (a quite old idea of mine): >>>> route the human readable numbers into a speech recognition engine >>>> (festival) to make them auditable and thus real usable for DVB-S dish >>>> tuning f. ex. >>>> >>>> Note: If the DVB-S dish is far away from the machine (card), auditable >>>> signals are necessary. >>>> >>>> ___ >>>> linux-dvb mailing list >>>> linux-dvb@linuxtv.org >>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>> In patch format.. Oh please.. I have no idea how to produce that! I >>> installed xxdiff, it perfectly shows what I've changed but I don't see >>> an option to save it to a patch file! >>> >>> You're lucky I've got a satellite dish so I should also be able to patch >>> szap and femon. I'll also produce a patched version of czap but my cable >>> card is not installed ATM and I don't feel like doing so (cable provider >>> is crap) but I'll probably get someone else on this list to test it. >>> >>> Please do not try to add the switch yourself without asking me if I'm >>> still working on it. Nobody needs double work. >>> >>> If somebody can tell me how to produce the so much wanted .diff files >>> I'll start working on it. >> >> A. Take the latest kernel patch (i. e. 2.6.21.1) as an example. >> B. format is as follows: >> --- a/(file to be changed) >> +++ b/(file to be changed) >> @@ -(starting line number),(total number of lines starting from the >> beginning line before the change) +(starting line number),(total >> number of lines starting from the beginning line after the change) >> (3 context lines starting with a space) >> (additions start with plus) >> (deletions start with minus) >> (3 context lines starting with a space) >> >> If this explanation still is too abstract, have a look at the example >> again. >> Don't forget to test the patch! >> No fuzz factors, no rejections please. >> For testing purposes keep the original file to be patched in a >> separate directory please. >> Now please give it a try - for sure you gonna make it! >> > > I've got an idea of how the .diff is constructed, but I simply refuse to > write them by hand. I've bought a computer NOT to do any more boring > repetitive work ;-). > > diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily. > > Tzap was patched already. > Szap patched, compiles, tested and OK. > Czap patched, compiles without errors, untested because I hate my cable > provider and the box I would have to install the cable card in is really > noisy and unstable. Whoever wants to test: please report results, czap > looks a little different from szap and tzap but I'm pretty certain it'll > work straightaway. I assume this is OK, you couldn't expect all linuxtv > developers to own cards for all DVB-systems anyway.. > Femon patched in a different way: Femon already has a "human readable" > switch, I just made BER and uncorrected show up as decimal instead of > hex in human readable mode. Adding another switch sounds pointless to me. > > The numbers/output seem to differ between devices and between szap and > tzap greatly so for now I'm not going to try to make them more > human-readable because of the possibility of breaking something. > > Everything attached. > > > > > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb There was some confusion cause of Uwe, but will my switch ever make it to the dvb-apps on linuxtv? Or is there something wrong with it? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] New tuning file for Astra 28.2E
Zoilo Gomez wrote: > Christoph Pfister wrote: >> Hi, >> >> Am Dienstag, 24. Juli 2007 11:45 schrieb Marvin Hankley: >> >>> Hi! >>> >>> Please find attached a more complete tuning file for Astra 28.2E. >>> >> Is that really needed? NIT linking exists which allows the scan apps to find >> the other transponders (ideally from a single initial tuning entry). >> Of course some providers manage to mess stuff up so that you need more (or >> all) entries to get the full channel list. > > Exactly; NITs seem to be incomplete all the time ... as of yet I still > have to see my first complete scan that is based on an ideal single > initial tuning entry on any satellite! > > Am I correct in thinking that things seem to change often as well? > > Another notorious mess is the new Astra 23E5 ... will post a frequency > list for that one as soon as I have time to investigate it. > > Z. > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > When I did a scan on the Hot Bird satellite with Kaffeine, I only found 10 channels. There was no NIT available at all. After searching for the transponder with the NIT info for a while I gave up, loaded the transponder file from http://joshyfun.peque.org/transponders/kaffeine.html and completed the scan.. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Please help: Looking for a solidly supported DVB-T USB stick
Stephen Williams wrote: > Surely this can't be too much to ask? I'm looking for a DVB-T USB > stick which I can buy now and is solidly supported, that's all. > > Previously i've picked up a couple of MSI Digivox II sticks that when > delivered turned out to be unsupported MSI Digivox II V2.0 sticks, so > it's no longer safe to order those. Then I picked up a couple of MSI > Mega Sky 580 sticks (the x5581 version) which appear to be incapable > of receiving a decent signal under windows or linux (note that I > haven't had signal problems with 4 previous DVB-T receivers). > > So i'm now hoping for "third time lucky". Any suggestions of supported > devices that are known to work without issues would be greatly > appreciated. > > I've checked the wiki for information but it all seems to be completed > out of date. > > Thanks, > Stephen > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > The Mega Sky 580 overall works fine, but it doesn't like a very strong signal - if you have a booster, try to weaken it a bit. I also have a Afatech AF9005, VT doesn't work yet (not sure what that is but wiki says so), but it doesn't have a problem with strong signals. Scanning with Kaffeine was also problematic last time I tried, but if you don't use Kaffeine it should work fine. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap
Uwe Bugla wrote: > Am Freitag, 20. Juli 2007 12:37:45 schrieben Sie: >> Uwe Bugla wrote: >>> Am Donnerstag, 19. Juli 2007 02:29:34 schrieben Sie: >>>> Uwe Bugla wrote: >>>>> Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans: >>>>>> I don't call myself a programmer (I've never seen any C guide), but >>>>>> somehow I figured out how to add an extra switch to tzap to make it >>>>>> print the status in (human-readable) decimal instead of hex. It is >>>>>> attached. It would be really nice if this would make it into the >>>>>> dvb-apps on linuxtv.. >>>>>> >>>>>> Talking about that, could anybody tell me the minimal and maximal >>>>>> and/or possible values for status, signal, snr, ber and uncorrected? >>>>>> If I would know them I could try to make the numbers more >>>>>> human-readable (eg signal ranging from 0 to 99 or so). >>>>> Could you please redo that: >>>>> - in patch format (=only the additions) >>>>> - equally for tzap, czap, szap and femon? >>>>> >>>>> Thus everybody could take advantage from that idea. >>>>> Would be a pleasure for us all if you did! >>>>> >>>>> My idea for further enlargement (a quite old idea of mine): >>>>> route the human readable numbers into a speech recognition engine >>>>> (festival) to make them auditable and thus real usable for DVB-S dish >>>>> tuning f. ex. >>>>> >>>>> Note: If the DVB-S dish is far away from the machine (card), auditable >>>>> signals are necessary. >>>>> >>>>> ___ >>>>> linux-dvb mailing list >>>>> linux-dvb@linuxtv.org >>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>> In patch format.. Oh please.. I have no idea how to produce that! I >>>> installed xxdiff, it perfectly shows what I've changed but I don't see >>>> an option to save it to a patch file! >>>> >>>> You're lucky I've got a satellite dish so I should also be able to patch >>>> szap and femon. I'll also produce a patched version of czap but my cable >>>> card is not installed ATM and I don't feel like doing so (cable provider >>>> is crap) but I'll probably get someone else on this list to test it. >>>> >>>> Please do not try to add the switch yourself without asking me if I'm >>>> still working on it. Nobody needs double work. >>>> >>>> If somebody can tell me how to produce the so much wanted .diff files >>>> I'll start working on it. >>> A. Take the latest kernel patch (i. e. 2.6.21.1) as an example. >>> B. format is as follows: >>> --- a/(file to be changed) >>> +++ b/(file to be changed) >>> @@ -(starting line number),(total number of lines starting from the >>> beginning line before the change) +(starting line number),(total number >>> of lines starting from the beginning line after the change) >>> (3 context lines starting with a space) >>> (additions start with plus) >>> (deletions start with minus) >>> (3 context lines starting with a space) >>> >>> If this explanation still is too abstract, have a look at the example >>> again. Don't forget to test the patch! >>> No fuzz factors, no rejections please. >>> For testing purposes keep the original file to be patched in a separate >>> directory please. >>> Now please give it a try - for sure you gonna make it! >> I've got an idea of how the .diff is constructed, but I simply refuse to >> write them by hand. I've bought a computer NOT to do any more boring >> repetitive work ;-). >> >> diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily. >> >> Tzap was patched already. >> Szap patched, compiles, tested and OK. >> Czap patched, compiles without errors, untested because I hate my cable >> provider and the box I would have to install the cable card in is really >> noisy and unstable. Whoever wants to test: please report results, czap >> looks a little different from szap and tzap but I'm pretty certain it'll >> work straightaway. I assume this is OK, you couldn't expect all linuxtv >> developers to own cards for all DVB-systems anyway.. >> Femon patched in a different way: Femon already has a "human readable" >> switch, I just made BER and uncorrected show up as decimal instead of >> hex in human readable mode. Adding another switch sounds pointless to me. >> >> The numbers/output seem to differ between devices and between szap and >> tzap greatly so for now I'm not going to try to make them more >> human-readable because of the possibility of breaking something. >> >> Everything attached. > > Thank you very much! > > Now if some of the "illustrous" may consacre a bit of time to push that into > the dvb-apps tree it would be real purrfect! > Because you were telling me what to do, I thought you were a developer.. Exciting.. I hope that work wasn't for nothing. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] extra switch for tzap
Uwe Bugla wrote:
Am Donnerstag, 19. Juli 2007 02:29:34 schrieben Sie:
Uwe Bugla wrote:
Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans:
I don't call myself a programmer (I've never seen any C guide), but
somehow I figured out how to add an extra switch to tzap to make it
print the status in (human-readable) decimal instead of hex. It is
attached. It would be really nice if this would make it into the
dvb-apps on linuxtv..
Talking about that, could anybody tell me the minimal and maximal and/or
possible values for status, signal, snr, ber and uncorrected? If I would
know them I could try to make the numbers more human-readable (eg signal
ranging from 0 to 99 or so).
Could you please redo that:
- in patch format (=only the additions)
- equally for tzap, czap, szap and femon?
Thus everybody could take advantage from that idea.
Would be a pleasure for us all if you did!
My idea for further enlargement (a quite old idea of mine):
route the human readable numbers into a speech recognition engine
(festival) to make them auditable and thus real usable for DVB-S dish
tuning f. ex.
Note: If the DVB-S dish is far away from the machine (card), auditable
signals are necessary.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
In patch format.. Oh please.. I have no idea how to produce that! I
installed xxdiff, it perfectly shows what I've changed but I don't see
an option to save it to a patch file!
You're lucky I've got a satellite dish so I should also be able to patch
szap and femon. I'll also produce a patched version of czap but my cable
card is not installed ATM and I don't feel like doing so (cable provider
is crap) but I'll probably get someone else on this list to test it.
Please do not try to add the switch yourself without asking me if I'm
still working on it. Nobody needs double work.
If somebody can tell me how to produce the so much wanted .diff files
I'll start working on it.
A. Take the latest kernel patch (i. e. 2.6.21.1) as an example.
B. format is as follows:
--- a/(file to be changed)
+++ b/(file to be changed)
@@ -(starting line number),(total number of lines starting from the beginning
line before the change) +(starting line number),(total number of lines
starting from the beginning line after the change)
(3 context lines starting with a space)
(additions start with plus)
(deletions start with minus)
(3 context lines starting with a space)
If this explanation still is too abstract, have a look at the example again.
Don't forget to test the patch!
No fuzz factors, no rejections please.
For testing purposes keep the original file to be patched in a separate
directory please.
Now please give it a try - for sure you gonna make it!
I've got an idea of how the .diff is constructed, but I simply refuse to
write them by hand. I've bought a computer NOT to do any more boring
repetitive work ;-).
diff -urN oldfile.c newfile.c > lolwat.diff appears to work luckily.
Tzap was patched already.
Szap patched, compiles, tested and OK.
Czap patched, compiles without errors, untested because I hate my cable
provider and the box I would have to install the cable card in is really
noisy and unstable. Whoever wants to test: please report results, czap
looks a little different from szap and tzap but I'm pretty certain it'll
work straightaway. I assume this is OK, you couldn't expect all linuxtv
developers to own cards for all DVB-systems anyway..
Femon patched in a different way: Femon already has a "human readable"
switch, I just made BER and uncorrected show up as decimal instead of
hex in human readable mode. Adding another switch sounds pointless to me.
The numbers/output seem to differ between devices and between szap and
tzap greatly so for now I'm not going to try to make them more
human-readable because of the possibility of breaking something.
Everything attached.
--- czap-hg.c 2007-07-18 05:18:38.0 +0200
+++ czap.c 2007-07-20 11:58:35.0 +0200
@@ -16,6 +16,7 @@
static char FRONTEND_DEV [80];
static char DEMUX_DEV [80];
+static int decread=0;
static int exit_after_tuning;
#define CHANNEL_FILE "channels.conf"
@@ -241,9 +242,18 @@
ioctl(fe_fd, FE_READ_BER, &ber);
ioctl(fe_fd, FE_READ_UNCORRECTED_BLOCKS, &uncorrected_blocks);
- printf ("status %02x | signal %04x | snr %04x | "
+ if(decread==1)
+ {
+ printf ("status %d | signal %d | snr %d | "
+ "ber %d | unc %d | ",
+ status, signal, snr, ber, uncorrected_blocks);
+ }
+ else
+ {
+ printf ("status %02x | signal %04x | snr %04x | "
"ber %08x | unc %08x | ",
status, signal, snr, ber, uncorrected_blocks);
+ }
if (status & FE_HAS_LOCK)
printf("FE_HAS_LOCK");
@@ -2
Re: [linux-dvb] extra switch for tzap
Uwe Bugla wrote: > Am Mittwoch, 18. Juli 2007 06:03:41 schrieb P. van Gaans: >> I don't call myself a programmer (I've never seen any C guide), but >> somehow I figured out how to add an extra switch to tzap to make it >> print the status in (human-readable) decimal instead of hex. It is >> attached. It would be really nice if this would make it into the >> dvb-apps on linuxtv.. >> >> Talking about that, could anybody tell me the minimal and maximal and/or >> possible values for status, signal, snr, ber and uncorrected? If I would >> know them I could try to make the numbers more human-readable (eg signal >> ranging from 0 to 99 or so). > > Could you please redo that: > - in patch format (=only the additions) > - equally for tzap, czap, szap and femon? > > Thus everybody could take advantage from that idea. > Would be a pleasure for us all if you did! > > My idea for further enlargement (a quite old idea of mine): > route the human readable numbers into a speech recognition engine (festival) > to make them auditable and thus real usable for DVB-S dish tuning f. ex. > > Note: If the DVB-S dish is far away from the machine (card), auditable > signals > are necessary. > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > In patch format.. Oh please.. I have no idea how to produce that! I installed xxdiff, it perfectly shows what I've changed but I don't see an option to save it to a patch file! You're lucky I've got a satellite dish so I should also be able to patch szap and femon. I'll also produce a patched version of czap but my cable card is not installed ATM and I don't feel like doing so (cable provider is crap) but I'll probably get someone else on this list to test it. Please do not try to add the switch yourself without asking me if I'm still working on it. Nobody needs double work. If somebody can tell me how to produce the so much wanted .diff files I'll start working on it. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] extra switch for tzap
I don't call myself a programmer (I've never seen any C guide), but
somehow I figured out how to add an extra switch to tzap to make it
print the status in (human-readable) decimal instead of hex. It is
attached. It would be really nice if this would make it into the
dvb-apps on linuxtv..
Talking about that, could anybody tell me the minimal and maximal and/or
possible values for status, signal, snr, ber and uncorrected? If I would
know them I could try to make the numbers more human-readable (eg signal
ranging from 0 to 99 or so).
/* tzap -- DVB-T zapping utility
*/
/*
* Added recording to a file
* arguments:
*
* -t timeout (seconds)
* -o filename output filename (use -o - for stdout)
* -s only print summary
* -S run silently (no output)
*
* Bernard Hatt 24/2/04
*/
#define _FILE_OFFSET_BITS 64
#define _LARGEFILE_SOURCE 1
#define _LARGEFILE64_SOURCE 1
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
#include
static char FRONTEND_DEV [80];
static char DEMUX_DEV [80];
static char DVR_DEV [80];
static int timeout_flag=0;
static int silent=0,timeout=0;
static int decread=0;
static int exit_after_tuning;
#define CHANNEL_FILE "channels.conf"
#define ERROR(x...) \
do {\
fprintf(stderr, "ERROR: "); \
fprintf(stderr, x); \
fprintf (stderr, "\n"); \
} while (0)
#define PERROR(x...)\
do {\
fprintf(stderr, "ERROR: "); \
fprintf(stderr, x); \
fprintf (stderr, " (%s)\n", strerror(errno)); \
} while (0)
typedef struct {
char *name;
int value;
} Param;
static const Param inversion_list [] = {
{ "INVERSION_OFF", INVERSION_OFF },
{ "INVERSION_ON", INVERSION_ON },
{ "INVERSION_AUTO", INVERSION_AUTO }
};
static const Param bw_list [] = {
{ "BANDWIDTH_6_MHZ", BANDWIDTH_6_MHZ },
{ "BANDWIDTH_7_MHZ", BANDWIDTH_7_MHZ },
{ "BANDWIDTH_8_MHZ", BANDWIDTH_8_MHZ }
};
static const Param fec_list [] = {
{ "FEC_1_2", FEC_1_2 },
{ "FEC_2_3", FEC_2_3 },
{ "FEC_3_4", FEC_3_4 },
{ "FEC_4_5", FEC_4_5 },
{ "FEC_5_6", FEC_5_6 },
{ "FEC_6_7", FEC_6_7 },
{ "FEC_7_8", FEC_7_8 },
{ "FEC_8_9", FEC_8_9 },
{ "FEC_AUTO", FEC_AUTO },
{ "FEC_NONE", FEC_NONE }
};
static const Param guard_list [] = {
{"GUARD_INTERVAL_1_16", GUARD_INTERVAL_1_16},
{"GUARD_INTERVAL_1_32", GUARD_INTERVAL_1_32},
{"GUARD_INTERVAL_1_4", GUARD_INTERVAL_1_4},
{"GUARD_INTERVAL_1_8", GUARD_INTERVAL_1_8},
{"GUARD_INTERVAL_AUTO", GUARD_INTERVAL_AUTO}
};
static const Param hierarchy_list [] = {
{ "HIERARCHY_1", HIERARCHY_1 },
{ "HIERARCHY_2", HIERARCHY_2 },
{ "HIERARCHY_4", HIERARCHY_4 },
{ "HIERARCHY_NONE", HIERARCHY_NONE },
{ "HIERARCHY_AUTO", HIERARCHY_AUTO }
};
static const Param constellation_list [] = {
{ "QPSK", QPSK },
{ "QAM_128", QAM_128 },
{ "QAM_16", QAM_16 },
{ "QAM_256", QAM_256 },
{ "QAM_32", QAM_32 },
{ "QAM_64", QAM_64 },
{ "QAM_AUTO", QAM_AUTO }
};
static const Param transmissionmode_list [] = {
{ "TRANSMISSION_MODE_2K", TRANSMISSION_MODE_2K },
{ "TRANSMISSION_MODE_8K", TRANSMISSION_MODE_8K },
{ "TRANSMISSION_MODE_AUTO", TRANSMISSION_MODE_AUTO }
};
#define LIST_SIZE(x) sizeof(x)/sizeof(Param)
static
int parse_param (int fd, const Param * plist, int list_size, int *param)
{
char c;
int character = 0;
int _index = 0;
while (1) {
if (read(fd, &c, 1) < 1)
return -1; /* EOF? */
if ((c == ':' || c == '\n')
&& plist->name[character] == '\0')
break;
while (toupper(c) != plist->name[character]) {
_index++;
plist++;
if (_index >= list_size) /* parse error, no valid */
return -2; /* parameter name found */
}
character++;
}
*param = plist->value;
return 0;
}
static
int parse_int(int fd, int *val)
{
char number[11]; /* 2^32 needs 10 digits... */
int character = 0;
while (1) {
if (read(fd, &number[character], 1) < 1)
return -1; /* EOF? */
if (number[character] == ':' || number[character] == '\n') {
number[character] = '\0';
break;
}
if (!isdigit(number[character]))
return -2; /* parse error, not a digit... */
character++;
if (character > 10) /* overflow, number too big */
return -3; /* to fit in 32 bit */
};
*val = strtol(number, NULL, 10);
return 0;
}
static
int find_channel(int fd, const char *channel)
{
int character = 0;
while (1) {
char c;
if (read(fd, &c, 1) < 1)
return -1; /* EOF! */
if ( '\n' == c ) /* start of line */
character = 0;
else if ( character >= 0 ) { /* we are in the namefield */
Re: [linux-dvb] tzap output not human readable
timecop wrote: > Edit the sores, and replace %04x with %d or wahtever suits your fancy. > never mind the fact that since actual real programmers write windows > apps, this wouldn't be a problem in teh first place)> > > -tc > > On 7/18/07, P. van Gaans <[EMAIL PROTECTED]> wrote: >> I tuned to something with tzap. That gives output like this: >> >> status 1f | signal 9a9a | snr fafa | ber 00013ed2 | unc | >> FE_HAS_LOCK >> status 1f | signal 9898 | snr fbfb | ber 00011dbe | unc | >> FE_HAS_LOCK >> status 1f | signal 9595 | snr fcfc | ber 00011678 | unc 0005 | >> FE_HAS_LOCK >> status 1f | signal 9090 | snr fcfc | ber 00011a26 | unc 0003 | >> FE_HAS_LOCK >> status 1f | signal 8f8f | snr fcfc | ber 0001289c | unc | >> FE_HAS_LOCK >> status 1f | signal 9393 | snr fcfc | ber 0001362a | unc 000a | >> FE_HAS_LOCK >> status 1f | signal 9595 | snr fcfc | ber 00012d46 | unc 0016 | >> FE_HAS_LOCK >> >> I've noticed none of the numbers are human-readable (and yes, I suspect >> anyone who can read hex at the speed tzap outputs it from being >> non-human ;)). Is it possible to make tzap output decimal numbers so I >> can compare signal quality and stuff between channels? >> >> ___ >> 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 > I was seriously almost going to ask you where I could find the sores, until I realized the meaning of the word "sore" in proper English and it's pronunciation. Am I allowed to rant on some people on this list? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] tzap output not human readable
I tuned to something with tzap. That gives output like this: status 1f | signal 9a9a | snr fafa | ber 00013ed2 | unc | FE_HAS_LOCK status 1f | signal 9898 | snr fbfb | ber 00011dbe | unc | FE_HAS_LOCK status 1f | signal 9595 | snr fcfc | ber 00011678 | unc 0005 | FE_HAS_LOCK status 1f | signal 9090 | snr fcfc | ber 00011a26 | unc 0003 | FE_HAS_LOCK status 1f | signal 8f8f | snr fcfc | ber 0001289c | unc | FE_HAS_LOCK status 1f | signal 9393 | snr fcfc | ber 0001362a | unc 000a | FE_HAS_LOCK status 1f | signal 9595 | snr fcfc | ber 00012d46 | unc 0016 | FE_HAS_LOCK I've noticed none of the numbers are human-readable (and yes, I suspect anyone who can read hex at the speed tzap outputs it from being non-human ;)). Is it possible to make tzap output decimal numbers so I can compare signal quality and stuff between channels? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technotrend S2-3600 HDTV-S2 USB 2.0
Erich Newell wrote: > What would be the process for this? Does the developer need direct > access to the hardware, or is it a simple matter of looking at a > couple of chipsets and modifying some code appropriately? (Please > excuse my ignorance in this) > > If it were a practical endeavor, I would be willing to purchase the > hardware and do testing if someone will commit to modifying the > drivers appropriately. > > Thoughts? > >>> Will the Technotrend S2-3600 HDTV-S2 USB 2.0 work with the drivers >>> currently under development by Manu? >> Currently, No. >> >> Will need to know what components are inside, to find out whether it >> can be supported. >> > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > First it must be known what chips, tuners etc are inside. If there are drivers for those, supporting the device will be relatively easy. If there are no drivers, they will have to be written by either getting the specs and writing or reverse engineering and writing. That is much more work. If the chips are not supported already, no specs are given and nobody feels like reverse engineering, it will never be supported. If the chips are supported already, it can be supported in a day (at least very fast). All depends on what is there to see inside the device, it's impossible to say anything now. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Timecop
Michael Krufky wrote: > timecop wrote: >> I would like to mention once again that I freaking hate the fact that >> this list does not modify Reply-To: header. >> > [snip] >> So my question is, why even bother with the Linux driver. > > My question to you... Why even read the list? Why reply? > > It's clear that you're not interested in this stuff (or are you?) > > Why spend your precious time reading about an operating system that you > disapprove of? > > I think that you secretly love Linux, and everything that it has to offer. > > Either that, or it's your only source of useful information. > > -mk > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > His reply did give me a funny idea though. VMWare and similar communicate to the host OS through the network, AFAIK. So maybe it would be possible to write a server-client to make it possible to run the DVB USB device on a Windows-guest, stream the whole TS over the network to the host OS and have a little server/client to change frequency and start/stop streaming. In Linux (or other non-windows host) you would probably have a virtual DVB device for a client so that it works in any application. It's horrifying and nasty, I wouldn't really like to use it myself ATM (I prefer buying a natively supported device even if I own an unsupported one already), but if there really wouldn't be any other way (e.g. no hope for a native driver), it may be an option to some. Or as a temporary solution until there's a driver (just like captive NTFS was until there was ntfs-3g). P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-S CI?
> P. van Gaans wrote: >> Christoph Pfister wrote: >> >>> 2007/7/7, P. van Gaans <[EMAIL PROTECTED]>: >>> >>>> P. van Gaans wrote: >>>> >>>>> e9hack wrote: >>>>> >>>>>> P. van Gaans wrote: >>>>>> >>>>>> >>>>>>> Some more news. I'm now looking at dvb_ca_en50221.c and I'm >>>>>>> pretty >>>> sure >>>> >>>>>>> the solution is in here and not in budget-av.c. Somewhere around >>>>>>> line >>>>>>> 270 is a thing that loops in a while and breaks after timeout. I >>>>>>> >>>> removed >>>> >>>>>>> the break (so it keeps looping). Now I see the following when I >>>>>>> >>>> insert a >>>> >>>>>>> CAM: >>>>>>> >>>>>>> [ 71.764000] budget-av: cam inserted A >>>>>>> [ 82.144000] dvb_ca adaptor 0: PC card did not respond :( >>>>>>> >>>>>>> So at least there's no more infinite loop with >>>> ejected-inserted-ejected >>>> >>>>>>> and so on. But it doesn't work either. It reaches >>>>>>> DVB_CA_SLOTSTATE_WAITREADY and times out there. From there it should >>>>>>> automatically change state, but it doesn't. Now I'm getting a little >>>>>>> stuck, because I don't really know what it's doing and what piece >>>>>>> >>>> really >>>> >>>>>>> gets stuck. >>>>>>> >>>>>>> I also removed the timeout from slotstate_waitready, now I don't get >>>>>>> errors anymore, but it (of course) doesn't work. And I broke the >>>>>>> >>>> ability >>>> >>>>>>> to eject the CAM, I'm guessing it's stuck in a loop after I >>>>>>> >>>> ejected and >>>> >>>>>>> re-inserted the CAM. >>>>>>> >>>>>>> >>>>>> It seems, there is a little bug within the debi functions. If a >>>>>> >>>> debi error occurs, SPCI_DEBI_S is not reset within PSR. >>>> >>>>>> In this case, saa7146_wait_for_debi_done returns always ETIMEDOUT. >>>>>> >>>> Ttpci_budget_debiread/write doesn't upload a debi >>>> >>>>>> command anymore. For testing, you can remove the first 'return >>>>>> >>>> result;' statement in both functions. >>>> >>>>>> - Hartmut >>>>>> >>>>>> ___ >>>>>> linux-dvb mailing list >>>>>> linux-dvb@linuxtv.org >>>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>>>> >>>>>> >>>>> I just booted my computer into Windows so I could at least watch TV >>>>> tonight. Guess not, the Windows software responds like there is no CAM >>>>> inserted at all. >>>>> >>>>> Please don't tell me I completely killed the card just by removing >>>>> some >>>>> timeouts! I didn't know my hardware could be at risk :( . I wonder if >>>>> it's really dead :( . >>>>> >>>>> ___ >>>>> linux-dvb mailing list >>>>> linux-dvb@linuxtv.org >>>>> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >>>>> >>>>> >>>> Things take a whole new turn. Apparently something went wrong with the >>>> cable to the CI daughterboard, after re-connecting it the card worked >>>> again in Windows. Now for Linux, with once again the normal v4l-dvb >>>> (not >>>> my modified version): >>>> >>>> [ 253.42] budget-av: cam inserted B >>>> [ 256.384000] dvb_ca adapter 0: DVB CAM detected and initialised >>>> successfully &
Re: [linux-dvb] KNC1 DVB-S CI?
Christoph Pfister wrote: > 2007/7/7, P. van Gaans <[EMAIL PROTECTED]>: >> P. van Gaans wrote: >> > e9hack wrote: >> >> P. van Gaans wrote: >> >> >> >>> Some more news. I'm now looking at dvb_ca_en50221.c and I'm pretty >> sure >> >>> the solution is in here and not in budget-av.c. Somewhere around line >> >>> 270 is a thing that loops in a while and breaks after timeout. I >> removed >> >>> the break (so it keeps looping). Now I see the following when I >> insert a >> >>> CAM: >> >>> >> >>> [ 71.764000] budget-av: cam inserted A >> >>> [ 82.144000] dvb_ca adaptor 0: PC card did not respond :( >> >>> >> >>> So at least there's no more infinite loop with >> ejected-inserted-ejected >> >>> and so on. But it doesn't work either. It reaches >> >>> DVB_CA_SLOTSTATE_WAITREADY and times out there. From there it should >> >>> automatically change state, but it doesn't. Now I'm getting a little >> >>> stuck, because I don't really know what it's doing and what piece >> really >> >>> gets stuck. >> >>> >> >>> I also removed the timeout from slotstate_waitready, now I don't get >> >>> errors anymore, but it (of course) doesn't work. And I broke the >> ability >> >>> to eject the CAM, I'm guessing it's stuck in a loop after I >> ejected and >> >>> re-inserted the CAM. >> >>> >> >> It seems, there is a little bug within the debi functions. If a >> debi error occurs, SPCI_DEBI_S is not reset within PSR. >> >> In this case, saa7146_wait_for_debi_done returns always ETIMEDOUT. >> Ttpci_budget_debiread/write doesn't upload a debi >> >> command anymore. For testing, you can remove the first 'return >> result;' statement in both functions. >> >> >> >> - Hartmut >> >> >> >> ___ >> >> linux-dvb mailing list >> >> linux-dvb@linuxtv.org >> >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> >> >> > I just booted my computer into Windows so I could at least watch TV >> > tonight. Guess not, the Windows software responds like there is no CAM >> > inserted at all. >> > >> > Please don't tell me I completely killed the card just by removing some >> > timeouts! I didn't know my hardware could be at risk :( . I wonder if >> > it's really dead :( . >> > >> > ___ >> > linux-dvb mailing list >> > linux-dvb@linuxtv.org >> > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > >> >> Things take a whole new turn. Apparently something went wrong with the >> cable to the CI daughterboard, after re-connecting it the card worked >> again in Windows. Now for Linux, with once again the normal v4l-dvb (not >> my modified version): >> >> [ 253.42] budget-av: cam inserted B >> [ 256.384000] dvb_ca adapter 0: DVB CAM detected and initialised >> successfully >> >> Ok! Kaffeine says: >> >> DvbCam::probe(): LLCI slot found on /dev/dvb/adapter0/ca0 >> DvbCam::probe(): CA module present on /dev/dvb/adapter0/ca0 > > This isn't sufficient - make sure the channel you're trying to watch > is marked as scrambled ... > >> But... No picture (and no, no sound either). No error visible. I'm now >> 100% sure the hardware is OK since it works on Windows now. And the >> messages in Linux make you think it should work here as well. But no >> picture? >> >> Tia, >> >> P. van Gaans > > Christoph > Is that really required? I didn't know. It's a very good suggestion, because my provider (Canal Digitaal) screwed up big time a while ago and set a FTA flag for all their channels, so to some receivers (including GlobeTV on Windows and to kaffeine) they appear as FTA. The solution was closer than I thought! I changed the channels to "scrambled" and it just works now! No need to change anything in v4l-dvb, the CI is just supported! I'll go test all my CAMs and update the wiki, thanks! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-S CI?
P. van Gaans wrote: > e9hack wrote: >> P. van Gaans wrote: >> >>> Some more news. I'm now looking at dvb_ca_en50221.c and I'm pretty sure >>> the solution is in here and not in budget-av.c. Somewhere around line >>> 270 is a thing that loops in a while and breaks after timeout. I removed >>> the break (so it keeps looping). Now I see the following when I insert a >>> CAM: >>> >>> [ 71.764000] budget-av: cam inserted A >>> [ 82.144000] dvb_ca adaptor 0: PC card did not respond :( >>> >>> So at least there's no more infinite loop with ejected-inserted-ejected >>> and so on. But it doesn't work either. It reaches >>> DVB_CA_SLOTSTATE_WAITREADY and times out there. From there it should >>> automatically change state, but it doesn't. Now I'm getting a little >>> stuck, because I don't really know what it's doing and what piece really >>> gets stuck. >>> >>> I also removed the timeout from slotstate_waitready, now I don't get >>> errors anymore, but it (of course) doesn't work. And I broke the ability >>> to eject the CAM, I'm guessing it's stuck in a loop after I ejected and >>> re-inserted the CAM. >>> >> It seems, there is a little bug within the debi functions. If a debi error >> occurs, SPCI_DEBI_S is not reset within PSR. >> In this case, saa7146_wait_for_debi_done returns always ETIMEDOUT. >> Ttpci_budget_debiread/write doesn't upload a debi >> command anymore. For testing, you can remove the first 'return result;' >> statement in both functions. >> >> - Hartmut >> >> ___ >> linux-dvb mailing list >> linux-dvb@linuxtv.org >> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb >> > I just booted my computer into Windows so I could at least watch TV > tonight. Guess not, the Windows software responds like there is no CAM > inserted at all. > > Please don't tell me I completely killed the card just by removing some > timeouts! I didn't know my hardware could be at risk :( . I wonder if > it's really dead :( . > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Things take a whole new turn. Apparently something went wrong with the cable to the CI daughterboard, after re-connecting it the card worked again in Windows. Now for Linux, with once again the normal v4l-dvb (not my modified version): [ 253.42] budget-av: cam inserted B [ 256.384000] dvb_ca adapter 0: DVB CAM detected and initialised successfully Ok! Kaffeine says: DvbCam::probe(): LLCI slot found on /dev/dvb/adapter0/ca0 DvbCam::probe(): CA module present on /dev/dvb/adapter0/ca0 But... No picture (and no, no sound either). No error visible. I'm now 100% sure the hardware is OK since it works on Windows now. And the messages in Linux make you think it should work here as well. But no picture? Tia, P. van Gaans ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-S CI?
e9hack wrote: > P. van Gaans wrote: > >> Some more news. I'm now looking at dvb_ca_en50221.c and I'm pretty sure >> the solution is in here and not in budget-av.c. Somewhere around line >> 270 is a thing that loops in a while and breaks after timeout. I removed >> the break (so it keeps looping). Now I see the following when I insert a >> CAM: >> >> [ 71.764000] budget-av: cam inserted A >> [ 82.144000] dvb_ca adaptor 0: PC card did not respond :( >> >> So at least there's no more infinite loop with ejected-inserted-ejected >> and so on. But it doesn't work either. It reaches >> DVB_CA_SLOTSTATE_WAITREADY and times out there. From there it should >> automatically change state, but it doesn't. Now I'm getting a little >> stuck, because I don't really know what it's doing and what piece really >> gets stuck. >> >> I also removed the timeout from slotstate_waitready, now I don't get >> errors anymore, but it (of course) doesn't work. And I broke the ability >> to eject the CAM, I'm guessing it's stuck in a loop after I ejected and >> re-inserted the CAM. >> > > It seems, there is a little bug within the debi functions. If a debi error > occurs, SPCI_DEBI_S is not reset within PSR. > In this case, saa7146_wait_for_debi_done returns always ETIMEDOUT. > Ttpci_budget_debiread/write doesn't upload a debi > command anymore. For testing, you can remove the first 'return result;' > statement in both functions. > > - Hartmut > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > I just booted my computer into Windows so I could at least watch TV tonight. Guess not, the Windows software responds like there is no CAM inserted at all. Please don't tell me I completely killed the card just by removing some timeouts! I didn't know my hardware could be at risk :( . I wonder if it's really dead :( . ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-S CI?
P. van Gaans wrote:
> Oliver Endriss wrote:
>> P. van Gaans wrote:
>>> http://linuxtv.org/wiki/index.php/KNC1_TV-Station_DVB-S
>>>
>>> The wiki says "The card has a CI connector but it most probably isn't
>>> supported by Linux.". I've got the card and indeed, it doesn't seem to
>>> work. There is a ca0 in /dev/dvb/adapter0 but in Kaffeine the encrypted
>>> channels are still black.
>>>
>>> But I wonder, with the DVB-C version of this card, the CI works without
>>> a hitch (and I should know, I own one). According to the wiki the DVB-T
>>> version also has a working CI. I somehow can't imagine the CI on the
>>> DVB-S version is so much different. Or am I wrong and is the CI not
>>> supported because it requires a lot of reverse engineering nobody feels
>>> like doing for this card?
>> Maybe it is not supported because the driver developer did not have the
>> hardware to play with...
>>
>>> Is there anything I could try?
>> If you have some programming skills you could try to debug budget-av.c
>> and try to find out what's going wrong...
>>
>> CU
>> Oliver
>>
>
> I put the card back in my machine (I was also trying a TT S-1500 but I
> guess that's broken or something), praying the KNC1 would at least give
> me some clue. And it did, dmesg shows an infinite loop when a CAM is
> inserted:
>
> [ 327.10] budget-av: cam inserted A
> [ 327.356000] budget-av: cam ejected 5
> [ 327.456000] budget-av: cam inserted A
> [ 327.712000] budget-av: cam ejected 5
> [ 327.812000] budget-av: cam inserted A
> [ 328.068000] budget-av: cam ejected 5
> [ 328.168000] budget-av: cam inserted A
>
> Goes on all the time. When I get the card out of the cineview (fysical),
> it stops.
>
> More stuff I figured out: the ca is not "open" and times out. I tried
> simply commenting out all the "if" thingies that can eject the CAM
> (because after commenting out ejected 5 that means CA not open, it would
> just give me ejected 1 that means -ETIMEDOUT). Now I got "dvb_ca adaptor
> 0: PC card did not respond :(" after trying to watch.
>
> My personal guess is the KNC1 needs more time to initialize. I'll look
> at it some more, but I'm not sure I can figure it out all by myself, so
> if anybody can tell me some more...
>
> By the way, I'm not really a programmer, but I can do a little PHP and
> this looks somewhat similar :P.
>
> Tia,
>
> P.
>
> ___
> linux-dvb mailing list
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
Some more news. I'm now looking at dvb_ca_en50221.c and I'm pretty sure
the solution is in here and not in budget-av.c. Somewhere around line
270 is a thing that loops in a while and breaks after timeout. I removed
the break (so it keeps looping). Now I see the following when I insert a
CAM:
[ 71.764000] budget-av: cam inserted A
[ 82.144000] dvb_ca adaptor 0: PC card did not respond :(
So at least there's no more infinite loop with ejected-inserted-ejected
and so on. But it doesn't work either. It reaches
DVB_CA_SLOTSTATE_WAITREADY and times out there. From there it should
automatically change state, but it doesn't. Now I'm getting a little
stuck, because I don't really know what it's doing and what piece really
gets stuck.
I also removed the timeout from slotstate_waitready, now I don't get
errors anymore, but it (of course) doesn't work. And I broke the ability
to eject the CAM, I'm guessing it's stuck in a loop after I ejected and
re-inserted the CAM.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] KNC1 DVB-S CI?
Oliver Endriss wrote:
> P. van Gaans wrote:
>> http://linuxtv.org/wiki/index.php/KNC1_TV-Station_DVB-S
>>
>> The wiki says "The card has a CI connector but it most probably isn't
>> supported by Linux.". I've got the card and indeed, it doesn't seem to
>> work. There is a ca0 in /dev/dvb/adapter0 but in Kaffeine the encrypted
>> channels are still black.
>>
>> But I wonder, with the DVB-C version of this card, the CI works without
>> a hitch (and I should know, I own one). According to the wiki the DVB-T
>> version also has a working CI. I somehow can't imagine the CI on the
>> DVB-S version is so much different. Or am I wrong and is the CI not
>> supported because it requires a lot of reverse engineering nobody feels
>> like doing for this card?
>
> Maybe it is not supported because the driver developer did not have the
> hardware to play with...
>
>> Is there anything I could try?
>
> If you have some programming skills you could try to debug budget-av.c
> and try to find out what's going wrong...
>
> CU
> Oliver
>
I put the card back in my machine (I was also trying a TT S-1500 but I
guess that's broken or something), praying the KNC1 would at least give
me some clue. And it did, dmesg shows an infinite loop when a CAM is
inserted:
[ 327.10] budget-av: cam inserted A
[ 327.356000] budget-av: cam ejected 5
[ 327.456000] budget-av: cam inserted A
[ 327.712000] budget-av: cam ejected 5
[ 327.812000] budget-av: cam inserted A
[ 328.068000] budget-av: cam ejected 5
[ 328.168000] budget-av: cam inserted A
Goes on all the time. When I get the card out of the cineview (fysical),
it stops.
More stuff I figured out: the ca is not "open" and times out. I tried
simply commenting out all the "if" thingies that can eject the CAM
(because after commenting out ejected 5 that means CA not open, it would
just give me ejected 1 that means -ETIMEDOUT). Now I got "dvb_ca adaptor
0: PC card did not respond :(" after trying to watch.
My personal guess is the KNC1 needs more time to initialize. I'll look
at it some more, but I'm not sure I can figure it out all by myself, so
if anybody can tell me some more...
By the way, I'm not really a programmer, but I can do a little PHP and
this looks somewhat similar :P.
Tia,
P.
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] KNC1 DVB-S CI?
http://linuxtv.org/wiki/index.php/KNC1_TV-Station_DVB-S The wiki says "The card has a CI connector but it most probably isn't supported by Linux.". I've got the card and indeed, it doesn't seem to work. There is a ca0 in /dev/dvb/adapter0 but in Kaffeine the encrypted channels are still black. But I wonder, with the DVB-C version of this card, the CI works without a hitch (and I should know, I own one). According to the wiki the DVB-T version also has a working CI. I somehow can't imagine the CI on the DVB-S version is so much different. Or am I wrong and is the CI not supported because it requires a lot of reverse engineering nobody feels like doing for this card? Is there anything I could try? Tia, P. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] How do you find a channel in Kaffeine?
Hi, I now have a recent version of Kaffeine (repos Ubuntu 7.04 feisty fawn), but I'm still having this problem: how do you search for a channel? I was thinking of something like typing the name of the channel I'm looking for somehow, but can't find how to do this. This feature seems so obvious to me I can't imagine it not being there, so I probably overlook it. Or is it really not there? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
Luca Olivetti wrote: > En/na Michael Krufky ha escrit: > > >> The driver will not be removed -- I apologize if my previous email was >> misinterpreted. I only stated that the driver should stay in the v4l-dvb >> mercurial master branch and not be pushed upstream until the issues are >> resolved. Don't worry :-) > > > And I apologize for being so blunt and for not putting "retire" in > quotes, since I did understand what you were saying and I just meant > "retire" from upstream kernel submission. > > Bye Ok, good :). Still, Luca, you probably understand the driver the best, would you mind looking at the problems some people apparently have if you would get a working AF9005 for free? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Dual tuner DVB-T
Petr Nejedly wrote: > P. van Gaans wrote: > > >>>Hmm, well, iirc it was a 8mbit stream, but I'm not sure if I also tried >>>a 3mbit stream, but I bet that still wouldn't have worked reliably. Not >>>much difference anyway. Because no, not my switch, dvbstream needs >>>replacement. Multicast simply sucks, what you want are peer to peer >>>connections. My switch has no problems handling these at 100mbit. No >>>SoHo switch has. But multicast? There's a reason IPTV ISP's don't switch >>>you know.. For Multicast you should use satellites, DVB-T transmitters >>>or (coaxial) VHF/UHF cable infrastructures. Not UTP with SoHo switches! > > > > So, well, your problem lies elsewhere. You probably have some slow (10baseT) > device connected (VoIP adapter, old DreamBox, network printer adapter, > whatever), or a wireless AP with enabled mcast routing. > > I have no problem multicasting nearly complete TS over my small LAN, but only > after I moved my old VoIP phone to different subnet so mcast doesn't reach it. > And also after setting mcast_rate on my wifi AP to 54mbit (default is 1mbit as > wifi mcast has no MAC-level acknowledge channel available). > > I'm also able to reliably mcast >10mbit into a busy large corporate LAN (thing > hundred of switches), but only after properly setting central switches to > support IGMP snooping, so the traffic doesn't reach older printers. > > Nenik > > > That's right, my Freesco box has a 10mbit ethernet card. But I'm not planning on replacing it. I don't know about my WiFi. Anyway, I wouldn't use multicast in nearly any home situation. Too sensitive to older/wifi devices. And usually there is more than enough bandwidth to send all the desired channels p2p over a home network. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] af9005/mt2060 module unload failure
Luca Olivetti wrote: > En/na Michael Krufky ha escrit: > > >>:-/ ... Do you plan on getting a replacement? > > > No > > >>Perhaps you may contact the >>vendor so that they may send you a sample at no charge? > > > They should be send me a sample of the 9015 > > >>How did your stick die? Maybe the driver broke it? > > > I don't think so, nobody else complained, and there isn't much > difference between my driver and the windows one. In fact, looking > around in various forums (of windows users), there are many complaints > of this stick getting very hot. > Anyway, if you feel you should retire the driver, do so, I won't > complain. At leas I can consider it as feedback (which was sorely > lacking until now). > > Bye > -- > Luca > > > ___ > linux-dvb mailing list > linux-dvb@linuxtv.org > http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb > Please don't remove the driver.. Linux' support for cheap USB DVB-T sticks is far from complete (or the list of what's supported is entirely different from what really is supported), I wouldn't want to see this being removed. All the feedback I can give you is that it works fine for me, apart from scanning channels in Kaffeine, but that might also be my fault. I you were to get a new AF9005 for free, would you mind taking another look at the driver? (IIRC you live in the EU, don't you?) ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Dual tuner DVB-T
Rudy Zijlstra wrote: > P. van Gaans wrote: > >> Stephen Rowles wrote: >> >> >>> P. van Gaans wrote: >>> >>> >>> >>>> Hi, >>>> >>>> Honestly, I don't see the point of streaming the whole TS. If you >>>> want to record/watch more than 2 programs at a time, get more >>>> USB-DVB-T-sticks, as much as you want! >>>> >>>> And don't listen to tc. >>>> >>> >>> Well I want to run linux, so windows media is out, plus it doesn't do >>> what I want anyway :) >>> >>> The reason for the whole TS is one to avoid tuning channels all the >>> time.. pretty much all the TV we watch is on Mux 1 or Mux 2 down here >>> :). If I can stream the whole TS from 2 tuners, I pretty much get >>> every channel available to either watch or record all the time :) >>> >>> I also have some streaming software that requires this, which will be >>> running the backend recordings.. so I have to have whole TS support >>> from the hardware, and the ability to re-tune while streaming. >>> (similar to what VDR requires). >>> >>> This will mean not only can I watch tv, and record tv on my media >>> centre box, but else where on the network can watch the channels as I >>> will send the TS out over my network (not wireless!) >>> >>> >> >> >> Please keep this on the list. >> >> Forget about streaming the whole TS over your network. You can't. It >> won't work. Not on any home/soho-equipment. A simple 3mbit stream with >> dvbstream over my network KILLS my 100mbit switch. Don't even think >> about a whole TS, let alone two! >> >> > > What kind of rubbish are you using? I'm regularly close at 100mbps on my > home network with no problems > > Sorry, ethernet switch that falls over at 3 mbps is pure rubbish in my > book. It needs replacement. > > Rudy > Hmm, well, iirc it was a 8mbit stream, but I'm not sure if I also tried a 3mbit stream, but I bet that still wouldn't have worked reliably. Not much difference anyway. Because no, not my switch, dvbstream needs replacement. Multicast simply sucks, what you want are peer to peer connections. My switch has no problems handling these at 100mbit. No SoHo switch has. But multicast? There's a reason IPTV ISP's don't switch you know.. For Multicast you should use satellites, DVB-T transmitters or (coaxial) VHF/UHF cable infrastructures. Not UTP with SoHo switches! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Dual tuner DVB-T
Stephen Rowles wrote: > P. van Gaans wrote: > >> Hi, >> >> Honestly, I don't see the point of streaming the whole TS. If you want >> to record/watch more than 2 programs at a time, get more >> USB-DVB-T-sticks, as much as you want! >> >> And don't listen to tc. > > Well I want to run linux, so windows media is out, plus it doesn't do > what I want anyway :) > > The reason for the whole TS is one to avoid tuning channels all the > time.. pretty much all the TV we watch is on Mux 1 or Mux 2 down here > :). If I can stream the whole TS from 2 tuners, I pretty much get every > channel available to either watch or record all the time :) > > I also have some streaming software that requires this, which will be > running the backend recordings.. so I have to have whole TS support from > the hardware, and the ability to re-tune while streaming. (similar to > what VDR requires). > > This will mean not only can I watch tv, and record tv on my media centre > box, but else where on the network can watch the channels as I will send > the TS out over my network (not wireless!) > Please keep this on the list. Forget about streaming the whole TS over your network. You can't. It won't work. Not on any home/soho-equipment. A simple 3mbit stream with dvbstream over my network KILLS my 100mbit switch. Don't even think about a whole TS, let alone two! ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Dual tuner DVB-T
Hi, Honestly, I don't see the point of streaming the whole TS. If you want to record/watch more than 2 programs at a time, get more USB-DVB-T-sticks, as much as you want! And don't listen to tc. Stephen Rowles wrote: > Hi all, > > I have a very small form factor PC there is just about space for one PCI > card, so I could in theory fit a dual tuner card in there. > > I've looked through the wiki, but there isn't much data on which cards > really work, so I would love some advice on what solutions actually work > and people are using. > > There is the Nova-T 500, but in the wiki this mentions serious problems? > Does this fully work now, streaming the whole TS, working with VDR etc? > > Or there is the DViCO Fusion HDTV Dual, it seems to have some problems > though, can anyone using this confirm that it works with VDR, tuning > while streaming, and streaming the whole TS? > > Other than that I am stumped, I could go with 2 usb tuners if there are > any known good ones that will stream the whole TS? I was looking at the > freecom one, but apparently that won't send the whole transport stream. > > Thank you > > Steve. > > ___ > 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] DVB-T HD in Sweden
I can't get it to play with my stuff, possibly because of that SD program in the transport stream (with the mtv3.fi URL). Sorry. Peter Fassberg wrote: > Hi! > > >>Samples are always nice, I could look at it. > > > wget http://moonraker.fassberg.se/hd2.ts > > mplayer -tsprog 610 hd2.ts > > > > -- Peter > ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Asus P7131 hybrid analog/DVB-T
Soeren Sonnenburg wrote: On Tue, 2007-05-01 at 00:33 +0200, P. van Gaans wrote: I bought an Asus P7131 hybrid. I'm only trying to use the DVB-T part. It is recognized as a Philips TDA10046H DVB-T. On the card there are several Philips chips (I may need a magnifying glass to identify them if required) and a very flat tuner that I can't identify. mine just arrived saturday and the chips on there are: • tda 10046a • saa7131e Scan just throws "Tuning failed!!!" at me for every frequency, and the +167 trick doesn't seem to work either. Antenna and cable are OK. HG just updated. You've probably updated to the dvb-stable tree, but should have used the development branch instead, with which the card seems to work (at least it works for me for ~24hrs now). Anyone knows some more tricks or something I may have forgotten? try that tree: http://mcentral.de/hg/~mrec/v4l-dvb-av7110/ Soeren Thanks, I didn't know if I had to post my solution too (iirc I didn't). Apparently the card needs a firmware, without the firmware it acts like I experienced. With the firmware it runs fine (with /hg/v4l-dvb). Pim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
Luca Olivetti wrote: En/na Mauro Carvalho Chehab ha escrit: Em Qui, 2007-05-03 às 13:55 +0200, Markus Rechberger escreveu: Is there anything against it? Markus On 5/1/07, P. van Gaans <[EMAIL PROTECTED]> wrote: I managed to screw up my message for a second time so I'll just write a whole new message. Would it be possible to push the AF9005 drvier from /hg/~manu/af9005 to the main repo? I'm not sure Luca's line in his reply to me will get noticed so I thought this deserved a whole new message. For me, it is ok, providing that Luca or Manu send us a pull request. Is this a special mail or something, or can this message considered as a pull request? ;-) I've did a really quick look at his patch. There are some CodingStyle issues that should be fixed, like hexadecimal values using uppercase. At the pull request, I'll take a closer look at the patch, before adding my SOB. Most CodingStyle issues can easily by running a really small script, available at scripts/Lindent at the kernel tree. The script content is: #!/bin/sh indent -npro -kr -i8 -ts8 -sob -l80 -ss -ncs "$@" I ran Lindent before submitting the patch to Manu !?!? (of course, you need to have the indent package installed at the local machine) It is interesting also to mark newer drivers as EXPERIMENTAL for one or two kernel releases. If AF9005 is intended to be added on kernel 2.6.22, this should be done ASAP, since the merge window is closing. Otherwise, if the driver is not stable enough, the better is to wait to the end of the window, then add it to the tree. I prefer the last option. Well, I've been using my driver since december and I didn't suffer any crash or problems. I had reports of funky usage number in lsmod, but I think that's because of my use of symbol_request/symbol_put (though it doesn't happen on my machine): I separated the remote decoding functions in a standalone module, so I can substitute the implementation (in fact I have a different one on my page that interfaces with lirc). Other users have been using it with no problems (or at least with no more problems than under windows, as P. van Gaans can testify ;-) That's true, on Windows it doesn't work at all for me. I heard that from others too. It works much better on Linux ;). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Push AF9005 driver to main repo?
Mauro Carvalho Chehab wrote: Em Qui, 2007-05-03 às 13:55 +0200, Markus Rechberger escreveu: Is there anything against it? Markus On 5/1/07, P. van Gaans <[EMAIL PROTECTED]> wrote: I managed to screw up my message for a second time so I'll just write a whole new message. Would it be possible to push the AF9005 drvier from /hg/~manu/af9005 to the main repo? I'm not sure Luca's line in his reply to me will get noticed so I thought this deserved a whole new message. For me, it is ok, providing that Luca or Manu send us a pull request. I've did a really quick look at his patch. There are some CodingStyle issues that should be fixed, like hexadecimal values using uppercase. At the pull request, I'll take a closer look at the patch, before adding my SOB. Most CodingStyle issues can easily by running a really small script, available at scripts/Lindent at the kernel tree. The script content is: #!/bin/sh indent -npro -kr -i8 -ts8 -sob -l80 -ss -ncs "$@" (of course, you need to have the indent package installed at the local machine) It is interesting also to mark newer drivers as EXPERIMENTAL for one or two kernel releases. If AF9005 is intended to be added on kernel 2.6.22, this should be done ASAP, since the merge window is closing. Otherwise, if the driver is not stable enough, the better is to wait to the end of the window, then add it to the tree. I prefer the last option. For what it's worth (assuming you mean system stability with "stable"), the only issue I had was I couldn't scan much channels (many were ignored but not all) with Kaffeine (but I could with scan), and possibly that is solved when I get a stronger signal. When just watching reception with the AF9005 seems to be more stable (less hickups and blocks) than reception with a new revision MSI Mega Sky 580, maybe due to tuner sensitivity, but the AF9005 isn't known for being very sensitive. Probably more important is that I didn't have a single system crash with the driver. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Push AF9005 driver to main repo?
I managed to screw up my message for a second time so I'll just write a whole new message. Would it be possible to push the AF9005 drvier from /hg/~manu/af9005 to the main repo? I'm not sure Luca's line in his reply to me will get noticed so I thought this deserved a whole new message. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] AF9005 not installable anymore?
Luca Olivetti wrote: En/na P. van Gaans ha escrit: It seems the driver from /hg/~manu/af9005 can't be used on a recent v4l-dvb version? Possibly I'm just messing up or I should use another directory or something, but I could imagine that code that wasn't changed for 2 weeks gets incompatible. Any help? A new device has been added in the meantime, so the patch doesn't apply cleanly anymore. You have to hand edit linux/drivers/media/dvb/dvb-usb/Kconfig adding the missing lines at the end: config DVB_USB_AF9005 tristate "Afatech AF9005 DVB-T USB1.1 support" depends on DVB_USB select DVB_TUNER_MT2060 if !DVB_FE_CUSTOMISE help Say Y here to support the Afatech AF9005 based DVB-T USB1.1 receiver and the TerraTec Cinergy T USB XE (Rev.1) config DVB_USB_AF9005_REMOTE tristate "Afatech AF9005 default remote control support" depends on DVB_USB_AF9005 help Say Y here to support the default remote control decoding for the Afatech AF9005 based receiver. Or just use the complete /hg/~manu/af9005 tree. Would it be possible to push the driver to the main repository? Bye Yes, that's what the error was about. Pushing it to the main repository would be great (wrote that in the title of this message as well to draw some attention, I'm not sure who is responsible for this). *second try* why isn't linux-dvb in the reply-to.. *shame* ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Asus P7131 hybrid analog/DVB-T
I bought an Asus P7131 hybrid. I'm only trying to use the DVB-T part. It is recognized as a Philips TDA10046H DVB-T. On the card there are several Philips chips (I may need a magnifying glass to identify them if required) and a very flat tuner that I can't identify. Scan just throws "Tuning failed!!!" at me for every frequency, and the +167 trick doesn't seem to work either. Antenna and cable are OK. HG just updated. Anyone knows some more tricks or something I may have forgotten? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] AF9005 not installable anymore?
It seems the driver from /hg/~manu/af9005 can't be used on a recent v4l-dvb version? Possibly I'm just messing up or I should use another directory or something, but I could imagine that code that wasn't changed for 2 weeks gets incompatible. Any help? ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
Luca Olivetti wrote: with or without the suggested modification? With. But Kaffeine is still slow (also with modification), and scan is faster (and picks up more channels). ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
Luca Olivetti wrote: En/na P. van Gaans ha escrit: Sorry, that doesn't seem to help, I don't see any difference at all. It doesn't seem to hurt either. Not that I was really expecting it to help (after all it cannot report an mpeg sync without a tps lock, or can it?), but it was the only thing I could think of driver side. Bye Sorry Luca, but my e-mail client automatically starts at the top of the message (Thunderbird), in any e-mail conversation with companies I receive top-posted replies (and they expect me to top-post back or else I risk not getting a response) and trust me it's really hard to remember to do a different posting style just for one person. I'm trying but it's so easy to forget. If bottom-posting were the "standard" I would use it by default but it simply isn't, at least not in e-mail. It's not intentional, I don't mean to annoy you but how can I remember? I gave "scan" a go and scan is a lot faster than Kaffeine. And good thing, more frequencies allow to be scanned, but still not all. On the ones that don't work I get "(tuning failed)". But if the driver wouldn't be the problem I couldn't explain why the MSI scans (also in Kaffeine) without problems. So "scan" works better.. I'm not far enough into the technical stuff to explain this. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
Sorry, that doesn't seem to help, I don't see any difference at all. It doesn't seem to hurt either. Some extra info: I see a lot of "Getting frontend event" and "polling" from Kaffeine. Especially a lot of "polling". Often looks like: polling Getting frontend event polling Getting frontend event polling Getting frontend event polling polling polling polling polling polling And after some more polling it gives up and tries another frequency where the same thing repeats. Just two times "getting" happens as well. Sometimes more "getting" also happens. But almost always when it is done "getting" it keeps polling for a while before switching to another frequency. Sometimes I get "Invalid section length or timeout : pid=17" or "Invalid section length or timeout : pid=0". On 762Mhz however I can make a successful scan (reproducable), almost immediatly it starts loading the channels. Takes a few sec and looks like this: polling, getting, polling, getting, polling, getting, Event: Frequency: 76200 and from there on it starts loading channels normally. The polling/getting seems to go faster here as well. Maybe this makes the problem more clear (or maybe it doesn't, I'm not sure). P. Luca Olivetti wrote: En/na P. van Gaans ha escrit: For my feeling speed isn't the problem, but where do I increase the timeout? I just saw that there isn't one in the scan utility, and probably this isn't the (only) problem: I report FE_HAS_LOCK when the af9005 says that it has seen the mpeg sync byte, while I use the tpsd_lock to indicate FE_HAS_CARRIER. Probably FE_HAS_LOCK should depend on both conditions. Try, as a test, in af9005-fe.c, function af9005_fe_read_status, where you see if (temp) *stat |= FE_HAS_SYNC | FE_HAS_VITERBI | FE_HAS_LOCK; change the condition to if (temp && (*stat & FE_HAS_CARRIER)) and tell me if you can scan this way. Bye ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] possible afatech af9005 bug
For my feeling speed isn't the problem, but where do I increase the timeout? I understand it's in the settings with 0.8.4 but my version is older (and I don't want to upgrade before my backup machine is back up. I'm waiting for a new PSU for it). Maybe I'll just wait a while, upgrade then so I get the new Kaffeine. If someone knows if I can also set it somewhere in a configuration file I'll try that first, otherwise I'll just wait. However I do note scanning takes very long for my feeling, so maybe.. Luca Olivetti wrote: En/na P. van Gaans ha escrit: So the bug is: you can't scan for channels with the stick. Well, hardly ever. On some specific frequency I do get results with the Afatech while scanning, but that's just one frequency filled with mostly (worthless) encrypted channels. With the MSI this is no problem, and if I use the channellist from the MSI on the Afatech it also works as expected. Only scanning with the Afatech itself somehow won't work properly. My Kaffeine version btw is 0.7.1 (will upgrade soon, Ubuntu 6.06), but I feel it shouldn't really matter that much, but to be complete. Maybe (just maybe) the afatech is slower/too slow to lock on a channel so kaffeine will time-out? Did you try with plain old "scan" and/or raising the timeut (if possible)? I don't remember how I got my channel list, but I think I primed it with scan then vdr did the rest. Bye ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] possible afatech af9005 bug
Yes, I'm back with my cheapass USB DVB-T stick. I recently bought a MSI Mega Sky 580 (found one at the back of the shelves) because the afatech didn't seem to be working very well. After some playing with the Mega Sky (it works), I plugged back in the Allnet all2006 aka Afatech af9005. Now comes the surprise: some pretty weak channels (transmitter 50km away) work pretty well, with only a few blocks here and there (still definitely watchable). BUT: that is with the channellist I made with the MSI stick. Also the Belgium channels (30km away) now work, and they work almost flawless! (few blocks here as well) and the last interesting FTA location here, Goes, 27km away, works too. This stick isn't that bad at all! Okay, the MSI seems to be better (no blocks I think instead of a few), but for the money the Afatech is reasonable. Earlier I just wasn't able to get any channel into my channellist, so I thought the tuner was extremely unsensitive and couldn't test any channel actually playing. But if you test the channels themselves instead of scanning for them, the channels themself work. Actually getting a channellist (with Kaffeine) for these channels, is still impossible with the Afatech, and I think that could be a bug. See: on the frequencies I scan, I do get frequency lists, so the stick sees something. The LED also says it's locking. And if I use a frequency list made with another DVB-T device, these channels often work mostly fine. It's still not the most sensitive tuner, but now that the channels are actually playing prove to me that at least it works. So the bug is: you can't scan for channels with the stick. Well, hardly ever. On some specific frequency I do get results with the Afatech while scanning, but that's just one frequency filled with mostly (worthless) encrypted channels. With the MSI this is no problem, and if I use the channellist from the MSI on the Afatech it also works as expected. Only scanning with the Afatech itself somehow won't work properly. My Kaffeine version btw is 0.7.1 (will upgrade soon, Ubuntu 6.06), but I feel it shouldn't really matter that much, but to be complete. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
Luca Olivetti wrote: En/na P. van Gaans ha escrit: (I don't post this message to the list) In your short replies I read I'm probably annoying you. Not at all! I'm sorry if it appears that way (I *am* annoyed by top posting though ;-) My replies aren't any longer because I don't have much more to say: I live very near to the transmitter and I have poor reception of one mux and the rest are so-so (both when I tried it under windows to sniff the data and under linux). Other users say it works fine for them, while other have the same reception problems. The commented out code was to try the opposite problem (too strong a signal) and according to Thomas Pinz it shouldn't really change anything, so don't bother trying it, it won't solve your problem as it didn't solve mine. I'm sorry. I'm no developer, I don't understand the technical stuff so I ask stupid questions. I'll go look for another solution, I guess the Afatech just isn't sensitive enough for my signal. Thanks for your help. This is probably a stupid question, but, you're using a roof-top antenna, and not the joke provided with the stick, right? Bye (I post this to the list again because it might be of some use to other users) I was annoyed by the joke that comes with the stick, well, in fact I was more annoyed by the fact the cable to convert the stick-connector to coax was missing. I cut the cable with the "joke" and screwed a coax connector onto it. My antenna isn't really on the roof, but it is just under it, indoors. It is impossible to locate the antenna at any higher point indoors. It is approx. 10 meters above the ground and on any other receiver I can see four different transmitters on it all around me. But I guess the signal isn't strong enough for the Afatech, quite possible since all my other receivers are quite sensitive. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Afatech af9005 unstable reception [added: mt2060 gain control?]
Luca Olivetti wrote:
En/na P. van Gaans ha escrit:
[please, keep this on list, and avoid top posting, I hate it and I was
tempted to ignore your message ]
Thanks, I tried but I get a load of compilation errors. I don't know
if I have a mt2060.
Look in the syslog, you should see an "MT2060: successfully identified"
or if you have a qt1010 "Quantek QT1010 successfully identified.".
I don't really know what I'm doing wrong, I tried
Oop, there's an error there. In the second block between #if 0...#endif
there's a "if (strong) {" line, change that to "if (state->strong) {"
debugging it but my little PHP knowledge is not enough to debug C
code. I just uncommented everything that said something about the
strong signal, maybe I uncommented too much?
there are just two sections of code in function af9005_fe_read_status
enclosed in "#if 0" just change that to "#if 1".
To the rest of the list, maybe there should be a standardized way to
adjust tuner gain in dvb_tuner_ops or is the mt2060 the only tuner with
adjustable gain (even if in its current incarnation mt2060.c doesn't do
it)?
Bye
Sorry, I forgot to add the linux-dvb address. But that should be in the
reply-to field anyway imho, or available as a setting. I simply forgot
to add.
What, top-posting? Wikipedia is helpful.. I didn't know, I prefer
top-posting, saves scrollingtime. In fact I was wondering why you were
bottom-posting. I'm used to forums, not to mailinglists. On forums you
decide yourself if you want to see everything top or bottomposted..
Seriously I didn't know it was a crime!
So I understand I have to change the 0 into a 1 and change state->strong
to temp? Not remove the # for if? If that's all correct I guess it
didn't really help. Maybe you just get what you pay for then.. On other
receivers I get signals from 60 kilometers away, on the afatach vitually
nothing (closest transmitter is 27 kilometer). Are you supposed to tape
the antenna to the transmitter?
But wait.. *looks at laptop*, suddenly the afatech stick reads the
channels from Wavre, Belgium. That's over 80 kilometers away and a
pretty weak transmitter. The much stronger signal from Schoten (35
kilometers or so) is blissfully ignored. The image contains some blocks
but it's better than the radio I had earlier.
Strange stuff..
___
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Kaffeine universal DVB-T scan file
Christoph Pfister wrote: Hi, 2007/4/14, P. van Gaans <[EMAIL PROTECTED]>: Say you live in The Netherlands. Frequencies change here all the time, and QAM settings and stuff also change all the time. Say you're living on the border, like me. I receive channels from The Netherlands and Belgium at the same time, but there's no scan file for that. There will also always be locations missing in the list. And what if you simply have no clue about where you live? Nobody thinks of them! Then again, nobody knows where they are ;-) So here is the solution: a file that'll make Kaffeine scan all UHF channels with "AUTO" for the QAM and other stuff, will be sufficient in most countries although scanning takes a bit longer. I hope it makes it into some next version of Kaffeine :). Pim There are enough cases where such a file doesn't work (think of offsets, 7 mhz transponders etc). Responsible for such complete scannings are the apps (kaffeine has auto scan which does pretty much the same as your file does and it tries offsets iirc). Christoph I couldn't find that option in my Kaffeine. Probably old version. Too bad. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] Technisat Airstar USB supported no longer
Hi, Sorry for not being complete. I do have the latest drivers (download today), and I have never seen the box working on Linux, but know from the Wiki that it should. I tried a few months ago as well, it didn't work back then either but back then I wasn't sure if it was my fault or something else. Back then I also had the latest drivers, with the stock kernel the device wouldn't be detected at that moment. There is a chance my box is a new revision. There's still the flexcop and MT352 inside though, I have no idea what could be new. Trent Piepho wrote: On Sat, 14 Apr 2007, P. van Gaans wrote: Now that I've seen my Afatech locking I'm sure my Linux distro, kaffeine and drivers are all fine. However my Technisat Airstar USB (that has been supported since quite a while) simply won't lock on anything and read no channel or whatever frequency. It's detected, yes, and it stops there. And yes, it works just fine on Bill's OS, the antenna is fine as well and the -/+167 trick doesn't help. I'm willing to help any developer to make it supported again. I already updated the wiki. Get the latest drivers from the linuxtv.org Hg repository if you haven't already. If they don't work and it used to work under linux, try updating to an older version and see if you can find where it broke. If you know it worked in kernel 2.6.x, you can look at the release date for the _previous_ kernel and update v4l-dvb hg to around a week after that date. For example, if it worked on 2.6.18, then check 2.6.17's release date, Jun 18th, and get a revision from around a week after that, say revision 4262. That's about what will have been in 2.6.18. There is no revision that exactly matches a given kernel but, that will be reasonably close. ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Technisat Airstar USB supported no longer
Hi, Now that I've seen my Afatech locking I'm sure my Linux distro, kaffeine and drivers are all fine. However my Technisat Airstar USB (that has been supported since quite a while) simply won't lock on anything and read no channel or whatever frequency. It's detected, yes, and it stops there. And yes, it works just fine on Bill's OS, the antenna is fine as well and the -/+167 trick doesn't help. I'm willing to help any developer to make it supported again. I already updated the wiki. Pim ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Kaffeine universal DVB-T scan file
Say you live in The Netherlands. Frequencies change here all the time, and QAM settings and stuff also change all the time. Say you're living on the border, like me. I receive channels from The Netherlands and Belgium at the same time, but there's no scan file for that. There will also always be locations missing in the list. And what if you simply have no clue about where you live? Nobody thinks of them! Then again, nobody knows where they are ;-) So here is the solution: a file that'll make Kaffeine scan all UHF channels with "AUTO" for the QAM and other stuff, will be sufficient in most countries although scanning takes a bit longer. I hope it makes it into some next version of Kaffeine :). Pim # All # T freq bw fec_hi fec_lo mod transmission-mode guard-interval hierarchy T 47400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 48200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 49000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 49800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 50600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 51400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 52200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 53000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 53800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 54600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 55400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 56200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 57000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 57800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 58600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 59400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 60200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 61000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 61800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 62600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 63400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 64200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 65000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 65800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 66600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 67400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 68200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 69000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 69800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 70600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 71400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 72200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 73000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 73800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 74600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 75400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 76200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 77000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 77800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 78600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 79400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 80200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 81000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 81800 8MHz AUTO NONE AUTO AUTO AUTO NONE T 82600 8MHz AUTO NONE AUTO AUTO AUTO NONE T 83400 8MHz AUTO NONE AUTO AUTO AUTO NONE T 84200 8MHz AUTO NONE AUTO AUTO AUTO NONE T 85000 8MHz AUTO NONE AUTO AUTO AUTO NONE T 85800 8MHz AUTO NONE AUTO AUTO AUTO NONE ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] Afatech af9005 unstable reception
My last question for a cheap USB DVB-T stick took a whole other turn. Earlier I bought an Allnet all2006 USB DVB-T stick, just praying it would run on Linux. It didn't. At least it didn't back then. On Windows I figured out it's an Afatech AF9005 clone. On Google I figured out there is a driver and firmware here, recently written: http://ventoso.org/luca/af9005/ Happy was I! I installed everything and yes, the device is detected. But it hardly ever locks correctly on a frequency. I see the "lock" thingie in Kaffeine light up, as well as a blue led on the stick. But few times do I read some channel information. Once I was able to read the radio transponder, but the radio stutters. That doesn't really say much, radio stutters with another DVB-T device on Windows as well at that frequency, and I have no idea if my reception or buggy software is the problem here. The main problem is I can't read all channels. I'm missing almost all the channels. The -/+167 trick didn't help. Pim ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] cheap USB DVB-T stick (Club3D ZAP-TV240M?)
Hi, Thanks for your reply. I've seen the Digitelmo for €14,95 a while ago, but I would really like a USB stick. I wanted to buy the Freecom but was checking out if the seller was reliable - and at the same time he upped the price from €20 to €30. Knowing what profit he makes now I feel less like buying :-(. Does anyone know if the following device would work: http://www.club3d.nl/index.php/products/zaptv/item/14 (Club3D ZAP-TV240M)? The 250M is supported but twice as expensive. Pim Tobias Stoeber wrote: Hi, well, I bought my Yakumo ~9 month ago at 39,95 Euro (local "real" super market), the price in Ebay was around 59 Euro at that time, so it was sold out rather quickly. But they got new ones and actually they still have a few in the shelves now. Regarding Ebay: well, it really depends. There are times where prices are low with a few sellers on different products, a week later prices are high again. I don'*t know, if the stick is still in production. As there are some fashions of Freecom/Yakumo sticks (to tell you have to look at the usb ids), I can imagine, that maybe a seller has aquired some quantities of an older model to sell for a lower price. In case of linux support, its always wise not to jump to the newest (unsupported) product. I'm very happy with my Yakumo (ids 14aa:0225 / 14aa:0226), so I can really recommend it. For an older notebook I purchased a PCMCIA card "Viola DIGITELMO 1", then at also 39 Euro. It it still sold here in local markets for about 69 Euro and in the internet it's "given away" for 24,95 (!) http://www.pollin.de/shop/detail.php?pg=OA==&a=NzMyOTkyOTk=&w=Mjk4OTM5&ts=0 Unfortunately the linux driver is not complete yet. The windows driver is a mess and the card gains quite some temperature while in use :( Okay, good luck with your DVB-T experience :) Tobias P. van Gaans schrieb: Thanks! The Freecom used to be very expensive, on eBay too, this must have changed. I hope the sticks themselves are still the same. A while ago I was looking for the Yakumo too, but just when I wanted to buy it was taken of the shelves. I'll try this. Tobias Stoeber wrote: Hi again, regarding the Freecom Stick, just try Ebay: http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=170096510925&category=136539 http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=130096954739&category=136539 http://item.express.ebay.de/ws/eBayISAPI.dll?ExpressItem&item=270105845628 http://cgi.ebay.de/ws/eBayISAPI.dll?ViewItem&item=130088651308&category=136539 Regards, Tobias P. van Gaans schrieb: I completely lost it here. I'm trying to buy an affordable (max 35 euro) USB DVB-T stick in The Netherlands or Germany. But the wiki is completely outdated and I have no idea how to figure out what stick works. Nothing from the Wiki is on the shelves, apart from the Freecom for 60 euro here and there. The MSI Mega Sky 580, now finally supported, was taken of the shelves yesterday (seriously). I only have two real requirements: possibility to attach an external antenna, and affordable. And supported by Linux of course. Any suggestions? Pim ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb ___ linux-dvb mailing list [EMAIL PROTECTED] http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
[linux-dvb] cheap USB DVB-T stick
I completely lost it here. I'm trying to buy an affordable (max 35 euro) USB DVB-T stick in The Netherlands or Germany. But the wiki is completely outdated and I have no idea how to figure out what stick works. Nothing from the Wiki is on the shelves, apart from the Freecom for 60 euro here and there. The MSI Mega Sky 580, now finally supported, was taken of the shelves yesterday (seriously). I only have two real requirements: possibility to attach an external antenna, and affordable. And supported by Linux of course. Any suggestions? Pim ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Re: [linux-dvb] [BUG] flexcop lockdep
I've got a Technisat Airstar USB that doesn't lock, so I'd like to try the patch whatever it's for. How do I apply it? Borgi2008 wrote: Hello, i've created a bugfixes. Hope it could helps you. Hendrik Borghorst ___ 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] Technotrend S-1500 with CI: common interface is not detected
I'll try to keep it short. I've got a TT S-1500 and the CAM can not be seen in /dev/dvb/adapter. It doesn't work either, no encrypted channel lights up. FTA channels do. However, on my KNC1 DVB-C with Cineview, there is a "ca0" in /dev/dvb/adapter and in Kaffeine I can watch encrypted channels. In dmesg I see info for the KNC1 card when ejecting/inserting CAMs, not a single line with info about the CI on the TT. I don't see in what other way I could possibly connect the TT budget CI to the card (the hardware). The CAM is not upside-down. The CAM was tested in another receiver and works. I have the latest v4l-dvb drivers. Ubuntu 6.10 Edgy. Any help is appreciated. ___ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
