ngene & Satix-S2 dual problems

ngene & Satix-S2 dual problems

[Robert Longbottom]

Hi all,

I have a Satix-S2 Dual that I'm trying to get to work properly so that I 
can use it under MythTv however I'm running into a few issues.  I 
previously posted about the problems I'm having here to the mythtv 
list[1], but didn't really get anywhere.  I've had chance to have a bit 
more of a play and I now seem to have a definite repeatable problem.

The problem is when a recording stops on one of the inputs, after about 
40s it causes the other input to loose it's signal lock and stop the 
recording as well.


Steps to demonstrate the problem (My Satix card is adapters 5 and 6)

In 3 seperate terminals set up femon/szap/cat to make a recording from 
one of the inputs:

1 - femon -a 6 -f 0 -H
2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
UNIVERSAL "BBC 1 London"
3 - cat /dev/dvb/adapter6/dvr0 > ad6.mpg

In 2 seperate terminals tune in the other input:

4 - femon -a 5 -f 0 -H
5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
UNIVERSAL "ITV1 London"

Both inputs are fine, signal is good, recording from adapter 6 works.

6 - Ctrl-C the szap process created in (5).

femon in (4) still reports status=SCVYL and decent signal strengh as if 
the adapter is still tuned and FE_HAS_LOCK.  After approximately 40 
seconds, either:

a) the signal drops significantly but the status remains at SCVYL and 
FE_HAS_LOCK

or

b) the signal drops and the status goes blank with no lock.

It doesn't seem to matter which of these two happen, but at the same 
time the recording on the other tuner looses it signal and stops 
recording, despite the fact that szap is still running in (2).  femon in 
(1) no longer reports FE_HAS_LOCK.

Strangely if I then try to restart the szap process created in terminal 
2 (to try and retune it) it just waits after printing out "using 
'/dev/dvb/....".  However if I then restart the szap process in terminal 
5, the one in terminal 2 suddenly kicks in and gets a lock.

Interestingly I found a link describing a 60s period the card is kept 
open for [2], which seems to be similar to my ~40s delay.  So it looks 
like when the second input on the card is closed the first input looses 
it's lock.

This obviously makes it pretty useless for MythTv and as a result it's 
not currently being used, which is a shame!

I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.

Does anyone else see this problem?  Is there anything I can do to try 
and fix / debug it?  Are there any bug fixes in the latest kernel that 
might help, or in the linux-dvb drivers that would help?

Any help or advice much appreciated.

Thanks,
Robert.

[1] - 
http://www.mailinglistarchive.com/html/mythtv-users@mythtv.org/2010-10/msg00725.html

[2] - https://patchwork.kernel.org/patch/87392/

Re: ngene & Satix-S2 dual problems

[Oliver Endriss]

Hi,

On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
> Hi all,
> 
> I have a Satix-S2 Dual that I'm trying to get to work properly so that I 
> can use it under MythTv however I'm running into a few issues.  I 
> previously posted about the problems I'm having here to the mythtv 
> list[1], but didn't really get anywhere.  I've had chance to have a bit 
> more of a play and I now seem to have a definite repeatable problem.
> 
> The problem is when a recording stops on one of the inputs, after about 
> 40s it causes the other input to loose it's signal lock and stop the 
> recording as well.
> 
> 
> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
> 
> In 3 seperate terminals set up femon/szap/cat to make a recording from 
> one of the inputs:
> 
> 1 - femon -a 6 -f 0 -H
> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
> UNIVERSAL "BBC 1 London"
> 3 - cat /dev/dvb/adapter6/dvr0 > ad6.mpg
> 
> In 2 seperate terminals tune in the other input:
> 
> 4 - femon -a 5 -f 0 -H
> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
> UNIVERSAL "ITV1 London"
> 
> Both inputs are fine, signal is good, recording from adapter 6 works.
> 
> 6 - Ctrl-C the szap process created in (5).
> 
> femon in (4) still reports status=SCVYL and decent signal strengh as if 
> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40 
> seconds, either:
> 
> a) the signal drops significantly but the status remains at SCVYL and 
> FE_HAS_LOCK
> 
> or
> 
> b) the signal drops and the status goes blank with no lock.
> 
> It doesn't seem to matter which of these two happen, but at the same 
> time the recording on the other tuner looses it signal and stops 
> recording, despite the fact that szap is still running in (2).  femon in 
> (1) no longer reports FE_HAS_LOCK.
> 
> Strangely if I then try to restart the szap process created in terminal 
> 2 (to try and retune it) it just waits after printing out "using 
> '/dev/dvb/....".  However if I then restart the szap process in terminal 
> 5, the one in terminal 2 suddenly kicks in and gets a lock.
> 
> Interestingly I found a link describing a 60s period the card is kept 
> open for [2], which seems to be similar to my ~40s delay.  So it looks 
> like when the second input on the card is closed the first input looses 
> it's lock.
> 
> This obviously makes it pretty useless for MythTv and as a result it's 
> not currently being used, which is a shame!
> 
> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
> 
> Does anyone else see this problem?  Is there anything I can do to try 
> and fix / debug it?  Are there any bug fixes in the latest kernel that 
> might help, or in the linux-dvb drivers that would help?
> 
> Any help or advice much appreciated.

Please try this driver:
http://linuxtv.org/hg/~endriss/ngene-test2

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------

Re: ngene & Satix-S2 dual problems

[Andre]

On 20 Nov 2010, at 19:22, Oliver Endriss wrote:

> Hi,
> 
> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>> Hi all,
>> 
>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I 
>> can use it under MythTv however I'm running into a few issues.  I 
>> previously posted about the problems I'm having here to the mythtv 
>> list[1], but didn't really get anywhere.  I've had chance to have a bit 
>> more of a play and I now seem to have a definite repeatable problem.
>> 
>> The problem is when a recording stops on one of the inputs, after about 
>> 40s it causes the other input to loose it's signal lock and stop the 
>> recording as well.
>> 
>> 
>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>> 
>> In 3 seperate terminals set up femon/szap/cat to make a recording from 
>> one of the inputs:
>> 
>> 1 - femon -a 6 -f 0 -H
>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>> UNIVERSAL "BBC 1 London"
>> 3 - cat /dev/dvb/adapter6/dvr0 > ad6.mpg
>> 
>> In 2 seperate terminals tune in the other input:
>> 
>> 4 - femon -a 5 -f 0 -H
>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>> UNIVERSAL "ITV1 London"
>> 
>> Both inputs are fine, signal is good, recording from adapter 6 works.
>> 
>> 6 - Ctrl-C the szap process created in (5).
>> 
>> femon in (4) still reports status=SCVYL and decent signal strengh as if 
>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40 
>> seconds, either:
>> 
>> a) the signal drops significantly but the status remains at SCVYL and 
>> FE_HAS_LOCK
>> 
>> or
>> 
>> b) the signal drops and the status goes blank with no lock.
>> 
>> It doesn't seem to matter which of these two happen, but at the same 
>> time the recording on the other tuner looses it signal and stops 
>> recording, despite the fact that szap is still running in (2).  femon in 
>> (1) no longer reports FE_HAS_LOCK.
>> 
>> Strangely if I then try to restart the szap process created in terminal 
>> 2 (to try and retune it) it just waits after printing out "using 
>> '/dev/dvb/....".  However if I then restart the szap process in terminal 
>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>> 
>> Interestingly I found a link describing a 60s period the card is kept 
>> open for [2], which seems to be similar to my ~40s delay.  So it looks 
>> like when the second input on the card is closed the first input looses 
>> it's lock.
>> 
>> This obviously makes it pretty useless for MythTv and as a result it's 
>> not currently being used, which is a shame!
>> 
>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>> 
>> Does anyone else see this problem?  Is there anything I can do to try 
>> and fix / debug it?  Are there any bug fixes in the latest kernel that 
>> might help, or in the linux-dvb drivers that would help?
>> 
>> Any help or advice much appreciated.
> 
> Please try this driver:
> http://linuxtv.org/hg/~endriss/ngene-test2

Great news, I'll give it a try this evening too.

Andre



> 
> CU
> Oliver
> 
> -- 
> ----------------------------------------------------------------
> VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
> 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
> Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
> ----------------------------------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: ngene & Satix-S2 dual problems

[Andre]

On 20 Nov 2010, at 19:22, Oliver Endriss wrote:

> Hi,
> 
> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>> Hi all,
>> 
>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I 
>> can use it under MythTv however I'm running into a few issues.  I 
>> previously posted about the problems I'm having here to the mythtv 
>> list[1], but didn't really get anywhere.  I've had chance to have a bit 
>> more of a play and I now seem to have a definite repeatable problem.
>> 
>> The problem is when a recording stops on one of the inputs, after about 
>> 40s it causes the other input to loose it's signal lock and stop the 
>> recording as well.
>> 
>> 
>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>> 
>> In 3 seperate terminals set up femon/szap/cat to make a recording from 
>> one of the inputs:
>> 
>> 1 - femon -a 6 -f 0 -H
>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>> UNIVERSAL "BBC 1 London"
>> 3 - cat /dev/dvb/adapter6/dvr0 > ad6.mpg
>> 
>> In 2 seperate terminals tune in the other input:
>> 
>> 4 - femon -a 5 -f 0 -H
>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>> UNIVERSAL "ITV1 London"
>> 
>> Both inputs are fine, signal is good, recording from adapter 6 works.
>> 
>> 6 - Ctrl-C the szap process created in (5).
>> 
>> femon in (4) still reports status=SCVYL and decent signal strengh as if 
>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40 
>> seconds, either:
>> 
>> a) the signal drops significantly but the status remains at SCVYL and 
>> FE_HAS_LOCK
>> 
>> or
>> 
>> b) the signal drops and the status goes blank with no lock.
>> 
>> It doesn't seem to matter which of these two happen, but at the same 
>> time the recording on the other tuner looses it signal and stops 
>> recording, despite the fact that szap is still running in (2).  femon in 
>> (1) no longer reports FE_HAS_LOCK.
>> 
>> Strangely if I then try to restart the szap process created in terminal 
>> 2 (to try and retune it) it just waits after printing out "using 
>> '/dev/dvb/....".  However if I then restart the szap process in terminal 
>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>> 
>> Interestingly I found a link describing a 60s period the card is kept 
>> open for [2], which seems to be similar to my ~40s delay.  So it looks 
>> like when the second input on the card is closed the first input looses 
>> it's lock.
>> 
>> This obviously makes it pretty useless for MythTv and as a result it's 
>> not currently being used, which is a shame!
>> 
>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>> 
>> Does anyone else see this problem?  Is there anything I can do to try 
>> and fix / debug it?  Are there any bug fixes in the latest kernel that 
>> might help, or in the linux-dvb drivers that would help?
>> 
>> Any help or advice much appreciated.
> 
> Please try this driver:
> http://linuxtv.org/hg/~endriss/ngene-test2

Well that's progress, trying Robert's procedure fails with my stock driver (Ubuntu 10.10's 2.6.35-22-generic) but recording continues with your ngene-test2 driver :-)

NB I needed to go grab ngene_18.fw before it would work and I have three unexpected extra frontends, adapter 0,1&2 as well as the configured 5&6, not sure what's going on there yet!

There's a ber bump on the other tuner when you retune but it carries on which is the main thing at this stage. Can see glitches at the corresponding spot in the recording but worth a try with Myth perhaps?

I've been running with only one of the tuners for months, perhaps best to switch off active eit collection though looking at that ber bump.

Great stuff Oliver.

Andre



> 
> CU
> Oliver
> 
> -- 
> ----------------------------------------------------------------
> VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
> 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
> Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
> ----------------------------------------------------------------
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

Re: ngene & Satix-S2 dual problems

[Robert Longbottom]

On 21 Nov 2010, at 11:40 AM, Andre <linux-media@dinkum.org.uk> wrote:

> 
> On 20 Nov 2010, at 19:22, Oliver Endriss wrote:
> 
>> Hi,
>> 
>> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>>> Hi all,
>>> 
>>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I 
>>> can use it under MythTv however I'm running into a few issues.  I 
>>> previously posted about the problems I'm having here to the mythtv 
>>> list[1], but didn't really get anywhere.  I've had chance to have a bit 
>>> more of a play and I now seem to have a definite repeatable problem.
>>> 
>>> The problem is when a recording stops on one of the inputs, after about 
>>> 40s it causes the other input to loose it's signal lock and stop the 
>>> recording as well.
>>> 
>>> 
>>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>>> 
>>> In 3 seperate terminals set up femon/szap/cat to make a recording from 
>>> one of the inputs:
>>> 
>>> 1 - femon -a 6 -f 0 -H
>>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>>> UNIVERSAL "BBC 1 London"
>>> 3 - cat /dev/dvb/adapter6/dvr0 > ad6.mpg
>>> 
>>> In 2 seperate terminals tune in the other input:
>>> 
>>> 4 - femon -a 5 -f 0 -H
>>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>>> UNIVERSAL "ITV1 London"
>>> 
>>> Both inputs are fine, signal is good, recording from adapter 6 works.
>>> 
>>> 6 - Ctrl-C the szap process created in (5).
>>> 
>>> femon in (4) still reports status=SCVYL and decent signal strengh as if 
>>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40 
>>> seconds, either:
>>> 
>>> a) the signal drops significantly but the status remains at SCVYL and 
>>> FE_HAS_LOCK
>>> 
>>> or
>>> 
>>> b) the signal drops and the status goes blank with no lock.
>>> 
>>> It doesn't seem to matter which of these two happen, but at the same 
>>> time the recording on the other tuner looses it signal and stops 
>>> recording, despite the fact that szap is still running in (2).  femon in 
>>> (1) no longer reports FE_HAS_LOCK.
>>> 
>>> Strangely if I then try to restart the szap process created in terminal 
>>> 2 (to try and retune it) it just waits after printing out "using 
>>> '/dev/dvb/....".  However if I then restart the szap process in terminal 
>>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>>> 
>>> Interestingly I found a link describing a 60s period the card is kept 
>>> open for [2], which seems to be similar to my ~40s delay.  So it looks 
>>> like when the second input on the card is closed the first input looses 
>>> it's lock.
>>> 
>>> This obviously makes it pretty useless for MythTv and as a result it's 
>>> not currently being used, which is a shame!
>>> 
>>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>>> 
>>> Does anyone else see this problem?  Is there anything I can do to try 
>>> and fix / debug it?  Are there any bug fixes in the latest kernel that 
>>> might help, or in the linux-dvb drivers that would help?
>>> 
>>> Any help or advice much appreciated.
>> 
>> Please try this driver:
>> http://linuxtv.org/hg/~endriss/ngene-test2
> 
> Well that's progress, trying Robert's procedure fails with my stock driver (Ubuntu 10.10's 2.6.35-22-generic) but recording continues with your ngene-test2 driver :-)
> 
> NB I needed to go grab ngene_18.fw before it would work and I have three unexpected extra frontends, adapter 0,1&2 as well as the configured 5&6, not sure what's going on there yet!
> 
> There's a ber bump on the other tuner when you retune but it carries on which is the main thing at this stage. Can see glitches at the corresponding spot in the recording but worth a try with Myth perhaps?
> 
> I've been running with only one of the tuners for months, perhaps best to switch off active eit collection though looking at that ber bump.
> 
> Great stuff Oliver.
> 
> Andre
> 
> 

That does sound like good news, I'll try and give it a go later today now that I have a process to test with. If it does appear to have fixed it then I'll switch myth over to using it later next week and see how it gets on. 

Will report back with the results later. 

Robert. 

> 
>> 
>> CU
>> Oliver
>> 
>> -- 
>> ----------------------------------------------------------------
>> VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
>> 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
>> Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
>> ----------------------------------------------------------------
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>> 
> 

Re: ngene & Satix-S2 dual problems

[Andre]

On 21 Nov 2010, at 13:07, Robert Longbottom wrote:

> 
> 
> On 21 Nov 2010, at 11:40 AM, Andre <linux-media@dinkum.org.uk> wrote:
> 
>> 
>> On 20 Nov 2010, at 19:22, Oliver Endriss wrote:
>> 
>>> Hi,
>>> 
>>> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>>>> Hi all,
>>>> 
>>>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I 
>>>> can use it under MythTv however I'm running into a few issues.  I 
>>>> previously posted about the problems I'm having here to the mythtv 
>>>> list[1], but didn't really get anywhere.  I've had chance to have a bit 
>>>> more of a play and I now seem to have a definite repeatable problem.
>>>> 
>>>> The problem is when a recording stops on one of the inputs, after about 
>>>> 40s it causes the other input to loose it's signal lock and stop the 
>>>> recording as well.
>>>> 
>>>> 
>>>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>>>> 
>>>> In 3 seperate terminals set up femon/szap/cat to make a recording from 
>>>> one of the inputs:
>>>> 
>>>> 1 - femon -a 6 -f 0 -H
>>>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>>>> UNIVERSAL "BBC 1 London"
>>>> 3 - cat /dev/dvb/adapter6/dvr0 > ad6.mpg
>>>> 
>>>> In 2 seperate terminals tune in the other input:
>>>> 
>>>> 4 - femon -a 5 -f 0 -H
>>>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l 
>>>> UNIVERSAL "ITV1 London"
>>>> 
>>>> Both inputs are fine, signal is good, recording from adapter 6 works.
>>>> 
>>>> 6 - Ctrl-C the szap process created in (5).
>>>> 
>>>> femon in (4) still reports status=SCVYL and decent signal strengh as if 
>>>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40 
>>>> seconds, either:
>>>> 
>>>> a) the signal drops significantly but the status remains at SCVYL and 
>>>> FE_HAS_LOCK
>>>> 
>>>> or
>>>> 
>>>> b) the signal drops and the status goes blank with no lock.
>>>> 
>>>> It doesn't seem to matter which of these two happen, but at the same 
>>>> time the recording on the other tuner looses it signal and stops 
>>>> recording, despite the fact that szap is still running in (2).  femon in 
>>>> (1) no longer reports FE_HAS_LOCK.
>>>> 
>>>> Strangely if I then try to restart the szap process created in terminal 
>>>> 2 (to try and retune it) it just waits after printing out "using 
>>>> '/dev/dvb/....".  However if I then restart the szap process in terminal 
>>>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>>>> 
>>>> Interestingly I found a link describing a 60s period the card is kept 
>>>> open for [2], which seems to be similar to my ~40s delay.  So it looks 
>>>> like when the second input on the card is closed the first input looses 
>>>> it's lock.
>>>> 
>>>> This obviously makes it pretty useless for MythTv and as a result it's 
>>>> not currently being used, which is a shame!
>>>> 
>>>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>>>> 
>>>> Does anyone else see this problem?  Is there anything I can do to try 
>>>> and fix / debug it?  Are there any bug fixes in the latest kernel that 
>>>> might help, or in the linux-dvb drivers that would help?
>>>> 
>>>> Any help or advice much appreciated.
>>> 
>>> Please try this driver:
>>> http://linuxtv.org/hg/~endriss/ngene-test2
>> 
>> Well that's progress, trying Robert's procedure fails with my stock driver (Ubuntu 10.10's 2.6.35-22-generic) but recording continues with your ngene-test2 driver :-)
>> 
>> NB I needed to go grab ngene_18.fw before it would work and I have three unexpected extra frontends, adapter 0,1&2 as well as the configured 5&6, not sure what's going on there yet!
>> 
>> There's a ber bump on the other tuner when you retune but it carries on which is the main thing at this stage. Can see glitches at the corresponding spot in the recording but worth a try with Myth perhaps?
>> 
>> I've been running with only one of the tuners for months, perhaps best to switch off active eit collection though looking at that ber bump.
>> 
>> Great stuff Oliver.
>> 
>> Andre
>> 
>> 
> 
> That does sound like good news, I'll try and give it a go later today now that I have a process to test with. If it does appear to have fixed it then I'll switch myth over to using it later next week and see how it gets on. 

I tried it with Myth 0.24 and just got six simultaneous HD recordings out of it :-)) total seven if you count the one I started to keep the HD-S2 card busy, can't try any more with that sat and my sub.

No glitches I can see, tried it a couple of times with different muxes, so far so good.
> 
> Will report back with the results later. 

You can have your thread back now ;-)

Andre


> 
> Robert. 
> 
>> 
>>> 
>>> CU
>>> Oliver
>>> 
>>> -- 
>>> ----------------------------------------------------------------
>>> VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
>>> 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
>>> Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
>>> ----------------------------------------------------------------
>>> --
>>> To unsubscribe from this list: send the line "unsubscribe linux-media" in
>>> the body of a message to majordomo@vger.kernel.org
>>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>> 
>> 
> 

Re: ngene & Satix-S2 dual problems

[Robert Longbottom]

On 21/11/2010 13:15, Andre wrote:
>
> On 21 Nov 2010, at 13:07, Robert Longbottom wrote:
>
>>
>>
>> On 21 Nov 2010, at 11:40 AM, Andre<linux-media@dinkum.org.uk>  wrote:
>>
>>>
>>> On 20 Nov 2010, at 19:22, Oliver Endriss wrote:
>>>
>>>> Hi,
>>>>
>>>> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>>>>> Hi all,
>>>>>
>>>>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I
>>>>> can use it under MythTv however I'm running into a few issues.  I
>>>>> previously posted about the problems I'm having here to the mythtv
>>>>> list[1], but didn't really get anywhere.  I've had chance to have a bit
>>>>> more of a play and I now seem to have a definite repeatable problem.
>>>>>
>>>>> The problem is when a recording stops on one of the inputs, after about
>>>>> 40s it causes the other input to loose it's signal lock and stop the
>>>>> recording as well.
>>>>>
>>>>>
>>>>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>>>>>
>>>>> In 3 seperate terminals set up femon/szap/cat to make a recording from
>>>>> one of the inputs:
>>>>>
>>>>> 1 - femon -a 6 -f 0 -H
>>>>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l
>>>>> UNIVERSAL "BBC 1 London"
>>>>> 3 - cat /dev/dvb/adapter6/dvr0>  ad6.mpg
>>>>>
>>>>> In 2 seperate terminals tune in the other input:
>>>>>
>>>>> 4 - femon -a 5 -f 0 -H
>>>>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l
>>>>> UNIVERSAL "ITV1 London"
>>>>>
>>>>> Both inputs are fine, signal is good, recording from adapter 6 works.
>>>>>
>>>>> 6 - Ctrl-C the szap process created in (5).
>>>>>
>>>>> femon in (4) still reports status=SCVYL and decent signal strengh as if
>>>>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40
>>>>> seconds, either:
>>>>>
>>>>> a) the signal drops significantly but the status remains at SCVYL and
>>>>> FE_HAS_LOCK
>>>>>
>>>>> or
>>>>>
>>>>> b) the signal drops and the status goes blank with no lock.
>>>>>
>>>>> It doesn't seem to matter which of these two happen, but at the same
>>>>> time the recording on the other tuner looses it signal and stops
>>>>> recording, despite the fact that szap is still running in (2).  femon in
>>>>> (1) no longer reports FE_HAS_LOCK.
>>>>>
>>>>> Strangely if I then try to restart the szap process created in terminal
>>>>> 2 (to try and retune it) it just waits after printing out "using
>>>>> '/dev/dvb/....".  However if I then restart the szap process in terminal
>>>>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>>>>>
>>>>> Interestingly I found a link describing a 60s period the card is kept
>>>>> open for [2], which seems to be similar to my ~40s delay.  So it looks
>>>>> like when the second input on the card is closed the first input looses
>>>>> it's lock.
>>>>>
>>>>> This obviously makes it pretty useless for MythTv and as a result it's
>>>>> not currently being used, which is a shame!
>>>>>
>>>>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>>>>>
>>>>> Does anyone else see this problem?  Is there anything I can do to try
>>>>> and fix / debug it?  Are there any bug fixes in the latest kernel that
>>>>> might help, or in the linux-dvb drivers that would help?
>>>>>
>>>>> Any help or advice much appreciated.
>>>>
>>>> Please try this driver:
>>>> http://linuxtv.org/hg/~endriss/ngene-test2
>>>
>>> Well that's progress, trying Robert's procedure fails with my stock driver (Ubuntu 10.10's 2.6.35-22-generic) but recording continues with your ngene-test2 driver :-)
>>>
>>> NB I needed to go grab ngene_18.fw before it would work and I have three unexpected extra frontends, adapter 0,1&2 as well as the configured 5&6, not sure what's going on there yet!
>>>
>>> There's a ber bump on the other tuner when you retune but it carries on which is the main thing at this stage. Can see glitches at the corresponding spot in the recording but worth a try with Myth perhaps?
>>>
>>> I've been running with only one of the tuners for months, perhaps best to switch off active eit collection though looking at that ber bump.
>>>
>>> Great stuff Oliver.
>>>
>>> Andre
>>>
>>>
>>
>> That does sound like good news, I'll try and give it a go later today now that I have a process to test with. If it does appear to have fixed it then I'll switch myth over to using it later next week and see how it gets on.
>
> I tried it with Myth 0.24 and just got six simultaneous HD recordings out of it :-)) total seven if you count the one I started to keep the HD-S2 card busy, can't try any more with that sat and my sub.
>
> No glitches I can see, tried it a couple of times with different muxes, so far so good.
>>
>> Will report back with the results later.
>
> You can have your thread back now ;-)

Thanks ;-)  The more people that test this and iron out the bugs the 
better :-)

I've run through my procedure again using the ngene-test2 drivers from 
Oliver and I can report success as well.  I too see a glitch on the 2nd 
tuner when you retune the 1st, or after about 30s from killing an szap 
against the 1st, but the stream on the second tuner continues, so thats 
a massive improvement.  Good work.

I'll give it a quick go with MythTV as well tonight, and later next 
week.  Previously when I tried this tuner with MythTV it would record 
upto 6 streams with no problem, but of couse when one tuner dropped out 
of use the streams using the other tuner would stop recording (but I 
didn't know why at the time).  I just need to set up a cunning array of 
recordings to test that through MythTV, but it looks pretty promising so 
far.

Oh, I also get the three extra dvb adapters, in my case 1,2 & 3.  (I 
already have two other dvb cards in this box that take 0 and 4)  Thats 
using these module parameters:

robert@quad /sys/module/ngene/parameters $ grep -iH . *
adapter_nr:5,6,-1,-1,-1,-1,-1,-1
debug:0
one_adapter:0
shutdown_workaround:0



If I use the default parameters:
robert@quad /sys/module/ngene/parameters $ grep -iH . *
adapter_nr:-1,-1,-1,-1,-1,-1,-1,-1
debug:0
one_adapter:1
shutdown_workaround:0

I only get one dvb adapter (/dev/dvb/adapter1), but it contains too much 
stuff (extra demuxes, dvrs & nets):

robert@quad /dev/dvb $ ls -l adapter1
total 0
crw-rw---- 1 root video 212,  0 Nov 21 17:09 demux0
crw-rw---- 1 root video 212,  7 Nov 21 17:09 demux1
crw-rw---- 1 root video 212, 11 Nov 21 17:09 demux2
crw-rw---- 1 root video 212, 14 Nov 21 17:09 demux3
crw-rw---- 1 root video 212, 17 Nov 21 17:09 demux4
crw-rw---- 1 root video 212,  1 Nov 21 17:09 dvr0
crw-rw---- 1 root video 212,  8 Nov 21 17:09 dvr1
crw-rw---- 1 root video 212, 12 Nov 21 17:09 dvr2
crw-rw---- 1 root video 212, 15 Nov 21 17:09 dvr3
crw-rw---- 1 root video 212, 18 Nov 21 17:09 dvr4
crw-rw---- 1 root video 212,  6 Nov 21 17:09 frontend0
crw-rw---- 1 root video 212, 10 Nov 21 17:09 frontend1
crw-rw---- 1 root video 212,  2 Nov 21 17:09 net0
crw-rw---- 1 root video 212,  9 Nov 21 17:09 net1
crw-rw---- 1 root video 212, 13 Nov 21 17:09 net2
crw-rw---- 1 root video 212, 16 Nov 21 17:09 net3
crw-rw---- 1 root video 212, 19 Nov 21 17:09 net4

dmesg reports the following when you do 'modprobe ngene' if that helps 
at all:

[ 4504.852993] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[ 4504.853039] ngene 0000:02:00.0: PCI INT A -> Link[APC5] -> GSI 16 
(level, low) -> IRQ 16
[ 4504.853048] ngene: Found Mystique SaTiX-S2 Dual (v2)
[ 4504.855133] ngene 0000:02:00.0: setting latency timer to 64
[ 4504.855667] ngene: Device version 1
[ 4504.857551] ngene: Loading firmware file ngene_18.fw.
[ 4504.876640] ngene 0000:02:00.0: irq 41 for MSI/MSI-X
[ 4504.878124] error in i2c_read_reg
[ 4504.878127] No CXD2099 detected at 40
[ 4504.878285] DVB: registering new adapter (nGene)
[ 4505.159774] LNBx2x attached on addr=a
[ 4505.159859] stv6110x_attach: Attaching STV6110x
[ 4505.159864] DVB: registering adapter 1 frontend 0 (STV090x 
Multistandard)...
[ 4505.165626] LNBx2x attached on addr=8
[ 4505.165894] stv6110x_attach: Attaching STV6110x
[ 4505.165901] DVB: registering adapter 1 frontend 0 (STV090x 
Multistandard)...

Thanks,
Robert.

Re: ngene & Satix-S2 dual problems

[Andre]

On 21 Nov 2010, at 17:23, Robert Longbottom wrote:

> On 21/11/2010 13:15, Andre wrote:
>> 
>> On 21 Nov 2010, at 13:07, Robert Longbottom wrote:
>> 
>>> 
>>> 
>>> On 21 Nov 2010, at 11:40 AM, Andre<linux-media@dinkum.org.uk>  wrote:
>>> 
>>>> 
>>>> On 20 Nov 2010, at 19:22, Oliver Endriss wrote:
>>>> 
>>>>> Hi,
>>>>> 
>>>>> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>>>>>> Hi all,
>>>>>> 
>>>>>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I
>>>>>> can use it under MythTv however I'm running into a few issues.  I
>>>>>> previously posted about the problems I'm having here to the mythtv
>>>>>> list[1], but didn't really get anywhere.  I've had chance to have a bit
>>>>>> more of a play and I now seem to have a definite repeatable problem.
>>>>>> 
>>>>>> The problem is when a recording stops on one of the inputs, after about
>>>>>> 40s it causes the other input to loose it's signal lock and stop the
>>>>>> recording as well.
>>>>>> 
>>>>>> 
>>>>>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>>>>>> 
>>>>>> In 3 seperate terminals set up femon/szap/cat to make a recording from
>>>>>> one of the inputs:
>>>>>> 
>>>>>> 1 - femon -a 6 -f 0 -H
>>>>>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l
>>>>>> UNIVERSAL "BBC 1 London"
>>>>>> 3 - cat /dev/dvb/adapter6/dvr0>  ad6.mpg
>>>>>> 
>>>>>> In 2 seperate terminals tune in the other input:
>>>>>> 
>>>>>> 4 - femon -a 5 -f 0 -H
>>>>>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l
>>>>>> UNIVERSAL "ITV1 London"
>>>>>> 
>>>>>> Both inputs are fine, signal is good, recording from adapter 6 works.
>>>>>> 
>>>>>> 6 - Ctrl-C the szap process created in (5).
>>>>>> 
>>>>>> femon in (4) still reports status=SCVYL and decent signal strengh as if
>>>>>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40
>>>>>> seconds, either:
>>>>>> 
>>>>>> a) the signal drops significantly but the status remains at SCVYL and
>>>>>> FE_HAS_LOCK
>>>>>> 
>>>>>> or
>>>>>> 
>>>>>> b) the signal drops and the status goes blank with no lock.
>>>>>> 
>>>>>> It doesn't seem to matter which of these two happen, but at the same
>>>>>> time the recording on the other tuner looses it signal and stops
>>>>>> recording, despite the fact that szap is still running in (2).  femon in
>>>>>> (1) no longer reports FE_HAS_LOCK.
>>>>>> 
>>>>>> Strangely if I then try to restart the szap process created in terminal
>>>>>> 2 (to try and retune it) it just waits after printing out "using
>>>>>> '/dev/dvb/....".  However if I then restart the szap process in terminal
>>>>>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>>>>>> 
>>>>>> Interestingly I found a link describing a 60s period the card is kept
>>>>>> open for [2], which seems to be similar to my ~40s delay.  So it looks
>>>>>> like when the second input on the card is closed the first input looses
>>>>>> it's lock.
>>>>>> 
>>>>>> This obviously makes it pretty useless for MythTv and as a result it's
>>>>>> not currently being used, which is a shame!
>>>>>> 
>>>>>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>>>>>> 
>>>>>> Does anyone else see this problem?  Is there anything I can do to try
>>>>>> and fix / debug it?  Are there any bug fixes in the latest kernel that
>>>>>> might help, or in the linux-dvb drivers that would help?
>>>>>> 
>>>>>> Any help or advice much appreciated.
>>>>> 
>>>>> Please try this driver:
>>>>> http://linuxtv.org/hg/~endriss/ngene-test2
>>>> 
>>>> Well that's progress, trying Robert's procedure fails with my stock driver (Ubuntu 10.10's 2.6.35-22-generic) but recording continues with your ngene-test2 driver :-)
>>>> 
>>>> NB I needed to go grab ngene_18.fw before it would work and I have three unexpected extra frontends, adapter 0,1&2 as well as the configured 5&6, not sure what's going on there yet!
>>>> 
>>>> There's a ber bump on the other tuner when you retune but it carries on which is the main thing at this stage. Can see glitches at the corresponding spot in the recording but worth a try with Myth perhaps?
>>>> 
>>>> I've been running with only one of the tuners for months, perhaps best to switch off active eit collection though looking at that ber bump.
>>>> 
>>>> Great stuff Oliver.
>>>> 
>>>> Andre
>>>> 
>>>> 
>>> 
>>> That does sound like good news, I'll try and give it a go later today now that I have a process to test with. If it does appear to have fixed it then I'll switch myth over to using it later next week and see how it gets on.
>> 
>> I tried it with Myth 0.24 and just got six simultaneous HD recordings out of it :-)) total seven if you count the one I started to keep the HD-S2 card busy, can't try any more with that sat and my sub.
>> 
>> No glitches I can see, tried it a couple of times with different muxes, so far so good.
>>> 
>>> Will report back with the results later.
>> 
>> You can have your thread back now ;-)
> 
> Thanks ;-)  The more people that test this and iron out the bugs the better :-)

I've got an email monitor looking for any mention of the ngene in here, mythtv, hts & vdr lists so I can see if there is any activity, looking for just this kind of email :-)


> 
> I've run through my procedure again using the ngene-test2 drivers from Oliver and I can report success as well.  I too see a glitch on the 2nd tuner when you retune the 1st, or after about 30s from killing an szap against the 1st, but the stream on the second tuner continues, so thats a massive improvement.  Good work.
> 
> I'll give it a quick go with MythTV as well tonight, and later next week.  Previously when I tried this tuner with MythTV it would record upto 6 streams with no problem, but of couse when one tuner dropped out of use the streams using the other tuner would stop recording (but I didn't know why at the time).  I just need to set up a cunning array of recordings to test that through MythTV, but it looks pretty promising so far.
> 
> Oh, I also get the three extra dvb adapters, in my case 1,2 & 3.  (I already have two other dvb cards in this box that take 0 and 4)  Thats using these module parameters:

That's definitely odd, it's the ngene that's generating them not any of the other cards I have. I just managed to get everything to fit in the default 8 adaptors, I can't use one_adaptor=1 as dvbloopback doesn't work with that.

The extra nodes seem to be a harmless oddity and this driver is a massive improvement, big thank you to Oliver.

Report back in a few days, my system records ~ 10 hours of HD a day, small percentage of which I actually watch so it should get a workout.

Andre

> 
> robert@quad /sys/module/ngene/parameters $ grep -iH . *
> adapter_nr:5,6,-1,-1,-1,-1,-1,-1
> debug:0
> one_adapter:0
> shutdown_workaround:0
> 
> 
> 
> If I use the default parameters:
> robert@quad /sys/module/ngene/parameters $ grep -iH . *
> adapter_nr:-1,-1,-1,-1,-1,-1,-1,-1
> debug:0
> one_adapter:1
> shutdown_workaround:0
> 
> I only get one dvb adapter (/dev/dvb/adapter1), but it contains too much stuff (extra demuxes, dvrs & nets):
> 
> robert@quad /dev/dvb $ ls -l adapter1
> total 0
> crw-rw---- 1 root video 212,  0 Nov 21 17:09 demux0
> crw-rw---- 1 root video 212,  7 Nov 21 17:09 demux1
> crw-rw---- 1 root video 212, 11 Nov 21 17:09 demux2
> crw-rw---- 1 root video 212, 14 Nov 21 17:09 demux3
> crw-rw---- 1 root video 212, 17 Nov 21 17:09 demux4
> crw-rw---- 1 root video 212,  1 Nov 21 17:09 dvr0
> crw-rw---- 1 root video 212,  8 Nov 21 17:09 dvr1
> crw-rw---- 1 root video 212, 12 Nov 21 17:09 dvr2
> crw-rw---- 1 root video 212, 15 Nov 21 17:09 dvr3
> crw-rw---- 1 root video 212, 18 Nov 21 17:09 dvr4
> crw-rw---- 1 root video 212,  6 Nov 21 17:09 frontend0
> crw-rw---- 1 root video 212, 10 Nov 21 17:09 frontend1
> crw-rw---- 1 root video 212,  2 Nov 21 17:09 net0
> crw-rw---- 1 root video 212,  9 Nov 21 17:09 net1
> crw-rw---- 1 root video 212, 13 Nov 21 17:09 net2
> crw-rw---- 1 root video 212, 16 Nov 21 17:09 net3
> crw-rw---- 1 root video 212, 19 Nov 21 17:09 net4
> 
> dmesg reports the following when you do 'modprobe ngene' if that helps at all:
> 
> [ 4504.852993] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
> [ 4504.853039] ngene 0000:02:00.0: PCI INT A -> Link[APC5] -> GSI 16 (level, low) -> IRQ 16
> [ 4504.853048] ngene: Found Mystique SaTiX-S2 Dual (v2)
> [ 4504.855133] ngene 0000:02:00.0: setting latency timer to 64
> [ 4504.855667] ngene: Device version 1
> [ 4504.857551] ngene: Loading firmware file ngene_18.fw.
> [ 4504.876640] ngene 0000:02:00.0: irq 41 for MSI/MSI-X
> [ 4504.878124] error in i2c_read_reg
> [ 4504.878127] No CXD2099 detected at 40
> [ 4504.878285] DVB: registering new adapter (nGene)
> [ 4505.159774] LNBx2x attached on addr=a
> [ 4505.159859] stv6110x_attach: Attaching STV6110x
> [ 4505.159864] DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
> [ 4505.165626] LNBx2x attached on addr=8
> [ 4505.165894] stv6110x_attach: Attaching STV6110x
> [ 4505.165901] DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
> 
> Thanks,
> Robert.
> 

Re: ngene & Satix-S2 dual problems

[Robert Longbottom]

On 21/11/2010 19:23, Andre wrote:
>
> On 21 Nov 2010, at 17:23, Robert Longbottom wrote:
>
>> On 21/11/2010 13:15, Andre wrote:
>>>
>>> On 21 Nov 2010, at 13:07, Robert Longbottom wrote:
>>>
>>>>
>>>>
>>>> On 21 Nov 2010, at 11:40 AM, Andre<linux-media@dinkum.org.uk>   wrote:
>>>>
>>>>>
>>>>> On 20 Nov 2010, at 19:22, Oliver Endriss wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> On Saturday 20 November 2010 16:52:34 Robert Longbottom wrote:
>>>>>>> Hi all,
>>>>>>>
>>>>>>> I have a Satix-S2 Dual that I'm trying to get to work properly so that I
>>>>>>> can use it under MythTv however I'm running into a few issues.  I
>>>>>>> previously posted about the problems I'm having here to the mythtv
>>>>>>> list[1], but didn't really get anywhere.  I've had chance to have a bit
>>>>>>> more of a play and I now seem to have a definite repeatable problem.
>>>>>>>
>>>>>>> The problem is when a recording stops on one of the inputs, after about
>>>>>>> 40s it causes the other input to loose it's signal lock and stop the
>>>>>>> recording as well.
>>>>>>>
>>>>>>>
>>>>>>> Steps to demonstrate the problem (My Satix card is adapters 5 and 6)
>>>>>>>
>>>>>>> In 3 seperate terminals set up femon/szap/cat to make a recording from
>>>>>>> one of the inputs:
>>>>>>>
>>>>>>> 1 - femon -a 6 -f 0 -H
>>>>>>> 2 - szap -a 6 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l
>>>>>>> UNIVERSAL "BBC 1 London"
>>>>>>> 3 - cat /dev/dvb/adapter6/dvr0>   ad6.mpg
>>>>>>>
>>>>>>> In 2 seperate terminals tune in the other input:
>>>>>>>
>>>>>>> 4 - femon -a 5 -f 0 -H
>>>>>>> 5 - szap -a 5 -f 0 -d 0 -r -H -p -c scanResult07Oct2010_Satix -l
>>>>>>> UNIVERSAL "ITV1 London"
>>>>>>>
>>>>>>> Both inputs are fine, signal is good, recording from adapter 6 works.
>>>>>>>
>>>>>>> 6 - Ctrl-C the szap process created in (5).
>>>>>>>
>>>>>>> femon in (4) still reports status=SCVYL and decent signal strengh as if
>>>>>>> the adapter is still tuned and FE_HAS_LOCK.  After approximately 40
>>>>>>> seconds, either:
>>>>>>>
>>>>>>> a) the signal drops significantly but the status remains at SCVYL and
>>>>>>> FE_HAS_LOCK
>>>>>>>
>>>>>>> or
>>>>>>>
>>>>>>> b) the signal drops and the status goes blank with no lock.
>>>>>>>
>>>>>>> It doesn't seem to matter which of these two happen, but at the same
>>>>>>> time the recording on the other tuner looses it signal and stops
>>>>>>> recording, despite the fact that szap is still running in (2).  femon in
>>>>>>> (1) no longer reports FE_HAS_LOCK.
>>>>>>>
>>>>>>> Strangely if I then try to restart the szap process created in terminal
>>>>>>> 2 (to try and retune it) it just waits after printing out "using
>>>>>>> '/dev/dvb/....".  However if I then restart the szap process in terminal
>>>>>>> 5, the one in terminal 2 suddenly kicks in and gets a lock.
>>>>>>>
>>>>>>> Interestingly I found a link describing a 60s period the card is kept
>>>>>>> open for [2], which seems to be similar to my ~40s delay.  So it looks
>>>>>>> like when the second input on the card is closed the first input looses
>>>>>>> it's lock.
>>>>>>>
>>>>>>> This obviously makes it pretty useless for MythTv and as a result it's
>>>>>>> not currently being used, which is a shame!
>>>>>>>
>>>>>>> I'm using the ngene driver from the stock 2.6.35.4 kernel on Gentoo.
>>>>>>>
>>>>>>> Does anyone else see this problem?  Is there anything I can do to try
>>>>>>> and fix / debug it?  Are there any bug fixes in the latest kernel that
>>>>>>> might help, or in the linux-dvb drivers that would help?
>>>>>>>
>>>>>>> Any help or advice much appreciated.
>>>>>>
>>>>>> Please try this driver:
>>>>>> http://linuxtv.org/hg/~endriss/ngene-test2
>>>>>
>>>>> Well that's progress, trying Robert's procedure fails with my stock driver (Ubuntu 10.10's 2.6.35-22-generic) but recording continues with your ngene-test2 driver :-)
>>>>>
>>>>> NB I needed to go grab ngene_18.fw before it would work and I have three unexpected extra frontends, adapter 0,1&2 as well as the configured 5&6, not sure what's going on there yet!
>>>>>
>>>>> There's a ber bump on the other tuner when you retune but it carries on which is the main thing at this stage. Can see glitches at the corresponding spot in the recording but worth a try with Myth perhaps?
>>>>>
>>>>> I've been running with only one of the tuners for months, perhaps best to switch off active eit collection though looking at that ber bump.
>>>>>
>>>>> Great stuff Oliver.
>>>>>
>>>>> Andre
>>>>>
>>>>>
>>>>
>>>> That does sound like good news, I'll try and give it a go later today now that I have a process to test with. If it does appear to have fixed it then I'll switch myth over to using it later next week and see how it gets on.
>>>
>>> I tried it with Myth 0.24 and just got six simultaneous HD recordings out of it :-)) total seven if you count the one I started to keep the HD-S2 card busy, can't try any more with that sat and my sub.
>>>
>>> No glitches I can see, tried it a couple of times with different muxes, so far so good.
>>>>
>>>> Will report back with the results later.
>>>
>>> You can have your thread back now ;-)
>>
>> Thanks ;-)  The more people that test this and iron out the bugs the better :-)
>
> I've got an email monitor looking for any mention of the ngene in here, mythtv, hts&  vdr lists so I can see if there is any activity, looking for just this kind of email :-)

Ah, neat :-)


>> I've run through my procedure again using the ngene-test2 drivers from Oliver and I can report success as well.  I too see a glitch on the 2nd tuner when you retune the 1st, or after about 30s from killing an szap against the 1st, but the stream on the second tuner continues, so thats a massive improvement.  Good work.
>>
>> I'll give it a quick go with MythTV as well tonight, and later next week.  Previously when I tried this tuner with MythTV it would record upto 6 streams with no problem, but of couse when one tuner dropped out of use the streams using the other tuner would stop recording (but I didn't know why at the time).  I just need to set up a cunning array of recordings to test that through MythTV, but it looks pretty promising so far.
>>
>> Oh, I also get the three extra dvb adapters, in my case 1,2&  3.  (I already have two other dvb cards in this box that take 0 and 4)  Thats using these module parameters:
>
> That's definitely odd, it's the ngene that's generating them not any of the other cards I have. I just managed to get everything to fit in the default 8 adaptors, I can't use one_adaptor=1 as dvbloopback doesn't work with that.

Yes, it's definitely ngene thats creating them, because if I rmmod it, 
then they dissapear.  My other two cards use other drivers.

> The extra nodes seem to be a harmless oddity and this driver is a massive improvement, big thank you to Oliver.

Indeed, they don't seem to break anything or stop the Satix card from 
working.  And yes, this driver is a massive improvement in terms of 
being able to use both tuners.

> Report back in a few days, my system records ~ 10 hours of HD a day, small percentage of which I actually watch so it should get a workout.

I've run a few tests this evening with MythTv recording up to 6 
simultaneous programs across the two tuners on the Satix and it seems to 
be holding up so far.  A mixture of SD and HD.  It did have a couple of 
instances where it didn't immediately get a lock on a couple of channels 
when I was surfing livetv, but I'm willing to put that down to just 
bedding in for now.

I'm just debating whether to leave it as the active card and see how it 
gets on.  Assuming it manages this evenings recordings ok, I think I 
will probably will.

Cheers,
Robert.

Re: ngene & Satix-S2 dual problems

[Ludovic BOUÉ]

Hi all,

I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2 
from http://linuxtv.org/hg/~endriss/ngene-test2/ under 
2.6.32-21-generic.

It contains too much nodes (extra demuxes, dvrs & nets):

> ubuntu@ubuntu:~/ngene-test2/v4l$ ls -l /dev/dvb/adapter*
> total 0
> crw-rw----+ 1 root video 212,  0 2010-12-26 13:08 demux0
> crw-rw----+ 1 root video 212,  4 2010-12-26 13:08 demux1
> crw-rw----+ 1 root video 212,  8 2010-12-26 13:08 demux2
> crw-rw----+ 1 root video 212, 11 2010-12-26 13:08 demux3
> crw-rw----+ 1 root video 212, 14 2010-12-26 13:08 demux4
> crw-rw----+ 1 root video 212,  1 2010-12-26 13:08 dvr0
> crw-rw----+ 1 root video 212,  5 2010-12-26 13:08 dvr1
> crw-rw----+ 1 root video 212,  9 2010-12-26 13:08 dvr2
> crw-rw----+ 1 root video 212, 12 2010-12-26 13:08 dvr3
> crw-rw----+ 1 root video 212, 15 2010-12-26 13:08 dvr4
> crw-rw----+ 1 root video 212,  3 2010-12-26 13:08 frontend0
> crw-rw----+ 1 root video 212,  7 2010-12-26 13:08 frontend1
> crw-rw----+ 1 root video 212,  2 2010-12-26 13:08 net0
> crw-rw----+ 1 root video 212,  6 2010-12-26 13:08 net1
> crw-rw----+ 1 root video 212, 10 2010-12-26 13:08 net2
> crw-rw----+ 1 root video 212, 13 2010-12-26 13:08 net3
> crw-rw----+ 1 root video 212, 16 2010-12-26 13:08 net4
Is it connected to this commit (http://linuxtv.org/hg/~endriss/ngene-test2/rev/eb4142f0d0ac) about "Support up to 4 tuners for cineS2 v5, duoflex & mystique v2" ?

Here is what dmesg reports I do 'modprobe ngene'

> [ 3248.072496] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
> [ 3248.072533] ngene 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 3248.072548] ngene: Found Mystique SaTiX-S2 Dual (v2)
> [ 3248.075765] ngene 0000:02:00.0: setting latency timer to 64
> [ 3248.075926] ngene: Device version 1
> [ 3248.075938] ngene 0000:02:00.0: firmware: requesting ngene_18.fw
> [ 3248.079319] ngene: Loading firmware file ngene_18.fw.
> [ 3248.090194]   alloc irq_desc for 28 on node -1
> [ 3248.090197]   alloc kstat_irqs on node -1
> [ 3248.090212] ngene 0000:02:00.0: irq 28 for MSI/MSI-X
> [ 3248.091778] error in i2c_read_reg
> [ 3248.091781] No CXD2099 detected at 40	<---- No dedicated ASIC is a
> Sony CXD2099AR
> [ 3248.091943] DVB: registering new adapter (nGene)
> [ 3248.414997] LNBx2x attached on addr=a
> [ 3248.421091] stv6110x_attach: Attaching STV6110x
> [ 3248.421095] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
> [ 3248.422500] LNBx2x attached on addr=8
> [ 3248.422568] stv6110x_attach: Attaching STV6110x
> [ 3248.422571] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
About the module :
> ubuntu@ubuntu:~/ngene-test2/v4l$ modinfo ngene
> filename:
> /lib/modules/2.6.32-21-generic/kernel/drivers/media/dvb/ngene/ngene.ko
> license:        GPL
> author:         Micronas, Ralph Metzler, Manfred Voelkel
> description:    nGene
> license:        GPL
> author:         Ralph Metzler <rjkm@metzlerbros.de>
> description:    cxd2099
> srcversion:     AC815F965A079912E969015
> alias:          pci:v000018C3d00000720sv00001461sd0000062Ebc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000DD20bc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000DD10bc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000DD00bc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000DB02bc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000DB01bc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000ABC4bc*sc*i*
> alias:          pci:v000018C3d00000720sv000018C3sd0000ABC3bc*sc*i*
> depends:        dvb-core
> vermagic:       2.6.32-21-generic SMP mod_unload modversions 586
> parm:           one_adapter:Use only one adapter. (int)
> parm:           shutdown_workaround:Activate workaround for shutdown
> problem with some chipsets. (int)
> parm:           debug:Print debugging information. (int)
> parm:           adapter_nr:DVB adapter numbers (array of short)

When I put the option "one_adapter=0" :

> sudo modprobe ngene debug=1 one_adapter=0

> [ 6077.066311] ngene 0000:02:00.0: PCI INT A disabled
> [ 6101.525377] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
> [ 6101.525405] ngene 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
> [ 6101.525418] ngene: Found Mystique SaTiX-S2 Dual (v2)
> [ 6101.530520] ngene 0000:02:00.0: setting latency timer to 64
> [ 6101.530683] ngene: Device version 1
> [ 6101.530692] ngene 0000:02:00.0: firmware: requesting ngene_18.fw
> [ 6101.532043] ngene: Loading firmware file ngene_18.fw.
> [ 6101.542919] ngene 0000:02:00.0: irq 28 for MSI/MSI-X
> [ 6101.545199] error in i2c_read_reg
> [ 6101.545206] No CXD2099 detected at 40
> [ 6101.545374] DVB: registering new adapter (nGene)
> [ 6101.844886] LNBx2x attached on addr=a
> [ 6101.845092] stv6110x_attach: Attaching STV6110x
> [ 6101.845101] DVB: registering adapter 0 frontend 0 (STV090x Multistandard)...
> [ 6101.846175] DVB: registering new adapter (nGene)
> [ 6101.850023] LNBx2x attached on addr=8
> [ 6101.850231] stv6110x_attach: Attaching STV6110x
> [ 6101.850238] DVB: registering adapter 1 frontend 0 (STV090x Multistandard)...
> [ 6101.850584] DVB: registering new adapter (nGene) <---- No need to register this 
> adapter
> [ 6101.852948] DVB: registering new adapter (nGene) <---- No need to register this 
> adapter 
> [ 6101.855690] DVB: registering new adapter (nGene) <---- No need to register this 
> adapter
You can see that adapter 2, 3 and 4 are registering and the is no need to.
> ubuntu@ubuntu:~/ngene-test2/v4l$ ls -l /dev/dvb/adapter*
> /dev/dvb/adapter0:
> total 0
> crw-rw----+ 1 root video 212, 0 2010-12-26 12:52 demux0
> crw-rw----+ 1 root video 212, 1 2010-12-26 12:52 dvr0
> crw-rw----+ 1 root video 212, 3 2010-12-26 12:52 frontend0
> crw-rw----+ 1 root video 212, 2 2010-12-26 12:52 net0
>
> /dev/dvb/adapter1:
> total 0
> crw-rw----+ 1 root video 212, 4 2010-12-26 12:52 demux0
> crw-rw----+ 1 root video 212, 5 2010-12-26 12:52 dvr0
> crw-rw----+ 1 root video 212, 7 2010-12-26 12:52 frontend0
> crw-rw----+ 1 root video 212, 6 2010-12-26 12:52 net0
>
> /dev/dvb/adapter2:
> total 0
> crw-rw----+ 1 root video 212,  8 2010-12-26 12:52 demux0
> crw-rw----+ 1 root video 212,  9 2010-12-26 12:52 dvr0
> crw-rw----+ 1 root video 212, 10 2010-12-26 12:52 net0
>
> /dev/dvb/adapter3:
> total 0
> crw-rw----+ 1 root video 212, 11 2010-12-26 12:52 demux0
> crw-rw----+ 1 root video 212, 12 2010-12-26 12:52 dvr0
> crw-rw----+ 1 root video 212, 13 2010-12-26 12:52 net0
>
> /dev/dvb/adapter4:
> total 0
> crw-rw----+ 1 root video 212, 14 2010-12-26 12:52 demux0
> crw-rw----+ 1 root video 212, 15 2010-12-26 12:52 dvr0
> crw-rw----+ 1 root video 212, 16 2010-12-26 12:52 net0
Is the no test to check how many andapters are needed with the card ? I
was working with stable driver dans 1.5 firmware.

Ludovic,


-- 
Ludovic BOUÉ

Re: ngene & Satix-S2 dual problems

[Andre]

On 26 Dec 2010, at 14:40, Ludovic BOUÉ wrote:

> Hi all,
> 
> I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2 
> from http://linuxtv.org/hg/~endriss/ngene-test2/ under 
> 2.6.32-21-generic.
> 
> It contains too much nodes (extra demuxes, dvrs & nets):

Yes, if you read this thread back you will see why and that it doesn't prevent anything working.

> was working with stable driver dans 1.5 firmware.

Again back in the thread you will see that with the in kernel driver (I hesitate to use the description stable) there is a serious problem when both tuners are in use, this work in progress driver fixes that problem.

The extra nodes are a pain, especially when you have a lot of tuners in one machine but tuners that stop working mid recording are much more of a pain!

Andre

Re: ngene & Satix-S2 dual problems

[Andre]

On 27 Dec 2010, at 11:12, Ludovic BOUE wrote:

> Hi,
> 
> About the CI part, from what I’ve read, it seems that the stream must be get from
> dvr0, than passed to sec0. And the final decrypted stream must be read
> from sec0.
> 
> I use Mumudvb and will not be able to handle this setup.

I hadn't found mumudvb before, interesting software, thanks.

The mumudvb pages on scrambled channels makes some suggestions, sounds like sasc-ng would be a better fit for this type of software, it's much more stable than a year ago too!

The rest I don't know about.

Andre

Re: ngene & Satix-S2 dual problems

[Oliver Endriss]

On Sunday 26 December 2010 15:40:15 Ludovic BOUÉ wrote:
> Hi all,
> 
> I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2 
> from http://linuxtv.org/hg/~endriss/ngene-test2/ under 
> 2.6.32-21-generic.
> 
> It contains too much nodes (extra demuxes, dvrs & nets):
> ...
> Is it connected to this commit (http://linuxtv.org/hg/~endriss/ngene-test2/rev/eb4142f0d0ac) about "Support up to 4 tuners for cineS2 v5, duoflex & mystique v2" ?

Yes.

Please note that this is an experimental repository.
This bug will be fixed before the code will be submitted upstream.
(It is more complicated that it might appear at the first glance.)

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------

Re: ngene & Satix-S2 dual problems

[Oliver Endriss]

On Monday 27 December 2010 22:49:51 Oliver Endriss wrote:
> On Sunday 26 December 2010 15:40:15 Ludovic BOUÉ wrote:
> > Hi all,
> > 
> > I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2 
> > from http://linuxtv.org/hg/~endriss/ngene-test2/ under 
> > 2.6.32-21-generic.
> > 
> > It contains too much nodes (extra demuxes, dvrs & nets):
> > ...
> > Is it connected to this commit (http://linuxtv.org/hg/~endriss/ngene-test2/rev/eb4142f0d0ac) about "Support up to 4 tuners for cineS2 v5, duoflex & mystique v2" ?
> 
> Yes.
> 
> Please note that this is an experimental repository.
> This bug will be fixed before the code will be submitted upstream.
> (It is more complicated that it might appear at the first glance.)

Meanwhile I reworked channel initialisation and shutdown,
and the device nodes should be correct for all configurations.

Please re-test and report any remaining problems.

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------

Re: ngene & Satix-S2 dual problems

[Ludovic BOUE]

Fist of all, I would thank you about your work,

I will re-test and report if I found an issue.


2010/12/28 Oliver Endriss <o.endriss@gmx.de>:
> On Monday 27 December 2010 22:49:51 Oliver Endriss wrote:
>> On Sunday 26 December 2010 15:40:15 Ludovic BOUÉ wrote:
>> > Hi all,
>> >
>> > I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2
>> > from http://linuxtv.org/hg/~endriss/ngene-test2/ under
>> > 2.6.32-21-generic.
>> >
>> > It contains too much nodes (extra demuxes, dvrs & nets):
>> > ...
>> > Is it connected to this commit (http://linuxtv.org/hg/~endriss/ngene-test2/rev/eb4142f0d0ac) about "Support up to 4 tuners for cineS2 v5, duoflex & mystique v2" ?
>>
>> Yes.
>>
>> Please note that this is an experimental repository.
>> This bug will be fixed before the code will be submitted upstream.
>> (It is more complicated that it might appear at the first glance.)
>
> Meanwhile I reworked channel initialisation and shutdown,
> and the device nodes should be correct for all configurations.
>
> Please re-test and report any remaining problems.
>
> CU
> Oliver
>
> --
> ----------------------------------------------------------------
> VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
> 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
> Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
> ----------------------------------------------------------------
>



-- 
Ludovic BOUE

Re: ngene & Satix-S2 dual problems

[Ludovic BOUÉ]

Fist of all, I would thank you about your work.
I have done a test again and it seems to work with your last change. I
didn't found any major issue.

14:14 root@telstar /home/lboue # modprobe ngene one_adapter=0 debug=1

[  584.013474] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[  584.013495] ngene 0000:04:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[  584.013503] ngene: Found Mystique SaTiX-S2 Dual (v2)
[  584.014226] ngene 0000:04:00.0: setting latency timer to 64
[  584.014305] ngene: Device version 1
[  584.014339] ngene 0000:04:00.0: firmware: requesting ngene_18.fw
[  584.016649] ngene: Loading firmware file ngene_18.fw.
[  584.027625] ngene 0000:04:00.0: irq 33 for MSI/MSI-X
[  584.029106] error in i2c_read_reg
[  584.029179] No CXD2099 detected at 40
[  584.342566] LNBx2x attached on addr=a
[  584.342659] stv6110x_attach: Attaching STV6110x
[  584.342662] DVB: registering new adapter (nGene)
[  584.342667] DVB: registering adapter 0 frontend 0 (STV090x
Multistandard)...
[  584.343681] LNBx2x attached on addr=8
[  584.343774] stv6110x_attach: Attaching STV6110x
[  584.343777] DVB: registering new adapter (nGene)
[  584.343782] DVB: registering adapter 1 frontend 0 (STV090x
Multistandard)...

There is two adapters with one frontend into each:
14:06 lboue@telstar ~ % ls /dev/dvb/adapter0
demux0  dvr0  frontend0  net0
14:06 lboue@telstar ~ % ls /dev/dvb/adapter1
demux0  dvr0  frontend0  net0


14:12 root@telstar /home/lboue # modprobe ngene one_adapter=1

[  403.560150] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[  403.560169] ngene 0000:04:00.0: PCI INT A -> GSI 16 (level, low) ->
IRQ 16
[  403.560177] ngene: Found Mystique SaTiX-S2 Dual (v2)
[  403.560873] ngene 0000:04:00.0: setting latency timer to 64
[  403.560952] ngene: Device version 1
[  403.560963] ngene 0000:04:00.0: firmware: requesting ngene_18.fw
[  403.563416] ngene: Loading firmware file ngene_18.fw.
[  403.574393] ngene 0000:04:00.0: irq 33 for MSI/MSI-X
[  403.575874] error in i2c_read_reg
[  403.575948] No CXD2099 detected at 40
[  403.893231] LNBx2x attached on addr=a
[  403.893323] stv6110x_attach: Attaching STV6110x
[  403.893327] DVB: registering new adapter (nGene)
[  403.893332] DVB: registering adapter 0 frontend 0 (STV090x
Multistandard)...
[  403.894359] LNBx2x attached on addr=8
[  403.894451] stv6110x_attach: Attaching STV6110x
[  403.894456] DVB: registering adapter 0 frontend 0 (STV090x
Multistandard)...

14:13 root@telstar /home/lboue # ls /dev/dvb/adapter0/
demux0  demux1  dvr0  dvr1  frontend0  frontend1  net0  net1

The is only the needed adapters but I think there is a errror about the
frontend number. It should be
DVB: registering adapter 0 frontend 1 (STV090x Multistandard)
instead of: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)

Best Regards

Le 28/12/2010 08:57, Oliver Endriss a écrit :
> On Monday 27 December 2010 22:49:51 Oliver Endriss wrote:
>> On Sunday 26 December 2010 15:40:15 Ludovic BOUÉ wrote:
>>> Hi all,
>>>
>>> I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2 
>>> from http://linuxtv.org/hg/~endriss/ngene-test2/ under 
>>> 2.6.32-21-generic.
>>>
>>> It contains too much nodes (extra demuxes, dvrs & nets):
>>> ...
>>> Is it connected to this commit (http://linuxtv.org/hg/~endriss/ngene-test2/rev/eb4142f0d0ac) about "Support up to 4 tuners for cineS2 v5, duoflex & mystique v2" ?
>> Yes.
>>
>> Please note that this is an experimental repository.
>> This bug will be fixed before the code will be submitted upstream.
>> (It is more complicated that it might appear at the first glance.)
> Meanwhile I reworked channel initialisation and shutdown,
> and the device nodes should be correct for all configurations.
>
> Please re-test and report any remaining problems.
>
> CU
> Oliver
>

-- 
Ludovic BOUÉ

Re: ngene & Satix-S2 dual problems

[Oliver Endriss]

Hi,

On Tuesday 28 December 2010 13:22:05 Ludovic BOUÉ wrote:
> ...
> [  403.893231] LNBx2x attached on addr=a
> [  403.893323] stv6110x_attach: Attaching STV6110x
> [  403.893327] DVB: registering new adapter (nGene)
> [  403.893332] DVB: registering adapter 0 frontend 0 (STV090x
> Multistandard)...
> [  403.894359] LNBx2x attached on addr=8
> [  403.894451] stv6110x_attach: Attaching STV6110x
> [  403.894456] DVB: registering adapter 0 frontend 0 (STV090x
> Multistandard)...
> 
> 14:13 root@telstar /home/lboue # ls /dev/dvb/adapter0/
> demux0  demux1  dvr0  dvr1  frontend0  frontend1  net0  net1
> 
> The is only the needed adapters but I think there is a errror about the
> frontend number. It should be
> DVB: registering adapter 0 frontend 1 (STV090x Multistandard)
> instead of: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)

Confirmed. There is a harmless bug in dvb_core:
The message is printed before the frontend number has been assigned.
I will commit a fix for that later.

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------

Re: ngene & Satix-S2 dual problems

[Andre]

On 28 Dec 2010, at 12:31, Ludovic BOUÉ wrote:

> 
> 
> Le 27/12/2010 10:07, Andre a écrit :
>> On 26 Dec 2010, at 14:40, Ludovic BOUÉ wrote:
>> 
>>> Hi all,
>>> 
>>> I have a Satix-S2 Dual and I'm trying to get to work without his CI in a first time. I'm trying ngene-test2 
>>> from http://linuxtv.org/hg/~endriss/ngene-test2/ under 
>>> 2.6.32-21-generic.
>>> 
>>> It contains too much nodes (extra demuxes, dvrs & nets):
>> Yes, if you read this thread back you will see why and that it doesn't prevent anything working.
>> 
>>> was working with stable driver dans 1.5 firmware.
>> Again back in the thread you will see that with the in kernel driver (I hesitate to use the description stable) there is a serious problem when both tuners are in use, this work in progress driver fixes that problem.
>> 
>> The extra nodes are a pain, especially when you have a lot of tuners in one machine but tuners that stop working mid recording are much more of a pain!
> 
> I seems to work with the last patch commited by Oliver Endriss. Did you
> try with a CI ?

No I didn't, I don't have a CI.

I'll try Olivers latest commit in a few days, I'm a long way from my Myth system right now :-)

Thanks again Oliver, much appreciated.

Andre

Re: ngene & Satix-S2 dual problems

[Andre]

On 28 Dec 2010, at 17:25, Andre wrote:
>> 
>> I seems to work with the last patch commited by Oliver Endriss. Did you
>> try with a CI ?
> 
> No I didn't, I don't have a CI.
> 
> I'll try Olivers latest commit in a few days, I'm a long way from my Myth system right now :-)

Finally got chance to try the latest commits, no extra nodes now and drivers work fine with several simultaneous HD recordings across both tuners.

Satix S2 dual v2 on Ubuntu 10.0.4.1 kernel 2.6.32-25-generic

Thanks

Andre

Re: ngene & Satix-S2 dual problems

[Robert Longbottom]

On 11 Jan 2011, at 15:25, Andre wrote:

>On 28 Dec 2010, at 17:25, Andre wrote:
>>/>  /
>>/>  I seems to work with the last patch commited by Oliver Endriss. Did you/
>>/>  try with a CI ?/
>>/  /
>>/  No I didn't, I don't have a CI./
>>/  /
>>/  I'll try Olivers latest commit in a few days, I'm a long way from my Myth system right now :-)/
>
>  Finally got chance to try the latest commits, no extra nodes now and drivers work fine with several simultaneous HD recordings across both tuners.
>
>  Satix S2 dual v2 on Ubuntu 10.0.4.1 kernel 2.6.32-25-generic
>
>  Thanks
>
>  Andre

Hi,
I've finally gotten round to trying the latest commits as well
and I can also report success.  No extra nodes, drivers appear to be working
ok after a very quick test.  I'll see how it goes over the next few days.

Satix S2 dual on Gentoo with kernel 2.6.35.4.

Cheers,
Robert.
  <http://vger.kernel.org/majordomo-info.html>

Re: ngene & Satix-S2 dual problems

[Ludovic BOUÉ]

Hi Oliver,

Are you planning to merge your ngene development repository to the
V4L-DVB Upstream repository ?

Ludovic,

Le 28/12/2010 16:01, Oliver Endriss a écrit :
> Hi,
>
> On Tuesday 28 December 2010 13:22:05 Ludovic BOUÉ wrote:
>> ...
>> [  403.893231] LNBx2x attached on addr=a
>> [  403.893323] stv6110x_attach: Attaching STV6110x
>> [  403.893327] DVB: registering new adapter (nGene)
>> [  403.893332] DVB: registering adapter 0 frontend 0 (STV090x
>> Multistandard)...
>> [  403.894359] LNBx2x attached on addr=8
>> [  403.894451] stv6110x_attach: Attaching STV6110x
>> [  403.894456] DVB: registering adapter 0 frontend 0 (STV090x
>> Multistandard)...
>>
>> 14:13 root@telstar /home/lboue # ls /dev/dvb/adapter0/
>> demux0  demux1  dvr0  dvr1  frontend0  frontend1  net0  net1
>>
>> The is only the needed adapters but I think there is a errror about the
>> frontend number. It should be
>> DVB: registering adapter 0 frontend 1 (STV090x Multistandard)
>> instead of: DVB: registering adapter 0 frontend 0 (STV090x Multistandard)
> Confirmed. There is a harmless bug in dvb_core:
> The message is printed before the frontend number has been assigned.
> I will commit a fix for that later.
>
> CU
> Oliver
>

-- 
Ludovic BOUÉ

Re: ngene & Satix-S2 dual problems

[Oliver Endriss]

On Monday 31 January 2011 15:46:30 Ludovic BOUÉ wrote:
> Are you planning to merge your ngene development repository to the
> V4L-DVB Upstream repository ?

The patches have already been submitted. See
http://www.mail-archive.com/linux-media@vger.kernel.org/msg26813.html

CU
Oliver

-- 
----------------------------------------------------------------
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/
4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/
Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
----------------------------------------------------------------