51 thoughts on “howto run a TechniSat Skystar HD2 on linux”

1. First off pleas let me say thanks!
   You have restored my faith in the Pinguine!
   I thought it would take this side of forever to get this Card (Skystar HD2 ~Twinhan VP1041 Clone), to work under either MythTV or VDR.
   Getting the Card ~recognized~ under either of those Systems wasn’t such a challenge. The problems started when you tried to use the reteched thing! But, with the info provided here notably on DVB-APPS and the Scan Patch. I was able to start to turn this card over on Mythbuntu 7.10.

   Now for the reasion I’m bothering to post this:

   to quote:

   CODE:
   sudo apt-get install mercurial

   Should probably be written as:
   CODE:
   sudo apt-get install mercurial linux-headers$(uname -r) build-essential

   I had to use that command or else the Mantis Driver would not compile. Granted there are many flavors of Linux not to mention Debian, but I can’t see anything worng with the rest of it.

   And like I said we kinda need to have (say on a clean install) the linux-headers for the current kernel now don’t we??

   Ah well I’m just happy to have my card working after all this time!
   Now I can finnaly ditch Windows, hopefully I can do the same for MythTv and pack off for the greener pastures of VDR soon…

2. hi glad that it helped you. well on a clean install of course we need the linux headers and the build essential package (on ubuntu) but i was assuming that you already have that stuff if you are gonna compile drivers ;)
   well if you have or find special patches and/or tricks for mythtv please get back at me.

3. Hi munzli,

   do I understand it correctly that you got the Skystar HD2 running with mythtv?

   I just read a forum thread about Mythbuntu 8.04 and they got the card running with scan and szap, though watching TV with mythtv was a problem.

   Do I need to patch mythtv to use the card for recording?

   Best regards,
   reeja.

4. hey
   nope this is how i got it running on a mythbuntu 8.04 witch scan and szap. i haven’t had time to try and get mythtv running, but i’ll post back as soon as i do. but from what i know is that there is a patch on the linuxtv.org site for mythtv, but like i said i need to try it myself

5. I’d be happy just to get the card to work. With kernel 2.6.25.7 and the latest mantis attempting to use sazp (or anything else) crashes the process thusly:

   [ 8152.985481] BUG: unable to handle kernel paging request at 000e7ef0
   [ 8152.985520] IP: []
   [ 8152.985547] *pde = 00000000
   [ 8152.985551] Oops: 0000 [#1] SMP
   [ 8152.985579] Modules linked in: battery container sbs sbshc ac video output ipv6 8021q iptable_filter ip_tables x_tables xfs parport_pc lp parport loop evdev mantis pcspkr lnbp21 mb86a16 stb6100 tda10021 tda10023 stb0899 stv0299 dvb_core i2c_core af_packet button iTCO_wdt iTCO_vendor_support intel_agp agpgart ext3 jbd mbcache sg sr_mod cdrom sd_mod ata_piix ata_generic sata_promise libata b44 ssb mii scsi_mod dock dm_mirror dm_snapshot dm_mod thermal processor fan fuse [last unloaded: dvbloopback]
   [ 8152.985865]
   [ 8152.985887] Pid: 9250, comm: kdvb-fe-0 Not tainted (2.6.25.7 #1)
   [ 8152.985917] EIP: 0060:[] EFLAGS: 00010206 CPU: 0
   [ 8152.985947] EIP is at 0xe7ef0
   [ 8152.985971] EAX: f54f1408 EBX: f54f1408 ECX: 00000003 EDX: 000e7ef0
   [ 8152.986002] ESI: f54f1408 EDI: f54f1800 EBP: 00000000 ESP: f77a1f84
   [ 8152.986032] DS: 007b ES: 007b FS: 00d8 GS: 0000 SS: 0068
   [ 8152.986061] Process kdvb-fe-0 (pid: 9250, ti=f77a0000 task=f7625080 task.ti=f77a0000)
   [ 8152.986094] Stack: f898914b c0422180 c0422180 f77a1f8c 00000000 f898a7d0 f7940e00 00000000
   [ 8152.986156] 00000003 f77a9e5c f77a9e54 f77a9e58 00000286 00000000 c011a400 00000000
   [ 8152.986217] fffffffc f54f1408 f898a770 00000000 c0136012 c0135fd0 00000000 00000000
   [ 8152.986278] Call Trace:
   [ 8152.986318] [] dvb_frontend_init 0x2b/0x60 [dvb_core]
   [ 8152.986364] [] dvb_frontend_thread 0x60/0x2f0 [dvb_core]
   [ 8152.986408] [] complete 0x40/0x60
   [ 8152.986442] [] dvb_frontend_thread 0x0/0x2f0 [dvb_core]
   [ 8152.986480] [] kthread 0x42/0x70
   [ 8152.986510] [] kthread 0x0/0x70
   [ 8152.986539] [] kernel_thread_helper 0x7/0x18
   [ 8152.986574] =======================
   [ 8152.986599] Code: Bad EIP value.
   [ 8152.986625] EIP: [] 0xe7ef0 SS:ESP 0068:f77a1f84
   [ 8152.986937] —[ end trace 2e0479cf340c9f02 ]—

   This is reproducable (Ubuntu 8.04)

6. that’s a kernel error that’s definitely hardware related. i haven’t tried the mantis drivers with kernel 2.6.25.7 since ubuntu 8.04 uses 2.6.24-19 atm which works without problems. what ubuntu 8.04 kernel did you try it on?

   if you’re lucky changing the pci slot could help but eip errors are caused through bad drivers or firmware. since the driver hasen’t been updated in the last 4 weeks either your card is different or it’s the 2.6.25 kernel.

   does the error occur while booting or while running szap? does the card get initialized correctly and/or is there a /dev/dvb/adapter0/dvr0?

   [edit]
   another thing is that you might have a wrong mix of video4linux and linux dvb modules loaded. try removing the kernel modules and check and see that only the modules are loaded that you actually need.
   do a
   mv /lib/modules/2.6.xx/kernel/drivers/media /tmp
depmod -a
   to remove them.

7. Seems the mantis driver only works with kernel versions below 2.6.25. I’ve got it working now with 2.6.23.12 (self-compiled).

   scan and szap work fine. I’ve even got mythtv up and running, but it had to be massaged by hand.

   When I scanned 11.914 Ghz on 19E, I couldn’t find the HD channels, unless I explicitly set the FEC (9/10) and modulation (8psk) by hand. When I looked at dtv_multiplex afterwards, it still had auto in fec and modulation, and trying to tune didn’t work. After changing dtv_multiplex with the correct values, I was able to then tune; I’m not sure if the wrong fec/modulation were the result of earlier scans, which didn’t work, and mythtv didn’t update the tables when I inserted the proper values within mythtv-setup.

   I’m still trying to get sasc-ng to work properly, as for some reason, it doesn’t, and I need this to use my SRG Viaccess card….

8. that’s strange i didn’t do any manual changes and the hd stations got scanned without problems.

   what changes or patches did you use to get your mythtv running?

   about the sasc-ng thing, i’ll be needing that too since i also need to get my srg viaccess module working, but i’m not quite sure if the CI from the SkyStar card even works!
   maybe this will help you a bit: http://omcentre.com.au/Getting-Pay-TV-to-Work-With-MythTV.102.0.html

9. To get mythtv running, you need the 0.21-fixes branch, and the patch here:

   http://svn.mythtv.org/trac/ticket/5403

   When you configure myth, add the following to the config command line:

   –extra-cflags=/path/to/mantis/linux/include –extra-cxxflags=/path/to/mantis/linux/include

   so that you get the correct headers for compilation. After that, run the setup, and it should just work.

   I dont know exactly why sasc doesn’t work, but I have had problems (with sasc specifically) before. My production mythtv system (0.22 trunk, revsion 16789, the last with qt3 support) works without problems, accessing the SRG card in my dreambox. The dvbloopback module works, as I can tune/record any FTA channel, including the test recording on Anixe HD!.

   I have another (Hauppauge Nova HD-S2) card which I never managed to get as far as this, so I’m relatively happy. Now, if only the mantis driver could be rolled into a standard kernel, and mythtv got real DVB-S2 support in the main trunk, I’d be much happier, but I’m not holding my breath (Not to diss the linux and mythtv developers, but the mantis driver uses the new DVBv3 API, which is now 5 years old, and still not standard).

10. @awf

    Which “Patch” did you use? *.patch, *.2.patch, *.3.patch, *.4.patch or *.5.patch?

    Did you also copy the frontend.h and version.h from /path/to/mantis/linux/include/linux/dvb to /usr/include/linux/dvb? Or are the –extra commands for ./config enough?

    As for the Nova I’d have thought that, that would’ve been allot simpler to get running as it’s (unless I’m way off base here), is just another TT-S3200 (Skystar HD) Clone, it should ~AFAIK~ work much the same way, but with the Multiproto Drivers, and NOT Mantis.

    But I’ll guess you already knew that.

    In anycase I’d be grateful as to any insight as to which “patch” is best.

    I’ve been using the *.5.patch myself, and I don’t get any errors as such, but I can not get mythtv to work with this patch. And Myth-Setup doen’t give me any options for the new S2 FEC’s 1/4, 1/3, 2/5, 3/5, 9/10 either.

    is there anything that I could be missing?

11. I used the “latest” patch (.5). My myth build says:

    /usr/local/bin/mythbackend –version
    Please include all output in bug reports.
    MythTV Version : 17644M
    MythTV Branch : branches/release-0-21-fixes
    Library API : 0.21.20080304-1
    Network Protocol : 40
    Options compiled in:
    linux release using_oss using_alsa using_backend using_dbox2 using_dvb using_frontend using_iptv using_ivtv using_joystick_menu using_opengl_vsync using_opengl_video using_v4l using_x11 using_xrandr using_xv using_xvmc using_xvmcw using_xvmc_vld using_bindings_perl using_bindings_python using_opengl using_ffmpeg_threads using_live

    I built mythtv (after patching) with the following conigure line:

    ./configure –enable-xvmc –enable-dvb –disable-hdhomerun –disable-firewire –enable-xvmc-opengl –enable-opengl-video –enable-opengl-vsync –enable-proc-opt –extra-cxxflags=-I/mnt/build/mantis/linux/include –extra-cflags=-I/mnt/build/mantis/linux/include

    I didn’t copy any files, the –extra flags to configure worked for me. Make sure to “make distclean” before you start….

    Unfortunately, I have been unable to get this to work with sasc-ng in any reasonably stable way, which makes the whole effort pretty much useless, since I want to watch/record stuff on HD Suisse and use my SRG card. Theres not much interesting on the FTA HD channels on the satellites I’m currently set up for (Hotbird and Astra)..

    As mentioned previously, my 0.22 trunk works flawlessly, but there is no support for DVB-S2 in the 0.22 trunk, so even the Nova card wasn’t that useful. I only hope that someday the kernel *AND* mythtv gets DVB-S2 (and DVB-C HD) support. Until then I’m “stuck” without High Definition (not so terrible, as I dont have anything reasonable yet to play the content back on!)

12. @ awf:
    If your [DVB-C] Card has support for QAM256, then you should be able to decode HD Content (e.g. h.264/MPEG4), almost out of the box. At least I was able to, using my KNC1 TV-Station (DVB-C) Card.

    From what I’ve learnd so far there is no DVB-C/C2 coming, as anything beeing broadcast @ QAM256 could be / Should be able to run both h.264 and MPEG4, this is certainly true enough with my experiences with both Mythbuntu 7.10 and sasc-ng

    So you might try (incase you forgot to do so to run the W32 Codec and libcss2 (IIRTC), from the Mythbunto Control thingy, assuming your uesing Mythbuntu that is…

13. **Edit** this is why I don’t bother with x-86-64 Versions.
    No Flash, no, Java, no Acorbat reader, and no W32 CODECS, make Mythbuntu, a whole load of no fun at all.

    So if W32 CODEC’s are indeed your problem, it would be best to consider coming back down to 32-Bit for a while…

14. I’m running my DVB-C card (Terratec 1200C) on my production system (0.22 trunk). These are all 32-bit P4 machines, BTW. It too, however, has some serious stability problems, again, which I’m not sure if they are sasc related. I dont think so, because with an “earlier” trunk version (and an earlier kernel too) I could record flawlessly. Now, recording from the DVB-C card is sort of a fishing expedition; I might be able to record, but mostly the recording just dies at point during the recording.

    This is not so terrible, since basically DVB-C around here is pretty crappy anyway, and the old dreambox works good enough….

15. thanks for the infos!

    another thing i found out is that to scan through a monoblock lnb you need the correct DiSEqC switching… do this with the scan option -s and don’t forget the first LNB would be “-s 0” and not 1!

16. @ awf
    I know you probably don’t want to hear this but, you might consider useing the older 7.10 version, I use a mixture of the Ubuntu / knopix walkthough’s from here (https://opensvn.csie.org/traccgi/sascng), and it just works!

    Your Cinergy is it the Mk3 version? I’m not so sure anymore I know there was a version of it that was 100% identical to the KNC1 ~which I have~ althogh it was rumored to have a duff Chip in it to the point were the CI add-on wouldn’t work.

    Having tried it out on the KNC1 I did try a Cinergy out as well with no luck then again I think that ~problem~ is a known one with the Mk3 Version. :(

    In anycase it should’ve been automagicly installed with the lattes 2.6.x kernels’ as is the case of my KNC1s’ DVB-C and DVB-S both with the Phillips SAA7146SH Chip. Or is there truth to the rumors that the Teratec have switched to the Mantis Chip?

    Then I could see your problem, so far as I can see it your best of getting a Card with the SAA7146 on it as it just works

17. since i’m using multilnb setup i can’t get any tv stations to work… scanning even produces a much smaller channels.conf :( still trying to figure out why

18. Well, if you are using 13E on diseqc A and 19E on diseqc B, I’m happy to send you my dtv_multiplex and channel tables; if you have them reversed you could just change the sourceids within mysql…….

19. @Michael R. Habel

    I think I have the Mk3 card; I remember back in the day it didn’t immediately work, as its pciid was completely unknown. It reports itself as:
    06:02.0 Multimedia controller: Philips Semiconductors SAA7146 (rev 01)
    Subsystem: TERRATEC Electronic GmbH Unknown device 1176

    I am actually running Ubuntu 7.10 on the production boxes, but again with my own kernels, and mecurial checkouts….

20. @ AWF
    Assuming your Card looks like this http://linuxtv.org/wiki/index.php/Image:Tt_cinergy_1200_dvb-c_pci.jpg

    Then we are tlaking about the samne Card. ‘Cause at some point in the last Year Terratec must have ditched that Rev. for the Twinhan Mantis design. The above is Hardware-wise 100% to the KNC1/Dvico Boards.

    I can’t recall where I came across the info but it seems that Terratec never released a CI Addapter (e.g. Cineview) for the 1200. As I recall the SAA7146AH on those board had some kind of defect where the CI just couldn’t ever work! Personaly I think this spans the entire Mk3 range myself as the whole reason in buying the 1200 in the first place was to test the CI out whis was NOT working on the KNC1 (DVB-C).

    I latter bought a KNC1 DVB-S (again as a test to screw with the CI, and on that Card it WORKED! I’ve since ditched the KNC1 DVB-S in favor of the Technotrend S-2300 (Full Feature), as I use VDR for my Cable and Satellite use. To be frank the Channel Management in Myth Blows Goats! (of course I’d be willing to put up with that if I could use my Skystar HD2 under MythTV).

    In anycase have you had a look here yet?
    http://linuxtv.org/wiki/index.php/TerraTec_Cinergy_1200_DVB-C
    It’s probably of no use to you, after all it would have been the first place I’d have looked myself.

    Just some thought on DVB-C and Myth:
    Do you have a Transponder list for your Cable Provider?
    My Cable provider has mixex QAM256 and QAM64 Transponders, and I have to manually enter these myself as nothing so far under Linux nor Windows (to the best of my knowledge) can auto-scan both QAM256 and QAM64 at the same time. even if it says scan QAM265/64 as an option. :(

    Are you giving to correct Frequencies in (i.e. in Hz) 113000000 Symblerate 6900000 (for 113000 and 6900 respectfully)

    That bit alone took this noob the better part of about a Month and a half (and that after another Two-and-a-half Months) screwing ’round with Ubuntu trying to compile Myth from scratch to figure that simple concept out, and find that the system was ~working~ the whole time.

    Thankfully I’ve come a bit further (although not much), since then…

21. Pingback: mythtv with mantis and DVB-S2 (TechniSat SkyStar HD2 continued…) at munzli’s blog

22. Hi munzli how are you?, I have a question for you ;).

    I had followed your description for using the Skystar HD2 on linux, I get it working (I must to change the pid in mantis_vp1041.h to #define TECHNISAT_SKYSTAR_HD2 0x0003, as my card had this one).

    As I say, all seems to be working (more and less), this is the output of szap2 (I’am at Astra 19.2):

    szap2 -r -n 975

    reading channels from file ‘/home/beth/.szap/channels.conf’
    zapping to 975 ‘TV GALICIA’:
    sat 0, frequency = 11685 MHz V, symbolrate 22000000, vpid = 0x1fff, apid = 0x1fff sid = 0x760e
    Delivery system=DVB-S
    using ‘/dev/dvb/adapter0/frontend0’ and ‘/dev/dvb/adapter0/demux0’

    do_tune: API version=3, delivery system = 0
    do_tune: Frequency = 1935000, Srate = 22000000
    do_tune: Frequency = 1935000, Srate = 22000000

    status 00 | signal 0000 | snr bf04 | ber 00000000 | unc fffffffe |
    status 1e | signal 014a | snr 0093 | ber 00000000 | unc fffffffe | FE_HAS_LOCK
    status 1e | signal 014a | snr 0091 | ber 00000000 | unc fffffffe | FE_HAS_LOCK

    And the problem becomes with the “easy part”, mplayer /dev/dvb/adapter0/dvr0 :

    mplayer /dev/dvb/adapter0/dvr0
    MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
    CPU: AMD Athlon(tm) 64 X2 Dual Core Processor 4200 (Family: 15, Model: 43, Stepping: 1)
    CPUflags: MMX: 1 MMX2: 1 3DNow: 1 3DNow2: 1 SSE: 1 SSE2: 1
    Compiled with runtime CPU detection.
    mplayer: could not connect to socket
    mplayer: No such file or directory
    Failed to open LIRC support. You will not be able to use your remote control.

    Playing /dev/dvb/adapter0/dvr0.

    And thats all I see, the graphical window don’t opens and nothings occurs, in the meantime szap2 runs and runs forever and nothing more.

    I had try totem, vlc, totem-xine, kaffeine and no luck too (I installed the need codecs (I think)) but no program can display the dvr0 file.

    Thanks for your support and best regards.

23. if you have a lock, which you do it should work!

    don’t forget that if it’s a DVB-S2 channel you need to add the option “-p” to szap2 like stated above:
    -p : add pat and pmt to TS recording (implies -r)

    maybe that also works with S channels… in my situation is wasn’t needed though

    [edit]
    and you might want to see if there’s a stream on your dvr0 device use:
    dd if=/dev/dvb/adapter0/dvr0 of=test.ts bs=1M count=10
    and then open the test.ts file if there’s data in it.

24. For strange that it seems to be, dd if=/dev/dvb/adapter0/dvr0 of=test.ts bs=1M count=10, blocks and never return, as a result the file is 0 bytes long. (using -p give the same results (ti is not a s2 channel)).

    Thats really strange because szap2 seems to work ok, so I really don’t know what is happening. The only change I made different with your explanation is the change of the pci identification number of the board, but without this change there is no /dev/dvb/adapter0/frontend0 needed for scanning channels.

    Umm, checking /var/log/messages I get:

    Aug 13 21:57:55 nemesis kernel: [ 1012.381425] newfec_to_oldfec: Unsupported FEC 9
    Aug 13 21:57:55 nemesis kernel: [ 1012.381431] dvb_frontend_ioctl: FESTATE_RETUNE: fepriv->state=2
    Aug 13 21:57:55 nemesis kernel: [ 1012.381777] mantis start feed & dma
    Aug 13 21:57:55 nemesis kernel: [ 1012.404905] stb6100_set_bandwidth: Bandwidth=51610000
    Aug 13 21:57:55 nemesis kernel: [ 1012.409086] stb6100_get_bandwidth: Bandwidth=52000000
    Aug 13 21:57:55 nemesis kernel: [ 1012.431684] stb6100_get_bandwidth: Bandwidth=52000000
    Aug 13 21:57:55 nemesis kernel: [ 1012.496104] stb6100_set_frequency: Frequency=1935000
    Aug 13 21:57:55 nemesis kernel: [ 1012.500284] stb6100_get_frequency: Frequency=1934982
    Aug 13 21:57:55 nemesis kernel: [ 1012.512264] stb6100_get_bandwidth: Bandwidth=52000000
    Aug 13 21:57:55 nemesis kernel: [ 1012.649770] mantis stop feed and dma
    Aug 13 21:57:55 nemesis kernel: [ 1012.649935] mantis start feed & dma
    Aug 13 21:57:59 nemesis kernel: [ 1016.228886] mantis stop feed and dma

    This with the -p param, without it I didn’t get the lines like mantis stop feed and dma/mantis start feed & dma. I don’t know if this can help.

    Can I tray something else?, rollback the pci id to it’s original value? (but I will not have frontend0).

    Again, thanks for your kind support, see you.

25. are you sure that your card is:
    #define TECHNISAT_SKYSTAR_HD2 0x0003instead of the normal #define TECHNISAT_SKYSTAR_HD2 0x0001??

    and is there a device /dev/dvb/adapter0/dvr0??

    somehow you aren’t getting a stream from the device eventhough you’re having a lock… don’t know an answer to that right now but i’ll keep my eyes open

26. Hi again ;)

    I don’t know if I can give your more information but here you have a bit more info:

    dmesg: (near the end)

    
[ 38.902473] found a VP-1041 PCI DSS/DVB-S/DVB-S2 device on (00:0a.0),
[ 38.902475] Mantis Rev 1 [1ae4:0003], irq: 18, latency: 32
[ 38.902477] memory: 0xf8022000, mmio: 0xf8a14000
[ 38.905165] MAC Address=[00:08:c9:e0:29:11]
[ 38.905196] mantis_alloc_buffers (0): DMA=0x37610000 cpu=0xf7610000 size=65536
[ 38.905200] mantis_alloc_buffers (0): RISC=0x1f895000 cpu=0xdf895000 size=1000
[ 38.905203] DVB: registering new adapter (Mantis dvb adapter)

    and later appears:

    [ 39.436071] stb0899_get_dev_id: Device ID=[8], Release=[2]
    [ 39.448591] stb0899_get_dev_id: Demodulator Core ID=[DMD1], Version=[1]
    [ 39.461125] stb0899_get_dev_id: FEC Core ID=[FEC1], Version=[1]
    [ 39.461127] stb0899_attach: Attaching STB0899
    [ 39.461129] mantis_frontend_init (0): found STB0899 DVB-S/DVB-S2 frontend @0x68
    [ 39.461132] stb6100_attach: Attaching STB6100
    [ 39.461485] DVB: registering frontend 0 (STB0899 Multistandard)...
    [ 39.461547] mantis_ca_init (0): Registering EN50221 device
    [ 39.495765] mantis_ca_init (0): Registered EN50221 device
    [ 39.495776] mantis_hif_init (0): Adapter(0) Initializing Mantis Host Interface

    As you can see: Mantis Rev 1 [1ae4:0003]

    This is my mantis_vp1041.h:

    #define __MANTIS_VP1041_H

    #include "dvb_frontend.h"
    #include "mantis_common.h"
    #include "stb0899_drv.h"
    #include "stb6100.h"
    #include "lnbp21.h"

    #define MANTIS_VP_1041_DVB_S2 0x0031
    //#define TECHNISAT_SKYSTAR_HD2 0x0001
    #define TECHNISAT_SKYSTAR_HD2 0x0003

    extern struct mantis_hwconfig vp1041_mantis_config;
    extern struct stb0899_config vp1041_config;
    extern struct stb6100_config vp1041_stb6100_config;

    #endif // __MANTIS_VP1041_H

    lspci -vv

    00:0a.0 Multimedia controller: Twinhan Technology Co. Ltd Mantis DTV PCI Bridge Controller [Ver 1.0] (rev 01)
    Subsystem: Unknown device 1ae4:0003
    Flags: bus master, medium devsel, latency 32, IRQ 18
    Memory at f8022000 (32-bit, prefetchable) [size=4K]

    lsmod | grep “mantis”

    mantis 43396 0
    lnbp21 3200 1 mantis
    mb86a16 21632 1 mantis
    stb6100 8836 1 mantis
    tda10021 7684 1 mantis
    tda10023 7300 1 mantis
    stb0899 36224 1 mantis
    stv0299 11528 1 mantis
    dvb_core 89340 2 mantis,stv0299
    i2c_core 24832 9 mantis,lnbp21,mb86a16,stb6100,tda10021,tda10023,stb0899,stv0299,i2c_viapro

    ls -l /dev/dvb/adapter0/

    total 0
    crw-rw---- 1 root video 212, 6 2008-08-15 10:08 ca0
    crw-rw---- 1 root video 212, 4 2008-08-15 10:08 demux0
    crw-rw---- 1 root video 212, 5 2008-08-15 10:08 dvr0
    crw-rw---- 1 root video 212, 3 2008-08-15 10:08 frontend0
    crw-rw---- 1 root video 212, 7 2008-08-15 10:08 net0

    I don’t know if this can help.

    Again thanks for your kind support, best regards.

27. Another hint:

    The only thing that I see different from you is the output of scan:

    
scanning /root/tmp/dvb-apps/util/scan/dvb-s/Astra-19.2E
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder 12551500 V 22000000 22000000
----------------------------------> Using 'STB0899 Multistandard' DVB-S
Tune to frequency 12551500
DVB-S IF freq is 1951500


    In your scan output you have “Using ‘STB0899 Multistandard’ DVB-S2” and mine “Using ‘STB0899 Multistandard’ DVB-S”, on mine there is no “2”, but I don’t know waht will this means.

    (scan produce a correct channel list and I can call szap2 without problems using this channel list)

    Again thanks.

28. the output i posted is only to show how you see if the DVB-S2 channels are getting scanned… normal DVB-S channels look the same as your output!

    anyway the channel scan isn’t the problem… because you are getting a lock on the channel when zapping… somehow your device or stream is the problem!

29. Hi again folk, take an eye on http://www.linuxtv.org/pipermail/linux-dvb/2008-August/027897.html

    I was getting data from the stream but at a low low feed rate, 3kB/s more and less, look the mails to the linux-dvb mailing lists.

    I really appreciate your comments and support.

    Thanks and kind regards.

30. A night test:

    time dd if=/dev/dvb/adapter0/dvr0 of=test_100M.ts bs=1M count=100
    100 0 records in
    100 0 records out
    104857600 bytes (105 MB) copied, 35327.8 s, 3.0 kB/s

    real 588m47.813s
    user 0m0.000s
    sys 0m1.020s

    Ooops, 10 hours for a 105 MB file, and the worst, I don’t know what I can do to see what is the content of the file, mplayer and similar doesn’t plays it.

    See you.

31. maybe
    file test_100M.ts
    will help… or look at the beginning or end of file in vi/emacs

32. Hi all!!

    Well, now I have things running more and less, thanks to the linux-dvb mailing list and the kind support of barry bouwmsa, we have found that the problem for all is the “scan” program, that have a non deterministic behavior and produce a wrong channels.conf with channels without its vid and aid fields.

    We didn’t isolated the problem, maybe the dish installation (I must make a signal & other tests, but on xp all is ok), the driver or the scan program itself, who knows.

    That’s all for the moment, now I am going for mythtv ;).

    Thanks for all and best regards.

33. I’ve tried your howto for a TechniSat SkyStar HD2 under Mythbuntu 8.10 without success. After building and installing the mantis modules and re-boot nothing shows in syslog for the mantis drivers. If I modprobe mantis the drivers appear in lsmod and in syslog. Any ideas why they don’t get picked up at boot time?

34. I’ve found that on boot lspci shows the Technisat SkyStar HD2 does not have any modules loaded, after #modprobe mantis, lspci shows module mantis in use, as it should. Question is why doesn’t module mantis get loaded on boot? I downloaded latest mantis from http://jusst.de/hg/mantis and it has the #define for 1ae4:0003.
    Note I’ve also got a Nova T 500 PCI card installed which gets detected etc but can’t see it should make any difference to the SkyStar.

35. have you checked if the modules are somewhere in your /etc/modprobe.d/ files?
    if not why don’t you just manually load the drivers in your /etc/modules file?

    maybe because you have the Nova running some modules might be loaded that shouldn’t for the skystar… if you manually modprobe are both cards up and running?

    and fyi theres a newer and better way of getting the card to run using S2API -> check this

    i haven’t tried this though…

36. Hi,

    I’ve installed S2API driver (s2-liplianin) on my MythBuntu 9.04 with Terratec Cinergy S2 PCI HD CI card. Scanning and zapping works fine, but I get sound and video distortions in MythTV. Does anyone have an idea how to fix it? If not, does CI interface works with mantis driver?

37. Hi

    I am runing mythbuntu 9.04 with Azurewav AD SP400 CI. DVB-S works fine, but i cant scan and watch DVB-S2. Can you help me?

38. Hello, my problem running a SkyStar HD2 is

    ./scan-2 -a 0 initial_tuning_data
    reports
    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
    FE_SET_PROPERTY DTV_CLEAR failed: Operation not supported
    FE_SET_PROPERTY DTV_CLEAR failed: Operation not supported
    ———————-> Using DVB-S2
    FE_SET_PROPERTY DTV_CLEAR failed: Operation not supported
    FE_SET_PROPERTY DTV_CLEAR failed: Operation not supported
    ERROR: initial tuning failed

    …
    Anybody out there to solve my problem?

    Thanks a lot

39. HI,

    I upgraded from Ubuntu 9.04 to 9.10 and now I can’t install the drivers for SkyStar HD2 anymore :-(

    Any ideas or hints?

    Ron

40. hi ron

    this post is pretty old and i recommend installing the S2API drivers! they work perfectly even with the mythtv version in the repositories (switching dvb-s and dvb-s2)

    just compile and install: http://mercurial.intuxication.org/hg/s2-liplianin/

    as far as i know the drivers are being merged so you can use the same old howto: http://linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_(VP-1041)#Mantis_driver

41. Hi Can anyone confirm having a dvbloopback lock with DVB API 5.1 with a s2 card? I’m expierencing no lock on the dvbloopback (physical works fine) with encrypted or free to air. Can’t see ‘has lock’ on the dvbloopback/virtual adapter. vdr-sc (vdr-SASC-NG) seems to have no errors at all.

    ==Below the physical adpater (0 and 1 are s2 physcal adapters)

    root@mb10:~# /root/szap-s2/szap-s2 -a 1 -c /root/astra_szap-s2.conf -p -r -S 0 “BVN”
    reading channels from file ‘/root/astra_szap-s2.conf’
    zapping to 6 ‘BVN’:
    delivery DVB-S, modulation QPSK
    sat 0, frequency 12574 MHz H, symbolrate 22000000, coderate auto, rolloff 0.35
    vpid 0x0203, apid 0x0060, sid 0x13a1
    using ‘/dev/dvb/adapter1/frontend0’ and ‘/dev/dvb/adapter1/demux0’
    status 1f | signal bf4f | snr 64b1 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    status 1f | signal bf4e | snr df91 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    status 1f | signal bf4e | snr df91 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
    status 1f | signal bf4e | snr e146 | ber 00000000 | unc 00000000 | FE_HAS_LOCK

    ==Below the virtual dvbloopback adapter (2 and 3 are virtual)

    root@mb10:~# /root/szap-s2/szap-s2 -a 3 -c /root/astra_szap-s2.conf -p -r -S 0 “BVN”
    reading channels from file ‘/root/astra_szap-s2.conf’
    zapping to 6 ‘BVN’:
    delivery DVB-S, modulation QPSK
    sat 0, frequency 12574 MHz H, symbolrate 22000000, coderate auto, rolloff 0.35
    vpid 0x0203, apid 0x0060, sid 0x13a1
    using ‘/dev/dvb/adapter3/frontend0’ and ‘/dev/dvb/adapter3/demux0’

    Greetings Djieno

42. UPDATE!

    to get this card working just normaly install mythtv and use this driver: http://www.linuxtv.org/wiki/index.php/Azurewave_AD_SP400_CI_(VP-1041)#Mantis_driver

    if compiling fails because of FiredTV just run:
    sudo make menuconfig
    and disable -> Multimedia Support -> DVB/ATSC Adapter -> Firedtv/Floppydtv

43. @Munzli: Are you satisfied with the tuning speed of the current driver state? I still think it’s rather slow compared to settop boxes.

    Here are my observations with a 1041 (same design as SS HD2):

    -Tuning time between 2-3 seconds, sometimes longer, it depends on the frequency
    -quite frequent missed locks at first try, instant lock on the same channel with the second try

    I think this driver misses some final polish to offer satisfying results.

    BTW: With Kernel 2.6.33 the mantis bridge has finally become part of the kernel.

44. Hello.
    How about the CI/CAM development?
    Is it already working or WIP marked?
    I’m buying one for a test with Irdeto CA module
    Thanks.

45. some people have noted that cam module works… i tried briefly and didn’t get it working with a viaccess card -> it doesn’t init properly. but if you have more information i’d love to hear about it

46. Hello,
    Here is what I get with newest drivers:

    [ 7.134256] Pid: 1144, comm: kdvb-ca-0:0 Not tainted 2.6.34-gentoo-r1 #2 ALiveNF6G-VSTA/To Be Filled By O.E.M.
    [ 7.134256] RIP: 0010:[] [] mantis_ca_slot_reset+0x4f/0x89 [mantis]
    [ 7.134256] RSP: 0018:ffff88007c28fe70 EFLAGS: 00010296
    [ 7.134256] RAX: ffffffff810c9166 RBX: ffff88007c39c000 RCX: 00000000696d77e2
    [ 7.134256] RDX: 00000000000000da RSI: 00000000696d77e2 RDI: 0000000000129fc4
    [ 7.134256] RBP: ffff88007c28fe80 R08: 0000000000000064 R09: 0000000000000001
    [ 7.134256] R10: ffff88007c1fbc18 R11: 0000000000014880 R12: ffff88007cbfae00
    [ 7.134256] R13: 0000000000000000 R14: 0000000000000000 R15: ffff88007b860000
    [ 7.134256] FS: 00007f92fd68f730(0000) GS:ffff880002100000(0000) knlGS:0000000000000000
    [ 7.134256] CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
    [ 7.134256] CR2: ffffffff810c9166 CR3: 000000007c054000 CR4: 00000000000006e0
    [ 7.141733] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
    [ 7.141733] DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
    [ 7.141733] Process kdvb-ca-0:0 (pid: 1144, threadinfo ffff88007c28e000, task ffff88007b860000)
    [ 7.141733] Stack:
    [ 7.141733] ffff88007ca1d840 ffff88007b059c18 ffff88007c28fee0 ffffffffa0006048
    [ 7.141733] ffff88007db8b000 0000000000000000 ffffffffa0005f27 0000000000000292
    [ 7.141733] 000000017c28fee0 ffff88007c28fef8 ffff88007b059c18 ffff88007ca1d840
    [ 7.141733] Call Trace:
    [ 7.141733] [] dvb_ca_en50221_thread+0x121/0x5a1 [dvb_core]
    [ 7.141733] [] ? dvb_ca_en50221_thread+0x0/0x5a1 [dvb_core]
    [ 7.141733] [] ? dvb_ca_en50221_thread+0x0/0x5a1 [dvb_core]
    [ 7.141733] [] kthread+0x7d/0x85
    [ 7.141733] [] kernel_thread_helper+0x4/0x10
    [ 7.141733] [] ? kthread+0x0/0x85
    [ 7.141733] [] ? kernel_thread_helper+0x0/0x10
    [ 7.141733] Code: 5d fb 0f a0 48 c7 c6 00 d5 0f a0 31 c0 e8 e3 cb 40 e1 bf ac c4 20 00 e8 04 f5 14 e1 48 8b 43 20 ba da 00 00 00 48 05 a8 00 00 00 10 bf ac c4 20 00 e8 e9 f4 14 e1 48 8b 43 20 31 d2 48 05 a8
    [ 7.141733] RIP [] mantis_ca_slot_reset+0x4f/0x89 [mantis]
    [ 7.141733] RSP
    [ 7.141733] CR2: ffffffff810c9166
    [ 7.141733] —[ end trace b227e3e78f0f9fdc ]—

    Does anyone have any idea does this mean?
    I think that CAM is not initializing…right?

47. I’ve run szap-s2 as following:(device 1 is a dvbloopback device which contains channel decrypted by sasc-ng)
    ./szap-s2 -a 1 -c hditaly.conf -r -p ‘CANAL+ SPORT HD;CYFRA +’ -H
    (szap-s2 doesn’t show signal receiving rate when -p option is given but without -p I can see receiving rate )

    then I try mplayer /dev/dvb/adapter1/dvr0
    this is mplayer output :
    MPlayer SVN-r1.0~rc3+svn20090426-4.4.3 (C) 2000-2009 MPlayer Team
    mplayer: could not connect to socket
    mplayer: No such file or directory
    Failed to open LIRC support. You will not be able to use your remote control.

    Playing /dev/dvb/adapter1/dvr0.
    TS file format detected.
    VIDEO MPEG2(pid=361) NO AUDIO! NO SUBS (yet)! PROGRAM N. 0

    sometimes it plays a little audio(with disconnection back and forth ) and no video
    what seems to be wrong?

    PS: I have h264 codec installed,ffmpeg,mad,gstreamer etc..

48. Hi, i installed ubuntu 10.04, followed instructions. when i type make, i get

    make -C /root/mantis/v4l
    make[1]: Entering directory `/root/mantis/v4l’
    perl scripts/make_config_compat.pl /lib/modules/2.6.32-25-generic-pae/build ./.myconfig ./config-compat.h
    creating symbolic links…
    Kernel build directory is /lib/modules/2.6.32-25-generic-pae/build
    make -C /lib/modules/2.6.32-25-generic-pae/build SUBDIRS=/root/mantis/v4l modules
    make[2]: Entering directory `/usr/src/linux-headers-2.6.32-25-generic-pae’
    CC [M] /root/mantis/v4l/tuner-xc2028.o
    In file included from /root/mantis/v4l/tuner-xc2028.h:10,
    from /root/mantis/v4l/tuner-xc2028.c:21:
    /root/mantis/v4l/dvb_frontend.h:52: error: field ‘fe_params’ has incomplete type
    /root/mantis/v4l/dvb_frontend.h:297: warning: ‘struct dvbfe_info’ declared inside parameter list
    /root/mantis/v4l/dvb_frontend.h:297: warning: its scope is only this definition or declaration, which is probably not what you want
    /root/mantis/v4l/dvb_frontend.h:298: warning: ‘enum dvbfe_delsys’ declared inside parameter list
    /root/mantis/v4l/dvb_frontend.h:299: warning: ‘enum dvbfe_delsys’ declared inside parameter list
    /root/mantis/v4l/dvb_frontend.h:316: error: field ‘fe_events’ has incomplete type
    /root/mantis/v4l/dvb_frontend.h:317: error: field ‘fe_params’ has incomplete type
    /root/mantis/v4l/dvb_frontend.h:354: warning: ‘enum dvbfe_fec’ declared inside parameter list
    /root/mantis/v4l/dvb_frontend.h:354: warning: ‘enum dvbfe_modulation’ declared inside parameter list
    /root/mantis/v4l/dvb_frontend.h:359: warning: ‘enum dvbfe_delsys’ declared inside parameter list
    /root/mantis/v4l/tuner-xc2028.c:49: error: ‘FIRMWARE_NAME_MAX’ undeclared here (not in a function)
    make[3]: *** [/root/mantis/v4l/tuner-xc2028.o] Error 1
    make[2]: *** [_module_/root/mantis/v4l] Error 2
    make[2]: Leaving directory `/usr/src/linux-headers-2.6.32-25-generic-pae’
    make[1]: *** [default] Error 2
    make[1]: Leaving directory `/root/mantis/v4l’
    make: *** [all] Error 2

    what can i do?

49. can i get some help to make ca0 working … i have ss hd2 + ci , but i get only this: :~$ ls /dev/dvb/adapter0/
    demux0 dvr0 frontend0 net0

    of course i plug a neotion cam via and a via 2.6 card active.

    all ok in win7

50. @vacarosie200

    like i’ve said i haven’t gotten the cam module working… haven’t tried in a couple of months either

This site uses Akismet to reduce spam. Learn how your comment data is processed.