LOCK Problems

[joolzg]

We have just bought 3 of these cards and installed them into our new "ubuntu server 11.04" servers.

installed dvblast and issued the command

sudo dvblast -a 0 -O 10000 -x text -f 11064000 -s 13000000 -F 56 -e -W -Y -U -c 11064.conf

this is for Turksat 42E, but all i get now is
debug: frontend has acquired signal
debug: frontend has acquired carrier
debug: frontend has lost carrier
debug: frontend has acquired carrier
debug: frontend has lost carrier
debug: frontend has acquired carrier
debug: frontend has lost carrier
debug: frontend has acquired carrier
debug: frontend has lost carrier
debug: frontend has acquired carrier
debug: frontend has lost carrier

we have checked the signal and it is good

any ideas what we should check

also we have to modify your makefile as it did not work out of the box on our system
Linux encoder1 2.6.38-8-generic #42-Ubuntu SMP Mon Apr 11 03:31:24 UTC 2011 x86_64 x86_64 x86_64 GNU/Linux

joolz

[steven]

Hi

do you use the latest driver
http://www.tbsdtv.com/download/common/l ... 110806.rar
and if it ok too, please write to our euro_support@tbsdtv.com he will help you .

Thanks

[tonygables]

Hi,

I am experiencing the same problem with my TBS6984. Were you able to come up with any solution?

Regards,
Tony

[richh]

Hi

I guess I "solved", betetr say yet work-around it:

Problem is bad handling of structures in frontend when S2API is called. Especialy it looks whem modulation QPSK is explicitely used it is doing something different. Till yet I did not solved if problem is realy in closed tbs6984fe.o module where we do not have debug ability or if it is part of problem in S2API or even by some stupid compilation bug in dvblast. I guess "Cody" should comment it more.

Solution for DVB-S (QPSK) on TBS6984 when using drivers tbs111118 is to modify dvblast (2.0) application to avoid sending dvbs2 structure parameters.

Modify /dvblast/dvb.c to disable usage dvbs2_cmdseq and direct him to dvbs_cmdseq

case FE_QPSK:
// if ( psz_modulation != NULL )
// {
// p = &dvbs2_cmdseq;
// p->props[MODULATION].u.data = GetModulation();
// p->props[PILOT].u.data = GetPilot();
// p->props[ROLLOFF].u.data = GetRollOff();
// }
// else
p = &dvbs_cmdseq;

p->props[INVERSION].u.data = GetInversion();
p->props[SYMBOL_RATE].u.data = i_srate;
p->props[FEC_INNER].u.data = GetFECInner(info.caps);
p->props[FREQUENCY].u.data = FrontendDoDiseqc();


Compile using
make
make install

BTW
If you are in doubts if TBS6984 realy working try to use application which is not calling S2API by FE_SET_PROPERTY but using (older?) FE_SET_FRONTEND. I found this issue solution by comparing functionality of scan from dvb-apps which is working all time. If scan is able to found channels then you can be sure TBS6984 hardware is ok.

Yet confimed on 2.6.33 + tbs111118. Can quite solid suppose it will work same on 3.1.5.

[winger]

HI! I have problem with one of four adapter (adapter4). Signal is 49%, but if I plug in this cable to the another adapter all working fine. Help.

delivery DVB-S2, modulation 8PSK
sat 3, frequency 12303 MHz V, symbolrate 26400000, coderate 2/3, rolloff 0.35
vpid 0x1fff, apid 0x1fff, sid 0x0000
using '/dev/dvb/adapter4/frontend0' and '/dev/dvb/adapter4/demux0'
status 00 | signal 49% | snr 0% | ber 0 | unc 0 |

root@user-desktop:~# dmesg |grep DVB

[ 14.261348] DVB: registering new adapter (SAA716x dvb adapter)
[ 14.610047] TurboSight TBS6984 DVB-S2 card port0 MAC=00:22:ab:90:09:98
[ 14.610050] DVB: registering adapter 2 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...
[ 14.610128] DVB: registering new adapter (SAA716x dvb adapter)
[ 14.690929] TurboSight TBS6984 DVB-S2 card port1 MAC=00:22:ab:90:09:99
[ 14.690932] DVB: registering adapter 4 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...
[ 14.691035] DVB: registering new adapter (SAA716x dvb adapter)
[ 14.774650] TurboSight TBS6984 DVB-S2 card port2 MAC=00:22:ab:90:09:9a
[ 14.774653] DVB: registering adapter 5 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...
[ 14.774765] DVB: registering new adapter (SAA716x dvb adapter)
[ 14.858582] TurboSight TBS6984 DVB-S2 card port3 MAC=00:22:ab:90:09:9b
[ 14.858585] DVB: registering adapter 6 frontend 0 (TurboSight TBS 6984 DVBS/S2 frontend)...

root@user-desktop:~# uname -a
Linux user-desktop 2.6.35-22-generic #33-Ubuntu SMP Sun Sep 19 20:34:50 UTC 2010 i686 GNU/Linux

root@user-desktop:~# lsmod | grep tbs
tbs6984fe 67487 4
saa716x_tbs_dvb 24731 0
tbs6928fe 9049 1 saa716x_tbs_dvb
tbs6922fe 11119 1 saa716x_tbs_dvb
saa716x_core 40199 72 saa716x_tbs_dvb
i2c_algo_bit 5168 2 i915,saa716x_tbs_dvb
stv090x 57309 1 saa716x_tbs_dvb
dvb_core 86902 4 saa716x_tbs_dvb,saa716x_core,stv0299,b2c2_flexcop

driver is latest 111118 !!!! help!

[smile]

Hi winger
Please put the driver update to V120216, the latest driver is V120216,not V11118. the download link http://www.tbsdtv.com/download/#tbs6984
and if the problem is still not solved ,please write to euro_support@tbsdtv.com ,he will help you.

Thanks.

[winger]

I will update my driver but the problem is still not solved (((

[SergioDanielG]

How many cards do you have? In dmesg log I see registered adapters 2, 4, 5 and 6. Wich is the fist adapter to the firs lnb connection?
Can you post the output of
# ls -R -l /dev/dvb/

Best regards.

[winger]

I have 4 cards in my PC. 3xSkyStar2 and one TBS6984

root@user-desktop:~# ls -R -l /dev/dvb/
/dev/dvb/:
total 0
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter0
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter1
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter2
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter3
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter4
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter5
drwxr-xr-x 2 root root 120 2012-03-06 07:36 adapter6

[SergioDanielG]

And can you identify which are TBS6984's adapters?
$ dvbsnoop -s feinfo -adapter 0
adapter 0 to 6 can help you to identify all adapters.
And are you sure if allways the same card identify as the same adapter? For example the first SkyStar is allways adapter0.
I question this because I have 3 cards and 4 adapters, and the adapters are enumerated depending if lnb cable is conected or not at start up.

Best regards.