TBSDTV Community Forum

Dear all,

I would like to ask for help. I already tried almost everything to make it run.
I got Ubuntu Linux installed 13.10 with kernel 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux
I compiled drivers : tbs-linux-drivers_v130927.zip
Drivers are loaded succesfully.

The issue:
If there is no CAM modul present - card is working perfectly. However as soon as I insert smartcard, the card is able to lock the signal but not able to receive any data.

Dmesg:
[ 9.793694] tbs6991se: module license 'TurboSight Proprietary: www.tbsdtv.com' taints kernel.
[ 9.793698] Disabling lock debugging due to kernel taint
[ 10.104037] Registered IR keymap rc-tbs-nec
[ 10.104165] input: saa716x IR (TurboSight TBS 6928) as /devices/pci0000:00/0000:00:03.0/0000:06:00.0/rc/rc0/input4
[ 10.104605] rc0: saa716x IR (TurboSight TBS 6928) as /devices/pci0000:00/0000:00:03.0/0000:06:00.0/rc/rc0
[ 10.104941] input: MCE IR Keyboard/Mouse (saa716x) as /devices/virtual/input/input5
[ 10.105616] rc rc0: lirc_dev: driver ir-lirc-codec (saa716x) registered at minor = 0
[ 10.105619] DVB: registering new adapter (SAA716x dvb adapter)
[ 10.345731] microcode: CPU1 sig=0x6fb, pf=0x10, revision=0x0
[ 10.348319] gpio_ich: GPIO from 206 to 255 on gpio_ich
[ 10.354828] microcode: CPU2 sig=0x6fb, pf=0x10, revision=0x0
[ 10.356436] microcode: CPU3 sig=0x6fb, pf=0x10, revision=0x0
[ 10.357073] microcode: Microcode Update Driver: v2.00 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 10.363274] kvm: disabled by bios
[ 10.368545] coretemp coretemp.0: Using relative temperature scale!
[ 10.368589] coretemp coretemp.0: Using relative temperature scale!
[ 10.368617] coretemp coretemp.0: Using relative temperature scale!
[ 10.368634] coretemp coretemp.0: Using relative temperature scale!
[ 10.476691] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input6
[ 10.576040] TurboSight TBS 6928 Frontend Attaching...
[ 10.879068] TurboSight TBS6928 DVB-S2 card MAC=00:22:ab:e0:33:56
[ 10.896247] tbsci: Initializing TBS 6928 v12 CI slot
[ 10.896684] tbsci: Adapter 0 CI slot initialized
[ 10.896688] DVB: registering adapter 0 frontend 0 (TurboSight TBS 6928 DVBS/S2 frontend)...
[ 867.834687] tbsci: Adapter 0 CI slot enabled
[ 867.834690] dvb_ca adapter 0: DVB CAM detected and initialised successfully

Can someone help me to make it working?

I also tried IRDETO CI+ and two different CONAX CI SMiT modules (chipset pairing) - no success at all

Is the kernel > 3.0 an issue? or

Thanks a lot
Lukas

I just want to add, that I already tried several HW(different motherboards) and also several version of UBUNTU(from 10.04LTS to the newest one) kernel from 2.6.xx to 3.11
Using kernel 2.6.xx I'm able to lock the signal from AMOS 4W sat transponders and also use tools like dvbsnoop, however for transponders from 1W (intelsat) I;m able to lock signal but dvbsnoop, dvbtraffic are not working at all (only in case that szap-s2 is running in background(not just lock the signal with -x parameters)).

So basically I would like to
- lock the signal with szap-s2 with -x -r parameter
- run dvbsnoop, parse the output
- make screenshots of each service
- in a loop for each transponder i want to monitor

Issues:
CAMs not working - unable to descramble channel (after plug it in - there is no output from card) - CONAX SMiT (chipset paring) and others like IRDETO
After lock the signal, no output from dvbsnoop or dvbtraffic (regarding 1W satellite transponders)

Can anyone help me please?
Any idea is really welcome
Thanks
Lukas

I dont use szap-s2 or any other tools really, just my own Ive written. But looking at the wiki it says -x is exit after tuning, why would you want that for what your doing ? looks like just -r is what you want.

my app tune-s2 will tune a transponder and then wait for you to exit, thats actually all it does. You could try that.

UDL

Thanks for reply, I will try.

Let me ask additional question:
I was thinking that if I run szap-s2 to tune to exact channel with parameter -x (lock and stop) that card will stay locked to that transponder (for 1W (amos) transponders it works that way, not for 1W Intelsat). Does it basically mean that it's necessary to run szap-s2 in background during the watch of TV channel, or working with dvbtraffic or dvbsnoop?

Thanks for response

Ciao
Lukas

Im not sure as I dont use szap-s2, but the -h states "tune and exit" not "tune and wait out" so I dont know.

tune-s2 defn just tunes then waits so that you can use dvbsnoop/dvbtraffic on the mux. Thats exactly the reason I wrote the app.

UDL