Dave Schile wrote:
I just tried using the modules from the kernel source 2.6.17.8 (that
is the latest stable kernel as of this writing) the dst module
couldn't even find the device.
Yes; I sometimes experience that exact problem as well, which in my case
can be fixed by a reboot (sorry, = not very nice, but that is as good as
I got it so far .....).
You may want to try again, and reboot if it cannot find the tuner.
Sorry if this does not appy to your case.
Here is dmesg after 'modprobe dst verbose=4'
################dmesg###################
bttv: driver version 0.9.16 loaded
bttv: using 8 buffers with 2080k (520 pages) each for capture
bttv: Bt8xx card found (0).
ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 201
bttv0: Bt878 (rev 17) at 0000:00:0a.0, irq: 201, latency: 32, mmio:
0xe6000000
bttv0: detected: Twinhan VisionPlus DVB [card=113], PCI subsystem ID
is 1822:0001
bttv0: using: Twinhan DST + clones [card=113,autodetected]
bttv0: gpio: en=00000000, out=00000000 in=00d500ff [init]
bttv0: using tuner=4
bttv0: add subdevice "dvb0"
bt878: AUDIO driver version 0.0.0 loaded
bt878: Bt878 AUDIO function found (0).
ACPI: PCI Interrupt 0000:00:0a.1[A] -> GSI 17 (level, low) -> IRQ 201
bt878_probe: card id=[0x11822],[ Twinhan VisionPlus DVB ] has DVB
functions.
bt878(0): Bt878 (rev 17) at 00:0a.1, irq: 201, latency: 32, memory:
0xe6001000
DVB: registering new adapter (bttv0).
dst_probe: unknown device.
frontend_init: Could not find a Twinhan DST.
dvb-bt8xx: A frontend driver was not found for device 109e/0878
subsystem 1822/0001
########################################
So, at leat I get a bit farther with the hg modules. I wish I hada
better idea of what the problem was. As I understand it, these cards
are supposed to be supported.
I notice in dmesg that the bttv module uses tuner=4. In my reading of
the Documentation I saw somewhere that tuner=4 means 'No tuner'.
Could that be the problem? Do I need to specify the tuner? And, if
so, how do I figure out what tuner I've got on this card?
Thanks much
From: Zoilo Gomez <zoilo@xxxxxxxxx>
Reply-To: zoilo@xxxxxxxxx
To: Dave Schile <daveschile@xxxxxxxxxxx>
CC: linux-dvb@xxxxxxxxxxx
Subject: Re: Please see if you can help: Twinhan VP 1025
DVB-S PCI Card
Date: Mon, 14 Aug 2006 03:27:27 +0200
MIME-Version: 1.0
Received: from smtp-vbr17.xs4all.nl ([194.109.24.37]) by
bay0-mc7-f15.bay0.hotmail.com with Microsoft SMTPSVC(6.0.3790.2444);
Sun, 13 Aug 2006 18:27:28 -0700
Received: from [192.168.192.1] (pf.xs4all.nl [80.127.68.106])by
smtp-vbr17.xs4all.nl (8.13.6/8.13.6) with ESMTP id
k7E1RRwr053766;Mon, 14 Aug 2006 03:27:27 +0200 (CEST)(envelope-from
zoilo@xxxxxxxxx)
X-Message-Info: LsUYwwHHNt3660MmjhEvYg2f34OAemlKtU9j2Z7TuGo=
User-Agent: Mozilla Thunderbird 1.0.6 (X11/20051215)
X-Accept-Language: en-us, en
References: <BAY101-F29289D8402290FE8EBEFD5C1490@xxxxxxx>
X-Virus-Scanned: by XS4ALL Virus Scanner
Return-Path: zoilo@xxxxxxxxx
X-OriginalArrivalTime: 14 Aug 2006 01:27:29.0397 (UTC)
FILETIME=[CEBD6A50:01C6BF40]
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
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
