Can't get a signal in DVBViewer

[BluetoothBG]

First of all, I'm sorry that I'm starting with such a topic because I ordered my TBS6891 card last week, received it yesterday and I'm very, very happy with it! Thank you very much, I've been visiting this forum for a while and I'm impressed by your attitude to the customers, that is how every company should be!

But unfortunately I would have to look for some help.
After receiving the new card I installed it in my PC (PCI-e x16 v2.0), installed the drivers (2.0.0.4) and everything was working like a charm. Today when I turned on my PC I couldn't get a signal in DVB Viewer - it shows the signal strength, but no picture. DVB Dream is the same, except there is no signal at all, on any of the tuners. I decided that there is a problem with my dish setup, so I put the cable in my old SkyStar HD2 card and there was a signal and picture. Next step was to move the TBS6981 to another slot (PCI-e x1) - after doing a "Scan devices" in DVB Viewer there was a improvement - I got a picture and etc., but on the next reboot it was gone again. After that I did flash the MB BIOS with the newest one, reinstalled Windows 7 and here I am... still can't get a picture and DVB Viewer fails at scanning with red "PAT" button. On the same LNB I have a Dreambox DM500s and it shows about 13.5 dB of signal strength, so I guess it's enough.





AltDVB scan

Device manager


Please, can you give me some advice what am I doing wrong or what else can I do?

Best regards,
Ivan

[cody]

Ivan, please, make screenshot of "Settings -> Options... -> Hardware" in DVBViewer when it's not working for you too. thanks!

[BluetoothBG]

cody, here it is:


I've also tried with "Tuner A" as Preferred device and "Tuner B" as Do not use, with or without "Direct tuning", but the result is the same. Actually I think that there is a problem with software because I did another clean install of Windows 7, and at first start of DVB Viewer it worked perfectly, so I don't think there is a problem with TBS6891, more like the drivers or applications are faulty. But given the fact that no one else is complaining about this, I guess there is something wrong with my setup.
After first launch of DVB Viewer I restarted the PC and after that the problem was there again - everything seems to be fine (Device Manager, Hardware tab on DVB Viewer), but still no picture.

I decided to do some more tests with AltDVB (which has always been my favorite DVB program), downloaded the latest BDA2 drivers (v0.2.0.6) and it is the same - it shows signal strength but no lock or signal.




I'm sorry to bother you with problem like this, but do you have any idea what else can I try?

[cody]

I'm sorry to bother you with problem like this, but do you have any idea what else can I try?

no, problem it's without any doubt very strange problem and as you said - it's true no one else has such problem and it's isolated to your setup for some reason. maybe, some strange hardware fault in your TBS 6981 prevents it from initializing after reboot, but that is really very wild guess, because i've never seen or heard about such fault before. if you turn off and then on the computer again if the cards recovers and start to get signal or not? since we can't figure out anything - it's just very weird problem, maybe, wise thing to do is arrange replacing the card with brand new one to rule out hardware fault as possible reason. please, send e-mail to euro_support@tbsdtv.com where we can discuss the details about it.

[BluetoothBG]

cody, thanks for your offer, but I still don't think that there is a 100% problem with the card itself. Today I bought a new dish and I'd like to do some more tests in the next 2-3 days, because I have doubts that the signal is not enough for the TBS6981. In one of our Bulgarian DVB forums I've read that CX24117 has a higher sensitivity than other chips and maybe is little "pretentious" about LNB and signal strength (which I'm not saying as a bad thing because as far as I know DVB-S2 specifications require better signal parameters). So my thought is that while Dreambox and SkyStar HD2 can work with worse signal, TBS6981 requires better signal quality to work as it should, I need to test if that is the case here.
I'm doing all this because today I happened to have picture after 2 consecutive reboots - although there were many artifacts in picture, as I restarted DVB viewer - in every 1 of 3 times there was a problem with the image, which is very strange. I'm also going to try the card in my server with CentOS 5.5 and another mainboard, just to rule out problem with Windows setup. I'll post the results here if I happen to find what is causing my problems.

[cody]

CX24117 has a higher sensitivity than other chips and maybe is little "pretentious" about LNB and signal strength (which I'm not saying as a bad thing because as far as I know DVB-S2 specifications require better signal parameters).

it's nothing specific for CX24117, because just DVB-S2 is more affected by phase noise and other parameters of the signal and in short it has higher requirements for stable reception than DVB-S.

So my thought is that while Dreambox and SkyStar HD2 can work with worse signal, TBS6981 requires better signal quality to work as it should, I need to test if that is the case here.

this is not correct, but it depends what you mean exactly by "better signal quality". it could be your LNB local oscillator is unstable.

I'm also going to try the card in my server with CentOS 5.5 and another mainboard, just to rule out problem with Windows setup. I'll post the results here if I happen to find what is causing my problems.

testing in Linux would be very helpful to narrow down what could cause the problem and will rule out a lot of possible potential root causes for the problem. BTW, please, test in Windows too with this driver:

http://rapidshare.com/files/418279442/t ... .0.0.7.rar

which should be able to deal better with your LNB in case its local oscillator is unstable as already i mentioned.

P.S. i forgot to mention that driver version 2.0.0.7 is just for test and the package contains only *.sys files for x86 and x64 and so depends on if you respectively run 32-bit or 64-bit Windows, you have to manually copy corresponding "tbs6981.sys" file to "Windows\System32\drivers" folder replacing the old file there and reboot your computer and then after driver version 2.0.0.7 is installed and loaded do the test.

[BluetoothBG]

Hi cody,
I did some tests with the .sys file you posted (driver v2.0.0.4 and .sys file v2.0.0.7), but results are the same. I also noticed that driver on the TBS6981 page is updated, so I tried it too (driver v2.0.0.5/.sys file v2.0.0.5, after that driver v2.0.0.5/.sys file v2.0.0.7) but without success. During the tests I replaced my dish and cable with new ones, now the LNB is connected via 20 m of RG6 cable, signal is still 13.2 dB (at the Dreambox) but the weather here is pretty bad the last two days (it's rainy and there are clouds all over the horizon).
I downloaded Linux drivers but they seem to require kernel >=2.6.31 and "stock" CentOS kernel is 2.6.18 May try with Fedora but I need to free up one HDD.

Here are some screenshots after the changes of the dish and cable:
Signal status on my old SkyStar2 on another PC via the same cable TBS6891 is connected to
TS Analyzer running for 3+ hours after successful lock
TBS IP Service with lock
TBS IP Service on the next restart with no lock

Right now I've changed the PCI-e slot again and card is working fine after 3 restarts, will test again in the morning.

P.S. About my previous post - what I meant with "better signal quality" was exactly about LNB signal and phase noise - I had doubts that LNB or cable connection is not very good, that's why I changed the cable. The post in our forum was exactly about bad reception (or rather bad auto-tuning) at low environment temperatures because of bad LNB, not very suitable for DVB-S2 reception. Yet I don't think that this is my case, because when card "locks" on the signal there is no connection with the weather - two days ago it was sunny, today it's rainy and cold. I hope to be able to do some tests under Linux, at least there are better indications in dBm, lock and etc., hopefully they will provide some more info.

Best regards,
Ivan

[BluetoothBG]

There was a problem with v4l and Fedora 13, so I did some tests with Ubuntu. After reboot results are the same.

Code: Select All Code

root@dvbtest:~# uname -a
Linux dvbtest 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:24:04 UTC 2010 i686 GNU/Linux

[   17.997740] cx23885 driver version 0.0.2 loaded
[   17.997779] cx23885 0000:02:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18
[   17.997849] CORE cx23885[0]: subsystem: 6981:8888, board: TurboSight TBS 6981 [card=29,autodetected]
[   19.148856] cx23885_dvb_register() allocating 1 frontend(s)
[   19.211573] cx23885[0]: cx23885 based dvb card
[   19.440041] DVB: registering new adapter (cx23885[0])
[   19.468070] cx23885_dvb_register() allocating 1 frontend(s)
[   19.504040] cx23885[0]: cx23885 based dvb card
[   19.548037] DVB: registering new adapter (cx23885[0])
[   19.576058] cx23885_dev_checkrevision() Hardware revision = 0xa5
[   19.576066] cx23885[0]/0: found at 0000:02:00.0, rev: 4, irq: 18, latency: 0, mmio: 0xfd600000
[   19.576074] cx23885 0000:02:00.0: setting latency timer to 64
[   19.576079] IRQ 18/cx23885[0]: IRQF_DISABLED is not guaranteed on shared IRQs

# modinfo tbs6981fe
filename:       /lib/modules/2.6.32-24-generic/kernel/drivers/media/dvb/frontends/tbs6981fe.ko
license:        TurboSight Proprietary
author:         Konstantin Dimitrov <kosio.dimitrov@gmail.com>
description:    TurboSight TBS 6981 Dual DVBS/S2 frontend driver module
depends:
vermagic:       2.6.32-24-generic SMP mod_unload modversions 586
parm:           pne:Phase noise enhancements 0:Off, 1:On (default:0) (int)
parm:           esno:SNR is reported in 0:Percentage, 1:(EsNo dB)*10 (default:0) (int)
parm:           dbm:Signal is reported in 0:Percentage, 1:-1*dBm (default:0) (int)

# dmesg | grep tbs6981fe
[   19.413919] tbs6981fe: module license 'TurboSight Proprietary' taints kernel.
[  146.262530] tbs6981fe: software version is 1.92


root@dvbtest:~# cat hellas_scan.conf
S1 12524000 H 30000000 7/8 35 QPSK
root@dvbtest:~#
root@dvbtest:~# scan-s2 -a1 hellas_scan.conf
API major 5, minor 1
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning hellas_scan.conf
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S  12524000 H 30000000 7/8 35 QPSK
----------------------------------> Using DVB-S
>>> tune to: 12524:hC78M2O35S0:S0.0W:30000:
DVB-S IF freq is 1924000
WARNING: >>> tuning failed!!!
>>> tune to: 12524:hC78M2O35S0:S0.0W:30000: (tuning failed)
DVB-S IF freq is 1924000
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.
root@dvbtest:~#
root@dvbtest:~# scan-s2 -a0 hellas_scan.conf
API major 5, minor 1
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning hellas_scan.conf
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
initial transponder DVB-S  12524000 H 30000000 7/8 AUTO AUTO
----------------------------------> Using DVB-S
>>> tune to: 12524:hC78S0:S0.0W:30000:
DVB-S IF freq is 1924000
WARNING: >>> tuning failed!!!
>>> tune to: 12524:hC78S0:S0.0W:30000: (tuning failed)
DVB-S IF freq is 1924000
WARNING: >>> tuning failed!!!
ERROR: initial tuning failed
dumping lists (0 services)
Done.


root@dvbtest:~# cat channels.conf
TheVoice:12524:h:0:30000:848:849:1015
root@dvbtest:~#
root@dvbtest:~# time szap-s2 -c channels.conf -H -p -r -S 0 "TheVoice" -a0
reading channels from file 'channels.conf'
zapping to 1 'TheVoice':
delivery DVB-S, modulation QPSK
sat 0, frequency 12524 MHz H, symbolrate 30000000, coderate auto, rolloff 0.35
vpid 0x0350, apid 0x0351, sid 0x03f7
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
^C

real    1m22.636s
user    0m0.000s
sys     0m0.000s
root@dvbtest:~#
root@istamov-desktop:~# time szap-s2 -c channels.conf -H -p -r -S 0 "TheVoice" -a1
reading channels from file 'channels.conf'
zapping to 1 'TheVoice':
delivery DVB-S, modulation QPSK
sat 0, frequency 12524 MHz H, symbolrate 30000000, coderate auto, rolloff 0.35
vpid 0x0350, apid 0x0351, sid 0x03f7
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
^C

real    1m21.652s
user    0m0.000s
sys     0m0.000s


root@dvbtest:~# ls -l /lib/firmware | grep cx23885
-rw-r--r--  1 root root   16382 2010-05-26 19:10 v4l-cx23885-avcore-01.fw
-rw-r--r--  1 root root   16382 2010-05-26 19:10 v4l-cx23885-enc.fw


[BluetoothBG]

Two more restarts and it's working now:

Code: Select All Code

root@dvbtest:~# szap-s2 -c channels.conf -H -p -r -S 0 "TheVoice" -a1
reading channels from file 'channels.conf'
zapping to 1 'TheVoice':
delivery DVB-S, modulation QPSK
sat 0, frequency 12524 MHz H, symbolrate 30000000, coderate auto, rolloff 0.35
vpid 0x0350, apid 0x0351, sid 0x03f7
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
status 1f | signal  74% | snr   0% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
status 1f | signal  74% | snr 100% | ber 0 | unc 0 | FE_HAS_LOCK
^C^[[A
root@dvbtest:~# szap-s2 -c channels.conf -p -r -S 0 "TheVoice" -a1
reading channels from file 'channels.conf'
zapping to 1 'TheVoice':
delivery DVB-S, modulation QPSK
sat 0, frequency 12524 MHz H, symbolrate 30000000, coderate auto, rolloff 0.35
vpid 0x0350, apid 0x0351, sid 0x03f7
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
status 1f | signal bf47 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf47 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf49 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf47 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf49 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf49 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf48 | snr ffff | ber 00000000 | unc 00000000 | FE_HAS_LOCK


root@dvbtest:~# scan-s2 -a1 hellas_scan.conf
API major 5, minor 1
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning hellas_scan.conf
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S  12524000 H 30000000 7/8 AUTO AUTO
----------------------------------> Using DVB-S
>>> tune to: 12524:hC78S0:S0.0W:30000:
DVB-S IF freq is 1924000
>>> parse_section, section number 0 out of 0...!
service_id = 0x0
service_id = 0x3EA
pmt_pid = 0x169
service_id = 0x3EB
pmt_pid = 0x29
service_id = 0x3ED
pmt_pid = 0x269
service_id = 0x3EE
pmt_pid = 0x1A9
service_id = 0x3EF
pmt_pid = 0x69
service_id = 0x3F2
pmt_pid = 0x329
service_id = 0x3F4
pmt_pid = 0xA9
service_id = 0x3F5
pmt_pid = 0x129
service_id = 0x3F6
pmt_pid = 0x2E9
service_id = 0x3F7
pmt_pid = 0x369
service_id = 0x3F8
pmt_pid = 0x229
service_id = 0x46A
pmt_pid = 0xE9
service_id = 0x3FB
pmt_pid = 0x1FE
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0190
  AUDIO     : PID 0x0191
>>> parse_section, section number 0 out of 0...!
  VIDEO     : PID 0x0350
  AUDIO     : PID 0x0351
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x003C
  AUDIO     : PID 0x003D
  TELETEXT  : PID 0x003E
>>> parse_section, section number 0 out of 0...!
0x0001 0x03EB: pmt_pid 0x0029 BULSATCOM -- BNT 1 (running, scrambled)
0x0001 0x03EF: pmt_pid 0x0069 BULSATCOM -- bTV (running, scrambled)
0x0001 0x03F4: pmt_pid 0x00A9 BULSATCOM -- Nova TV (running, scrambled)
0x0001 0x046A: pmt_pid 0x00E9 BULSATCOM -- Diema (running, scrambled)
0x0001 0x03F5: pmt_pid 0x0129 BULSATCOM -- Diema 2 (running, scrambled)
0x0001 0x03EA: pmt_pid 0x0169 BULSATCOM -- Planeta TV (running, scrambled)
0x0001 0x03F2: pmt_pid 0x0329 BULSATCOM -- TV Plus (running, scrambled)
0x0001 0x03F8: pmt_pid 0x0229 BULSATCOM -- Discovery Channel (running, scrambled)
0x0001 0x03ED: pmt_pid 0x0269 BULSATCOM -- HBO (running, scrambled)
0x0001 0x03F6: pmt_pid 0x02E9 BULSATCOM -- Hobby TV (running, scrambled)
0x0001 0x03EE: pmt_pid 0x01A9 BULSATCOM -- TV7 (running, scrambled)
0x0001 0x03F7: pmt_pid 0x0369 BULSATCOM -- The Voice (running)
0x0001 0x03FB: pmt_pid 0x01FE BULSATCOM -- DATAs (running)
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0050
  AUDIO     : PID 0x0051
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  TELETEXT  : PID 0x0092
  VIDEO     : PID 0x0090
  AUDIO     : PID 0x0091
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x00D0
  AUDIO     : PID 0x00D1
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0110
  AUDIO     : PID 0x0111
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0150
  AUDIO     : PID 0x0151
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0310
  AUDIO     : PID 0x0311
>>> parse_section, section number 0 out of 0...!
  OTHER     : PID 0x0133 TYPE 0x0B
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0210
  AUDIO     : PID 0x0211
  AUDIO     : PID 0x0212
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x0250
  AUDIO     : PID 0x0251
>>> parse_section, section number 0 out of 0...!
  CA ID     : PID 0x0604
  CA ID     : PID 0x5501
  CA ID     : PID 0x5581
  VIDEO     : PID 0x02D0
  AUDIO     : PID 0x02D1
>>> parse_section, section number 0 out of 0...!
Network Name 'Bulsatcom'
dumping lists (13 services)
Planeta TV;BULSATCOM:12524:hC78M2S0:S39.0E:30000:336:337=bul:0:0:1002:1:1:0
BNT 1;BULSATCOM:12524:hC78M2S0:S39.0E:30000:60:61=bul:62:0:1003:1:1:0
HBO;BULSATCOM:12524:hC78M2S0:S39.0E:30000:592:593=bul:0:0:1005:1:1:0
TV7;BULSATCOM:12524:hC78M2S0:S39.0E:30000:400:401=bul:0:0:1006:1:1:0
bTV;BULSATCOM:12524:hC78M2S0:S39.0E:30000:80:81=bul:0:0:1007:1:1:0
TV Plus;BULSATCOM:12524:hC78M2S0:S39.0E:30000:784:785=bul:0:0:1010:1:1:0
Nova TV;BULSATCOM:12524:hC78M2S0:S39.0E:30000:144:145=bul:146:0:1012:1:1:0
Diema 2;BULSATCOM:12524:hC78M2S0:S39.0E:30000:272:273=bul:0:0:1013:1:1:0
Hobby TV;BULSATCOM:12524:hC78M2S0:S39.0E:30000:720:721=bul:0:0:1014:1:1:0
The Voice;BULSATCOM:12524:hC78M2S0:S39.0E:30000:848:849=bul:0:0:1015:1:1:0
Discovery Channel;BULSATCOM:12524:hC78M2S0:S39.0E:30000:528:529=bul,530=eng:0:0:1016:1:1:0
Diema;BULSATCOM:12524:hC78M2S0:S39.0E:30000:208:209=bul:0:0:1130:1:1:0
Done.


[  682.115189] cx23885 0000:02:00.0: PCI INT A disabled
[  686.126566] cx23885 driver version 0.0.2 loaded
[  686.126608] cx23885 0000:02:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[  686.126702] CORE cx23885[0]: subsystem: 6981:8888, board: TurboSight TBS 6981 [card=29,autodetected]
[  686.852169] cx23885_dvb_register() allocating 1 frontend(s)
[  686.852174] cx23885[0]: cx23885 based dvb card
[  686.852176] TBS 6981 Frontend 0 Attaching...
[  686.871095] DVB: registering new adapter (cx23885[0])
[  686.871098] DVB: registering adapter 0 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[  686.900238] TurboSight TBS6981 Dual DVB-S2 card port0 MAC=xx:xx:xx:xx:xx:xx
[  686.900242] cx23885_dvb_register() allocating 1 frontend(s)
[  686.913341] cx23885[0]: cx23885 based dvb card
[  686.913346] TBS 6981 Frontend 1 Attaching...
[  686.932266] DVB: registering new adapter (cx23885[0])
[  686.932270] DVB: registering adapter 1 frontend 0 (TurboSight TBS 6981 DVBS/S2 frontend)...
[  686.961632] TurboSight TBS6981 Dual DVB-S2 card port1 MAC=xx:xx:xx:xx:xx:xx
[  686.961638] cx23885_dev_checkrevision() Hardware revision = 0xa5
[  686.961646] cx23885[0]/0: found at 0000:02:00.0, rev: 4, irq: 16, latency: 0, mmio: 0xfd600000
[  686.961656] cx23885 0000:02:00.0: setting latency timer to 64
[  686.961662] IRQ 16/cx23885[0]: IRQF_DISABLED is not guaranteed on shared IRQs
[  696.158897] tbs6981fe: software version is 1.92

# dmesg | grep tbs6981fe
[  278.378896] tbs6981fe: software version is 1.92

# modinfo tbs6981fe
filename:       /lib/modules/2.6.32-24-generic/kernel/drivers/media/dvb/frontends/tbs6981fe.ko
license:        TurboSight Proprietary
author:         Konstantin Dimitrov <kosio.dimitrov@gmail.com>
description:    TurboSight TBS 6981 Dual DVBS/S2 frontend driver module
depends:
vermagic:       2.6.32-24-generic SMP mod_unload modversions 586
parm:           pne:Phase noise enhancements 0:Off, 1:On (default:0) (int)
parm:           esno:SNR is reported in 0:Percentage, 1:(EsNo dB)*10 (default:0) (int)
parm:           dbm:Signal is reported in 0:Percentage, 1:-1*dBm (default:0) (int)



[cody]

in very short i believe we all now can be sure what i suspect and suggested from the very beginning that it seems hardware fault in your TBS 6981 card. please, send mail to euro_support@tbsdtv.com for arranging a replacement with new board.