I wonder if you might be experiencing the same problem that I have been
describing over the last week.
It seems to me that hg (and in fact all snapshots after January 2006)
are broken with respect to tuning by dst: whenever I run 'dvbscan -v
<freqlist>', I get tuning value 0x00 all the time.
Have you tried to use the native drivers that come with 2.6.17.8,
instead of using the latest hg-version? For me that works a lot better:
the tuning values returned are then 0x1f, and the PMTs come up immediately.
Then again, I used a Twinhan Cab/CI 2031 card, but it is worth a try I
think.
Z.
Dave Schile wrote:
Hi list,
I've been struggling with this for awhile now and I'm in need of some
insight. The problem seems to be that the front end is unable to tune
to or monitor a signal. Here is some background info:
Card:
Twinhan 1025 VisionPlus PCI DVB-S
Kernel/Dist:
2.6.17.8, Debian testing.
I just used hg to download the latest v4l-dvb and dvb-apps from
Mercurial and everything compiled and installed fine. The drivers all
modprobe fine. I modpobe in this order:
dvb-core
bttv
dvb-bt8xx
dst
Is there anything I'm missing there?
dmesg says:
###############dmesg#####################
DVB: registering new adapter (bttv0).
dst(0) dst_get_device_id: Recognise [DST-03T]
dst(0) dst_get_device_id: Unsupported
dst(0) dst_check_mb86a15: Found a MB86A15 NIM
dst(0) dst_get_device_id: [DST-03T] has a [MB 86A15]
dst(0) dst_get_device_id: [DST-03T] has a [MB 86A15]
DST type flags : 0x2 ts204 0x4 symdiv 0x10 firmware version = 2
dst(0) dst_get_mac: MAC Address=[00:08:ca:19:d2:00]
DVB: registering frontend 0 (DST DVB-S)...
###########################################
this seems fne to me.
Now the problems...
dvbtune to the satellite Galaxy 10R at 123 degrees west., I'm in
southern California:
# dvbtune -f 11800000 -p V -s 26657
Using DVB card "DST DVB-S"
tuning DVB-S to L-Band:0, Pol:V Srate=26657000, 22kHz=off
polling....
Getting frontend event
FE_STATUS:
polling....
polling....
polling....
Just goes on and on polling...
Then I look a dvbsnoop frontend info:
# dvbsnoop -s feinfo
dvbsnoop V1.4.00 -- http://dvbsnoop.sourceforge.net/
---------------------------------------------------------
FrontEnd Info...
---------------------------------------------------------
Device: /dev/dvb/adapter0/frontend0
Basic capabilities:
Name: "DST DVB-S"
Frontend-type: QPSK (DVB-S)
Frequency (min): 950.000 MHz
Frequency (max): 2150.000 MHz
Frequency stepsiz: 1.000 MHz
Frequency tolerance: 29500
Symbol rate (min): 1.000000 MSym/s
Symbol rate (max): 45.000000 MSym/s
Symbol rate tolerance: 0 ppm
Notifier delay: 0 ms
Frontend capabilities:
auto inversion
FEC AUTO
QPSK
Current parameters:
Frequency: 0.000 MHz
Inversion: AUTO
Symbol rate: 26.657000 MSym/s
FEC: FEC AUTO
You can see that the freq is not set. An interesting note is that up
in the basic capabilities section is lists frequency(max) as 2150.00
MHz. Is that right? The Ku-band satelite frequency is listed on
lyngsat.com as being 11800 MHz. What am I missing there?
Heres an interestng error from dvbsnoop:
# dvbsnoop -pd 9 -s signal
dvbsnoop V1.4.00 -- http://dvbsnoop.sourceforge.net/
DEMUX : /dev/dvb/adapter0/demux0
DVR : /dev/dvb/adapter0/dvr0
FRONTEND: /dev/dvb/adapter0/frontend0
---------------------------------------------------------
Transponder/Frequency signal strength statistics...
Capabilities: BER: 1 SNR: 1 SIG: 1 STAT: 1 UBLK: 1
---------------------------------------------------------
Error(95): frontend ioctl: Operation not supported
cycle: 1 d_time: 0.001 s
I've searched but I can't figure out what the Error(95) is . Any ideas?
a similar message comes from dvbtune:
# dvbtune -m
FE READ_BER: : Operation not supported
FE READ UNCORRECTED BLOCKS: : Operation not supported
Signal=0, Verror=0, SNR=0dB, BlockErrors=0, ()
FE READ_BER: : Operation not supported
FE READ UNCORRECTED BLOCKS: : Operation not supported
Signal=0, Verror=0, SNR=0dB, BlockErrors=0, ()
FE READ_BER: : Operation not supported
FE READ UNCORRECTED BLOCKS: : Operation not supported
Signal=0, Verror=0, SNR=0dB, BlockErrors=0, ()
FE READ_BER: : Operation not supported
and on and on..
Finally I get this from every option of dst_test that I run. I can't
find any documentation on this app though, so I'm not sure how it's
supposed to work.
# dst_test -i
main: Error opening /dev/dvb/adapter0/ca0
This seems to be because ca0 is missing:
/dev/dvb/adapter0# ls
demux0 dvr0 frontend0 net0
I would REALLY apprecate any help or insght you might have on this.
thank you very much for your consideration.
Dave
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
