Skip to contentSkip to conversation

Technotrend Budget S2-3200 Digital artefacts on HDchannels

linux-dvb Newsy Paper 11 participants 40 messages Jan 26, 2009 – Feb 14, 2009 2 messages not in the archive Media (V4L/DVB)

lore
Share & tools
lore
#0 lore raw

the transponders you don't get lock are problem transponders of s2-3200. The driver is still not able to lock on dvb-s2 30000 3/4 transponders :(

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's version). or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

regards

Newsy

--- Newsy Paper <[email protected]> schrieb am Mo, 26.1.2009:

Quoted 54 lines

Von: Newsy Paper <[email protected]>
Betreff: Re: [linux-dvb] Technotrend Budget S2-3200 Digital artefacts on HDchannels
An: [email protected]
Datum: Montag, 26. Januar 2009, 13:09
the transponders you don't get lock are problem
transponders of s2-3200.
The driver is still not able to lock on dvb-s2 30000 3/4
transponders :(

Which software do you use to play HD content? you need either xine-lib 1.2 with external ffmpeg (recent developer's version).
or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

regards

Newsy

--- Tomas Drajsajtl <[email protected]> schrieb am Mo, 26.1.2009:

Quoted 2 lines

Von: Tomas Drajsajtl <[email protected]>
Betreff: Re: [linux-dvb] Technotrend Budget S2-3200

Digital artefacts on HDchannels

Quoted 3 lines

An: [email protected], [email protected]
Datum: Montag, 26. Januar 2009, 8:14

Quoted 1 line

Nat Geo HD and Histoy Channel HD are the only two

HD

Quoted 9 lines

channels I can

Quoted 1 line

lock, and I have problems with digital artefacts,

lines across the

Quoted 1 line

screen missing data and tons of errors from the

frontend. See below for

Quoted 1 line

error log.

Hi Jonas,
just guessing - try another card slot. If there are

more

Quoted 2 lines

devices on one IRQ
the transfer speed from the card can be lower and

causing

Quoted 4 lines

problems at
channels with higher bitrate. I had similar colision between PCI network and
sound cards. When I moved one card to another slot,

the

Quoted 6 lines

problem was solved.

Regards,
Tomas

Quoted 7 lines
Quoted 6 lines

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead
[email protected]
[email protected]

http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#1 lore raw
Quoted 10 lines · Newsy Paper

the transponders you don't get lock are problem transponders of s2-3200. The driver is still not able to lock on dvb-s2 30000 3/4 transponders :(

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's version). or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

regards

Newsy

I can confirm this. I use S30W (Hispasat) and one of the providers, Meo, broadcasts everything on DVB-S2 30000 3/4.
I can't get a lock on any of the transponders/channels. And to make matters worse, not even scan-s2 can get a really usable channel list. I had to build the list by hand, according to
http://pt.kingofsat.net/pack-meo.php page.

And it still doesn't work.

I use vdr-xine and xineliboutput with vdr 1.7.0 and up, plus xine-vdpau to no avail.

What's the point of having a DVB-S2 card if we can't tune to those channels? What's missing in the S2-3200 drivers?

Chris

#2 lore raw
Quoted 10 lines · Newsy Paper

the transponders you don't get lock are problem transponders of s2-3200. The driver is still not able to lock on dvb-s2 30000 3/4 transponders :(

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's version). or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

regards

Newsy

I can confirm this. I use S30W (Hispasat) and one of the providers, Meo, broadcasts everything on DVB-S2 30000 3/4.
I can't get a lock on any of the transponders/channels. And to make matters worse, not even scan-s2 can get a really usable channel list. I had to build the list by hand, according to
http://pt.kingofsat.net/pack-meo.php page.

And it still doesn't work.

I use vdr-xine and xineliboutput with vdr 1.7.0 and up, plus xine-vdpau to no avail.

What's the point of having a DVB-S2 card if we can't tune to those channels? What's missing in the S2-3200 drivers?

Chris

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#3 lore raw
Quoted 22 lines · Chris Silva
Quoted 5 lines · Newsy Paper

the transponders you don't get lock are problem transponders of s2-3200. The driver is still not able to lock on dvb-s2 30000 3/4 transponders :(

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's

version).

Quoted 1 line

or xine-vdpau (if you have a NVIDIA graka that supports h264 hw

acceleration).

Quoted 4 lines

regards

Newsy

I can confirm this. I use S30W (Hispasat) and one of the providers, Meo, broadcasts everything on DVB-S2 30000 3/4.
I can't get a lock on any of the transponders/channels. And to make matters worse, not even scan-s2 can get a really usable channel list. I had to build the list by hand, according to
http://pt.kingofsat.net/pack-meo.php page.

Quoted 7 lines

And it still doesn't work.

I use vdr-xine and xineliboutput with vdr 1.7.0 and up, plus xine-vdpau to no avail.

What's the point of having a DVB-S2 card if we can't tune to those channels? What's missing in the S2-3200 drivers?

What drivers do you use?
I saw that Igor did some changes in his repository to lock on high SR channels.

Quoted 10 lines

Chris

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#4 lore raw
Quoted 29 lines · Alex Betis
Quoted 28 lines · Chris Silva
Quoted 9 lines · Newsy Paper

the transponders you don't get lock are problem transponders of s2-3200. The driver is still not able to lock on dvb-s2 30000 3/4 transponders :(

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's version).
or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

Quoted 3 lines

regards

Newsy

I can confirm this. I use S30W (Hispasat) and one of the providers, Meo, broadcasts everything on DVB-S2 30000 3/4.
I can't get a lock on any of the transponders/channels. And to make matters worse, not even scan-s2 can get a really usable channel list. I had to build the list by hand, according to
http://pt.kingofsat.net/pack-meo.php page.

And it still doesn't work.

I use vdr-xine and xineliboutput with vdr 1.7.0 and up, plus xine-vdpau to no avail.

Quoted 7 lines
Quoted 2 lines

What's the point of having a DVB-S2 card if we can't tune to those channels? What's missing in the S2-3200 drivers?

What drivers do you use?
I saw that Igor did some changes in his repository to lock on high SR channels.

I've tried with both v4l-dvb and Igor repository. Haven't tried with latest changes Igor made.

I'll try it tonight and comment on the state.

But for now, I'm somewhat disappointed. It's been over 6 months trying to make DVB-S2 transponders to work and no result to show.

But wey... DVB-S works perfectly.

Chris

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#5 lore raw
Quoted 41 lines · Chris Silva
Quoted 29 lines · Alex Betis
Quoted 28 lines · Chris Silva
Quoted 9 lines · Newsy Paper

the transponders you don't get lock are problem transponders of s2-3200. The driver is still not able to lock on dvb-s2 30000 3/4 transponders :(

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's version).
or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

Quoted 3 lines

regards

Newsy

I can confirm this. I use S30W (Hispasat) and one of the providers, Meo, broadcasts everything on DVB-S2 30000 3/4.
I can't get a lock on any of the transponders/channels. And to make matters worse, not even scan-s2 can get a really usable channel list. I had to build the list by hand, according to
http://pt.kingofsat.net/pack-meo.php page.

And it still doesn't work.

I use vdr-xine and xineliboutput with vdr 1.7.0 and up, plus xine-vdpau to no avail.

Quoted 7 lines
Quoted 2 lines

What's the point of having a DVB-S2 card if we can't tune to those channels? What's missing in the S2-3200 drivers?

What drivers do you use?
I saw that Igor did some changes in his repository to lock on high SR channels.

I've tried with both v4l-dvb and Igor repository. Haven't tried with latest changes Igor made.

Quoted 9 lines

I'll try it tonight and comment on the state.

But for now, I'm somewhat disappointed. It's been over 6 months trying to make DVB-S2 transponders to work and no result to show.

But wey... DVB-S works perfectly.

Chris

Latest changes I can see at
http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

Chris

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#6 lore raw
Quoted 56 lines · Chris Silva
Quoted 1 line · Chris Silva

On Mon, Jan 26, 2009 at 3:44 PM, Alex Betis <[email protected]>

Quoted 1 line · wrote:
Quoted 1 line

On Mon, Jan 26, 2009 at 5:41 PM, Chris Silva <[email protected]>

Quoted 4 lines · wrote:
Quoted 4 lines
Quoted 4 lines
Quoted 1 line · Newsy Paper

the transponders you don't get lock are problem transponders of

s2-3200.

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

The driver is still not able to lock on dvb-s2 30000 3/4 transponders

:(

Quoted 34 lines
Quoted 23 lines
Quoted 23 lines
Quoted 10 lines

Which software do you use to play HD content?
you need either xine-lib 1.2 with external ffmpeg (recent developer's version).
or xine-vdpau (if you have a NVIDIA graka that supports h264 hw acceleration).

regards

Newsy

I can confirm this. I use S30W (Hispasat) and one of the providers, Meo, broadcasts everything on DVB-S2 30000 3/4.
I can't get a lock on any of the transponders/channels. And to make matters worse, not even scan-s2 can get a really usable channel list. I had to build the list by hand, according to
http://pt.kingofsat.net/pack-meo.php page.

And it still doesn't work.

I use vdr-xine and xineliboutput with vdr 1.7.0 and up, plus xine-vdpau to no avail.

Quoted 7 lines
Quoted 2 lines

What's the point of having a DVB-S2 card if we can't tune to those channels? What's missing in the S2-3200 drivers?

What drivers do you use?
I saw that Igor did some changes in his repository to lock on high SR channels.

I've tried with both v4l-dvb and Igor repository. Haven't tried with latest changes Igor made.

Quoted 9 lines

I'll try it tonight and comment on the state.

But for now, I'm somewhat disappointed. It's been over 6 months trying to make DVB-S2 transponders to work and no result to show.

But wey... DVB-S works perfectly.

Chris

Quoted 6 lines

Latest changes I can see at
http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

Quoted 10 lines

Chris

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#7 lore raw
Quoted 11 lines · Alex Betis

Latest changes I can see at

Quoted 5 lines

http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

Regards,
Manu

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#8 lore raw
Quoted 14 lines · Manu Abraham
Quoted 10 lines · Alex Betis
Quoted 7 lines

Latest changes I can see at
http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

Quoted 9 lines

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

Regards,
Manu

I don't know if the drivers or not but my card (TT S2-3650 CI) broke, got my money back
from the company and i ordered a Tevii S650 from Germany which will arrive this week.

Faruk

#9 lore raw
In reply to Manu Abraham
Quoted 17 lines · Manu Abraham
Quoted 11 lines · Alex Betis

Latest changes I can see at

Quoted 5 lines

http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

Quoted 5 lines

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if its still ok?

Does your mantis driver work ok with such channels?

Quoted 6 lines

Regards,
Manu

Quoted 6 lines

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#10 lore raw
Quoted 15 lines · Alex Betis
Quoted 13 lines · Manu Abraham
Quoted 9 lines · Alex Betis

Latest changes I can see at

Quoted 5 lines

http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

Quoted 7 lines
Quoted 5 lines

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if its still ok?

The first time i saw it was that the DVB-S2 demod was returning no carrier. After some time it was stating timing error for DVB-S as well. Finally it all ended up with demodulator I2C ACK failure, and eventually a frozen machine after a week (my test boxes run throughout)

Touching the demodulator, i happened to have almost a burned finger. I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since he was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left his machine on after i did some tests on it. Eventually he too had the same results. Finally we changed cards.

Quoted 2 lines

Does your mantis driver work ok with such channels?

I don't have such channels. Tested with a max of 27.5 MSPS

Regards,
Manu

#11 lore raw
Quoted 15 lines · Manu Abraham
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator, if you

happen

Quoted 6 lines
Quoted 4 lines

to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if its still ok?

The first time i saw it was that the DVB-S2 demod was returning no carrier. After some time it was stating timing error for DVB-S as well. Finally it all ended up with demodulator I2C ACK failure, and eventually a frozen machine after a week (my test boxes run throughout)

Quoted 7 lines

Touching the demodulator, i happened to have almost a burned finger. I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since he was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left his machine on after i did some tests on it. Eventually he too had the same results. Finally we changed cards.

What frequency did you use to burn it?

I didn't see anyone here on the list that reported a hardware failure so far.

By the way, Igor returned the chip frequency for 27.5 channels to 99MHz and raised it a bit for higher SR channels, so there is no danger for majority of the users.

Quoted 10 lines
Quoted 3 lines

Does your mantis driver work ok with such channels?

I don't have such channels. Tested with a max of 27.5 MSPS

Regards,
Manu

Quoted 6 lines

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#12 lore raw
Quoted 24 lines · Alex Betis
Quoted 14 lines · Manu Abraham
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator, if you

happen

Quoted 6 lines
Quoted 4 lines

to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if its still ok?

The first time i saw it was that the DVB-S2 demod was returning no carrier. After some time it was stating timing error for DVB-S as well. Finally it all ended up with demodulator I2C ACK failure, and eventually a frozen machine after a week (my test boxes run throughout)

Quoted 7 lines

Touching the demodulator, i happened to have almost a burned finger. I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since he was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left his machine on after i did some tests on it. Eventually he too had the same results. Finally we changed cards.

Quoted 1 line

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do with the frequency of the transponder, but just the master clock. You can run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 2 lines

I didn't see anyone here on the list that reported a hardware failure so far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Quoted 3 lines

By the way, Igor returned the chip frequency for 27.5 channels to 99MHz and raised it a bit for higher SR channels, so there is no danger for majority of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of bounds of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Quoted 1 line

From your statement (and the patch), it is clearly evident that you

don't understand head or tail what you are stating or patched the code for:

For a lower sampling frequency (aka Symbol rate), you need a higher clock and or higher time period. For higher sampling rates (Symbol Rates) the the master clock has to be decimated to avoid overflows

This implies the patch to increase the master clock for acquisition at a higher symbol rate was utter nonsense only.

All i have is to say:

Alas !

#13 lore raw
Quoted 3 lines · Manu Abraham

For a lower sampling frequency (aka Symbol rate), you need a higher clock and or higher time period. For higher sampling rates (Symbol Rates) the the master clock has to be decimated to avoid overflows

Sorry, an error in one part. ^^

For a lower SRATE, you need a lower clock and a longer period of time. With a higher SRATE for the same coeffecients, you are bound to overflow, unless you decimate certain register contents. Recalculating those register values are quite tedious and lots of calculations involved for a different master clock.

The result with a higher master clock (with the same coeffecients), if you happened to see some positive results, it was the result of some overflow or underflow, which is for sure.

Manu

#14 lore raw
In reply to Manu Abraham
Quoted 36 lines · Manu Abraham
Quoted 11 lines · Alex Betis
Quoted 8 lines · On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham <[email protected] wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator, if you

happen

Quoted 5 lines
Quoted 4 lines

to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if

its

Quoted 14 lines
Quoted 6 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was returning no carrier. After some time it was stating timing error for DVB-S as well. Finally it all ended up with demodulator I2C ACK failure, and eventually a frozen machine after a week (my test boxes run throughout)

Quoted 7 lines

Touching the demodulator, i happened to have almost a burned finger. I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since he was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left his machine on after i did some tests on it. Eventually he too had the same results. Finally we changed cards.

Quoted 1 line

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do with the frequency of the transponder, but just the master clock. You can run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 5 lines
Quoted 2 lines

I didn't see anyone here on the list that reported a hardware failure so far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a manufacturer. I wrote a fact.
Intel also rate their chips and everybody overclocks them to crazy ratings.

Quoted 4 lines
Quoted 4 lines

By the way, Igor returned the chip frequency for 27.5 channels to 99MHz

Quoted 8 lines

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger for

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of bounds of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of quieting people who try to help.

Again, I'm commenting facts. As I saw from the reports the overclock seems to help with the problem.

Quoted 4 lines

From your statement (and the patch), it is clearly evident that you don't understand head or tail what you are stating or patched the code for:

So be so kind, and add comments to the code you write so everybody could find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone else will understand your code.

Again, facts are that the patch help and make the device more stable for DVB-S channels.

Oh well, I hate that I had to get so low with my message, but that's that happen when someone try to align with your expressions.
In case you didn't know, you're not alone in the universe, get used to it.

Quoted 10 lines

For a lower sampling frequency (aka Symbol rate), you need a higher clock and or higher time period. For higher sampling rates (Symbol Rates) the the master clock has to be decimated to avoid overflows

This implies the patch to increase the master clock for acquisition at a higher symbol rate was utter nonsense only.

All i have is to say:

Quoted 9 lines

Alas !

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#15 lore raw
Quoted 75 lines · Alex Betis
Quoted 34 lines · Manu Abraham
Quoted 11 lines · Alex Betis
Quoted 8 lines · On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham <[email protected] wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator, if you

happen

Quoted 5 lines
Quoted 4 lines

to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if

its

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was returning no carrier. After some time it was stating timing error for DVB-S as well. Finally it all ended up with demodulator I2C ACK failure, and eventually a frozen machine after a week (my test boxes run throughout)

Quoted 8 lines
Quoted 7 lines

Touching the demodulator, i happened to have almost a burned finger. I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since he was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left his machine on after i did some tests on it. Eventually he too had the same results. Finally we changed cards.

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do with the frequency of the transponder, but just the master clock. You can run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 4 lines
Quoted 2 lines

I didn't see anyone here on the list that reported a hardware failure so far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a manufacturer. I wrote a fact.
Intel also rate their chips and everybody overclocks them to crazy ratings.

Quoted 10 lines
Quoted 3 lines

By the way, Igor returned the chip frequency for 27.5 channels to 99MHz

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger for

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of bounds of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of quieting people who try to help.

Again, I'm commenting facts. As I saw from the reports the overclock seems to help with the problem.

Quoted 3 lines

From your statement (and the patch), it is clearly evident that you don't understand head or tail what you are stating or patched the code for:

So be so kind, and add comments to the code you write so everybody could find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone else will understand your code.

Quoted 8 lines

Again, facts are that the patch help and make the device more stable for DVB-S channels.

Oh well, I hate that I had to get so low with my message, but that's that happen when someone try to align with your expressions.
In case you didn't know, you're not alone in the universe, get used to it.

I should be the one who should be kicked for trying to help you.

#16 lore raw
Quoted 85 lines · Manu Abraham
Quoted 75 lines · Alex Betis
Quoted 34 lines · Manu Abraham
Quoted 11 lines · Alex Betis
Quoted 8 lines · On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham <[email protected] wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator, if you

happen

Quoted 5 lines
Quoted 4 lines

to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone know if

its

Quoted 6 lines
Quoted 6 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was returning no carrier. After some time it was stating timing error for DVB-S as well. Finally it all ended up with demodulator I2C ACK failure, and eventually a frozen machine after a week (my test boxes run throughout)

Quoted 8 lines
Quoted 7 lines

Touching the demodulator, i happened to have almost a burned finger. I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since he was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left his machine on after i did some tests on it. Eventually he too had the same results. Finally we changed cards.

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do with the frequency of the transponder, but just the master clock. You can run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 4 lines
Quoted 2 lines

I didn't see anyone here on the list that reported a hardware failure so far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a manufacturer. I wrote a fact.
Intel also rate their chips and everybody overclocks them to crazy ratings.

Quoted 10 lines
Quoted 3 lines

By the way, Igor returned the chip frequency for 27.5 channels to 99MHz

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger for

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of bounds of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of quieting people who try to help.

Again, I'm commenting facts. As I saw from the reports the overclock seems to help with the problem.

Quoted 3 lines

From your statement (and the patch), it is clearly evident that you don't understand head or tail what you are stating or patched the code for:

So be so kind, and add comments to the code you write so everybody could find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone else will understand your code.

Quoted 8 lines

Again, facts are that the patch help and make the device more stable for DVB-S channels.

Oh well, I hate that I had to get so low with my message, but that's that happen when someone try to align with your expressions.
In case you didn't know, you're not alone in the universe, get used to it.

Quoted 8 lines

I should be the one who should be kicked for trying to help you.

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I am writing just to share my experience with tt3200 drivers. The following are just observations about the behavior of my card:

1. The card has never tuned reliably with the v4l-dvb s2api driver or the multiproto driver. This concerns not just high rate dvb-s2 transponders but also some plain dvb-s transponders as well. And this is not just random hiccups but consistent behavior. German Eurosport @ 19.2e is a prime example.
2. When Igor first increased the high clock to 135MHz, there was a marked improvement. All of the tuning issues were gone. However I am using a rotor and the higher clock rate somehow broke rotor control.
3. Next Igor backed down the high clock to 99MHz and introduced a "very high clock" of 135MHz. Tuning went back to unreliable. Rotor control was ok.
4. I bought a hvr4000. And now all of my issues are gone.

#17 lore raw

Le 28.01.2009 07:03:00, n37 a écrit :

Quoted 133 lines
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 11:27 PM, Manu Abraham

Quoted 3 lines · <[email protected]>wrote:
Quoted 3 lines
Quoted 3 lines
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham

<[email protected]

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines · wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator,

if you

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

happen

Quoted 2 lines
Quoted 2 lines

to
be that lucky one, with that change. At least a few people

have burned

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines

demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone

know if

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

its

Quoted 2 lines
Quoted 2 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was returning

no

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

carrier. After some time it was stating timing error for DVB-S

as

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

well. Finally it all ended up with demodulator I2C ACK failure,

and

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

eventually a frozen machine after a week (my test boxes run

throughout)

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Touching the demodulator, i happened to have almost a burned

finger.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since

he

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left

his

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

machine on after i did some tests on it. Eventually he too had

the

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines
Quoted 1 line

same results. Finally we changed cards.

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do

with

Quoted 1 line
Quoted 1 line
Quoted 1 line

the frequency of the transponder, but just the master clock. You

can

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 1 line

I didn't see anyone here on the list that reported a hardware

failure so

Quoted 5 lines
Quoted 5 lines
Quoted 3 lines
Quoted 1 line

far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a

manufacturer.

Quoted 2 lines
Quoted 2 lines

I wrote a fact.
Intel also rate their chips and everybody overclocks them to crazy

ratings.

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

By the way, Igor returned the chip frequency for 27.5 channels

to
99MHz

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger

for

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of

bounds

Quoted 6 lines
Quoted 6 lines
Quoted 2 lines

of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of

quieting
people

Quoted 3 lines
Quoted 3 lines

who try to help.

Again, I'm commenting facts. As I saw from the reports the

overclock seems

Quoted 4 lines
Quoted 4 lines

to help with the problem.

Quoted 1 line

From your statement (and the patch), it is clearly evident that

you

Quoted 4 lines
Quoted 4 lines
Quoted 2 lines

don't understand head or tail what you are stating or patched the code for:

So be so kind, and add comments to the code you write so everybody

could

Quoted 2 lines
Quoted 2 lines

find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone else

will

Quoted 3 lines
Quoted 3 lines

understand your code.

Again, facts are that the patch help and make the device more

stable for

Quoted 5 lines
Quoted 5 lines

DVB-S channels.

Oh well, I hate that I had to get so low with my message, but

that's that

Quoted 2 lines
Quoted 2 lines

happen when someone try to align with your expressions. In case you didn't know, you're not alone in the universe, get

used
to it.

Quoted 6 lines

I should be the one who should be kicked for trying to help you.

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead

[email protected]

Quoted 3 lines

[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I am writing just to share my experience with tt3200 drivers. The following are just observations about the behavior of my card:

Quoted 13 lines

1. The card has never tuned reliably with the v4l-dvb s2api driver or the multiproto driver. This concerns not just high rate dvb-s2 transponders but also some plain dvb-s transponders as well. And this is not just random hiccups but consistent behavior. German Eurosport @
19.2e is a prime example.
2. When Igor first increased the high clock to 135MHz, there was a marked improvement. All of the tuning issues were gone. However I am using a rotor and the higher clock rate somehow broke rotor control.
3. Next Igor backed down the high clock to 99MHz and introduced a "very high clock" of 135MHz. Tuning went back to unreliable. Rotor control was ok.
4. I bought a hvr4000. And now all of my issues are gone.

I am thinking about it also :(
Does it work reliably with dvb-s/s2 and CAM?
Thx
Bye
Manu

#18 lore raw

Hi,
I have also TT-3200 and would like to have driver which are not able to burn anything, but to WORK as they should. I am currently using liplianindvb repository, because it seems only one working with my card. To bad that they have code which "can burn demodulator" in some case, as i don't wanna that. Well till now i have had luck then seems so, but....
I can use multiproto driver to but they should work OK with tt-3200 (i can test them to if needed) have only Astra 19.2E and Hotbird 13.0.

There should be also respect to ppl who build driver and stuff we are using, and Thank to them.

#19 lore raw
Quoted 9 lines · crow

Hi,
I have also TT-3200 and would like to have driver which are not able to burn anything, but to WORK as they should. I am currently using liplianindvb repository, because it seems only one working with my card. To bad that they have code which "can burn demodulator" in some case, as i don't wanna that. Well till now i have had luck then seems so, but....
I can use multiproto driver to but they should work OK with tt-3200 (i can test them to if needed) have only Astra 19.2E and Hotbird 13.0.

You can use either multiproto or S2API according to your desire. The S2API based driver is found here: http://jusst.de/hg/v4l-dvb

If you want to try the multiproto version the driver is found here:
http://jusst.de/hg/multiproto

Please do a vanilla test of the v4l-dvb tree (from jusst.de), whether you see any further difference.

Please try the changes that which i posted on top of the multiproto or the v4l-dvb tree and test your changes.

You can test with loading the modules with the verbose=5 option, such that you can see what's happening internally.

To test, rather than doing a scan, you should try doing a szap, since it is better for testing and to find issues. Testing with scan
will not help much as there will be other issues involved in it as
well.

Regards,
Manu

#20 lore raw
In reply to Manu
Quoted 17 lines
Quoted 16 lines

I am writing just to share my experience with tt3200 drivers. The following are just observations about the behavior of my card:

1. The card has never tuned reliably with the v4l-dvb s2api driver or the multiproto driver. This concerns not just high rate dvb-s2 transponders but also some plain dvb-s transponders as well. And this is not just random hiccups but consistent behavior. German Eurosport @
19.2e is a prime example.
2. When Igor first increased the high clock to 135MHz, there was a marked improvement. All of the tuning issues were gone. However I am using a rotor and the higher clock rate somehow broke rotor control.
3. Next Igor backed down the high clock to 99MHz and introduced a "very high clock" of 135MHz. Tuning went back to unreliable. Rotor control was ok.
4. I bought a hvr4000. And now all of my issues are gone.

Quoted 2 lines

I am thinking about it also :(
Does it work reliably with dvb-s/s2 and CAM?

concerning of dvb-s/s2 - yes it works well
concerning of CAM - I didn't check, I don't know

Goga

#21 lore raw
In reply to Manu
Quoted 138 lines · Manu
Quoted 123 lines · Le 28.01.2009 07:03:00, n37 a écrit :
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 11:27 PM, Manu Abraham

Quoted 2 lines · <[email protected]>wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham

<[email protected]

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines · wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your demodulator,

if you

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

happen

Quoted 2 lines
Quoted 2 lines

to
be that lucky one, with that change. At least a few people

have burned

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines

demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone

know if

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

its

Quoted 2 lines
Quoted 2 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was returning

no

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

carrier. After some time it was stating timing error for DVB-S

as

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

well. Finally it all ended up with demodulator I2C ACK failure,

and

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

eventually a frozen machine after a week (my test boxes run

throughout)

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Touching the demodulator, i happened to have almost a burned

finger.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this, since

he

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger, left

his

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

machine on after i did some tests on it. Eventually he too had

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines
Quoted 1 line

same results. Finally we changed cards.

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do

with

Quoted 1 line
Quoted 1 line
Quoted 1 line

the frequency of the transponder, but just the master clock. You

can

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 1 line

I didn't see anyone here on the list that reported a hardware

failure so

Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
Quoted 1 line

far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a

manufacturer.

Quoted 2 lines
Quoted 2 lines

I wrote a fact.
Intel also rate their chips and everybody overclocks them to crazy

ratings.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

By the way, Igor returned the chip frequency for 27.5 channels

to
99MHz

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger

for

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of

bounds

Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of

quieting
people

Quoted 3 lines
Quoted 3 lines

who try to help.

Again, I'm commenting facts. As I saw from the reports the

overclock seems

Quoted 4 lines
Quoted 4 lines

to help with the problem.

Quoted 1 line

From your statement (and the patch), it is clearly evident that

you

Quoted 3 lines
Quoted 3 lines
Quoted 2 lines

don't understand head or tail what you are stating or patched the code for:

So be so kind, and add comments to the code you write so everybody

could

Quoted 2 lines
Quoted 2 lines

find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone else

will

Quoted 3 lines
Quoted 3 lines

understand your code.

Again, facts are that the patch help and make the device more

stable for

Quoted 5 lines
Quoted 5 lines

DVB-S channels.

Oh well, I hate that I had to get so low with my message, but

that's that

Quoted 2 lines
Quoted 2 lines

happen when someone try to align with your expressions. In case you didn't know, you're not alone in the universe, get

used
to it.

Quoted 5 lines

I should be the one who should be kicked for trying to help you.

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead

[email protected]

Quoted 3 lines

[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I am writing just to share my experience with tt3200 drivers. The following are just observations about the behavior of my card:

Quoted 13 lines

1. The card has never tuned reliably with the v4l-dvb s2api driver or the multiproto driver. This concerns not just high rate dvb-s2 transponders but also some plain dvb-s transponders as well. And this is not just random hiccups but consistent behavior. German Eurosport @
19.2e is a prime example.
2. When Igor first increased the high clock to 135MHz, there was a marked improvement. All of the tuning issues were gone. However I am using a rotor and the higher clock rate somehow broke rotor control.
3. Next Igor backed down the high clock to 99MHz and introduced a "very high clock" of 135MHz. Tuning went back to unreliable. Rotor control was ok.
4. I bought a hvr4000. And now all of my issues are gone.

Quoted 1 line

I am thinking about it also :(

You are free to choose whatever hardware you want.

In your last post you wrote, you wanted some fixes to get going. Now when there are fixes to test, you don't want to test .. ??

Regards,
Manu

#22 lore raw

Le 28.01.2009 15:52:26, Manu Abraham a écrit :

Quoted 156 lines
Quoted 6 lines · Manu
Quoted 5 lines · Le 28.01.2009 07:03:00, n37 a écrit :
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 11:27 PM, Manu Abraham

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines · <[email protected]>wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham

<[email protected]

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines · wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your

demodulator,

Quoted 4 lines
Quoted 4 lines

if you

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

happen

Quoted 2 lines
Quoted 2 lines

to
be that lucky one, with that change. At least a few people

Quoted 8 lines
Quoted 8 lines

have burned

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines

demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone

know if

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

its

Quoted 2 lines
Quoted 2 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was

returning

Quoted 2 lines
Quoted 2 lines

no

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

carrier. After some time it was stating timing error for DVB-

S

Quoted 2 lines
Quoted 2 lines

as

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

well. Finally it all ended up with demodulator I2C ACK

failure,

Quoted 7 lines
Quoted 7 lines

and

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

eventually a frozen machine after a week (my test boxes run

throughout)

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Touching the demodulator, i happened to have almost a burned

finger.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this,

since

Quoted 3 lines
Quoted 3 lines

he

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger,

left

Quoted 2 lines
Quoted 2 lines

his

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

machine on after i did some tests on it. Eventually he too

had

Quoted 6 lines
Quoted 6 lines

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines
Quoted 1 line

same results. Finally we changed cards.

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do

with

Quoted 1 line
Quoted 1 line
Quoted 1 line

the frequency of the transponder, but just the master clock.

You

Quoted 6 lines
Quoted 6 lines

can

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 1 line

I didn't see anyone here on the list that reported a hardware

Quoted 8 lines
Quoted 8 lines

failure so

Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
Quoted 1 line

far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a

manufacturer.

Quoted 2 lines
Quoted 2 lines

I wrote a fact.
Intel also rate their chips and everybody overclocks them to

crazy

Quoted 22 lines
Quoted 22 lines

ratings.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

By the way, Igor returned the chip frequency for 27.5 channels

to
99MHz

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger

for

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of

bounds

Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of

quieting
people

Quoted 2 lines
Quoted 2 lines

who try to help.

Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Quoted 1 line

Again, I'm commenting facts. As I saw from the reports the

overclock seems

Quoted 4 lines
Quoted 4 lines

to help with the problem.

Quoted 1 line

From your statement (and the patch), it is clearly evident that

you

Quoted 1 line
Quoted 1 line
Quoted 1 line

don't understand head or tail what you are stating or patched

the

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

code for:

So be so kind, and add comments to the code you write so

everybody

Quoted 3 lines
Quoted 3 lines

could

Quoted 2 lines
Quoted 2 lines

find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone

else

Quoted 20 lines
Quoted 20 lines

will

Quoted 3 lines
Quoted 3 lines

understand your code.

Again, facts are that the patch help and make the device more

stable for

Quoted 5 lines
Quoted 5 lines

DVB-S channels.

Oh well, I hate that I had to get so low with my message, but

that's that

Quoted 2 lines
Quoted 2 lines

happen when someone try to align with your expressions. In case you didn't know, you're not alone in the universe, get

used
to it.

Quoted 5 lines

I should be the one who should be kicked for trying to help you.

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead

Quoted 8 lines
Quoted 8 lines

[email protected]

Quoted 3 lines

[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I am writing just to share my experience with tt3200 drivers. The following are just observations about the behavior of my card:

1. The card has never tuned reliably with the v4l-dvb s2api driver

or

Quoted 2 lines
Quoted 2 lines

the multiproto driver. This concerns not just high rate dvb-s2 transponders but also some plain dvb-s transponders as well. And

this

Quoted 1 line
Quoted 1 line

is not just random hiccups but consistent behavior. German

Eurosport

Quoted 4 lines
Quoted 4 lines

@
19.2e is a prime example.
2. When Igor first increased the high clock to 135MHz, there was a marked improvement. All of the tuning issues were gone. However I

am

Quoted 1 line
Quoted 1 line

using a rotor and the higher clock rate somehow broke rotor

control.

Quoted 5 lines
Quoted 4 lines

3. Next Igor backed down the high clock to 99MHz and introduced a "very high clock" of 135MHz. Tuning went back to unreliable. Rotor control was ok.
4. I bought a hvr4000. And now all of my issues are gone.

Quoted 6 lines
Quoted 1 line

I am thinking about it also :(

You are free to choose whatever hardware you want.

In your last post you wrote, you wanted some fixes to get going. Now when there are fixes to test, you don't want to test .. ??

Manu, I am trying your patch with latest multiproto with no luck so far. I need a bit more time though to make sure the frequency I have is not a bit off (that already happened) so I need to test several freq (I am using szap and simpledvbtune BTW, I hope these are the right tools). I do hope to sort these issues with your help.
Bye
Manu

#23 lore raw
In reply to Manu Abraham

Le 28.01.2009 15:52:26, Manu Abraham a écrit :

Quoted 156 lines
Quoted 6 lines · Manu
Quoted 5 lines · Le 28.01.2009 07:03:00, n37 a écrit :
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 11:27 PM, Manu Abraham

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines · <[email protected]>wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 10:14 PM, Manu Abraham

<[email protected]

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines
Quoted 2 lines · wrote:
Quoted 1 line · Alex Betis
Quoted 1 line

It won't. All you will manage to do is burn your

demodulator,

Quoted 4 lines
Quoted 4 lines

if you

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

happen

Quoted 2 lines
Quoted 2 lines

to
be that lucky one, with that change. At least a few people

Quoted 8 lines
Quoted 8 lines

have burned

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines

demodulators by now, from what i do see.

What are the symptoms of burned demodulator? How can someone

know if

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

its

Quoted 2 lines
Quoted 2 lines
Quoted 1 line

still ok?

The first time i saw it was that the DVB-S2 demod was

returning

Quoted 2 lines
Quoted 2 lines

no

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

carrier. After some time it was stating timing error for DVB-

S

Quoted 2 lines
Quoted 2 lines

as

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

well. Finally it all ended up with demodulator I2C ACK

failure,

Quoted 7 lines
Quoted 7 lines

and

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

eventually a frozen machine after a week (my test boxes run

throughout)

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Touching the demodulator, i happened to have almost a burned

finger.

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

I wanted to know whether this was a single case. During the development phase, i did mention it to Julian about this,

since

Quoted 3 lines
Quoted 3 lines

he

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

was the very first person to test for the stb0899 driver. He jovially laughed about a burned demodulator and a finger,

left

Quoted 2 lines
Quoted 2 lines

his

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

machine on after i did some tests on it. Eventually he too

had

Quoted 6 lines
Quoted 6 lines

the

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 2 lines
Quoted 1 line

same results. Finally we changed cards.

What frequency did you use to burn it?

It was a long time back, don't remember. It has nothing to do

with

Quoted 1 line
Quoted 1 line
Quoted 1 line

the frequency of the transponder, but just the master clock.

You

Quoted 6 lines
Quoted 6 lines

can

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

run it to a maximum of 108Mhz overclocked, 99Mhz to be safe and sufficient.

Quoted 1 line

I didn't see anyone here on the list that reported a hardware

Quoted 8 lines
Quoted 8 lines

failure so

Quoted 4 lines
Quoted 4 lines
Quoted 3 lines
Quoted 1 line

far.

May god help you. I didn't know that you knew more than the demodulator manufacturer !

Please speak for yourself, I never said I know more than a

manufacturer.

Quoted 2 lines
Quoted 2 lines

I wrote a fact.
Intel also rate their chips and everybody overclocks them to

crazy

Quoted 22 lines
Quoted 22 lines

ratings.

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

By the way, Igor returned the chip frequency for 27.5 channels

to
99MHz

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

and

Quoted 1 line

raised it a bit for higher SR channels, so there is no danger

for

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

majority

Quoted 1 line

of the users.

Ok, be happy with his change and keep quiet. 135Mhz is out of

bounds

Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

of the hardware specification. You are on your own. Raising the master clock, doesn't bring you any advantage.

Did someone overclock you as well?
Chill out!
It would be better if you'll be more productive instead of

quieting
people

Quoted 2 lines
Quoted 2 lines

who try to help.

Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Quoted 1 line

Again, I'm commenting facts. As I saw from the reports the

overclock seems

Quoted 4 lines
Quoted 4 lines

to help with the problem.

Quoted 1 line

From your statement (and the patch), it is clearly evident that

you

Quoted 1 line
Quoted 1 line
Quoted 1 line

don't understand head or tail what you are stating or patched

the

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

code for:

So be so kind, and add comments to the code you write so

everybody

Quoted 3 lines
Quoted 3 lines

could

Quoted 2 lines
Quoted 2 lines

find its head and tail when trying to fix bugs.
It is clearly evident that you don't really want that someone

else

Quoted 20 lines
Quoted 20 lines

will

Quoted 3 lines
Quoted 3 lines

understand your code.

Again, facts are that the patch help and make the device more

stable for

Quoted 5 lines
Quoted 5 lines

DVB-S channels.

Oh well, I hate that I had to get so low with my message, but

that's that

Quoted 2 lines
Quoted 2 lines

happen when someone try to align with your expressions. In case you didn't know, you're not alone in the universe, get

used
to it.

Quoted 5 lines

I should be the one who should be kicked for trying to help you.

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead

Quoted 8 lines
Quoted 8 lines

[email protected]

Quoted 3 lines

[email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

I am writing just to share my experience with tt3200 drivers. The following are just observations about the behavior of my card:

1. The card has never tuned reliably with the v4l-dvb s2api driver

or

Quoted 2 lines
Quoted 2 lines

the multiproto driver. This concerns not just high rate dvb-s2 transponders but also some plain dvb-s transponders as well. And

this

Quoted 1 line
Quoted 1 line

is not just random hiccups but consistent behavior. German

Eurosport

Quoted 4 lines
Quoted 4 lines

@
19.2e is a prime example.
2. When Igor first increased the high clock to 135MHz, there was a marked improvement. All of the tuning issues were gone. However I

am

Quoted 1 line
Quoted 1 line

using a rotor and the higher clock rate somehow broke rotor

control.

Quoted 5 lines
Quoted 4 lines

3. Next Igor backed down the high clock to 99MHz and introduced a "very high clock" of 135MHz. Tuning went back to unreliable. Rotor control was ok.
4. I bought a hvr4000. And now all of my issues are gone.

Quoted 6 lines
Quoted 1 line

I am thinking about it also :(

You are free to choose whatever hardware you want.

In your last post you wrote, you wanted some fixes to get going. Now when there are fixes to test, you don't want to test .. ??

Sorry, bad news: no lock though I tried 11493 to 11500 MHz. Is it possible that this is because of the FEC not being detected? I am out of idea here, hope you can help.
Bye
Manu

#24 lore raw
In reply to Manu Abraham

Le 26.01.2009 13:50:24, Manu Abraham a écrit :

Quoted 20 lines
Quoted 3 lines · Alex Betis

Latest changes I can see at

Quoted 1 line

http://mercurial.intuxication.org/hg/s2-liplianin/ were made about

7

Quoted 2 lines
Quoted 2 lines

to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm

getting.

Quoted 2 lines
Quoted 2 lines

I can't see anything related do high SR channels on Igor

repository.

Quoted 2 lines

He did it few months ago. If you're on latest than you should have

it.

Quoted 2 lines
Quoted 6 lines

It won't. All you will manage to do is burn your demodulator, if you happen
to
be that lucky one, with that change. At least a few people have burned
demodulators by now, from what i do see.

Hmm OK, but is there by any chance a fix for those issues somewhere or in the pipe at least? I am willing to test (as I already offered), I can compile the drivers, spread printk or whatever else is needed to get useful reports. Let me know if I can help sort this problem. BTW in my case it is DVB-S2 30000 SR and FEC 5/6.
Thx
Bye
Manu

#25 lore raw
In reply to Manu Abraham
Quoted 14 lines · Manu Abraham
Quoted 10 lines · Alex Betis
Quoted 7 lines

Latest changes I can see at
http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

Quoted 8 lines

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

Regards,
Manu

Manu, would you be so kind to explain why it will burn the demodulator? It happens only with 30000 transponders? And only with this card? Does this mean I can't use my card to see channels on 30000 transponders?

Chris

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#26 lore raw
Quoted 1 line · Chris Silva

On Mon, Jan 26, 2009 at 5:50 PM, Manu Abraham <[email protected]>

Quoted 16 lines · wrote:
Quoted 16 lines · Alex Betis
Quoted 8 lines
Quoted 6 lines

Latest changes I can see at
http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

Quoted 8 lines
Quoted 2 lines

Regards,
Manu

Manu, would you be so kind to explain why it will burn the demodulator? It happens only with 30000 transponders? And only with this card? Does this mean I can't use my card to see channels on 30000 transponders?

Chris

Regarding the documentation the demodulator is designed to run at max. freq. 99MHz. Some series of demods burn when the freq is set above this value. But this value is enough for most of transponders with SR up to 30000.

Some Russian transponders have SR 43500 - so the demod is set a little bit above 3x of this value. This could be dangerous.

This patch (or change) doesn't solve the problem with SR of 30000 and FEC 3/4 or 5/6.

BR,

Ales

#27 lore raw
Quoted 32 lines · Ales Jurik
Quoted 1 line · Chris Silva

On Mon, Jan 26, 2009 at 5:50 PM, Manu Abraham <[email protected]>

Quoted 14 lines · wrote:
Quoted 14 lines · Alex Betis
Quoted 7 lines
Quoted 6 lines

Latest changes I can see at
http://mercurial.intuxication.org/hg/s2-liplianin/ were made about 7 to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm getting.

I can't see anything related do high SR channels on Igor repository.

He did it few months ago. If you're on latest than you should have it.

It won't. All you will manage to do is burn your demodulator, if you happen to
be that lucky one, with that change. At least a few people have burned demodulators by now, from what i do see.

Quoted 7 lines
Quoted 2 lines

Regards,
Manu

Manu, would you be so kind to explain why it will burn the demodulator? It happens only with 30000 transponders? And only with this card? Does this mean I can't use my card to see channels on 30000 transponders?

Chris

Regarding the documentation the demodulator is designed to run at max. freq. 99MHz. Some series of demods burn when the freq is set above this value. But this value is enough for most of transponders with SR up to 30000.

Some Russian transponders have SR 43500 - so the demod is set a little bit above 3x of this value. This could be dangerous.

Quoted 6 lines

This patch (or change) doesn't solve the problem with SR of 30000 and FEC 3/4 or 5/6.

BR,

Ales

True, very much.

Regards,
Manu

A message that is not in the archive (sent off-list or not yet received): 1232998154.24736.2@manu-laptop

#29 lore raw
Quoted 23 lines · Manu
Quoted 15 lines · Manu Abraham
Quoted 2 lines · Alex Betis

Latest changes I can see at

Quoted 1 line

http://mercurial.intuxication.org/hg/s2-liplianin/ were made about

7

Quoted 2 lines
Quoted 2 lines

to 10 days ago. Is this correct? If that's correct, then I'm using latest Igor drivers. And behavior described above is what I'm

getting.

Quoted 1 line
Quoted 1 line

I can't see anything related do high SR channels on Igor

repository.

Quoted 1 line

He did it few months ago. If you're on latest than you should have

it.

Quoted 1 line
Quoted 6 lines

It won't. All you will manage to do is burn your demodulator, if you happen
to
be that lucky one, with that change. At least a few people have burned
demodulators by now, from what i do see.

Quoted 5 lines

Hmm OK, but is there by any chance a fix for those issues somewhere or in the pipe at least? I am willing to test (as I already offered), I can compile the drivers, spread printk or whatever else is needed to get useful reports. Let me know if I can help sort this problem. BTW in my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply in time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the issues.

BTW: lot of patience you have compared to the other users :)

Regards,
Manu

linux/drivers/media/dvb/frontends/stb0899_algo.c Tue Jan 27 23:48:52 2009 +0400 renamed from linux/drivers/media/dvb/frontends/stb0899_algo.c Tue Jan 27 23:29:44 2009 +0400 +4 -0
@@ -1345,6 +1345,10 @@
                FecLockTime     = 20;   /* 20 ms max time to lock FEC, 20Mbs< SYMB <= 25Mbs             */
        }
 
+       /* give a factor of safety */
+       searchTime *= 3;
+       FecLockTime *= 3;
+
        /* Maintain Stream Merger in reset during acquisition   */
        reg = stb0899_read_reg(state, STB0899_TSTRES);
        STB0899_SETFIELD_VAL(FRESRS, reg, 1);

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#30 lore raw
Quoted 11 lines · Manu Abraham
Quoted 6 lines

Hmm OK, but is there by any chance a fix for those issues somewhere or in the pipe at least? I am willing to test (as I already offered), I can compile the drivers, spread printk or whatever else is needed to get useful reports. Let me know if I can help sort this problem. BTW in my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply in time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Quoted 6 lines

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the issues.

Manu,
I've tried to increase those timers long ago when played around with my card (Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that wasn't always locking.
I didn't notice much improvements. The thing that did help was increasing the resolution of scan zigzags.
I've sent a patch on that ML and people were happy with the results. The patch went to Igor's repository, don't know were it goes from there.

I believe DVB-S2 lock suffer from the same problem, but in that case the zigzag is done in the chip and not in the driver.
Since I have no documentation of the chip I was stuck and left it. So if you have the knowledge or documentation of the chip,
try to go in that direction.

By the way, question to those who have such channels:
Does windows based applications show those channels properly?

Quoted 9 lines

BTW: lot of patience you have compared to the other users :)

Regards,
Manu

Quoted 6 lines

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#31 lore raw
Quoted 18 lines · Alex Betis
Quoted 9 lines · Manu Abraham
Quoted 5 lines

Hmm OK, but is there by any chance a fix for those issues somewhere or in the pipe at least? I am willing to test (as I already offered), I can compile the drivers, spread printk or whatever else is needed to get useful reports. Let me know if I can help sort this problem. BTW in my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply in time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Quoted 6 lines

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the issues.

Quoted 7 lines

Manu,
I've tried to increase those timers long ago when played around with my card (Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that wasn't always locking.
I didn't notice much improvements. The thing that did help was increasing the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the results.

I did look at your patch, but that was completely against the tuning algorithm.

[..]

Quoted 2 lines

I believe DVB-S2 lock suffer from the same problem, but in that case the zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

linux/drivers/media/dvb/frontends/stb0899_drv.c Wed Jan 28 01:08:25 2009 +0400 renamed from linux/drivers/media/dvb/frontends/stb0899_drv.c Tue Jan 27 23:29:44 2009 +0400 +3 -6
diff -r a4731ed28cac linux/drivers/media/dvb/frontends/stb0899_drv.c
@@ -1461,19 +1461,16 @@
        struct stb0899_config *config = state->config;
 
        s32 iter_scale;
-       u32 reg;
 
        iter_scale = 17 * (internal->master_clk / 1000);
        iter_scale += 410000;
-       iter_scale /= (internal->srate / 1000000);
-       iter_scale /= 1000;
+       iter_scale /= (internal->srate / 1000);
 
        if (iter_scale > config->ldpc_max_iter)
                iter_scale = config->ldpc_max_iter;
 
-       reg = STB0899_READ_S2REG(STB0899_S2DEMOD, MAX_ITER);
-       STB0899_SETFIELD_VAL(MAX_ITERATIONS, reg, iter_scale);
-       stb0899_write_s2reg(state, STB0899_S2DEMOD, STB0899_BASE_MAX_ITER, STB0899_OFF0_MAX_ITER, reg);
+       stb0899_write_s2reg(state, STB0899_S2DEMOD, STB0899_BASE_MAX_ITER, STB0899_OFF0_MAX_ITER, iter_scale);
+       stb0899_write_s2reg(state, STB0899_S2DEMOD, STB0899_BASE_ITER_SCALE, STB0899_OFF0_ITER_SCALE, iter_scale);
 }
 
 static enum dvbfe_search stb0899_search(struct dvb_frontend *fe, struct dvb_frontend_parameters *p)
#32 lore raw
Quoted 5 lines · Manu Abraham
Quoted 2 lines · Alex Betis

Manu,
I've tried to increase those timers long ago when played around with my

card

Quoted 8 lines
Quoted 5 lines

(Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that wasn't always locking.
I didn't notice much improvements. The thing that did help was increasing the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

I use Igor's version, but he merges v4l changes quite often. Can you point me to a patch or code that was changes? I want to make sure I have that fix.

Quoted 6 lines
Quoted 3 lines

I've sent a patch on that ML and people were happy with the results.

I did look at your patch, but that was completely against the tuning algorithm.

Well, you know, it works :)
What is the algorithm? I didn't make major changes beside increasing the zigzag resolution for different scan stages and zigzag around the frequency that previous stage was able to detect instead of starting from the beginning. Sounds logical to me.

Quoted 8 lines

[..]

Quoted 2 lines

I believe DVB-S2 lock suffer from the same problem, but in that case the zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

I didn't tried to watch any DVB-S2 channels yet, not sure I have any FTA with my current directions.
But I'll try that change later for scanning.

BTW, too bad the code has very few comments inside to understand all the numeric values used for calculations.

Quoted 10 lines

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead [email protected] [email protected]
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

#33 lore raw
In reply to Manu Abraham

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoted 34 lines · Manu Abraham
Quoted 17 lines · Alex Betis
Quoted 9 lines · Manu Abraham
Quoted 5 lines

Hmm OK, but is there by any chance a fix for those issues somewhere or in the pipe at least? I am willing to test (as I already offered), I can compile the drivers, spread printk or whatever else is needed to get useful reports. Let me know if I can help sort this problem. BTW in my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply in time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Quoted 6 lines

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the issues.

Quoted 7 lines

Manu,
I've tried to increase those timers long ago when played around with my card (Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that wasn't always locking.
I didn't notice much improvements. The thing that did help was increasing the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the results.

I did look at your patch, but that was completely against the tuning algorithm.

Quoted 10 lines

[..]

Quoted 2 lines

I believe DVB-S2 lock suffer from the same problem, but in that case the zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

- From what I understand the driver still has some issues. Got feedback from another guy with Canal Digital in Norway that he has the same issues as me.

Not sure if the diff was an attempt to fix the digital artefacts but I tried applying the diff manually on the source I grabbed from
http://jusst.de/hg/v4l-dvb/ but did not notice any improvements or difference with the artefacts. Would any logs be helpful?

If there is anything else I could try I'm willing to try it out. I appreciate your effort. Thanks.

Jonas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iEYEARECAAYFAkmHIuMACgkQpvOo+MDrK1H1wACggFIUgXQHcJxBhjCCGXtDLe44 b7EAn0VW7orjhEdbhyWgQhOITWopLxwg
=dSFB
-----END PGP SIGNATURE-----

#34 lore raw
In reply to Manu Abraham
Quoted 35 lines · Manu Abraham
Quoted 18 lines · Alex Betis
Quoted 9 lines · Manu Abraham
Quoted 5 lines

Hmm OK, but is there by any chance a fix for those issues somewhere or in the pipe at least? I am willing to test (as I already offered), I can compile the drivers, spread printk or whatever else is needed to get useful reports. Let me know if I can help sort this problem. BTW in my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply in time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Quoted 6 lines

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the issues.

Quoted 7 lines

Manu,
I've tried to increase those timers long ago when played around with my card (Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that wasn't always locking.
I didn't notice much improvements. The thing that did help was increasing the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the results.

I did look at your patch, but that was completely against the tuning algorithm.

Quoted 8 lines

[..]

Quoted 2 lines

I believe DVB-S2 lock suffer from the same problem, but in that case the zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

Manu,

I've tried both multiproto branches you indicated above, *with* and *without* the patches you sent to the ML (fix_iterations.patch and increase timeout.patch) on this thread.
Sadly, same behavior as S2API V4L-DVB current branch. No lock on 30000 3/4 channels. It achieves a 0.5 second jittery sound but no image. It seems the driver is struggling to correctly lock on that channel, but doesn't get there in time... Or maybe the hardware... Dunno...

Channels like

ASTRA HD+;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279=27:0;1283=deu:0:0:131:133:6:0 PREMIERE HD,PREM HD;PREMIERE:11914:hC910M2O35S1:S19.2E:27500:767=27:0;771=deu,772=eng:32:1837,1833,1834,9C4:129:133:6:0 DISCOVERY HD,DISC HD;PREMIERE:11914:hC910M2O35S1:S19.2E:27500:1023=27:0;1027=deu:32:1837,1833,1834,9C4:130:133:6

work just fine.

But channels like

National Geographic HD;National Geographic HD:11731:vC34M5O25S1:S30.0W:29000:6496=27:6497:0:1802:943:54:47:0 MOV HD;MOV HD:11731:vC34M5O25S1:S30.0W:29000:6512=27:6513=por:0:1802:944:54:47:0 Sport TV - HD;Sport TV - HD:11731:vC34M5O25S1:S30.0W:29000:6528=27:6529=por:0:1802:945:54:47:0 RTP HD;RTP HD:11731:vC34M5O25S1:S30.0W:29000:6544=27:6545:0:1802:946:54:47:0 TVCine 4 HD;TVCine 4 HD:11731:vC34M5O25S1:S30.0W:29000:6560=27:6561:0:1802:947:54:47:0 Disney Cinemagic HD:11731:vC34M5O25S1:S30.0W:29000:6576=27:6577=por:0:1802:948:54:47:0 Eurosport HD:11731:vC34M5O25S1:S30.0W:29000:6592=27:6593=por:0:1802:949:54:47:0

or

[0065];:12012:hC34M5S1:S30.0W:30000:4097:4098:4100:100:101:0:0:0 [0066];:12012:hC34M5S1:S30.0W:30000:4105:4106:4100:100:102:0:0:0 [0067];:12012:hC34M5S1:S30.0W:30000:4113:4114:4100:100:103:0:0:0 [0068];:12012:hC34M5S1:S30.0W:30000:4121:4122:4100:100:104:0:0:0 [0069];:12012:hC34M5S1:S30.0W:30000:4129:4130:4100:100:105:0:0:0 [006a];:12012:hC34M5S1:S30.0W:30000:4137:4138:4100:100:106:0:0:0 [006b];:12012:hC34M5S1:S30.0W:30000:4145:4146:4100:100:107:0:0:0

simply don't work.

BTW, I think the channels above that don't work have a 0x0B stream indication. Satellite operators are misleading on the stream (h.222) when in fact they are h.264. Read that were on the ML. Don't know if it affects anything, but hey... I have to try everything! ;)

I'm available to any tests necessary to fix this once and for all, if possible.

Just let me know.

Thanks for all your hard work.

Chris

#35 lore raw

Le 02.02.2009 18:43:33, Chris Silva a écrit :

Quoted 112 lines
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 9:56 PM, Manu Abraham

Quoted 2 lines · <[email protected]>wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Hmm OK, but is there by any chance a fix for those issues

somewhere or

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in the pipe at least? I am willing to test (as I already

offered), I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

can compile the drivers, spread printk or whatever else is

needed
to

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

get useful reports. Let me know if I can help sort this problem.

BTW in

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply

in

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the

issues.

Quoted 3 lines
Quoted 3 lines

Manu,
I've tried to increase those timers long ago when played around

with my card

Quoted 2 lines
Quoted 2 lines

(Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that

wasn't

Quoted 2 lines
Quoted 2 lines

always locking.
I didn't notice much improvements. The thing that did help was

increasing

Quoted 6 lines
Quoted 1 line

the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the

results.

Quoted 2 lines

I did look at your patch, but that was completely against the

tuning

Quoted 5 lines

algorithm.

[..]

Quoted 1 line

I believe DVB-S2 lock suffer from the same problem, but in that

case the

Quoted 5 lines
Quoted 1 line

zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

Manu,

I've tried both multiproto branches you indicated above, *with* and *without* the patches you sent to the ML (fix_iterations.patch and increase timeout.patch) on this thread.
Sadly, same behavior as S2API V4L-DVB current branch. No lock on 30000
3/4 channels. It achieves a 0.5 second jittery sound but no image. It seems the driver is struggling to correctly lock on that channel, but doesn't get there in time... Or maybe the hardware... Dunno...

Channels like

ASTRA HD +;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279=27:0;1283=deu:0:0:131:133:6:0 PREMIERE HD,PREM HD;PREMIERE:11914:hC910M2O35S1:S19.2E:27500:767=27:0;771=deu,772=eng:32:1837,1833,1834,9C4:129:133:6:0 DISCOVERY HD,DISC HD;PREMIERE:11914:hC910M2O35S1:S19.2E:27500:1023=27:0;1027=deu:32:1837,1833,1834,9C4:130:133:6

work just fine.

But channels like

National Geographic HD;National Geographic HD:11731:vC34M5O25S1:S30.0W:29000:6496=27:6497:0:1802:943:54:47:0 MOV HD;MOV HD:11731:vC34M5O25S1:S30.0W:29000:6512=27:6513=por:0:1802:944:54:47:0 Sport TV - HD;Sport TV - HD:11731:vC34M5O25S1:S30.0W:29000:6528=27:6529=por:0:1802:945:54:47:0 RTP HD;RTP HD:11731:vC34M5O25S1:S30.0W:29000:6544=27:6545:0:1802:946:54:47:0 TVCine 4 HD;TVCine 4 HD:11731:vC34M5O25S1:S30.0W:29000:6560=27:6561:0:1802:947:54:47:0 Disney Cinemagic HD:11731:vC34M5O25S1:S30.0W:29000:6576=27:6577=por:0:1802:948:54:47:0 Eurosport HD:11731:vC34M5O25S1:S30.0W:29000:6592=27:6593=por:0:1802:949:54:47:0

or

[0065];:12012:hC34M5S1:S30.0W:30000:4097:4098:4100:100:101:0:0:0 [0066];:12012:hC34M5S1:S30.0W:30000:4105:4106:4100:100:102:0:0:0 [0067];:12012:hC34M5S1:S30.0W:30000:4113:4114:4100:100:103:0:0:0 [0068];:12012:hC34M5S1:S30.0W:30000:4121:4122:4100:100:104:0:0:0 [0069];:12012:hC34M5S1:S30.0W:30000:4129:4130:4100:100:105:0:0:0 [006a];:12012:hC34M5S1:S30.0W:30000:4137:4138:4100:100:106:0:0:0 [006b];:12012:hC34M5S1:S30.0W:30000:4145:4146:4100:100:107:0:0:0

simply don't work.

Quoted 7 lines

BTW, I think the channels above that don't work have a 0x0B stream indication. Satellite operators are misleading on the stream (h.222) when in fact they are h.264. Read that were on the ML. Don't know if it affects anything, but hey... I have to try everything! ;)

I'm available to any tests necessary to fix this once and for all, if possible.

Could I suggest something (probably stupid): I think that the TT 3650 is the same card but using USB, right (I mean it uses the stb0899/ stb6100 chips also)? So if someone could sniff the usb transactions during a successfull lock on a problematic channel (using windows then), we could see what is different.
I do not have neither Windows, neither this card, but a good soul could help us here.
Manu, is that sensible?
Bye
Manu (the other one ;-)

#36 lore raw
In reply to Chris Silva

Le 02.02.2009 18:43:33, Chris Silva a écrit :

Quoted 112 lines
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 9:56 PM, Manu Abraham

Quoted 2 lines · <[email protected]>wrote:
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

Hmm OK, but is there by any chance a fix for those issues

somewhere or

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in the pipe at least? I am willing to test (as I already

offered), I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

can compile the drivers, spread printk or whatever else is

needed
to

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

get useful reports. Let me know if I can help sort this problem.

BTW in

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply

in

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the

issues.

Quoted 3 lines
Quoted 3 lines

Manu,
I've tried to increase those timers long ago when played around

with my card

Quoted 2 lines
Quoted 2 lines

(Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that

wasn't

Quoted 2 lines
Quoted 2 lines

always locking.
I didn't notice much improvements. The thing that did help was

increasing

Quoted 6 lines
Quoted 1 line

the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the

results.

Quoted 2 lines

I did look at your patch, but that was completely against the

tuning

Quoted 5 lines

algorithm.

[..]

Quoted 1 line

I believe DVB-S2 lock suffer from the same problem, but in that

case the

Quoted 5 lines
Quoted 1 line

zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

Manu,

I've tried both multiproto branches you indicated above, *with* and *without* the patches you sent to the ML (fix_iterations.patch and increase timeout.patch) on this thread.
Sadly, same behavior as S2API V4L-DVB current branch. No lock on 30000
3/4 channels. It achieves a 0.5 second jittery sound but no image. It seems the driver is struggling to correctly lock on that channel, but doesn't get there in time... Or maybe the hardware... Dunno...

Channels like

ASTRA HD +;BetaDigital:11914:hC910M2O35S1:S19.2E:27500:1279=27:0;1283=deu:0:0:131:133:6:0 PREMIERE HD,PREM HD;PREMIERE:11914:hC910M2O35S1:S19.2E:27500:767=27:0;771=deu,772=eng:32:1837,1833,1834,9C4:129:133:6:0 DISCOVERY HD,DISC HD;PREMIERE:11914:hC910M2O35S1:S19.2E:27500:1023=27:0;1027=deu:32:1837,1833,1834,9C4:130:133:6

work just fine.

But channels like

National Geographic HD;National Geographic HD:11731:vC34M5O25S1:S30.0W:29000:6496=27:6497:0:1802:943:54:47:0 MOV HD;MOV HD:11731:vC34M5O25S1:S30.0W:29000:6512=27:6513=por:0:1802:944:54:47:0 Sport TV - HD;Sport TV - HD:11731:vC34M5O25S1:S30.0W:29000:6528=27:6529=por:0:1802:945:54:47:0 RTP HD;RTP HD:11731:vC34M5O25S1:S30.0W:29000:6544=27:6545:0:1802:946:54:47:0 TVCine 4 HD;TVCine 4 HD:11731:vC34M5O25S1:S30.0W:29000:6560=27:6561:0:1802:947:54:47:0 Disney Cinemagic HD:11731:vC34M5O25S1:S30.0W:29000:6576=27:6577=por:0:1802:948:54:47:0 Eurosport HD:11731:vC34M5O25S1:S30.0W:29000:6592=27:6593=por:0:1802:949:54:47:0

or

[0065];:12012:hC34M5S1:S30.0W:30000:4097:4098:4100:100:101:0:0:0 [0066];:12012:hC34M5S1:S30.0W:30000:4105:4106:4100:100:102:0:0:0 [0067];:12012:hC34M5S1:S30.0W:30000:4113:4114:4100:100:103:0:0:0 [0068];:12012:hC34M5S1:S30.0W:30000:4121:4122:4100:100:104:0:0:0 [0069];:12012:hC34M5S1:S30.0W:30000:4129:4130:4100:100:105:0:0:0 [006a];:12012:hC34M5S1:S30.0W:30000:4137:4138:4100:100:106:0:0:0 [006b];:12012:hC34M5S1:S30.0W:30000:4145:4146:4100:100:107:0:0:0

simply don't work.

Quoted 7 lines

BTW, I think the channels above that don't work have a 0x0B stream indication. Satellite operators are misleading on the stream (h.222) when in fact they are h.264. Read that were on the ML. Don't know if it affects anything, but hey... I have to try everything! ;)

I'm available to any tests necessary to fix this once and for all, if possible.

Could I suggest something (probably stupid): I think that the TT 3650 is the same card but using USB, right (I mean it uses the stb0899/ stb6100 chips also)? So if someone could sniff the usb transactions during a successfull lock on a problematic channel (using windows then), we could see what is different.
I do not have neither Windows, neither this card, but a good soul could help us here.
Manu, is that sensible?
Bye
Manu (the other one ;-)

#37 lore raw
Quoted 58 lines · Manu
Quoted 57 lines · Chris Silva
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 9:56 PM, Manu Abraham

Quoted 1 line · <[email protected]>wrote:
Quoted 1 line
Quoted 1 line
Quoted 1 line

Hmm OK, but is there by any chance a fix for those issues

somewhere or

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in the pipe at least? I am willing to test (as I already

offered), I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

can compile the drivers, spread printk or whatever else is

needed
to

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

get useful reports. Let me know if I can help sort this problem.

BTW in

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or reply

in

Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

time nor spend much time on it earlier, but that said i was quite stuck up with some other things.

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the

issues.

Quoted 2 lines
Quoted 2 lines

Manu,
I've tried to increase those timers long ago when played around

with my card

Quoted 2 lines
Quoted 2 lines

(Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that

wasn't

Quoted 2 lines
Quoted 2 lines

always locking.
I didn't notice much improvements. The thing that did help was

increasing

Quoted 5 lines
Quoted 1 line

the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb tree. Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the

results.

Quoted 1 line

I did look at your patch, but that was completely against the

tuning

Quoted 5 lines

algorithm.

[..]

Quoted 1 line

I believe DVB-S2 lock suffer from the same problem, but in that

case the

Quoted 4 lines
Quoted 1 line

zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

Manu,

Quoted 8 lines
Quoted 8 lines

I've tried both multiproto branches you indicated above, *with* and *without* the patches you sent to the ML (fix_iterations.patch and increase timeout.patch) on this thread.
Sadly, same behavior as S2API V4L-DVB current branch. No lock on 30000
3/4 channels. It achieves a 0.5 second jittery sound but no image. It seems the driver is struggling to correctly lock on that channel, but doesn't get there in time... Or maybe the hardware... Dunno...

Can you please send me a complete trace with the stb6100 and stb0899 modules loaded with verbose=5 for the 30MSPS transponder what you are trying ? One simple szap would be enough (no scan please) based on the http://jusst.de/hg/v4l-dvb tree.

Before you start testing, start clean from a cold boot after a powerdown. This makes it a bit more easier identify things.

Regards,
Manu

#38 lore raw

Le 05.02.2009 19:50:18, Manu Abraham a écrit :

Quoted 75 lines
Quoted 7 lines · Manu
Quoted 6 lines · Chris Silva
Quoted 2 lines · Manu Abraham
Quoted 1 line · Alex Betis

On Tue, Jan 27, 2009 at 9:56 PM, Manu Abraham

<[email protected]>wrote:

Quoted 8 lines
Quoted 8 lines
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Hmm OK, but is there by any chance a fix for those issues

somewhere or

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

in the pipe at least? I am willing to test (as I already

offered), I

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

can compile the drivers, spread printk or whatever else is

needed
to

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

get useful reports. Let me know if I can help sort this

problem.

Quoted 3 lines
Quoted 3 lines

BTW in

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 1 line

my case it is DVB-S2 30000 SR and FEC 5/6.

It was quite not appreciable on my part to provide a fix or

reply

Quoted 2 lines
Quoted 2 lines

in

Quoted 1 line
Quoted 1 line
Quoted 1 line

time nor spend much time on it earlier, but that said i was

quite

Quoted 12 lines
Quoted 12 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

stuck up with some other things.

Can you please pull a copy of the multiproto tree
http://jusst.de/hg/multiproto or the v4l-dvb tree from
http://jusst.de/hg/v4l-dvb

and apply the following patch and comment what your result is ? Before applying please do check whether you still have the

issues.

Quoted 2 lines
Quoted 2 lines

Manu,
I've tried to increase those timers long ago when played around

with my card

Quoted 8 lines
Quoted 8 lines
Quoted 2 lines
Quoted 2 lines

(Twinhan 1041) and scan utility.
I must say that I've concentrated mostly on DVB-S channels that

wasn't

Quoted 2 lines
Quoted 2 lines

always locking.
I didn't notice much improvements. The thing that did help was

increasing

Quoted 2 lines
Quoted 1 line

the resolution of scan zigzags.

With regards to the zig-zag, one bug is fixed in the v4l-dvb

tree.

Quoted 11 lines
Quoted 11 lines
Quoted 3 lines

Most likely you haven't tried that change.

Quoted 1 line

I've sent a patch on that ML and people were happy with the

results.

Quoted 1 line

I did look at your patch, but that was completely against the

tuning

Quoted 5 lines

algorithm.

[..]

Quoted 1 line

I believe DVB-S2 lock suffer from the same problem, but in that

Quoted 8 lines
Quoted 8 lines

case the

Quoted 4 lines
Quoted 1 line

zigzag is done in the chip and not in the driver.

Along with the patch i sent, does the attached patch help you in anyway (This works out for DVB-S2 only)?

Manu,

I've tried both multiproto branches you indicated above, *with*

and

Quoted 5 lines
Quoted 5 lines

*without* the patches you sent to the ML (fix_iterations.patch and increase timeout.patch) on this thread.
Sadly, same behavior as S2API V4L-DVB current branch. No lock on 30000
3/4 channels. It achieves a 0.5 second jittery sound but no image.

It

Quoted 1 line
Quoted 1 line

seems the driver is struggling to correctly lock on that channel,

but

Quoted 1 line
Quoted 1 line

doesn't get there in time... Or maybe the hardware... Dunno...

Quoted 7 lines

Can you please send me a complete trace with the stb6100 and stb0899 modules loaded with verbose=5 for the 30MSPS transponder what you are trying ? One simple szap would be enough (no scan please) based on the http://jusst.de/hg/v4l-dvb tree.

Before you start testing, start clean from a cold boot after a powerdown. This makes it a bit more easier identify things.

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

A message that is not in the archive (sent off-list or not yet received): [email protected]

#40 lore raw
Quoted 8 lines · Manu
Quoted 7 lines

Can you please send me a complete trace with the stb6100 and stb0899 modules loaded with verbose=5 for the 30MSPS transponder what you are trying ? One simple szap would be enough (no scan please) based on the http://jusst.de/hg/v4l-dvb tree.

Before you start testing, start clean from a cold boot after a powerdown. This makes it a bit more easier identify things.

Quoted 10 lines

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

Sorry for the late reply, but the new list confuses the hell out of me and I missed this message, somehow...

Attached is a log file with the results of dvb-apps/szap on a 30000 3/4 channel using a http://jusst.de/hg/v4l-dvb clean compile and cold boot as recommended.

Also loaded stb6100 and stb0899 with verbose=5

Command line used and result:

root@vdr:/usr/local/src/v4l-dvb_multi/dvb-apps/util/szap# ./szap -c
/video/channels.conf -n 7
reading channels from file '/video/channels.conf'
zapping to 7 '[006b]':
sat 0, frequency = 12012 MHz H, symbolrate 30000000, vpid = 0x1031,
apid = 0x1032 sid = 0x1004
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |
[...]
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |

After that szapping to that problematic channel, I tried a DVB-S channel, which locks without problems.

root@vdr:/usr/local/src/v4l-dvb_multi/dvb-apps/util/szap# ./szap -c
/video/channels.conf -H -n 33
reading channels from file '/video/channels.conf'
zapping to 33 'FOX':
sat 0, frequency = 11617 MHz V, symbolrate 27500000, vpid = 0x1b30,
apid = 0x1b31 sid = 0x0000
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal  49% | snr   0% | ber 0 | unc -2 |
status 1e | signal   0% | snr   0% | ber 0 | unc -2 | FE_HAS_LOCK

Going to test your the same multiproto tree _with_ both patches you mentioned early on this thread.

BTW, I can see all those channels just fine using a DM800 and the provider original decoder with my subscription card.

I'm positive that dish/lnb/connections aren't the problem.

Thanks for taking the time to address this particular issue.

Chris

#41 lore raw
Quoted 60 lines · Chris Silva
Quoted 8 lines · Manu
Quoted 7 lines

Can you please send me a complete trace with the stb6100 and stb0899 modules loaded with verbose=5 for the 30MSPS transponder what you are trying ? One simple szap would be enough (no scan please) based on the http://jusst.de/hg/v4l-dvb tree.

Before you start testing, start clean from a cold boot after a powerdown. This makes it a bit more easier identify things.

Quoted 10 lines

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

Sorry for the late reply, but the new list confuses the hell out of me and I missed this message, somehow...

Attached is a log file with the results of dvb-apps/szap on a 30000 3/4 channel using a http://jusst.de/hg/v4l-dvb clean compile and cold boot as recommended.

Also loaded stb6100 and stb0899 with verbose=5

Command line used and result:

root@vdr:/usr/local/src/v4l-dvb_multi/dvb-apps/util/szap# ./szap -c
/video/channels.conf -n 7
reading channels from file '/video/channels.conf'
zapping to 7 '[006b]':
sat 0, frequency = 12012 MHz H, symbolrate 30000000, vpid = 0x1031,
apid = 0x1032 sid = 0x1004
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |
[...]
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |
status 00 | signal 7fb2 | snr 0000 | ber 00000000 | unc fffffffe |

After that szapping to that problematic channel, I tried a DVB-S channel, which locks without problems.

root@vdr:/usr/local/src/v4l-dvb_multi/dvb-apps/util/szap# ./szap -c
/video/channels.conf -H -n 33
reading channels from file '/video/channels.conf'
zapping to 33 'FOX':
sat 0, frequency = 11617 MHz V, symbolrate 27500000, vpid = 0x1b30,
apid = 0x1b31 sid = 0x0000
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
status 00 | signal  49% | snr   0% | ber 0 | unc -2 |
status 1e | signal   0% | snr   0% | ber 0 | unc -2 | FE_HAS_LOCK

Going to test your the same multiproto tree _with_ both patches you mentioned early on this thread.

Quoted 9 lines

BTW, I can see all those channels just fine using a DM800 and the provider original decoder with my subscription card.

I'm positive that dish/lnb/connections aren't the problem.

Thanks for taking the time to address this particular issue.

Chris

As promised, a log with the exact same conditions described above, but with increase_timeout.patch and fix_iterations.patch applied, referred to on this same thread.

Chris