[linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Dave Lister]

Hello all,

I'd like to ask for your help. After weeks of research and
deliberation I bought two SkyStar HD2 PCI cards (quite a lot money for
me). It seemed to be working for everybody. BUT I have already spent
two days reading mailing lists, downloading repositories, compiling
drivers, apps, kernels and bending code to make it compile. Please,
does anybody know how to help me?

In short the driver doesn't seem to communicate with the card at all.
It's unable to send DiSEqC commands (not necessary in my case), unable
to tune the tuner, unable to report any signal strength info etc. I
have a dark sense of foreboding about this, because as things stand
now, it seems I'll have to recoup my losses (can't return these cards)
and buy different ones, possibly more expensive. Just these two cost
me half my month's salary. I was so damn sure they'll work - from all
the reports and success stories on the web, even LinuxTV said so. If
you knew my wife... I mean this is going to be a disaster. :(


Drivers tried: http://jusst.de/hg/multiproto,
http://jusst.de/hg/mantis (couldn't make it compile)
Driver used: http://mercurial.intuxication.org/hg/s2-liplianin
Kernels tried w/driver: Debian 2.6.29; Debian 2.6.26; vanilla 2.6.29
DVB apps/utils: 1.1.1+rev1207-4
S2API DVB apps/utils: http://mercurial.intuxication.org/hg/{szap-s2,scan-s2}

lspci -vv:
07:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV
PCI Bridge Controller [Ver 1.0] (rev 01)
	Subsystem: Device 1ae4:0003
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort+ <MAbort- >SERR- <PERR+ INTx-
	Latency: 32 (2000ns min, 63750ns max)
	Interrupt: pin A routed to IRQ 19
	Region 0: Memory at ec200000 (32-bit, prefetchable) [size=4K]
	Kernel driver in use: Mantis
	Kernel modules: mantis

Boot-up dmesg:
[    6.704959] Mantis 0000:07:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
[    6.705100] irq: 19, latency: 32
[    6.705101]  memory: 0xec200000, mmio: 0xf8286000
[    6.705183] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (07:01.0),
[    6.705228]     Mantis Rev 1 [1ae4:0003], irq: 19, latency: 32
[    6.705261]     memory: 0xec200000, mmio: 0xf8286000
[    6.708020]     MAC Address=[00:08:c9:e0:40:6a]
[    6.708075] mantis_alloc_buffers (0): DMA=0x35d40000 cpu=0xf5d40000
size=65536
[    6.708128] mantis_alloc_buffers (0): RISC=0x36327000
cpu=0xf6327000 size=1000
[    6.708179] DVB: registering new adapter (Mantis dvb adapter)
[    7.253355] stb0899_attach: Attaching STB0899
[    7.253397] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2
frontend @0x68
[    7.253449] stb6100_attach: Attaching STB6100
[    7.253836] LNBx2x attached on addr=8DVB: registering adapter 0
frontend 0 (STB0899 Multistandard)...
[    7.253938] mantis_ca_init (0): Registering EN50221 device
[    7.254033] mantis_ca_init (0): Registered EN50221 device
[    7.254096] mantis_hif_init (0): Adapter(0) Initializing Mantis
Host Interface

Sat cable has 98% signal, Astra 19.2E, working in a TV/STB sitting
right next to the PC. I reconnect the cable from the TV into SkyStar
and try tuning:

birko:~# scan-s2 -v /usr/share/dvb/dvb-s/Astra-19.2E
API major 5, minor 0
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning /usr/share/dvb/dvb-s/Astra-19.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12551500 V 22000000 5/6 AUTO AUTO
initial transponder DVB-S2 12551500 V 22000000 5/6 AUTO AUTO
----------------------------------> Using DVB-S
>>> tune to: 12551:vC56S0:S0.0W:22000:
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 13V, hiband (index 2)
DVB-S IF freq is 1951500
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
----------------------------------> Using DVB-S2
>>> tune to: 12551:vC56S1:S0.0W:22000:
DiSEqC: uncommitted switch pos 0
DiSEqC: switch pos 0, 13V, hiband (index 2)
DVB-S IF freq is 1951500
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
>>> tuning status == 0x00
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.

Meanwhile, this is written to dmesg (repeating):
[43395.935293] stb6100_set_bandwidth: Bandwidth=51610000
[43395.943657] stb6100_get_bandwidth: Bandwidth=10000000
[43395.970435] stb6100_get_bandwidth: Bandwidth=10000000
[43396.062102] stb6100_set_frequency: Frequency=1951500
[43396.070464] stb6100_get_frequency: Frequency=0
[43396.084862] stb6100_get_bandwidth: Bandwidth=10000000
[43396.622789] stb6100_set_bandwidth: Bandwidth=51610000
[43396.631150] stb6100_get_bandwidth: Bandwidth=10000000
[43396.657947] stb6100_get_bandwidth: Bandwidth=10000000
[43396.754182] stb6100_set_frequency: Frequency=1951500
[43396.762548] stb6100_get_frequency: Frequency=0
[43396.776884] stb6100_get_bandwidth: Bandwidth=10000000
[43397.314789] stb6100_set_bandwidth: Bandwidth=51610000
[43397.323151] stb6100_get_bandwidth: Bandwidth=10000000
[43397.349932] stb6100_get_bandwidth: Bandwidth=10000000
[43397.442099] stb6100_set_frequency: Frequency=1951500
[43397.450460] stb6100_get_frequency: Frequency=0
[43397.464861] stb6100_get_bandwidth: Bandwidth=10000000
[43398.002788] stb6100_set_bandwidth: Bandwidth=51610000
[43398.011150] stb6100_get_bandwidth: Bandwidth=10000000
[43398.037932] stb6100_get_bandwidth: Bandwidth=10000000
[43398.130098] stb6100_set_frequency: Frequency=1951500
[43398.138459] stb6100_get_frequency: Frequency=0

Szap/szap-s2 also doesn't work. The channel in question is the same
one, being displayed on TV/STB, when I re-plug the sat. cable into the
TV (not changing channels, STB has it locked and as soon as I provide
signal, it works). The STB parallel-story is there for you to see
there are no switching issues, no signal weakness, etc.

birko:~# szap-s2 -c channels.conf CT1
reading channels from file 'channels.conf'
zapping to 3 'CT1':
delivery DVB-S2, modulation QPSK
sat 0, frequency 12382 MHz V, symbolrate 27500000, coderate 3/4, rolloff 0.35
vpid 0x0065, apid 0x006f, sid 0x4f5b
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
FE_SET_TONE failed: Connection timed out
FE_DISEQC_SEND_BURST failed: Connection timed out
FE_SET_TONE failed: Connection timed out
status 00 | signal 006f | snr 0001 | ber 00000000 | unc fffffffe |
status 00 | signal 006f | snr 0001 | ber 00000000 | unc fffffffe |
status 00 | signal 006f | snr 0001 | ber 00000000 | unc fffffffe |
... repeated; same values even if sat. cable disconnected ...

Meanwhile in dmesg:
[43679.573136] mantis start feed & dma
[43679.602799] stb6100_set_bandwidth: Bandwidth=47125000
[43679.611161] stb6100_get_bandwidth: Bandwidth=10000000
[43679.710092] stb6100_set_frequency: Frequency=1782000
[43679.718453] stb6100_get_frequency: Frequency=0
[43680.947291] stb6100_set_bandwidth: Bandwidth=47125000
[43680.955653] stb6100_get_bandwidth: Bandwidth=10000000
[43681.050093] stb6100_set_frequency: Frequency=1782000
[43681.058454] stb6100_get_frequency: Frequency=0
[43682.286788] stb6100_set_bandwidth: Bandwidth=47125000
[43682.295149] stb6100_get_bandwidth: Bandwidth=10000000
[43682.394092] stb6100_set_frequency: Frequency=1782000
[43682.402453] stb6100_get_frequency: Frequency=0
[43683.630788] stb6100_set_bandwidth: Bandwidth=47125000
[43683.639150] stb6100_get_bandwidth: Bandwidth=10000000
[43683.652591] mantis stop feed and dma


What do you think? Is there any chance of finding a working driver?

Thank you,
David Lister

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Hartmut]

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

I have the same card since 6 weeks and it works in "non HD-TV-mode" on
opensuse 11.0. The driver is: Driver used:
http://mercurial.intuxication.org/hg/s2-liplianin. From what you wrote I
think the card is working. But try to scan in this way:

scan-s2 -a 1 -s 0 -x 0 -t 1 /usr/share/dvb/dvb-s/Astra-19.2E >
~/.szap/channels1.conf

This worked for me. -a 1 is the my second TV-card, you should use 0, -s
0 is OK, -x 0 finds only free-to-air-channels, t -1 finds only TV. You
output in dmesg is OK, shows that the card is working.

Hartmut
 
Dave Lister schrieb:
> Hello all,
>
> I'd like to ask for your help. After weeks of research and
> deliberation I bought two SkyStar HD2 PCI cards (quite a lot money for
> me). It seemed to be working for everybody. BUT I have already spent
> two days reading mailing lists, downloading repositories, compiling
> drivers, apps, kernels and bending code to make it compile. Please,
> does anybody know how to help me?
>
> In short the driver doesn't seem to communicate with the card at all.
> It's unable to send DiSEqC commands (not necessary in my case), unable
> to tune the tuner, unable to report any signal strength info etc. I
> have a dark sense of foreboding about this, because as things stand
> now, it seems I'll have to recoup my losses (can't return these cards)
> and buy different ones, possibly more expensive. Just these two cost
> me half my month's salary. I was so damn sure they'll work - from all
> the reports and success stories on the web, even LinuxTV said so. If
> you knew my wife... I mean this is going to be a disaster. :(
>
>
> Drivers tried: http://jusst.de/hg/multiproto,
> http://jusst.de/hg/mantis (couldn't make it compile)
> Driver used: http://mercurial.intuxication.org/hg/s2-liplianin
> Kernels tried w/driver: Debian 2.6.29; Debian 2.6.26; vanilla 2.6.29
> DVB apps/utils: 1.1.1+rev1207-4
> S2API DVB apps/utils: http://mercurial.intuxication.org/hg/{szap-s2,scan-s2}
>
> lspci -vv:
> 07:01.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV
> PCI Bridge Controller [Ver 1.0] (rev 01)
> 	Subsystem: Device 1ae4:0003
> 	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
> Stepping- SERR- FastB2B- DisINTx-
> 	Status: Cap- 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
> <TAbort+ <MAbort- >SERR- <PERR+ INTx-
> 	Latency: 32 (2000ns min, 63750ns max)
> 	Interrupt: pin A routed to IRQ 19
> 	Region 0: Memory at ec200000 (32-bit, prefetchable) [size=4K]
> 	Kernel driver in use: Mantis
> 	Kernel modules: mantis
>
> Boot-up dmesg:
> [    6.704959] Mantis 0000:07:01.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [    6.705100] irq: 19, latency: 32
> [    6.705101]  memory: 0xec200000, mmio: 0xf8286000
> [    6.705183] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (07:01.0),
> [    6.705228]     Mantis Rev 1 [1ae4:0003], irq: 19, latency: 32
> [    6.705261]     memory: 0xec200000, mmio: 0xf8286000
> [    6.708020]     MAC Address=[00:08:c9:e0:40:6a]
> [    6.708075] mantis_alloc_buffers (0): DMA=0x35d40000 cpu=0xf5d40000
> size=65536
> [    6.708128] mantis_alloc_buffers (0): RISC=0x36327000
> cpu=0xf6327000 size=1000
> [    6.708179] DVB: registering new adapter (Mantis dvb adapter)
> [    7.253355] stb0899_attach: Attaching STB0899
> [    7.253397] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2
> frontend @0x68
> [    7.253449] stb6100_attach: Attaching STB6100
> [    7.253836] LNBx2x attached on addr=8DVB: registering adapter 0
> frontend 0 (STB0899 Multistandard)...
> [    7.253938] mantis_ca_init (0): Registering EN50221 device
> [    7.254033] mantis_ca_init (0): Registered EN50221 device
> [    7.254096] mantis_hif_init (0): Adapter(0) Initializing Mantis
> Host Interface
>
> Sat cable has 98% signal, Astra 19.2E, working in a TV/STB sitting
> right next to the PC. I reconnect the cable from the TV into SkyStar
> and try tuning:
>
> birko:~# scan-s2 -v /usr/share/dvb/dvb-s/Astra-19.2E
> API major 5, minor 0
> ERROR: Cannot open rotor configuration file 'rotor.conf'.
> scanning /usr/share/dvb/dvb-s/Astra-19.2E
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> initial transponder DVB-S  12551500 V 22000000 5/6 AUTO AUTO
> initial transponder DVB-S2 12551500 V 22000000 5/6 AUTO AUTO
> ----------------------------------> Using DVB-S
>   
>>>> tune to: 12551:vC56S0:S0.0W:22000:
>>>>         
> DiSEqC: uncommitted switch pos 0
> DiSEqC: switch pos 0, 13V, hiband (index 2)
> DVB-S IF freq is 1951500
>   
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>>         
> WARNING: >>> tuning failed!!!
> ----------------------------------> Using DVB-S2
>   
>>>> tune to: 12551:vC56S1:S0.0W:22000:
>>>>         
> DiSEqC: uncommitted switch pos 0
> DiSEqC: switch pos 0, 13V, hiband (index 2)
> DVB-S IF freq is 1951500
>   
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>> tuning status == 0x00
>>>>         
> WARNING: >>> tuning failed!!!
> ERROR: initial tuning failed
> dumping lists (0 services)
> Done.
>
> Meanwhile, this is written to dmesg (repeating):
> [43395.935293] stb6100_set_bandwidth: Bandwidth=51610000
> [43395.943657] stb6100_get_bandwidth: Bandwidth=10000000
> [43395.970435] stb6100_get_bandwidth: Bandwidth=10000000
> [43396.062102] stb6100_set_frequency: Frequency=1951500
> [43396.070464] stb6100_get_frequency: Frequency=0
> [43396.084862] stb6100_get_bandwidth: Bandwidth=10000000
> [43396.622789] stb6100_set_bandwidth: Bandwidth=51610000
> [43396.631150] stb6100_get_bandwidth: Bandwidth=10000000
> [43396.657947] stb6100_get_bandwidth: Bandwidth=10000000
> [43396.754182] stb6100_set_frequency: Frequency=1951500
> [43396.762548] stb6100_get_frequency: Frequency=0
> [43396.776884] stb6100_get_bandwidth: Bandwidth=10000000
> [43397.314789] stb6100_set_bandwidth: Bandwidth=51610000
> [43397.323151] stb6100_get_bandwidth: Bandwidth=10000000
> [43397.349932] stb6100_get_bandwidth: Bandwidth=10000000
> [43397.442099] stb6100_set_frequency: Frequency=1951500
> [43397.450460] stb6100_get_frequency: Frequency=0
> [43397.464861] stb6100_get_bandwidth: Bandwidth=10000000
> [43398.002788] stb6100_set_bandwidth: Bandwidth=51610000
> [43398.011150] stb6100_get_bandwidth: Bandwidth=10000000
> [43398.037932] stb6100_get_bandwidth: Bandwidth=10000000
> [43398.130098] stb6100_set_frequency: Frequency=1951500
> [43398.138459] stb6100_get_frequency: Frequency=0
>
> Szap/szap-s2 also doesn't work. The channel in question is the same
> one, being displayed on TV/STB, when I re-plug the sat. cable into the
> TV (not changing channels, STB has it locked and as soon as I provide
> signal, it works). The STB parallel-story is there for you to see
> there are no switching issues, no signal weakness, etc.
>
> birko:~# szap-s2 -c channels.conf CT1
> reading channels from file 'channels.conf'
> zapping to 3 'CT1':
> delivery DVB-S2, modulation QPSK
> sat 0, frequency 12382 MHz V, symbolrate 27500000, coderate 3/4, rolloff 0.35
> vpid 0x0065, apid 0x006f, sid 0x4f5b
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> FE_SET_TONE failed: Connection timed out
> FE_DISEQC_SEND_BURST failed: Connection timed out
> FE_SET_TONE failed: Connection timed out
> status 00 | signal 006f | snr 0001 | ber 00000000 | unc fffffffe |
> status 00 | signal 006f | snr 0001 | ber 00000000 | unc fffffffe |
> status 00 | signal 006f | snr 0001 | ber 00000000 | unc fffffffe |
> ... repeated; same values even if sat. cable disconnected ...
>
> Meanwhile in dmesg:
> [43679.573136] mantis start feed & dma
> [43679.602799] stb6100_set_bandwidth: Bandwidth=47125000
> [43679.611161] stb6100_get_bandwidth: Bandwidth=10000000
> [43679.710092] stb6100_set_frequency: Frequency=1782000
> [43679.718453] stb6100_get_frequency: Frequency=0
> [43680.947291] stb6100_set_bandwidth: Bandwidth=47125000
> [43680.955653] stb6100_get_bandwidth: Bandwidth=10000000
> [43681.050093] stb6100_set_frequency: Frequency=1782000
> [43681.058454] stb6100_get_frequency: Frequency=0
> [43682.286788] stb6100_set_bandwidth: Bandwidth=47125000
> [43682.295149] stb6100_get_bandwidth: Bandwidth=10000000
> [43682.394092] stb6100_set_frequency: Frequency=1782000
> [43682.402453] stb6100_get_frequency: Frequency=0
> [43683.630788] stb6100_set_bandwidth: Bandwidth=47125000
> [43683.639150] stb6100_get_bandwidth: Bandwidth=10000000
> [43683.652591] mantis stop feed and dma
>
>
> What do you think? Is there any chance of finding a working driver?
>
> Thank you,
> David Lister
>
> _______________________________________________
> linux-dvb users mailing list
> For V4L/DVB development, please use instead linux-media@vger.kernel.org
> linux-dvb@linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
>   


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

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

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Dave Lister]

2009/4/10 Hartmut <spieluhr@ewetel.net>:
> I have the same card since 6 weeks and it works in "non HD-TV-mode" on
> opensuse 11.0. The driver is: Driver used:
> http://mercurial.intuxication.org/hg/s2-liplianin. From what you wrote I
> think the card is working. But try to scan in this way:
>
> scan-s2 -a 1 -s 0 -x 0 -t 1 /usr/share/dvb/dvb-s/Astra-19.2E >
> ~/.szap/channels1.conf
>
> This worked for me. -a 1 is the my second TV-card, you should use 0, -s 0 is
> OK, -x 0 finds only free-to-air-channels, t -1 finds only TV. You output in
> dmesg is OK, shows that the card is working.
>

It's really working? That would be great, because s2-liplianin is
S2API-based; DVB API v5 is AFAIK the future. I've only had _some_
success with the multiproto mantis driver just today, but that one is
deprecated and I'm not very happy about it. Now I can see basic DVB-S
picture, but the rest is almost unusable. I'd like to ask you for a
few details about your setup. I'd be very grateful for this info, as
it might allow me to switch to the new driver:

1) cat /proc/version
2) lspci -v -v
3) lsmod
4) dmesg (or a logfile containing your SkyStar HD2 driver msg)
5) scan-s2 (console output & dmesg logs about bandwidth/frequency get/set)
6) which revision of s2-liplianin you use? (could you .tar.gz and
upload for me?)

>From what I've seen of others' logs, mine is actually different: every
time the driver changes tuning frequency, it then calls "get" to
verify the change;  this works for everybody, but in my logs you can
see that frequency is _always_ = 0. Whatever the driver sets, the 0
doesn't change. The same goes for "bandwidth", it never changes from
the default value of 10000000. Example:

NOT OK (my S2API mantis):
stb6100_set_bandwidth: Bandwidth=51610000 <- request
stb6100_get_bandwidth: Bandwidth=10000000 <- no change
stb6100_get_bandwidth: Bandwidth=10000000
stb6100_set_frequency: Frequency=1951500 <- request
stb6100_get_frequency: Frequency=0 <- no change!

OK (my multiproto mantis):
stb6100_set_bandwidth: Bandwidth=48475000 <- request
stb6100_get_bandwidth: Bandwidth=48000000 <- changed
stb6100_set_frequency: Frequency=1925000 <- request
stb6100_get_frequency: Frequency=1925015 <- changed

Otherwise, I think you're right, I'm also confident that the driver
talks with the HW, but the crucial communication - tuning, locking,
etc. - doesn't get through. I have no idea why. Perhaps with your info
I'll be able to find the difference and port the necessary code from
multiproto to S2API. I think that's my only chance.


Best regards,
-- 
David Lister

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[VDR User]

There is a new mantis tree being uploaded at:
http://jusst.de/hg/mantis-v4l

Please try this tree.  The upload should finish within 2 hours and is
using DVB api 5 (aka s2api).

Cheers

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Dave Lister]

2009/4/11 Hartmut <spieluhr@ewetel.net>:
> I tried the multiproto-driver first and had not very good results. This
> driver is out for some month. I installed then the liplianin-driver via hg
> clone as shown at the following page:
>
> http://www.linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_(VP-1041)#Drivers
>
> That worked at once.
>
> lspci:
> 00:09.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI
> Bridge Controller [Ver 1.0] (rev 01)
>         Subsystem: Device 1ae4:0003
>         Flags: bus master, medium devsel, latency 32, IRQ 17
>         Memory at fb000000 (32-bit, prefetchable) [size=4K]
>         Kernel driver in use: Mantis
>         Kernel modules: mantis
>
> dmesg:
> mantis stop feed and dma
> stb6100_set_bandwidth: Bandwidth=51610000
> stb6100_get_bandwidth: Bandwidth=52000000
> stb6100_get_bandwidth: Bandwidth=52000000
> stb6100_set_frequency: Frequency=1944000
> stb6100_get_frequency: Frequency=1944000
> stb6100_get_bandwidth: Bandwidth=52000000
> mantis start feed & dma
>

Well, it seems we have the same exact card (HW revision), but it did
not work with liplianin in my setup. It works for you, that's why I
was asking about the components in your setup. I really need to know
your kernel version + its distrib. revision ("cat /proc/version") and
the revision of your working liplianin copy ("cd
your-liplianin-source; hg log | head").

My setup:
Linux version 2.6.26-1-686 (Debian 2.6.26-9) (waldi@debian.org)
liplianin-s2: 11145:2866ecb5e66b (Sun Mar 15 18:24:26 2009)

Be quite grateful if you could furnish me with this basic info. Don't
forget to "CC: linux-dvb@linuxtv.org" when replying to me. :)

Best regards,

-- 
David Lister

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Dave Lister]

2009/4/11 VDR User <user.vdr@gmail.com>:
> There is a new mantis tree being uploaded at:
> http://jusst.de/hg/mantis-v4l
>
> Please try this tree.  The upload should finish within 2 hours and is
> using DVB api 5 (aka s2api).
>
> Cheers
> --
> 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
>

The compilation seemed perfect, but this appeared near the middle:

CC [M]  /n/data/src/mantis-v4l/v4l/hopper_cards.o
/n/data/src/mantis-v4l/v4l/hopper_cards.c:20:24: error: mantis_pci.h:
No such file or directory
/n/data/src/mantis-v4l/v4l/hopper_cards.c: In function 'hopper_pci_probe':
/n/data/src/mantis-v4l/v4l/hopper_cards.c:154: error: implicit
declaration of function 'mantis_pci_init'
/n/data/src/mantis-v4l/v4l/hopper_cards.c:214: error: implicit
declaration of function 'mantis_pci_exit'
/n/data/src/mantis-v4l/v4l/hopper_cards.c:200: warning: label 'fail5'
defined but not used
make[3]: *** [/n/data/src/mantis-v4l/v4l/hopper_cards.o] Error 1

There was no mantis_pci.[ch]. I copied these two files from the old
http://jusst.de/hg/mantis tree. Compilation OK, but then, after a bit
I got this:

CC [M]  ./mantis-v4l/v4l/mantis_ca.o
make[3]: *** No rule to make target
`./mantis-v4l/v4l/mantis_pcmcia.o', needed by
`./mantis-v4l/v4l/tda18271.o'.  Stop.
make[2]: *** [_module_./mantis-v4l/v4l] Error 2

Again, I copied mantis_pcmcia.c from the old tree and the compilation
finished. Later when I tried updating my copy, the files were there -
somebody fixed this as I was writing this mail, so I recompiled with
new files. :)

RESULTS (using "s2" dvb-apps):
- scanning DVB-S works
- scanning DVB-S2 doesn't work
- zapping DVB-S is fast

BUT there is a big problem now; even when I have FE_HAS_LOCK,
/dev/dvb/adapter0/dvr0 is dead; trying to read dvr0 blocks as if there
was no lock! Any suggestions? I'd really like to make this work - this
driver seems the best of both worlds! :)


-- 
David Lister

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Hartmut]

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

Dave Lister schrieb:
> 2009/4/11 Hartmut <spieluhr@ewetel.net>:
>   
>> I tried the multiproto-driver first and had not very good results. This
>> driver is out for some month. I installed then the liplianin-driver via hg
>> clone as shown at the following page:
>>
>> http://www.linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_(VP-1041)#Drivers
>>
>> That worked at once.
>>
>> lspci:
>> 00:09.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI
>> Bridge Controller [Ver 1.0] (rev 01)
>>         Subsystem: Device 1ae4:0003
>>         Flags: bus master, medium devsel, latency 32, IRQ 17
>>         Memory at fb000000 (32-bit, prefetchable) [size=4K]
>>         Kernel driver in use: Mantis
>>         Kernel modules: mantis
>>
>> dmesg:
>> mantis stop feed and dma
>> stb6100_set_bandwidth: Bandwidth=51610000
>> stb6100_get_bandwidth: Bandwidth=52000000
>> stb6100_get_bandwidth: Bandwidth=52000000
>> stb6100_set_frequency: Frequency=1944000
>> stb6100_get_frequency: Frequency=1944000
>> stb6100_get_bandwidth: Bandwidth=52000000
>> mantis start feed & dma
>>
>>     
>
> Well, it seems we have the same exact card (HW revision), but it did
> not work with liplianin in my setup. It works for you, that's why I
> was asking about the components in your setup. I really need to know
> your kernel version + its distrib. revision ("cat /proc/version") and
> the revision of your working liplianin copy ("cd
> your-liplianin-source; hg log | head").
>
> My setup:
> Linux version 2.6.26-1-686 (Debian 2.6.26-9) (waldi@debian.org)
> liplianin-s2: 11145:2866ecb5e66b (Sun Mar 15 18:24:26 2009)
>
> Be quite grateful if you could furnish me with this basic info. Don't
> forget to "CC: linux-dvb@linuxtv.org" when replying to me. :)
>
> Best regards,
>
>   
hartmut@Jupiter:~> cat /proc/version
Linux version 2.6.25.20-0.1-default (geeko@buildhost) (gcc version 4.3.1
20080507 (prerelease) [gcc-4_3-branch revision 135036] (SUSE Linux) ) #1
SMP 2008-12-12 20:30:38 +0100

hartmut@Jupiter:/usr/src/s2-liplianin> hg log | head
Not trusting file /usr/src/s2-liplianin/.hg/hgrc from untrusted user
root, group root
Not trusting file /usr/src/s2-liplianin/.hg/hgrc from untrusted user
root, group root
changeset:   10883:974d10d5c462
tag:         tip
parent:      10876:982623bbc9ff
parent:      10882:c770b20d15c6
user:        Igor M. Liplianin <liplianin@me.by>
date:        Sat Feb 28 05:57:40 2009 +0200
summary:     Merge with http://linuxtv.org/hg/v4l-dvb

changeset:   10882:c770b20d15c6
user:        Mauro Carvalho Chehab <mchehab@redhat.com>
hartmut@Jupiter:/usr/src/s2-liplianin>


Hartmut


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

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

_______________________________________________
linux-dvb users mailing list
For V4L/DVB development, please use instead linux-media@vger.kernel.org
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[Dave Lister]

2009/4/11 Dave Lister <foceni@gmail.com>:
>
> RESULTS (using "s2" dvb-apps):
> - scanning DVB-S works
> - scanning DVB-S2 doesn't work
> - zapping DVB-S is fast
>
> BUT there is a big problem now; even when I have FE_HAS_LOCK,
> /dev/dvb/adapter0/dvr0 is dead; trying to read dvr0 blocks as if there
> was no lock! Any suggestions? I'd really like to make this work - this
> driver seems the best of both worlds! :)
>

My bad, didn't know -r had to be used with szap. :) Now both drivers
(mantis-v4l, liplianin-s2) seem to work fine, although when I do
something with DVB-S2, I loose signal altogether and have to reboot.
Module reload doesn't help, so I'd say the drivers botch something
inside the HW. :) Will report back as soon as I know more.

Thank you for helping me out, everybody!

-- 
David Lister

Re: [linux-dvb] SkyStar HD2 (TwinHan VP-1041/Mantis) S2API support

[VDR User]

On Sat, Apr 11, 2009 at 5:47 AM, Dave Lister <foceni@gmail.com> wrote:
> 2009/4/11 VDR User <user.vdr@gmail.com>:
>> There is a new mantis tree being uploaded at:
>> http://jusst.de/hg/mantis-v4l
>>
>> Please try this tree.  The upload should finish within 2 hours and is
>> using DVB api 5 (aka s2api).
>
> The compilation seemed perfect, but this appeared near the middle:
>
> CC [M]  /n/data/src/mantis-v4l/v4l/hopper_cards.o
> /n/data/src/mantis-v4l/v4l/hopper_cards.c:20:24: error: mantis_pci.h:
> No such file or directory
> /n/data/src/mantis-v4l/v4l/hopper_cards.c: In function 'hopper_pci_probe':
> /n/data/src/mantis-v4l/v4l/hopper_cards.c:154: error: implicit
> declaration of function 'mantis_pci_init'
> /n/data/src/mantis-v4l/v4l/hopper_cards.c:214: error: implicit
> declaration of function 'mantis_pci_exit'
> /n/data/src/mantis-v4l/v4l/hopper_cards.c:200: warning: label 'fail5'
> defined but not used
> make[3]: *** [/n/data/src/mantis-v4l/v4l/hopper_cards.o] Error 1
>
> There was no mantis_pci.[ch]. I copied these two files from the old
> http://jusst.de/hg/mantis tree. Compilation OK, but then, after a bit
> I got this:
>
> CC [M]  ./mantis-v4l/v4l/mantis_ca.o
> make[3]: *** No rule to make target
> `./mantis-v4l/v4l/mantis_pcmcia.o', needed by
> `./mantis-v4l/v4l/tda18271.o'.  Stop.
> make[2]: *** [_module_./mantis-v4l/v4l] Error 2
>
> Again, I copied mantis_pcmcia.c from the old tree and the compilation
> finished. Later when I tried updating my copy, the files were there -
> somebody fixed this as I was writing this mail, so I recompiled with
> new files. :)
>
> RESULTS (using "s2" dvb-apps):
> - scanning DVB-S works
> - scanning DVB-S2 doesn't work
> - zapping DVB-S is fast
>
> BUT there is a big problem now; even when I have FE_HAS_LOCK,
> /dev/dvb/adapter0/dvr0 is dead; trying to read dvr0 blocks as if there
> was no lock! Any suggestions? I'd really like to make this work - this
> driver seems the best of both worlds! :)

Can you please try a fresh clone of the tree?  I believe the fixes
have now been applied.  Thanks!