Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Simeon Simeonov]

Hi Manu,

Thanks for the reply
Yes, indeed I tried over the weekend and by selecting the higher limitation by ISEL register:

if (!lnbp21_attach(mantis->fe, &mantis->adapter, 0, 0x40)) {

My rotor now moves. Do you think it is better to use static current protection?

But unfortunately that is not the end of the story. The problem that I am
having now is that patched mythtv rewrites the limits in my rotor?! And the weird thing is 
it does in such a way that I had to take the motor apart to recalibrate it. It looks like there are
hard limits in the rotor (Aston 1.2) firmware which are not the software limits because trying to reset 
them either from Linux side or from Windoz did not help. So I actually had to take it apart to recalibrate
the motor inside the rotor. I do not think there is a problem with the rotor itself because I have been using it for over 2 years with my other Twinhah 102g card without any problems.
I also wrote a small command line program (using libsec) that will do only rotor commands. With that
program I can do goto n, store, reset, soft limits. All there operations work fine. Goto nn steps also
works somewhat even though it is not taking the specified number of steps precisely. I am not sure why.

Getting back to my mythtv setup - I have a committed switch behind the rotor. So the rotor command is followed by (with 15ms delay) the switch, tone burst and then tunning commands. I turned on the verbose in mantis module and looked what i2c reports. The diseqc sequence looks correct. The only thing I see is that the fifo gets filled up by the end of the sequence so we have to wait for a few cycles before sending the next byte. So now I am thinking could there be any problems if the pause between writing the diseqc bytes is a bit longer since we write byte, check if fifo is full and then write the next byte. What do you think about that? I was thinking of trying to write the whole diseqc command and then check fifo or even better first check fifo and then write the command since we have 15ms between commands anyway.
On the side - switch works 50% of the times so I should look into that too. It is a really good Spaun switch and even with 102g works flawlessly.


Thanks for the help!
Simeon



----- Original Message ----
From: Manu Abraham <abraham.manu@gmail.com>
To: Simeon Simeonov <simeonov_2000@yahoo.com>
Cc: linux-dvb@linuxtv.org
Sent: Sunday, February 24, 2008 12:26:34 PM
Subject: Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

Manu Abraham wrote:
> Simeon Simeonov wrote:
>> Hi Gernot,
>>
>> I can confirm that I have similar experience to yours.
>> By the way do you know if one can control from the soft side (register or some other means)
>> the max current output for the card. I am having a problem when trying to tune with a rotor.
>> On the Linux side the current seems to be capped at 300 mA as on the XP I see it goes to
>> about 440 mA. I was still surprised that this card can supply less current than the 102g but
>> we take what we get ...

Can you please try this change, whether it helps in your case ?

In mantis_dvb.c

line #251

if (!lnbp21_attach(mantis->fe, &mantis->adapter, 0, 0)) {

change it to

if (!lnbp21_attach(mantis->fe, &mantis->adapter, 0x80, 0x40)) {

and see whether it helps in improving your current limited situation.
according to the specification it should yield 500 - 650mA

A word of caution, make sure that the auxilliary power connector is
connected. Current drawn will be a bit much higher in this case,
additionally Static Current Limiting is used, hence additional dissipation,
which means more current drawn which might overload the PCI bus, hence
  it would be nice to use the auxilliary power connector.

Regards,
Manu





      ____________________________________________________________________________________
Be a better friend, newshound, and 
know-it-all with Yahoo! Mobile.  Try it now.  http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Simeon Simeonov wrote:
> Hi Manu,
> 
> Thanks for the reply
> Yes, indeed I tried over the weekend and by selecting the higher limitation by ISEL register:
> 
> if (!lnbp21_attach(mantis->fe, &mantis->adapter, 0, 0x40)) {
> 
> My rotor now moves. Do you think it is better to use static current protection?

It is similar to an Auto transmission car in comparison to a manual 
transmission one.
It depends how well you can handle it. Dynamic limitation is done by 
using PWM. The
advantage of using static limiting is a slightly higher dissipation but 
you see in some
practical cases that it can provide more current or maybe that it 
behaves a bit more
better in comparison. When you have more dissipation, the device draws a 
larger
current from the bus, but that's all about it. (Normally many people 
don't like Static
limitation due to the additional dissipation and current drawn, since it 
is not advisable
to sink large currents from the PCI bus and hence an additional 
auxiliary power connector
is provided on the card. Most cards generally draw power from the PCI 
bus alone)

> But unfortunately that is not the end of the story. The problem that I am
> having now is that patched mythtv rewrites the limits in my rotor?! And the weird thing is 
> it does in such a way that I had to take the motor apart to recalibrate it. It looks like there are
> hard limits in the rotor (Aston 1.2) firmware which are not the software limits because trying to reset 
> them either from Linux side or from Windoz did not help. So I actually had to take it apart to recalibrate
> the motor inside the rotor. I do not think there is a problem with the rotor itself because I have been using it for over 2 years with my other Twinhah 102g card without any problems.
> I also wrote a small command line program (using libsec) that will do only rotor commands. With that
> program I can do goto n, store, reset, soft limits. All there operations work fine. Goto nn steps also
> works somewhat even though it is not taking the specified number of steps precisely. I am not sure why.
> 
> Getting back to my mythtv setup - I have a committed switch behind the rotor. So the rotor command is followed by (with 15ms delay) the switch, tone burst and then tunning commands. I turned on the verbose in mantis module and looked what i2c reports. The diseqc sequence looks correct. The only thing I see is that the fifo gets filled up by the end of the sequence so we have to wait for a few cycles before sending the next byte. So now I am thinking could there be any problems if the pause between writing the diseqc bytes is a bit longer since we write byte, check if fifo is full and then write the next byte. What do you think about that? I was thinking of trying to write the whole diseqc command and then check fifo or even better first check fifo and then write the command since we have 15ms between commands anyway.
> On the side - switch works 50% of the times so I should look into that too. It is a really good Spaun switch and even with 102g works flawlessly.

Ok, does sending the commands as it is on the fly help for you, rather 
than storing
all of them in the FIFO and whack them out in a disciplined way ?

If it looks working better that way, will try that and ask others as 
well whether they
see similar benefits ?


Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Simeon Simeonov]

Hi Manu,

Here is some more info about my diseqc problem:

> Ok, does sending the commands as it is on the fly help for you, rather 
> than storing
> all of them in the FIFO and whack them out in a disciplined way ?
>
> If it looks working better that way, will try that and ask others as
> well whether they
> see similar benefits ?

The short answer is no,  I do not see any benefits of sending the whole
diseqc command.

Unfortunately I still do not have a good idea what exactly the problem is.
Here is what I tried:
1. Bypass the rotor and connect directly to the switch: in that case switch
works 100% of the times even though I am first sending a rotor switch command
and then switch command and no repeats. This I checked with both mythtv
and szap.
2. Connect the rotor and send a rotor, followed by a switch command with no repeats.
In this case rotor works fine but the switch works 1/10 times. But my rotor does not
get reprogrammed
3. Send more than 2 diseqc command - being repeat for either switch or rotor or both.
Well if the rotor does not have to move (I have 2 satellites that I can use for that)
switch works about half of the time but as soon as try to move the rotor it gets all
reprogrammed.

I really have no idea what is happening. Again I looked up the mantis i2c commands
and all diseqc ones that are sent look correct. 
Any hints are welcome.

Thanks for your help,
Simeon






      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Simeon Simeonov]

Hi Gernot,

I can confirm that I have similar experience to yours.
By the way do you know if one can control from the soft side (register or some other means)
the max current output for the card. I am having a problem when trying to tune with a rotor.
On the Linux side the current seems to be capped at 300 mA as on the XP I see it goes to
about 440 mA. I was still surprised that this card can supply less current than the 102g but
we take what we get ...

Thanks for the help,
Simeon

----- Original Message ----
From: Gernot Pansy <pansyg@gmx.at>
To: linux-dvb@linuxtv.org
Sent: Monday, February 18, 2008 1:08:59 PM
Subject: Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

hy,

the wiki is not up2date. 

Twinhan VP-1041 support is now in the mantis tree (inkl. multiproto)

hg clone http://jusst.de/hg/mantis

but for me, the old initialization parameters works much better. with the new 
ones i get only a destructed picture (unwatchable).  

gernot

On Monday 18 February 2008 20:05:03 Tim Hewett wrote:
> I'm trying to get a new Technisat Skystar HD2 working. It looks like
> it is a Twinhan VP-1041/Azurewave AD SP400 rebadge.
>
> The card hardware and satellite feed has been confirmed to work ok
> under Windows using Technisat's software.
>
> I am using the current multiproto DVB drivers, downloaded today. These
> were patched, built and installed successfully as described for the
> Azurewave AD SP400 in the linuxdvb wiki, but the card was not
> recognised on bootup even though it was allocated a DVB adaptor
> number. This appeared in dmesg:
>
> [   57.359723] found a UNKNOWN PCI UNKNOWN device on (01:06.0),
> [   57.359802]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
> [   57.359858]     memory: 0xe5100000, mmio: 0xffffc200000fc000
> [   57.363015]     MAC Address=[00:08:c9:e0:26:92]
> [   57.363133] mantis_alloc_buffers (0): DMA=0x1b7a0000
> cpu=0xffff81001b7a0000 size=65536
> [   57.363242] mantis_alloc_buffers (0): RISC=0x1ae24000
> cpu=0xffff81001ae24000 size=1000
> [   57.363348] DVB: registering new adapter (Mantis dvb adapter)
>
>
> This is the output of lspci -vvn:
>
> 01:06.0 0480: 1822:4e35 (rev 01)
>     Subsystem: 1ae4:0001
>     Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>     Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>     Latency: 32 (2000ns min, 63750ns max)
>     Interrupt: pin A routed to IRQ 16
>     Region 0: Memory at e5100000 (32-bit, prefetchable) [size=4K]
>
> This is the output of lsusb -vv:
>
> 01:06.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV
> PCI Bridge Controller [Ver 1.0] (rev 01)
>     Subsystem: Unknown device 1ae4:0001
>     Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
>     Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>     Latency: 32 (2000ns min, 63750ns max)
>     Interrupt: pin A routed to IRQ 16
>     Region 0: Memory at e5100000 (32-bit, prefetchable) [size=4K]
>
> Note that subsystem IDs 1ae4:0001 are different to those listed in the
> wiki for the Azurewave (1822:0031).
>
> I changed #define MANTIS_VP_1041_DVB_S2    in linux/drivers/media/dvb/
> mantis/mantis_vp1041.h from 0x0031 to 0x0001, which changed the dmesg
> output on reboot to this:
>
> [   59.546375] found a VP-1041 PCI DVB-S/DVB-S2 device on (01:06.0),
> [   59.546456]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
> [   59.546512]     memory: 0xe5100000, mmio: 0xffffc200000fc000
> [   59.549609]     MAC Address=[00:08:c9:e0:26:92]
> [   59.549719] mantis_alloc_buffers (0): DMA=0x1b7b0000
> cpu=0xffff81001b7b0000 size=65536
> [   59.549827] mantis_alloc_buffers (0): RISC=0x1af43000
> cpu=0xffff81001af43000 size=1000
> [   59.549933] DVB: registering new adapter (Mantis dvb adapter)
> [   60.137583] stb0899_attach: Attaching STB0899
> [   60.137665] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2
> frontend @0x68
> [   60.152161] stb6100_attach: Attaching STB6100
> [   60.168021] DVB: registering frontend 3 (STB0899 Multistandard)...
>
> So that change seemed to cause the card to be recognised.
>
> Then I tried the replacement scan and szap as suggested by the
> Azurewave wiki, but the card will not tune.
>
> So it appears to be almost working, but I'm not sure what tests to try
> or changes to make to see if it will work.



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb





      ____________________________________________________________________________________
Never miss a thing.  Make Yahoo your home page. 
http://www.yahoo.com/r/hs

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Simeon Simeonov wrote:
> Hi Gernot,
> 
> I can confirm that I have similar experience to yours.
> By the way do you know if one can control from the soft side (register or some other means)
> the max current output for the card. I am having a problem when trying to tune with a rotor.
> On the Linux side the current seems to be capped at 300 mA as on the XP I see it goes to
> about 440 mA. I was still surprised that this card can supply less current than the 102g but
> we take what we get ...


The card has an auxiliary power supply i/p, which should be connected, 
if you are using a larger load.
With a higher load and if you draw power from the PCI bus, it could be 
bad, as there are some
limitations to the current drawn from a PCI slot. Also, you can set the 
SEC chip for a different current
limitation.

Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Manu Abraham wrote:
> Simeon Simeonov wrote:
>> Hi Gernot,
>>
>> I can confirm that I have similar experience to yours.
>> By the way do you know if one can control from the soft side (register or some other means)
>> the max current output for the card. I am having a problem when trying to tune with a rotor.
>> On the Linux side the current seems to be capped at 300 mA as on the XP I see it goes to
>> about 440 mA. I was still surprised that this card can supply less current than the 102g but
>> we take what we get ...

Can you please try this change, whether it helps in your case ?

In mantis_dvb.c

line #251

if (!lnbp21_attach(mantis->fe, &mantis->adapter, 0, 0)) {

change it to

if (!lnbp21_attach(mantis->fe, &mantis->adapter, 0x80, 0x40)) {

and see whether it helps in improving your current limited situation.
according to the specification it should yield 500 - 650mA

A word of caution, make sure that the auxilliary power connector is
connected. Current drawn will be a bit much higher in this case,
additionally Static Current Limiting is used, hence additional dissipation,
which means more current drawn which might overload the PCI bus, hence
  it would be nice to use the auxilliary power connector.

Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

[-- Attachment #1.1: Type: text/plain, Size: 10504 bytes --]

Gernot,

I have now tried the mantis tree. It also needed the  
MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card,  
but after doing that it was recognised:

[   56.586237] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
[   56.586330] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC1] ->  
GSI 16 (level, low) -> IRQ 16
[   56.586556] irq: 16, latency: 32
[   56.586557]  memory: 0xe5100000, mmio: 0xffffc200000f8000
[   56.586708] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (01:06.0),
[   56.586791]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
[   56.586847]     memory: 0xe5100000, mmio: 0xffffc200000f8000
[   56.589867]     MAC Address=[00:08:c9:e0:26:92]
[   56.589972] mantis_alloc_buffers (0): DMA=0x1aa10000  
cpu=0xffff81001aa10000 size=65536
[   56.590081] mantis_alloc_buffers (0): RISC=0x1b7f0000  
cpu=0xffff81001b7f0000 size=1000
[   56.590187] DVB: registering new adapter (Mantis dvb adapter)
[   57.106676] stb0899_write_regs [0xf1b6]: 02
[   57.107730] stb0899_write_regs [0xf1c2]: 00
[   57.108781] stb0899_write_regs [0xf1c3]: 00
[   57.110884] _stb0899_read_reg: Reg=[0xf000], data=82
[   57.110964] stb0899_get_dev_id: ID reg=[0x82]
[   57.111040] stb0899_get_dev_id: Device ID=[8], Release=[2]
[   57.117425] _stb0899_read_s2reg Device=[0xf3fc], Base  
address=[0x00000400], Offset=[0xf334], Data=[0x444d4431]
[   57.123732] _stb0899_read_s2reg Device=[0xf3fc], Base  
address=[0x00000400], Offset=[0xf33c], Data=[0x00000001]
[   57.123735] stb0899_get_dev_id: Demodulator Core ID=[DMD1],  
Version=[1]
[   57.130121] _stb0899_read_s2reg Device=[0xfafc], Base  
address=[0x00000800], Offset=[0xfa2c], Data=[0x46454331]
[   57.136428] _stb0899_read_s2reg Device=[0xfafc], Base  
address=[0x00000800], Offset=[0xfa34], Data=[0x00000001]
[   57.136430] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1]
[   57.136509] stb0899_attach: Attaching STB0899
[   57.136586] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2  
frontend @0x68
[   57.136690] stb6100_attach: Attaching STB6100
[   57.137118] DVB: registering frontend 1 (STB0899 Multistandard)...

However it still doesn't tune. e.g.:

root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l  
UNIVERSAL -t 0 -a 1 BBC1West
reading channels from file '/root/.szap/channels.conf'
zapping to 1 'BBC1West':
sat 0, frequency = 10818 MHz V, symbolrate 22000000, vpid = 0x0901,  
apid = 0x0904 sid = 0x0002
Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
----------------------------------> Using 'STB0899 DVB-S' DVB-S
do_tune: API version=3, delivery system = 0
do_tune: Frequency = 1068000, Srate = 22000000
do_tune: Frequency = 1068000, Srate = 22000000


Whereas this is the result when using an ordinary Skystar 2 card  
(which works fine):

root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l  
UNIVERSAL -t 0 -a 0 BBC1West
reading channels from file '/root/.szap/channels.conf'
zapping to 1 'BBC1West':
sat 0, frequency = 10818 MHz V, symbolrate 22000000, vpid = 0x0901,  
apid = 0x0904 sid = 0x0002
Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
----------------------------------> Using 'ST STV0299 DVB-S' DVB-S
do_tune: API version=3, delivery system = 0
do_tune: Frequency = 1068000, Srate = 22000000
do_tune: Frequency = 1068000, Srate = 22000000


couldn't find pmt-pid for sid 0002
status 1f | signal cac8 | snr cb6d | ber 000061d0 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal c9f0 | snr d15e | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK
status 1f | signal ca1d | snr d176 | ber 00000000 | unc 00000000 |  
FE_HAS_LOCK


Using szap on the Skystar HD2 caused lots of logs to dmesg:

[   97.691029] stb0899_search: set DVB-S params
[   97.691112] stb0899_search: delivery system=1
[   97.691188] stb0899_search: Frequency=1068000, Srate=22000000
[   97.691269] stb0899_search: Parameters IN RANGE
[   97.692611] _stb0899_read_reg: Reg=[0xf1c2], data=20
[   97.694085] _stb0899_read_reg: Reg=[0xf1c3], data=00
[   97.694166] stb0899_set_delsys: Delivery System -- DVB-S
[   97.695848] _stb0899_read_reg: Reg=[0xf533], data=01
[   97.695929] stb0899_write_regs [0xf533]: 09
[   97.697420] stb0899_write_regs [0xf548]: b1
[   97.698913] stb0899_write_regs [0xf549]: 40
[   97.700410] stb0899_write_regs [0xf54a]: 42
[   97.701778] stb0899_write_regs [0xf54b]: 12
[   97.704225] _stb0899_read_reg: Reg=[0xff11], data=00
[   97.704308] stb0899_write_regs [0xff11]: 80
[   97.705797] stb0899_write_regs [0xf1c2]: 78 07
[   97.707631] stb0899_set_mclk: state->config=ffffffff882654a0
[   97.707713] stb0899_set_mclk: mdiv=21
[   97.707788] stb0899_write_regs [0xf1b3]: 15
[   97.710338] _stb0899_read_reg: Reg=[0xf1b3], data=15
[   97.710427] stb0899_get_mclk: div=21, mclk=99000000
[   97.710505] stb0899_set_mclk: MasterCLOCK=99000000
[   97.710582] stb0899_search: DVB-S delivery system
[   97.712051] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.712131] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.712211] stb0899_write_regs [0xf12a]: dc
[   97.715358] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.717042] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.717121] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.717202] stb0899_write_regs [0xf12a]: dc
[   97.720769] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.726992] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.727071] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.727150] stb0899_write_regs [0xf12a]: dc
[   97.730951] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.731030] stb6100_set_bandwidth: Bandwidth=51610000
[   97.732640] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.732719] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.732800] stb0899_write_regs [0xf12a]: dc
[   97.740229] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.740309] stb6100_get_bandwidth: Bandwidth=52000000
[   97.740311] stb0899_write_regs [0xf157]: 11
[   97.741801] stb0899_search: running DVB-S search algo ..
[   97.741898] stb0899_set_srate: -->
[   97.741973] stb0899_write_regs [0xf446]: 38 e3 90
[   97.744156] stb0899_write_regs [0xf41c]: 89
[   97.746593] _stb0899_read_reg: Reg=[0xf41d], data=94
[   97.746672] stb0899_write_regs [0xf41d]: a7
[   97.748164] stb0899_dvbs_algo: Set the timing loop to acquisition
[   97.748262] stb0899_write_regs [0xf417]: 46
[   97.749648] stb0899_write_regs [0xf41b]: ee
[   97.750809] stb0899_dvbs_algo: Derot Percent=30 Srate=22000000  
mclk=1647
[   97.750893] stb0899_dvbs_algo: RESET stream merger
[   97.752023] _stb0899_read_reg: Reg=[0xff11], data=80
[   97.752103] stb0899_write_regs [0xff11]: c0
[   97.754207] _stb0899_read_reg: Reg=[0xf583], data=5c
[   97.754286] stb0899_write_regs [0xf583]: 3c
[   97.755338] stb0899_write_regs [0xf41e]: 01
[   97.756392] stb0899_write_regs [0xf53d]: 19
[   97.758498] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.758577] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.758656] stb0899_write_regs [0xf12a]: dc
[   97.764979] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.765058] stb6100_get_bandwidth: Bandwidth=52000000
[   97.765060] stb0899_write_regs [0xf43e]: 00 00
[   97.766462] stb0899_write_regs [0xf439]: 00
[   97.768568] _stb0899_read_reg: Reg=[0xf41b], data=ee
[   97.768646] stb0899_write_regs [0xf41b]: ee
[   97.769700] stb0899_dvbs_algo: Tuner set frequency
[   97.770830] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.770909] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.770989] stb0899_write_regs [0xf12a]: dc
[   97.777313] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.777392] stb0899_get_params: Get DVB-S params
[   97.778522] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.778601] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.778680] stb0899_write_regs [0xf12a]: dc
[   97.784985] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.786116] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.786195] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.786274] stb0899_write_regs [0xf12a]: dc
[   97.789079] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.790210] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.790300] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.790380] stb0899_write_regs [0xf12a]: dc
[   97.793185] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.802463] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.802544] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.802623] stb0899_write_regs [0xf12a]: dc
[   97.805428] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.806559] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.806637] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.806716] stb0899_write_regs [0xf12a]: dc
[   97.809521] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.845351] stb6100_set_frequency: Frequency=1068000
[   97.846406] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.846484] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.846563] stb0899_write_regs [0xf12a]: dc
[   97.852886] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.852965] stb6100_get_frequency: Frequency=1068002
[   97.857361] stb0899_dvbs_algo: current derot freq=0
[   97.858492] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.858574] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
[   97.858653] stb0899_write_regs [0xf12a]: dc
[   97.864975] _stb0899_read_reg: Reg=[0xf12a], data=5c
[   97.865054] stb6100_get_bandwidth: Bandwidth=52000000
[   97.869318] stb0899_write_regs [0xf439]: f2
[   97.871424] _stb0899_read_reg: Reg=[0xf438], data=80
[   97.872554] _stb0899_read_reg: Reg=[0xf439], data=02
[   97.872633] stb0899_check_tmg: ------->TIMING OK !
[   97.874113] stb0899_read_regs [0xf43e]: fd 6d
[   97.874117] stb0899_search_tmg: ------->TIMING OK ! Derot Freq = -659
[   97.874199] stb0899_dvbs_algo: TIMING OK ! Derot freq=-659, mclk=1647
[   97.875335] _stb0899_read_reg: Reg=[0xf41b], data=ee
[   97.875413] stb0899_write_regs [0xf41b]: ee
[   97.876467] stb0899_search_carrier: Derot Freq=-659, mclk=1647
[   97.882354] _stb0899_read_reg: Reg=[0xf41b], data=ee

Those logs don't look too bad superficially, but it's still not working.

Tim.

> hy,
>
> the wiki is not up2date.
>
> Twinhan VP-1041 support is now in the mantis tree (inkl. multiproto)
>
> hg clone http://jusst.de/hg/mantis
>
> but for me, the old initialization parameters works much better.  
> with the new
> ones i get only a destructed picture (unwatchable).
>
> gernot

[-- Attachment #1.2: Type: text/html, Size: 14326 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Gernot Pansy]

hy,

have you tried some other channel on a diffrent multiplex?

i have also troubles on 2 multiplexes, but i believe that's trough my bad 
signal strength (it's the same on windows).

otherwise there have to be some initialization registers configured 
differently. manu is the only guy, how knows about that and can help you.

gernot

On Tuesday 19 February 2008 00:51:49 Tim Hewett wrote:
> Gernot,
>
> I have now tried the mantis tree. It also needed the
> MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card,
> but after doing that it was recognised:
>
> [   56.586237] ACPI: PCI Interrupt Link [APC1] enabled at IRQ 16
> [   56.586330] ACPI: PCI Interrupt 0000:01:06.0[A] -> Link [APC1] ->
> GSI 16 (level, low) -> IRQ 16
> [   56.586556] irq: 16, latency: 32
> [   56.586557]  memory: 0xe5100000, mmio: 0xffffc200000f8000
> [   56.586708] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (01:06.0),
> [   56.586791]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
> [   56.586847]     memory: 0xe5100000, mmio: 0xffffc200000f8000
> [   56.589867]     MAC Address=[00:08:c9:e0:26:92]
> [   56.589972] mantis_alloc_buffers (0): DMA=0x1aa10000
> cpu=0xffff81001aa10000 size=65536
> [   56.590081] mantis_alloc_buffers (0): RISC=0x1b7f0000
> cpu=0xffff81001b7f0000 size=1000
> [   56.590187] DVB: registering new adapter (Mantis dvb adapter)
> [   57.106676] stb0899_write_regs [0xf1b6]: 02
> [   57.107730] stb0899_write_regs [0xf1c2]: 00
> [   57.108781] stb0899_write_regs [0xf1c3]: 00
> [   57.110884] _stb0899_read_reg: Reg=[0xf000], data=82
> [   57.110964] stb0899_get_dev_id: ID reg=[0x82]
> [   57.111040] stb0899_get_dev_id: Device ID=[8], Release=[2]
> [   57.117425] _stb0899_read_s2reg Device=[0xf3fc], Base
> address=[0x00000400], Offset=[0xf334], Data=[0x444d4431]
> [   57.123732] _stb0899_read_s2reg Device=[0xf3fc], Base
> address=[0x00000400], Offset=[0xf33c], Data=[0x00000001]
> [   57.123735] stb0899_get_dev_id: Demodulator Core ID=[DMD1],
> Version=[1]
> [   57.130121] _stb0899_read_s2reg Device=[0xfafc], Base
> address=[0x00000800], Offset=[0xfa2c], Data=[0x46454331]
> [   57.136428] _stb0899_read_s2reg Device=[0xfafc], Base
> address=[0x00000800], Offset=[0xfa34], Data=[0x00000001]
> [   57.136430] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1]
> [   57.136509] stb0899_attach: Attaching STB0899
> [   57.136586] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2
> frontend @0x68
> [   57.136690] stb6100_attach: Attaching STB6100
> [   57.137118] DVB: registering frontend 1 (STB0899 Multistandard)...
>
> However it still doesn't tune. e.g.:
>
> root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l
> UNIVERSAL -t 0 -a 1 BBC1West
> reading channels from file '/root/.szap/channels.conf'
> zapping to 1 'BBC1West':
> sat 0, frequency = 10818 MHz V, symbolrate 22000000, vpid = 0x0901,
> apid = 0x0904 sid = 0x0002
> Querying info .. Delivery system=DVB-S
> using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
> ----------------------------------> Using 'STB0899 DVB-S' DVB-S
> do_tune: API version=3, delivery system = 0
> do_tune: Frequency = 1068000, Srate = 22000000
> do_tune: Frequency = 1068000, Srate = 22000000
>
>
> Whereas this is the result when using an ordinary Skystar 2 card
> (which works fine):
>
> root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l
> UNIVERSAL -t 0 -a 0 BBC1West
> reading channels from file '/root/.szap/channels.conf'
> zapping to 1 'BBC1West':
> sat 0, frequency = 10818 MHz V, symbolrate 22000000, vpid = 0x0901,
> apid = 0x0904 sid = 0x0002
> Querying info .. Delivery system=DVB-S
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> ----------------------------------> Using 'ST STV0299 DVB-S' DVB-S
> do_tune: API version=3, delivery system = 0
> do_tune: Frequency = 1068000, Srate = 22000000
> do_tune: Frequency = 1068000, Srate = 22000000
>
>
> couldn't find pmt-pid for sid 0002
> status 1f | signal cac8 | snr cb6d | ber 000061d0 | unc 00000000 |
> FE_HAS_LOCK
> status 1f | signal c9f0 | snr d15e | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK
> status 1f | signal ca1d | snr d176 | ber 00000000 | unc 00000000 |
> FE_HAS_LOCK
>
>
> Using szap on the Skystar HD2 caused lots of logs to dmesg:
>
> [   97.691029] stb0899_search: set DVB-S params
> [   97.691112] stb0899_search: delivery system=1
> [   97.691188] stb0899_search: Frequency=1068000, Srate=22000000
> [   97.691269] stb0899_search: Parameters IN RANGE
> [   97.692611] _stb0899_read_reg: Reg=[0xf1c2], data=20
> [   97.694085] _stb0899_read_reg: Reg=[0xf1c3], data=00
> [   97.694166] stb0899_set_delsys: Delivery System -- DVB-S
> [   97.695848] _stb0899_read_reg: Reg=[0xf533], data=01
> [   97.695929] stb0899_write_regs [0xf533]: 09
> [   97.697420] stb0899_write_regs [0xf548]: b1
> [   97.698913] stb0899_write_regs [0xf549]: 40
> [   97.700410] stb0899_write_regs [0xf54a]: 42
> [   97.701778] stb0899_write_regs [0xf54b]: 12
> [   97.704225] _stb0899_read_reg: Reg=[0xff11], data=00
> [   97.704308] stb0899_write_regs [0xff11]: 80
> [   97.705797] stb0899_write_regs [0xf1c2]: 78 07
> [   97.707631] stb0899_set_mclk: state->config=ffffffff882654a0
> [   97.707713] stb0899_set_mclk: mdiv=21
> [   97.707788] stb0899_write_regs [0xf1b3]: 15
> [   97.710338] _stb0899_read_reg: Reg=[0xf1b3], data=15
> [   97.710427] stb0899_get_mclk: div=21, mclk=99000000
> [   97.710505] stb0899_set_mclk: MasterCLOCK=99000000
> [   97.710582] stb0899_search: DVB-S delivery system
> [   97.712051] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.712131] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.712211] stb0899_write_regs [0xf12a]: dc
> [   97.715358] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.717042] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.717121] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.717202] stb0899_write_regs [0xf12a]: dc
> [   97.720769] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.726992] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.727071] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.727150] stb0899_write_regs [0xf12a]: dc
> [   97.730951] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.731030] stb6100_set_bandwidth: Bandwidth=51610000
> [   97.732640] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.732719] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.732800] stb0899_write_regs [0xf12a]: dc
> [   97.740229] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.740309] stb6100_get_bandwidth: Bandwidth=52000000
> [   97.740311] stb0899_write_regs [0xf157]: 11
> [   97.741801] stb0899_search: running DVB-S search algo ..
> [   97.741898] stb0899_set_srate: -->
> [   97.741973] stb0899_write_regs [0xf446]: 38 e3 90
> [   97.744156] stb0899_write_regs [0xf41c]: 89
> [   97.746593] _stb0899_read_reg: Reg=[0xf41d], data=94
> [   97.746672] stb0899_write_regs [0xf41d]: a7
> [   97.748164] stb0899_dvbs_algo: Set the timing loop to acquisition
> [   97.748262] stb0899_write_regs [0xf417]: 46
> [   97.749648] stb0899_write_regs [0xf41b]: ee
> [   97.750809] stb0899_dvbs_algo: Derot Percent=30 Srate=22000000
> mclk=1647
> [   97.750893] stb0899_dvbs_algo: RESET stream merger
> [   97.752023] _stb0899_read_reg: Reg=[0xff11], data=80
> [   97.752103] stb0899_write_regs [0xff11]: c0
> [   97.754207] _stb0899_read_reg: Reg=[0xf583], data=5c
> [   97.754286] stb0899_write_regs [0xf583]: 3c
> [   97.755338] stb0899_write_regs [0xf41e]: 01
> [   97.756392] stb0899_write_regs [0xf53d]: 19
> [   97.758498] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.758577] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.758656] stb0899_write_regs [0xf12a]: dc
> [   97.764979] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.765058] stb6100_get_bandwidth: Bandwidth=52000000
> [   97.765060] stb0899_write_regs [0xf43e]: 00 00
> [   97.766462] stb0899_write_regs [0xf439]: 00
> [   97.768568] _stb0899_read_reg: Reg=[0xf41b], data=ee
> [   97.768646] stb0899_write_regs [0xf41b]: ee
> [   97.769700] stb0899_dvbs_algo: Tuner set frequency
> [   97.770830] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.770909] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.770989] stb0899_write_regs [0xf12a]: dc
> [   97.777313] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.777392] stb0899_get_params: Get DVB-S params
> [   97.778522] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.778601] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.778680] stb0899_write_regs [0xf12a]: dc
> [   97.784985] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.786116] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.786195] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.786274] stb0899_write_regs [0xf12a]: dc
> [   97.789079] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.790210] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.790300] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.790380] stb0899_write_regs [0xf12a]: dc
> [   97.793185] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.802463] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.802544] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.802623] stb0899_write_regs [0xf12a]: dc
> [   97.805428] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.806559] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.806637] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.806716] stb0899_write_regs [0xf12a]: dc
> [   97.809521] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.845351] stb6100_set_frequency: Frequency=1068000
> [   97.846406] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.846484] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.846563] stb0899_write_regs [0xf12a]: dc
> [   97.852886] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.852965] stb6100_get_frequency: Frequency=1068002
> [   97.857361] stb0899_dvbs_algo: current derot freq=0
> [   97.858492] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.858574] stb0899_i2c_gate_ctrl: Enabling I2C Repeater ...
> [   97.858653] stb0899_write_regs [0xf12a]: dc
> [   97.864975] _stb0899_read_reg: Reg=[0xf12a], data=5c
> [   97.865054] stb6100_get_bandwidth: Bandwidth=52000000
> [   97.869318] stb0899_write_regs [0xf439]: f2
> [   97.871424] _stb0899_read_reg: Reg=[0xf438], data=80
> [   97.872554] _stb0899_read_reg: Reg=[0xf439], data=02
> [   97.872633] stb0899_check_tmg: ------->TIMING OK !
> [   97.874113] stb0899_read_regs [0xf43e]: fd 6d
> [   97.874117] stb0899_search_tmg: ------->TIMING OK ! Derot Freq = -659
> [   97.874199] stb0899_dvbs_algo: TIMING OK ! Derot freq=-659, mclk=1647
> [   97.875335] _stb0899_read_reg: Reg=[0xf41b], data=ee
> [   97.875413] stb0899_write_regs [0xf41b]: ee
> [   97.876467] stb0899_search_carrier: Derot Freq=-659, mclk=1647
> [   97.882354] _stb0899_read_reg: Reg=[0xf41b], data=ee
>
> Those logs don't look too bad superficially, but it's still not working.
>
> Tim.
>
> > hy,
> >
> > the wiki is not up2date.
> >
> > Twinhan VP-1041 support is now in the mantis tree (inkl. multiproto)
> >
> > hg clone http://jusst.de/hg/mantis
> >
> > but for me, the old initialization parameters works much better.
> > with the new
> > ones i get only a destructed picture (unwatchable).
> >
> > gernot



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Gernot Pansy wrote:
> hy,
> 
> have you tried some other channel on a diffrent multiplex?
> 
> i have also troubles on 2 multiplexes, but i believe that's trough my bad 
> signal strength (it's the same on windows).
> 
> otherwise there have to be some initialization registers configured 
> differently. manu is the only guy, how knows about that and can help you.
> 

It is a 1:1 clone of the 1040/1. Will add in the id's to the mantis tree.

Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Tim Hewett wrote:
> Gernot,
> 
> I have now tried the mantis tree. It also needed 
> the MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this card, 
> but after doing that it was recognised:
> 

Applied the ID's to the mantis tree alongwith some other 
fixes/optimizations.
Please do test the updated mantis tree.


Regards,
Manu

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

Manu,

I tried the changes, the card is now recognised at boot time without  
needing any manual changes to the code.

However it now no longer tunes:


root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l  
UNIVERSAL -t 0 -a 4 BBCNews24
reading channels from file '/root/.szap/channels.conf'
zapping to 6 'BBCNEWS24':
sat 1, frequency = 10773 MHz H, symbolrate 22000000, vpid = 0x0917,  
apid = 0x0919 sid = 0x0002
Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0'
----------------------------------> Using 'STB0899 DVB-S' DVB-S
do_tune: API version=3, delivery system = 0
do_tune: Frequency = 1023000, Srate = 22000000
do_tune: Frequency = 1023000, Srate = 22000000



root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap#


Many logs appear in dmesg:

[  252.991931] mantis_ack_wait (0): Slave RACK Fail !
[  252.993633] dvb_frontend_ioctl: DVBFE_GET_INFO
[  252.993637] stb0899_get_info: Querying DVB-S2 info
[  253.096348] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  253.094642] stb0899_search: set DVB-S2 params
[  253.097053] mantis start feed & dma
[  256.103782] mantis_ack_wait (0): Slave RACK Fail !
[  256.103965] stb6100_set_bandwidth: Bandwidth=39700000
[  259.105856] mantis_ack_wait (0): Slave RACK Fail !
[  259.106039] stb6100_get_bandwidth: Bandwidth=-1
[  262.117917] mantis_ack_wait (0): Slave RACK Fail !
[  262.118100] stb6100_set_frequency: Frequency=1068000
[  262.841409] mantis stop feed and dma
[  265.119990] mantis_ack_wait (0): Slave RACK Fail !
[  265.120173] stb6100_get_frequency: Frequency=493128704
[  265.614395] dvb_frontend_ioctl: DVBFE_GET_INFO
[  265.614400] stb0899_get_info: Querying DVB-S info
[  265.715893] newfec_to_oldfec: Unsupported FEC 9
[  265.715898] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  265.715929] mantis start feed & dma
[  265.716116] stb0899_search: set DVB-S params
[  268.725269] mantis_ack_wait (0): Slave RACK Fail !
[  268.725452] stb6100_set_bandwidth: Bandwidth=51610000
[  271.187024] mantis stop feed and dma
[  271.727343] mantis_ack_wait (0): Slave RACK Fail !
[  271.727526] stb6100_get_bandwidth: Bandwidth=-1
[  271.739040] stb6100_get_bandwidth: Bandwidth=40000000
[  274.747393] mantis_ack_wait (0): Slave RACK Fail !
[  274.747576] stb6100_set_frequency: Frequency=1068000
[  277.749467] mantis_ack_wait (0): Slave RACK Fail !
[  277.749649] stb6100_get_frequency: Frequency=487856768
[  280.755535] mantis_ack_wait (0): Slave RACK Fail !
[  280.755718] stb6100_get_bandwidth: Bandwidth=-32512
[  280.926082] dvb_frontend_ioctl: DVBFE_GET_INFO
[  280.926088] stb0899_get_info: Querying DVB-S info
[  281.027825] newfec_to_oldfec: Unsupported FEC 9
[  281.027831] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  281.026363] stb0899_search: set DVB-S params
[  281.028754] mantis start feed & dma
[  282.410988] mantis stop feed and dma
[  284.037242] mantis_ack_wait (0): Slave RACK Fail !
[  284.037425] stb6100_set_bandwidth: Bandwidth=51610000
[  287.039315] mantis_ack_wait (0): Slave RACK Fail !
[  287.039497] stb6100_get_bandwidth: Bandwidth=-1
[  287.051012] stb6100_get_bandwidth: Bandwidth=40000000
[  290.059364] mantis_ack_wait (0): Slave RACK Fail !
[  290.059547] stb6100_set_frequency: Frequency=1023000
[  293.061438] mantis_ack_wait (0): Slave RACK Fail !
[  293.061620] stb6100_get_frequency: Frequency=487856768
[  296.067506] mantis_ack_wait (0): Slave RACK Fail !
[  296.067688] stb6100_get_bandwidth: Bandwidth=-32512
[  296.229928] dvb_frontend_ioctl: DVBFE_GET_INFO
[  296.229932] stb0899_get_info: Querying DVB-S2 info
[  296.331851] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  296.331874] mantis start feed & dma
[  296.332053] stb0899_search: set DVB-S2 params
[  298.388761] mantis stop feed and dma
[  299.341223] mantis_ack_wait (0): Slave RACK Fail !
[  299.341407] stb6100_set_bandwidth: Bandwidth=39700000
[  302.343297] mantis_ack_wait (0): Slave RACK Fail !
[  302.343479] stb6100_get_bandwidth: Bandwidth=-1
[  305.355357] mantis_ack_wait (0): Slave RACK Fail !
[  305.355540] stb6100_set_frequency: Frequency=1023000
[  308.357430] mantis_ack_wait (0): Slave RACK Fail !
[  308.357613] stb6100_get_frequency: Frequency=493128704
[  308.853981] dvb_frontend_ioctl: DVBFE_GET_INFO
[  308.853987] stb0899_get_info: Querying DVB-S info
[  308.955298] newfec_to_oldfec: Unsupported FEC 9
[  308.955302] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  308.953772] stb0899_search: set DVB-S params
[  308.956175] mantis start feed & dma
[  311.688916] mantis stop feed and dma
[  311.962710] mantis_ack_wait (0): Slave RACK Fail !
[  311.962893] stb6100_set_bandwidth: Bandwidth=51610000
[  314.964783] mantis_ack_wait (0): Slave RACK Fail !
[  314.964966] stb6100_get_bandwidth: Bandwidth=-1
[  314.977227] stb6100_get_bandwidth: Bandwidth=40000000
[  317.984834] mantis_ack_wait (0): Slave RACK Fail !
[  317.985016] stb6100_set_frequency: Frequency=1023000
[  320.986907] mantis_ack_wait (0): Slave RACK Fail !
[  320.987088] stb6100_get_frequency: Frequency=487856768
[  323.992976] mantis_ack_wait (0): Slave RACK Fail !
[  323.993157] stb6100_get_bandwidth: Bandwidth=-32512

HTH,

Tim.


On 23 Feb 2008, at 22:22, Manu Abraham wrote:

> Tim Hewett wrote:
>> Gernot,
>> I have now tried the mantis tree. It also needed the  
>> MANTIS_VP_1041_DVB_S2 #define to be changed to 0x0001 for this  
>> card, but after doing that it was recognised:
>
> Applied the ID's to the mantis tree alongwith some other fixes/ 
> optimizations.
> Please do test the updated mantis tree.
>
>
> Regards,
> Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Tim Hewett wrote:
> Manu,
> 
> I tried the changes, the card is now recognised at boot time without 
> needing any manual changes to the code.
> 
> However it now no longer tunes:

Sigh! missed out something while i carried forward something. I have
applied the fix to the tree just now. Please try again.

Regards,
Manu



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

Manu,

Thanks, it now tunes to horizontal transponders though not vertical  
ones. I think others have been having similar symptoms with the mantis/ 
multiproto trees.

It won't tune to any DVB-S2 transponder, but that has not changed  
since previously.

Output from successful tuning:

root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l  
UNIVERSAL -t 0 -a 4 BBCNews24
reading channels from file '/root/.szap/channels.conf'
zapping to 6 'BBCNEWS24':
sat 1, frequency = 10773 MHz H, symbolrate 22000000, vpid = 0x0917,  
apid = 0x0919 sid = 0x0002
Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0'
----------------------------------> Using 'STB0899 DVB-S' DVB-S
do_tune: API version=3, delivery system = 0
do_tune: Frequency = 1023000, Srate = 22000000
do_tune: Frequency = 1023000, Srate = 22000000


couldn't find pmt-pid for sid 0002
status 1e | signal 0128 | snr 0072 | ber 00000000 | unc fffffffe |  
FE_HAS_LOCK
status 1e | signal 0128 | snr 0071 | ber 00000000 | unc fffffffe |  
FE_HAS_LOCK
status 1e | signal 0128 | snr 0073 | ber 00000000 | unc fffffffe |  
FE_HAS_LOCK

root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap#


Output from unsuccessful tuning:

root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap# ./szap -r -p -l  
UNIVERSAL -t 0 -a 4 BBC1West
reading channels from file '/root/.szap/channels.conf'
zapping to 1 'BBC1West':
sat 1, frequency = 10818 MHz V, symbolrate 22000000, vpid = 0x0901,  
apid = 0x0903 sid = 0x0002
Querying info .. Delivery system=DVB-S
using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0'
----------------------------------> Using 'STB0899 DVB-S' DVB-S
do_tune: API version=3, delivery system = 0
do_tune: Frequency = 1068000, Srate = 22000000
do_tune: Frequency = 1068000, Srate = 22000000



root@kubuntu7:~/linuxtv-dvb-apps-1.1.1/util/szap#


Messages in dmesg for successful tuning:

[  402.455361] dvb_frontend_ioctl: DVBFE_GET_INFO
[  402.455366] stb0899_get_info: Querying DVB-S info
[  402.556373] newfec_to_oldfec: Unsupported FEC 9
[  402.556377] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  402.556998] mantis start feed & dma
[  402.557255] stb0899_search: set DVB-S params
[  402.567810] stb6100_set_bandwidth: Bandwidth=51610000
[  402.569927] stb6100_get_bandwidth: Bandwidth=52000000
[  402.581331] stb6100_get_bandwidth: Bandwidth=52000000
[  402.613394] stb6100_set_frequency: Frequency=1023000
[  402.615510] stb6100_get_frequency: Frequency=1022994
[  402.621496] stb6100_get_bandwidth: Bandwidth=52000000
[  404.541047] _stb0899_read_reg: Read error, Reg=[0xf525], Status=-121
[  404.541749] mantis stop feed and dma


Messages in dmesg for unsuccessful tuning:

[  428.255926] dvb_frontend_ioctl: DVBFE_GET_INFO
[  428.255935] stb0899_get_info: Querying DVB-S info
[  428.358369] newfec_to_oldfec: Unsupported FEC 9
[  428.358375] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
[  428.358384] stb0899_search: set DVB-S params
[  428.366099] mantis start feed & dma
[  428.370052] stb6100_set_bandwidth: Bandwidth=51610000
[  428.372169] stb6100_get_bandwidth: Bandwidth=52000000
[  428.383571] stb6100_get_bandwidth: Bandwidth=52000000
[  428.415643] stb6100_set_frequency: Frequency=1068000
[  428.417759] stb6100_get_frequency: Frequency=1068002
[  428.423743] stb6100_get_bandwidth: Bandwidth=52000000
[  428.855068] stb0899_search: set DVB-S params
[  428.867399] stb6100_set_bandwidth: Bandwidth=51610000
[  428.869513] stb6100_get_bandwidth: Bandwidth=52000000
[  428.880942] stb6100_get_bandwidth: Bandwidth=52000000
[  428.912989] stb6100_set_frequency: Frequency=1068000
[  428.915105] stb6100_get_frequency: Frequency=1068002
[  428.921089] stb6100_get_bandwidth: Bandwidth=52000000
[  429.360404] stb0899_search: set DVB-S params
[  429.372735] stb6100_set_bandwidth: Bandwidth=51610000
[  429.374877] stb6100_get_bandwidth: Bandwidth=52000000
[  429.386280] stb6100_get_bandwidth: Bandwidth=52000000
[  429.420690] stb6100_set_frequency: Frequency=1068000
[  429.423096] stb6100_get_frequency: Frequency=1068002
[  429.428790] stb6100_get_bandwidth: Bandwidth=52000000
[  429.858115] stb0899_search: set DVB-S params
[  429.870449] stb6100_set_bandwidth: Bandwidth=51610000
[  429.872856] stb6100_get_bandwidth: Bandwidth=52000000
[  429.884544] stb6100_get_bandwidth: Bandwidth=52000000
[  429.918035] stb6100_set_frequency: Frequency=1068000
[  429.920436] stb6100_get_frequency: Frequency=1068002
[  429.926137] stb6100_get_bandwidth: Bandwidth=52000000
[  430.325501] stb0899_search: set DVB-S params
[  430.337835] stb6100_set_bandwidth: Bandwidth=51610000
[  430.340273] stb6100_get_bandwidth: Bandwidth=52000000
[  430.351963] stb6100_get_bandwidth: Bandwidth=52000000
[  430.385421] stb6100_set_frequency: Frequency=1068000
[  430.387816] stb6100_get_frequency: Frequency=1068002
[  430.393523] stb6100_get_bandwidth: Bandwidth=52000000
[  430.834833] stb0899_search: set DVB-S params
[  430.847166] stb6100_set_bandwidth: Bandwidth=51610000
[  430.849576] stb6100_get_bandwidth: Bandwidth=52000000
[  430.861267] stb6100_get_bandwidth: Bandwidth=52000000
[  430.894753] stb6100_set_frequency: Frequency=1068000
[  430.897148] stb6100_get_frequency: Frequency=1068002
[  430.902855] stb6100_get_bandwidth: Bandwidth=52000000
[  431.133659] mantis stop feed and dma

HTH,

Tim.


On 23 Feb 2008, at 23:43, Manu Abraham wrote:

> Tim Hewett wrote:
>> Manu,
>> I tried the changes, the card is now recognised at boot time  
>> without needing any manual changes to the code.
>> However it now no longer tunes:
>
> Sigh! missed out something while i carried forward something. I have
> applied the fix to the tree just now. Please try again.
>
> Regards,
> Manu
>
>


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Tim Hewett wrote:
> Manu,
> 
> Thanks, it now tunes to horizontal transponders though not vertical 
> ones. I think others have been having similar symptoms with the 
> mantis/multiproto trees.

Can someone replicate this behaviour: not tuning to vertical transponders ?
Do you have any switches or a rotor in the SEC chain ?

> It won't tune to any DVB-S2 transponder, but that has not changed since 
> previously.


Hmm .. Are you really sure ?


> Messages in dmesg for successful tuning:
> 
> [  402.455361] dvb_frontend_ioctl: DVBFE_GET_INFO
> [  402.455366] stb0899_get_info: Querying DVB-S info
> [  402.556373] newfec_to_oldfec: Unsupported FEC 9
> [  402.556377] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
> [  402.556998] mantis start feed & dma
> [  402.557255] stb0899_search: set DVB-S params
> [  402.567810] stb6100_set_bandwidth: Bandwidth=51610000
> [  402.569927] stb6100_get_bandwidth: Bandwidth=52000000
> [  402.581331] stb6100_get_bandwidth: Bandwidth=52000000
> [  402.613394] stb6100_set_frequency: Frequency=1023000
> [  402.615510] stb6100_get_frequency: Frequency=1022994
> [  402.621496] stb6100_get_bandwidth: Bandwidth=52000000
> [  404.541047] _stb0899_read_reg: Read error, Reg=[0xf525], Status=-121
> [  404.541749] mantis stop feed and dma

I will need the stb0899 and stb6100 modules to be loaded with verbose=5
parameter, for understanding what's happening.


Regards,
Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

Manu,

On 24 Feb 2008, at 00:38, Manu Abraham wrote:

> Do you have any switches or a rotor in the SEC chain ?


I have a Diseqc 1.0 switch on this card.

I just retested using Technisat's Windows software and the vertical  
transponders still don't work, same for DVB-S2 transponders. Strange,  
they worked perfectly every time previously, e.g. BBCHD on 10847/v on  
Astra 2D. But not today. For now, my system is the problem.

Definitely still no tuning to DVB-S2 transponders under Linux,  
horizontal or vertical. Horizontal ones work ok with Technisat's  
Windows software.

Tim.

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

Manu,

The Diseqc switch has been removed and now all polarities tune, and  
DVB-S2 works as well.

Thanks!

Tim.


On 24 Feb 2008, at 00:38, Manu Abraham wrote:

> Tim Hewett wrote:
>> Manu,
>> Thanks, it now tunes to horizontal transponders though not vertical  
>> ones. I think others have been having similar symptoms with the  
>> mantis/multiproto trees.
>
> Can someone replicate this behaviour: not tuning to vertical  
> transponders ?
> Do you have any switches or a rotor in the SEC chain ?
>
>> It won't tune to any DVB-S2 transponder, but that has not changed  
>> since previously.
>
>
> Hmm .. Are you really sure ?
>
>
>> Messages in dmesg for successful tuning:
>> [  402.455361] dvb_frontend_ioctl: DVBFE_GET_INFO
>> [  402.455366] stb0899_get_info: Querying DVB-S info
>> [  402.556373] newfec_to_oldfec: Unsupported FEC 9
>> [  402.556377] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
>> [  402.556998] mantis start feed & dma
>> [  402.557255] stb0899_search: set DVB-S params
>> [  402.567810] stb6100_set_bandwidth: Bandwidth=51610000
>> [  402.569927] stb6100_get_bandwidth: Bandwidth=52000000
>> [  402.581331] stb6100_get_bandwidth: Bandwidth=52000000
>> [  402.613394] stb6100_set_frequency: Frequency=1023000
>> [  402.615510] stb6100_get_frequency: Frequency=1022994
>> [  402.621496] stb6100_get_bandwidth: Bandwidth=52000000
>> [  404.541047] _stb0899_read_reg: Read error, Reg=[0xf525],  
>> Status=-121
>> [  404.541749] mantis stop feed and dma
>
> I will need the stb0899 and stb6100 modules to be loaded with  
> verbose=5
> parameter, for understanding what's happening.
>
>
> Regards,
> Manu
>


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Manu Abraham]

Tim Hewett wrote:
> Manu,
> 
> The Diseqc switch has been removed and now all polarities tune, and 
> DVB-S2 works as well.
> 

Bad diseqc switch ?

Regards,
Manu




> Thanks!
> 
> Tim.
> 
> 
> On 24 Feb 2008, at 00:38, Manu Abraham wrote:
> 
>> Tim Hewett wrote:
>>> Manu,
>>> Thanks, it now tunes to horizontal transponders though not vertical 
>>> ones. I think others have been having similar symptoms with the 
>>> mantis/multiproto trees.
>>
>> Can someone replicate this behaviour: not tuning to vertical 
>> transponders ?
>> Do you have any switches or a rotor in the SEC chain ?
>>
>>> It won't tune to any DVB-S2 transponder, but that has not changed 
>>> since previously.
>>
>>
>> Hmm .. Are you really sure ?
>>
>>
>>> Messages in dmesg for successful tuning:
>>> [  402.455361] dvb_frontend_ioctl: DVBFE_GET_INFO
>>> [  402.455366] stb0899_get_info: Querying DVB-S info
>>> [  402.556373] newfec_to_oldfec: Unsupported FEC 9
>>> [  402.556377] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
>>> [  402.556998] mantis start feed & dma
>>> [  402.557255] stb0899_search: set DVB-S params
>>> [  402.567810] stb6100_set_bandwidth: Bandwidth=51610000
>>> [  402.569927] stb6100_get_bandwidth: Bandwidth=52000000
>>> [  402.581331] stb6100_get_bandwidth: Bandwidth=52000000
>>> [  402.613394] stb6100_set_frequency: Frequency=1023000
>>> [  402.615510] stb6100_get_frequency: Frequency=1022994
>>> [  402.621496] stb6100_get_bandwidth: Bandwidth=52000000
>>> [  404.541047] _stb0899_read_reg: Read error, Reg=[0xf525], Status=-121
>>> [  404.541749] mantis stop feed and dma
>>
>> I will need the stb0899 and stb6100 modules to be loaded with verbose=5
>> parameter, for understanding what's happening.
>>
>>
>> Regards,
>> Manu
>>
> 
> 


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

I have three diseqc switches, all different models, they all behave in  
this way. The PC also has three Skystar 2 (non HD) card and they all  
have trouble with these switches. I had hoped that because the Skystar  
HD2 has its own power supply separate from the PCI bus, that might  
help, but no.

My Technomate TM1000 receiver has no problems with any of the switches.

Different subject: I want to modify dvbstream to be able to tune the  
SkyStar HD2, is there any information on the changes to the API? I  
have tried to follow the changes made to szap.c, but so far without  
any success in terms of getting dvbstream to tune.

Tim.


On 24 Feb 2008, at 16:27, Manu Abraham wrote:

> Tim Hewett wrote:
>> Manu,
>> The Diseqc switch has been removed and now all polarities tune, and  
>> DVB-S2 works as well.
>
> Bad diseqc switch ?
>
> Regards,
> Manu


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

[linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Tim Hewett]

[-- Attachment #1.1: Type: text/plain, Size: 3294 bytes --]

I'm trying to get a new Technisat Skystar HD2 working. It looks like  
it is a Twinhan VP-1041/Azurewave AD SP400 rebadge.

The card hardware and satellite feed has been confirmed to work ok  
under Windows using Technisat's software.

I am using the current multiproto DVB drivers, downloaded today. These  
were patched, built and installed successfully as described for the  
Azurewave AD SP400 in the linuxdvb wiki, but the card was not  
recognised on bootup even though it was allocated a DVB adaptor  
number. This appeared in dmesg:

[   57.359723] found a UNKNOWN PCI UNKNOWN device on (01:06.0),
[   57.359802]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
[   57.359858]     memory: 0xe5100000, mmio: 0xffffc200000fc000
[   57.363015]     MAC Address=[00:08:c9:e0:26:92]
[   57.363133] mantis_alloc_buffers (0): DMA=0x1b7a0000  
cpu=0xffff81001b7a0000 size=65536
[   57.363242] mantis_alloc_buffers (0): RISC=0x1ae24000  
cpu=0xffff81001ae24000 size=1000
[   57.363348] DVB: registering new adapter (Mantis dvb adapter)


This is the output of lspci -vvn:

01:06.0 0480: 1822:4e35 (rev 01)
	Subsystem: 1ae4:0001
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2000ns min, 63750ns max)
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e5100000 (32-bit, prefetchable) [size=4K]

This is the output of lsusb -vv:

01:06.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV  
PCI Bridge Controller [Ver 1.0] (rev 01)
	Subsystem: Unknown device 1ae4:0001
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-  
Stepping- SERR- FastB2B-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-  
<TAbort- <MAbort- >SERR- <PERR-
	Latency: 32 (2000ns min, 63750ns max)
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at e5100000 (32-bit, prefetchable) [size=4K]

Note that subsystem IDs 1ae4:0001 are different to those listed in the  
wiki for the Azurewave (1822:0031).

I changed #define MANTIS_VP_1041_DVB_S2	in linux/drivers/media/dvb/ 
mantis/mantis_vp1041.h from 0x0031 to 0x0001, which changed the dmesg  
output on reboot to this:

[   59.546375] found a VP-1041 PCI DVB-S/DVB-S2 device on (01:06.0),
[   59.546456]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
[   59.546512]     memory: 0xe5100000, mmio: 0xffffc200000fc000
[   59.549609]     MAC Address=[00:08:c9:e0:26:92]
[   59.549719] mantis_alloc_buffers (0): DMA=0x1b7b0000  
cpu=0xffff81001b7b0000 size=65536
[   59.549827] mantis_alloc_buffers (0): RISC=0x1af43000  
cpu=0xffff81001af43000 size=1000
[   59.549933] DVB: registering new adapter (Mantis dvb adapter)
[   60.137583] stb0899_attach: Attaching STB0899
[   60.137665] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2  
frontend @0x68
[   60.152161] stb6100_attach: Attaching STB6100
[   60.168021] DVB: registering frontend 3 (STB0899 Multistandard)...

So that change seemed to cause the card to be recognised.

Then I tried the replacement scan and szap as suggested by the  
Azurewave wiki, but the card will not tune.

So it appears to be almost working, but I'm not sure what tests to try  
or changes to make to see if it will work.

[-- Attachment #1.2: Type: text/html, Size: 19364 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] Help with Skystar HD2 (Twinhan VP-1041/Azurewave AD SP400 rebadge)

[Gernot Pansy]

hy,

the wiki is not up2date. 

Twinhan VP-1041 support is now in the mantis tree (inkl. multiproto)

hg clone http://jusst.de/hg/mantis

but for me, the old initialization parameters works much better. with the new 
ones i get only a destructed picture (unwatchable).  

gernot

On Monday 18 February 2008 20:05:03 Tim Hewett wrote:
> I'm trying to get a new Technisat Skystar HD2 working. It looks like
> it is a Twinhan VP-1041/Azurewave AD SP400 rebadge.
>
> The card hardware and satellite feed has been confirmed to work ok
> under Windows using Technisat's software.
>
> I am using the current multiproto DVB drivers, downloaded today. These
> were patched, built and installed successfully as described for the
> Azurewave AD SP400 in the linuxdvb wiki, but the card was not
> recognised on bootup even though it was allocated a DVB adaptor
> number. This appeared in dmesg:
>
> [   57.359723] found a UNKNOWN PCI UNKNOWN device on (01:06.0),
> [   57.359802]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
> [   57.359858]     memory: 0xe5100000, mmio: 0xffffc200000fc000
> [   57.363015]     MAC Address=[00:08:c9:e0:26:92]
> [   57.363133] mantis_alloc_buffers (0): DMA=0x1b7a0000
> cpu=0xffff81001b7a0000 size=65536
> [   57.363242] mantis_alloc_buffers (0): RISC=0x1ae24000
> cpu=0xffff81001ae24000 size=1000
> [   57.363348] DVB: registering new adapter (Mantis dvb adapter)
>
>
> This is the output of lspci -vvn:
>
> 01:06.0 0480: 1822:4e35 (rev 01)
> 	Subsystem: 1ae4:0001
> 	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> 	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> 	Latency: 32 (2000ns min, 63750ns max)
> 	Interrupt: pin A routed to IRQ 16
> 	Region 0: Memory at e5100000 (32-bit, prefetchable) [size=4K]
>
> This is the output of lsusb -vv:
>
> 01:06.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV
> PCI Bridge Controller [Ver 1.0] (rev 01)
> 	Subsystem: Unknown device 1ae4:0001
> 	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B-
> 	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
> 	Latency: 32 (2000ns min, 63750ns max)
> 	Interrupt: pin A routed to IRQ 16
> 	Region 0: Memory at e5100000 (32-bit, prefetchable) [size=4K]
>
> Note that subsystem IDs 1ae4:0001 are different to those listed in the
> wiki for the Azurewave (1822:0031).
>
> I changed #define MANTIS_VP_1041_DVB_S2	in linux/drivers/media/dvb/
> mantis/mantis_vp1041.h from 0x0031 to 0x0001, which changed the dmesg
> output on reboot to this:
>
> [   59.546375] found a VP-1041 PCI DVB-S/DVB-S2 device on (01:06.0),
> [   59.546456]     Mantis Rev 1 [1ae4:0001], irq: 16, latency: 32
> [   59.546512]     memory: 0xe5100000, mmio: 0xffffc200000fc000
> [   59.549609]     MAC Address=[00:08:c9:e0:26:92]
> [   59.549719] mantis_alloc_buffers (0): DMA=0x1b7b0000
> cpu=0xffff81001b7b0000 size=65536
> [   59.549827] mantis_alloc_buffers (0): RISC=0x1af43000
> cpu=0xffff81001af43000 size=1000
> [   59.549933] DVB: registering new adapter (Mantis dvb adapter)
> [   60.137583] stb0899_attach: Attaching STB0899
> [   60.137665] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2
> frontend @0x68
> [   60.152161] stb6100_attach: Attaching STB6100
> [   60.168021] DVB: registering frontend 3 (STB0899 Multistandard)...
>
> So that change seemed to cause the card to be recognised.
>
> Then I tried the replacement scan and szap as suggested by the
> Azurewave wiki, but the card will not tune.
>
> So it appears to be almost working, but I'm not sure what tests to try
> or changes to make to see if it will work.



_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb