Moderator Control Panel ]

Scan failures

Re: Scan failures

Postby cody » Thu Sep 09, 2010 7:47 pm

so, then will have to use the following command line:

./szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10750,10750,11700
cody
 
Posts: 627
Joined: Tue Apr 13, 2010 11:20 pm

Re: Scan failures

Postby jimlas53 » Fri Sep 10, 2010 1:14 am

I wound up re-installing the OS, rebuilding and installing the drivers, and I've run szap-s2.
Here are the results:

./szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10750,10750,11700
reading channels from file 'channels.conf'
zapping to 1 'HEST':
delivery DVB-S, modulation QPSK
sat 0, frequency 12060 MHz H, symbolrate 26700000, coderate auto, rolloff 0.35
vpid 0x04ba, apid 0x04b0, sid 0x000c
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
opening frontend failed: Permission denied

modinfo shows this:
modinfo tbs6981fe
filename: /lib/modules/2.6.32-25-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-25-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)

To get around the permission problem:

sudo szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10750,10750,11700
reading channels from file 'channels.conf'
zapping to 1 'HEST':
delivery DVB-S, modulation QPSK
sat 0, frequency 12060 MHz H, symbolrate 26700000, coderate auto, rolloff 0.35
vpid 0x04ba, apid 0x04b0, sid 0x000c
using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'


The program never shows any further info until I kill it with ctrl-C
jimlas53
 
Posts: 10
Joined: Tue Sep 07, 2010 8:58 am

Re: Scan failures

Postby cody » Fri Sep 10, 2010 3:13 am

the cable is connected to which LNB input? in Linux 'szap-s2' switch "-a 0" is default and that is LNB2 on the card and "-a 1" is adapter1 and that is LNB1 on the card. so, if you cable is connected to:

* LNB1:

./szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10750,10750,11700 -a 1

* LNB2:

./szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10750,10750,11700 -a 0

or you can skip "-a 0", because it's by default:

./szap-s2 -c channels.conf -p -r -S 0 "HEST" -l 10750,10750,11700

if you want to get some output from 'szap-s2' even in case there is no lock to the signal and no data stream is coming out from the card you have to remove "-r -p" switches:

./szap-s2 -c channels.conf -S 0 "HEST" -l 10750,10750,11700 -a 1

./szap-s2 -c channels.conf -S 0 "HEST" -l 10750,10750,11700 -a 0

also, please, after reboot and run 'szap-s2' for the first time provide the output from 'dmesg | grep tbs6981fe'.
cody
 
Posts: 627
Joined: Tue Apr 13, 2010 11:20 pm

Re: Scan failures

Postby jimlas53 » Fri Sep 10, 2010 5:24 am

OK, some progress!

sudo szap-s2 -c channels.conf -S 0 "HEST" -l 10750,10750,11700 -a 1
reading channels from file 'channels.conf'
zapping to 1 'HEST':
delivery DVB-S, modulation QPSK
sat 0, frequency 12060 MHz H, symbolrate 26700000, coderate auto, rolloff 0.35
vpid 0x04ba, apid 0x04b0, sid 0x000c
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
status 1f | signal bf35 | snr 0000 | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf36 | snr e81a | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf36 | snr e81a | ber 00000000 | unc 00000000 | FE_HAS_LOCK
status 1f | signal bf37 | snr e81a | ber 00000000 | unc 00000000 | FE_HAS_LOCK
^C

dmesg |grep tbs6981fe
[ 563.679371] tbs6981fe: software version is 1.92

This time I did not have to run as SU, either.
jimlas53
 
Posts: 10
Joined: Tue Sep 07, 2010 8:58 am

Re: Scan failures

Postby jimlas53 » Fri Sep 10, 2010 5:30 am

The scan-s2 results:
scan-s2 -a1 ses1-101w
API major 5, minor 1
ERROR: Cannot open rotor configuration file 'rotor.conf'.
scanning ses1-101w
using '/dev/dvb/adapter1/frontend0' and '/dev/dvb/adapter1/demux0'
initial transponder DVB-S 12060000 H 26700000 3/4 AUTO AUTO
initial transponder DVB-S2 12060000 H 26700000 3/4 AUTO AUTO
----------------------------------> Using DVB-S
>>> tune to: 12060:hC34S0:S0.0W:26700:
DVB-S IF freq is 1460000
>>> parse_section, section number 0 out of 0...!
service_id = 0x0
service_id = 0x1
pmt_pid = 0x1389

... Whole lotta stuff...

28-A E History AC3;:12060:hC34M2S0:S1.0E:26700:1860:874:0:0:28:1:101:0
29-A E Biography AC3;:12060:hC34M2S0:S1.0E:26700:1960:974:0:0:29:1:101:0
30-A E AC3;:12060:hC34M2S0:S1.0E:26700:1060:1074:0:0:30:1:101:0
ENC11_AC3;:12060:hC34M2S0:S1.0E:26700:1110:1174:0:0:31:1:101:0
ENC12_AC3;:12060:hC34M2S0:S1.0E:26700:1210:1274:0:0:32:1:101:0

So can I assume the card and drivers are now working?
jimlas53
 
Posts: 10
Joined: Tue Sep 07, 2010 8:58 am

Re: Scan failures

Postby jimlas53 » Fri Sep 10, 2010 8:08 am

Then again, after reboot, no working again.
Something is not right here...
jimlas53
 
Posts: 10
Joined: Tue Sep 07, 2010 8:58 am

Re: Scan failures

Postby cody » Fri Sep 10, 2010 3:04 pm

jimlas53 Wrote:Then again, after reboot, no working again.


what you mean by that? what exactly has happened after you rebooted and tried 'szap-s2' then?
cody
 
Posts: 627
Joined: Tue Apr 13, 2010 11:20 pm

Previous

Return to Linux

Who is online

Users browsing this forum: No registered users and 5 guests