tuning failed [Solved]

[taylord1984]

Hi.
I seem to be having a problem with this card. Installed it in my media/server pc with the latest drivers(v1204050) with out any compiling problems what so ever. I just cant seem to scan, it keeps saying tuning failed when I use

Code: Select All Code

scan-s2 -a 0  /usr/share/dvb/dvb-s/Astra-28.2E

or

Code: Select All Code

scan -a 0  /usr/share/dvb/dvb-s/Astra-28.2E

and in the kern.log it says
Apr 12 20:11:00 MediaBorg kernel: [174439.018198] TurboSight TBS 6981 Frontend:
Apr 12 20:11:00 MediaBorg kernel: [174439.018202] tbs6981fe - modulation 6 is not supported

I just don't get what I am doing wrong. I am using Ubuntu 11.10 fully updated with 3.0.0-17-generic-pae i686 kernel. I am pointing at Astra-28.2E as my free to air sat box on the tv works fine. Drivers load fine from what I can tell
dale@MediaBorg:~$ dmesg | grep cx23885
[ 16.560640] cx23885 driver version 0.0.3 loaded
[ 16.560714] cx23885 0000:0b:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 16.561665] CORE cx23885[0]: subsystem: 6981:8888, board: TurboSight TBS 6981 [card=33,autodetected]
[ 17.310450] cx25840 2-0044: cx23885 A/V decoder found @ 0x88 (cx23885[0])
[ 17.974596] cx25840 2-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382 bytes)
[ 17.982437] cx23885_dvb_register() allocating 1 frontend(s)
[ 17.982448] cx23885[0]: cx23885 based dvb card
[ 19.065625] DVB: registering new adapter (cx23885[0])
[ 19.094266] cx23885_dvb_register() allocating 1 frontend(s)
[ 19.094679] cx23885[0]: cx23885 based dvb card
[ 19.240095] DVB: registering new adapter (cx23885[0])
[ 19.268977] cx23885_dev_checkrevision() Hardware revision = 0xa5
[ 19.268991] cx23885[0]/0: found at 0000:0b:00.0, rev: 4, irq: 17, latency: 0, mmio: 0xfbe00000
[ 19.269008] cx23885 0000:0b:00.0: setting latency timer to 64
[ 19.328322] input: cx23885 IR (TurboSight TBS 6981) as /devices/pci0000:00/0000:00:1c.0/0000:05:00.0/0000:06:05.0/0000:0b:00.0/rc/rc0/input6
[ 19.332485] rc0: cx23885 IR (TurboSight TBS 6981) as /devices/pci0000:00/0000:00:1c.0/0000:05:00.0/0000:06:05.0/0000:0b:00.0/rc/rc0
[ 19.333407] input: MCE IR Keyboard/Mouse (cx23885) as /devices/virtual/input/input7
[ 19.333726] rc rc0: lirc_dev: driver ir-lirc-codec (cx23885) registered at minor = 0

Edit: to add my card is getting 12V supply to it.
just trying to cover every thing lol

[SergioDanielG]

Cna you try re-compiling szap and scan? Use file included in linux drivers from tbs.

Best regards.

[taylord1984]

Cheers for the reply but still no luck

[cody]

Hi, section III.4 of the supplied README_TBS6981 file can give you an answer. so, when you see error message like the one you get:

tbs6981fe - modulation 6 is not supported

or something "is not supported" that means for sure your application software configuration is wrong and sends to the driver some request that is wrong. so, in your particular case you use "/usr/share/dvb/dvb-s/Astra-28.2E", which i guess either is using the old syntax (from the DVB-S only times) or if it's configured according to the format explained in ection III.4 of README_TBS6981 file then the last parameter on the configuration line is set to AUTO, e.g. it's not:

S1 11778000 V 27500000 3/4 35 QPSK
S2 11362000 H 22000000 2/3 35 8PSK

but wrongly it's:

S1 11778000 V 27500000 3/4 35 AUTO
S2 11362000 H 22000000 2/3 35 AUTO

so, i hope that information will help you to get started using your 6981 card in Linux.

[taylord1984]

Hi, section III.4 of the supplied README_TBS6981 file can give you an answer. so, when you see error message like the one you get:

tbs6981fe - modulation 6 is not supported

or something "is not supported" that means for sure your application software configuration is wrong and sends to the driver some request that is wrong. so, in your particular case you use "/usr/share/dvb/dvb-s/Astra-28.2E", which i guess either is using the old syntax (from the DVB-S only times) or if it's configured according to the format explained in ection III.4 of README_TBS6981 file then the last parameter on the configuration line is set to AUTO, e.g. it's not:

S1 11778000 V 27500000 3/4 35 QPSK
S2 11362000 H 22000000 2/3 35 8PSK

but wrongly it's:

S1 11778000 V 27500000 3/4 35 AUTO
S2 11362000 H 22000000 2/3 35 AUTO

so, i hope that information will help you to get started using your 6981 card in Linux.

I Have tried setting it up so it don't say auto to and still I get the same out put. All mythtv don't work to. Its starting to drive me up the wall .

S1 10714000 H 22000000 5/6 35 QPSK
S2 10847000 V 23000000 8/9 35 QPSK
Is that the way to set it up?

[cody]

I Have tried setting it up so it don't say auto to and still I get the same out put. All mythtv don't work to. Its starting to drive me up the wall .

S1 10714000 H 22000000 5/6 35 QPSK
S2 10847000 V 23000000 8/9 35 QPSK
Is that the way to set it up?

yes, those 2 lines seem correct to me. so, you're saying that 'scan-s2' using configuration file, which contains the above 2 lines still generates "modulation 6 is not supported" error message in your 'dmesg' output, correct? it's just highly unlikely, but let's double check with 'szap-s2'. so, you can create manually configuration file for 'szap-s2' with few channels from the above frequencies like it's explained in section II.4 of the README_TBS6981, for example:

CH4:10714:h:0:22000:2315:2316:9211
BBC:10847:v:0:22000:5500:5501:6940

and then try to lock them with:

# szap-s2 -a 0 -c chan.conf -S 0 "CH4"
or
# szap-s2 -a 1 -c chan.conf -S 0 "CH4"

# szap-s2 -a 0-c chan.conf -S 1 "BBC"
or
# szap-s2 -a 2-c chan.conf -S 1 "BBC"

do you get lock? are there any error messages reported to 'dmesg' output?

[cody]

BBC:10847:v:0:22000:5500:5501:6940

sorry, i made a type - it should be:

BBC:10847:v:0:23000:5500:5501:6940

[taylord1984]

I Have tried setting it up so it don't say auto to and still I get the same out put. All mythtv don't work to. Its starting to drive me up the wall .

S1 10714000 H 22000000 5/6 35 QPSK
S2 10847000 V 23000000 8/9 35 QPSK
Is that the way to set it up?

yes, those 2 lines seem correct to me. so, you're saying that 'scan-s2' using configuration file, which contains the above 2 lines still generates "modulation 6 is not supported" error message in your 'dmesg' output, correct? it's just highly unlikely, but let's double check with 'szap-s2'. so, you can create manually configuration file for 'szap-s2' with few channels from the above frequencies like it's explained in section II.4 of the README_TBS6981, for example:

CH4:10714:h:0:22000:2315:2316:9211
BBC:10847:v:0:22000:5500:5501:6940

and then try to lock them with:

# szap-s2 -a 0 -c chan.conf -S 0 "CH4"
or
# szap-s2 -a 1 -c chan.conf -S 0 "CH4"

# szap-s2 -a 0-c chan.conf -S 1 "BBC"
or
# szap-s2 -a 2-c chan.conf -S 1 "BBC"

do you get lock? are there any error messages reported to 'dmesg' output?

dmesg after my own scan from my last post don't log any thing.

# szap-s2 -a 0 -c chan.conf -S 0 "CH4"
status 01 | signal 7f46 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 7f46 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 7f46 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 7f47 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 7f47 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 7f47 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 7f48 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 7f48 | snr 0000 | ber 00000000 | unc 00000000 |
status 03 | signal 7f48 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 7f47 | snr 0000 | ber 00000000 | unc 00000000 |
status 01 | signal 7f48 | snr 0000 | ber 00000000 | unc 00000000 |
it just keeps going is that right??

szap-s2 -a 1 -c chan.conf -S 0 "CH4"
status 1f | signal bf91 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf91 | snr da73 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf91 | snr da73 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf91 | snr da73 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf91 | snr da73 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf91 | snr da73 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf92 | snr da73 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
It locked yes

so scanned with
scan-s2 -a 1 Astra-28.2E
and it worked i still don't get it tho. got it plunged into lnb1 so thought that would be 0 and 1=2.

So Need to know how I run this using only 1 lnb on both tuners?
BTW thanks for your help

[cody]

so, in Linux tuners are numbered in the following way : the one closest to the motherboard when the TBS board is inserted is '0', the one above '0' is '1' and so on - that is done in that way by request of many of our Linux users, because that makes if the board is installed in 'horizontal'-type of computer case then the most up tuner is the highest number, which makes sense. in short for 6981 that means TunerB is '0' and TunerA is '1' in Linux. that should explain it.

so, for the other question - in very short you need Dual LNB.

[taylord1984]

Ahh ok thanks. I'm all new to satellite TV so will look into unicabble as I don't wont any more wires coming throw the wall. should of researched it better. Been a nightmare setting up the dish and as you know the card lol
Again thanks for your time.