<div dir="ltr"><div class="gmail_quote">On Tue, Jan 27, 2009 at 11:27 PM, Manu Abraham <span dir="ltr"><<a href="mailto:abraham.manu@gmail.com">abraham.manu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Alex Betis wrote:<br>
> On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham <<a href="mailto:abraham.manu@gmail.com">abraham.manu@gmail.com</a>>wrote:<br>
><br>
>> Alex Betis wrote:<br>
>>>> It won't. All you will manage to do is burn your demodulator, if you<br>
>> happen<br>
>>>> to<br>
>>>> be that lucky one, with that change. At least a few people have burned<br>
>>>> demodulators by now, from what i do see.<br>
>>>><br>
>>> What are the symptoms of burned demodulator? How can someone know if its<br>
>>> still ok?<br>
>> The first time i saw it was that the DVB-S2 demod was returning no<br>
>> carrier. After some time it was stating timing error for DVB-S as<br>
>> well. Finally it all ended up with demodulator I2C ACK failure, and<br>
>> eventually a frozen machine after a week (my test boxes run throughout)<br>
>><br>
>> Touching the demodulator, i happened to have almost a burned finger.<br>
>> I wanted to know whether this was a single case. During the<br>
>> development phase, i did mention it to Julian about this, since he<br>
>> was the very first person to test for the stb0899 driver. He<br>
>> jovially laughed about a burned demodulator and a finger, left his<br>
>> machine on after i did some tests on it. Eventually he too had the<br>
>> same results. Finally we changed cards.<br>
><br>
> What frequency did you use to burn it?<br>
<br>
<br>
It was a long time back, don't remember. It has nothing to do with<br>
the frequency of the transponder, but just the master clock. You can<br>
run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and<br>
sufficient.<br>
<br>
<br>
> I didn't see anyone here on the list that reported a hardware failure so<br>
> far.<br>
<br>
May god help you. I didn't know that you knew more than the<br>
demodulator manufacturer !</blockquote><div>Please speak for yourself, I never said I know more than a manufacturer.<br>I wrote a fact.<br>Intel also rate their chips and everybody overclocks them to crazy ratings.<br> <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
<br>
> By the way, Igor returned the chip frequency for 27.5 channels to 99MHz and<br>
> raised it a bit for higher SR channels, so there is no danger for majority<br>
> of the users.<br>
<br>
Ok, be happy with his change and keep quiet. 135Mhz is out of bounds<br>
of the hardware specification. You are on your own. Raising the<br>
master clock, doesn't bring you any advantage.</blockquote><div>Did someone overclock you as well? <br>Chill out! <br>It would be better if you'll be more productive instead of quieting people who try to help.<br>
<br>Again, I'm commenting facts. As I saw from the reports the overclock seems to help with the problem.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>