[linux-dvb] Where to look?

To: linux-dvb@linuxtv.org
Subject: [linux-dvb] Where to look?
From: Dennis Noordsij <dennis.noordsij@wiral.com>
Date: Thu, 3 Oct 2002 23:02:24 +0300
Content-transfer-encoding: quoted-printable
Content-type: text/plain; charset="us-ascii"
Organization: Wiral Oy
Sender: linux-dvb-bounce@linuxtv.org
User-agent: KMail/1.4.3
Example of the problem:
(Hauppauge (TT-based) rev 2.1 DVB-C)

When running dvbtune, I always get the following output, except the content is 
always different, see below:

bert dvbtune # ./dvbtune -f 289850000 -s 5900 -qam 128 -i
Using DVB card "VES1820/Grundig tuner as used on the Siemens DVB-C card"
tuning DVB-C to 289850000, srate=5900000
polling....
Getting frontend event
FE_STATUS:
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Event:  Frequency: 289850388
        SymbolRate: 5900000
        FEC_inner:  9
Bit error rate: 21
Signal strength: 54484
SNR: 61423
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
<transponder type="C" freq="289850000" srate="5900000">
Nothing to read from fd_pat
<service id="17" ca="1">
<description tag="0x48" type="1" provider_name="YLE" service_name="TV1" />
</service>
<service id="33" ca="1">
<description tag="0x48" type="1" provider_name="YLE" service_name="TV2" />
</service>
<service id="81" ca="1">
<description tag="0x48" type="1" provider_name="YLE" service_name="FST" />
</service>
<service id="193" ca="1">
<description tag="0x48" type="1" provider_name="YLE" service_name="YLE24" />
</service>
<service id="209" ca="1">
<description tag="0x48" type="1" provider_name="YLE" service_name="YLE Teema" 
/>
</service>
<service id="1140" ca="1">
<description tag="0x48" type="1" provider_name="Viasat" service_name="TV1000 
1" />
</service>
<service id="275" ca="1">
<description tag="0x48" type="2" provider_name="YLE" service_name="YLEN 
KLASSINEN" />
</service>

...... etc ..... few more ......


But, when I run it again:

<service id="28645" ca="1">
<description tag="0x48" type="1" provider_name="MTV Networks" 
service_name="MTV Base" />
</service>
<service id="28649" ca="1">
<description tag="0x48" type="1" provider_name="MTV Networks" 
service_name="MTV 2" />
</service>
<service id="2" ca="1">
<description tag="0x48" type="1" provider_name="UPCtv/EuroHITS" 
service_name="UPCtv Reality" />
</service>
<service id="5" ca="1">
<description tag="0x48" type="1" provider_name="UPCtv/EuroHITS" 
service_name="UPCtv Extreme Sports" />
</service>
</transponder>



And then again:

<service id="1103" ca="1">
<descriptor tag="0x4a" data="0003000f2710804654560165020008" 
text=".......FTV.e..." />
<descriptor tag="0xa4" 
data="6c5b0000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000" 
text="l.................................................................................................................." 
/>
<descriptor tag="0xe7" 
data="004000601340e03800000300000032000000ffffffff0000000003000000030000000000000000901100888411008884110000000000050000000090110000f01100c0e71100e028120000801100030000" 
text=".......8......2.................................................................." 
/>
<descriptor tag="0x00" 
data="3a0140883c01409b7c0040883c01402f000000883c0140883c0140883c0140b83a01400f000000c83a014000000000000000001c360140000000000f0000000000002fc83a0140ce5c004001000000a5830408b83a0140ec300140c83a0140f0f10240a4f0ffbf794f0040c83a014003000000a4f0ffbf75500040030300000000000000000000ac330a00a48100000100000054360140e0380000c05713400000000000f0ffff4eca00403b76026c3b76022f34f0ffbfec" 
text="....................................................6...................................0..............yO..............uP...............3..........T6...8...W..........N....v.l.v..4...." 
/>
<descriptor tag="0x30" data="40" text="." />
<descriptor tag="0x98" 
data="01401e0c00408a450040a43c01401e0c00400e0000000e0000003b7602000e000000f4350140ec300140003401401e0c0040b4f4ffbf4c4100400000" 
text=".......E...................v.......5...0...4..........LA...." />
<descriptor tag="0xd6" 
data="14000000000000100000380a0000000000005e809b3d000000004efa7b3d00000000000000003b760240c83a01400000000000000000000004003d000000ec3001400f0000005836014034f5ffbf9b3a0040a5830408ffffffff0cf1ff" 
text="..........8...............N............v.......................0......X6..4.................." 
/>
<descriptor tag="0xbf" 
data="3a01405836014001000000000000000f0000000000000000000000000000000300000000000000000000000cf1ffbf000000000000000000000000ae6401400a00000000000000a583040858360140b83a0140000400007f454c460101010000000000000000000300030001000000f08101003400000010201200000000008b7602008b760200b0f1ffbf917700408b7602408b7602401269690d1269690d5376020053760200d0f1ffbf91770040537602405376024010" 
text="...X6.......................................................d..............X6...........ELF........................4............v...v.......w...v...v...ii..ii.Sv..Sv.......w..Sv..Sv..." 
/>
</service>
</transponder>


And again:

Nothing to read from fd_pat
<service id="65" ca="1">
<description tag="0x48" type="1" provider_name="Ruutunelonen Oy" 
service_name="Nelonen D" />
</service>
<service id="113" ca="1">
<description tag="0x48" type="1" provider_name="Swelcom Oy" 
service_name="Elokuvakanava" />
</service>
<service id="129" ca="1">
<description tag="0x48" type="1" provider_name="Canal +" service_name="Canal 
+" />
</service>
<service id="3110" ca="1">
<description tag="0x48" type="1" provider_name="Viasat" service_name="TV1000 
3" />
</service>
<service id="257" ca="1">
<description tag="0x48" type="1" provider_name="Ruutunelonen Oy" 
service_name="Nelonen Plus" />
</service>
</transponder>


All these services do exist, but on totally different muxes. Only rarely will 
dvbtune output a channel that is actually on this mux, and even then it does 
not show any actual PID's for those channels.

If I tell dvbtune to tune to a specific PID on a specific mux (which I know is 
right) it will do so just fine.

But I am using the exact same sources for dvbtune as I did when I had the card 
in another PC, and then it provided the right results always.

Basically, I am just curious what would cause this. A 
cable/interference/card/hardware related issue, or an incompatibility in 
software/driver/util/firmware, etc (or just me? :-)

I get the same results with the "old" and new (time-shifting) firmware, both 
of the NEWSTRUCT branch, whereas on the other PC the "old" firmware tuned 
fine, and the new firmware could never get a lock.

Intriguing :-)

Cheers to all,
Dennis

PS - for reference:

bert dvbtune # lsmod
Module                  Size  Used by    Not tainted
dvb-ttpci              71824   0  (unused)
ves1820                 3932   1
grundig_29504-491       3552   0
grundig_29504-401       3656   0
alps_bsrv2              3832   0
alps_bsru6              5676   0
dvb_demux              10176   1  [dvb-ttpci]
dvb-core               31916   2  [dvb-ttpci ves1820 grundig_29504-491 
grundig_29504-401 alps_bsrv2 alps_bsru6]
videodev                5696   1  [dvb-ttpci]

dmesg:

Linux video capture interface: v1.00
dvb_register_adapter: registering new adapter (Technotrend/Hauppauge PCI 
rev2.1).
saa7146_core.o: : bus:0, rev:1, mem:0xc687f000.
av7110 (0): AV7111 - firm f0240009, rtsl b0250018, vid 71010068, app 00012502
dvb_frontend_init: initialising frontend 0:0 (VES1820/Grundig tuner as used on 
the Siemens DVB-C card)...
ves1820.c: setup for tuner sp5659c
Linux video capture interface: v1.00
dvb_register_adapter: registering new adapter (Technotrend/Hauppauge PCI 
rev2.1).
saa7146_core.o: : bus:0, rev:1, mem:0xc687f000.
av7110 (0): AV7111 - firm f0240009, rtsl b0250018, vid 71010068, app 00012502
dvb_frontend_init: initialising frontend 0:0 (VES1820/Grundig tuner as used on 
the Siemens DVB-C card)...
ves1820.c: setup for tuner sp5659c

top:
 PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
 2606 root       9   0     0    0     0 SW    0.0  0.0   0:00 arm_mon
 2607 root       9   0     0    0     0 SW    0.0  0.0   0:23 kdvb-fe

/proc/pci:
  Bus  0, device  18, function  0:
    Multimedia controller: Philips Semiconductors SAA7146 (rev 1).
      IRQ 11.
      Master Capable.  Latency=32.  Min Gnt=15.Max Lat=38.
      Non-prefetchable 32 bit memory at 0xf1000000 [0xf10001ff].

bert dvbtune # uname -a
Linux bert 2.4.19 #1 Thu Oct 3 18:21:36 EEST 2002 i586 GenuineIntel

I will try the old (non-NEWSTRUCT) drivers and see what happens there.




--
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.
Prev by Date: [linux-dvb] Re: Problem with dvbtune
Next by Date: [linux-dvb] Ouch!
Previous by thread: [linux-dvb] Re: Fwd: make insmod problems on new computer
Next by thread: [linux-dvb] Ouch!
Index(es):
- Date
- Thread
Home | Main Index | Thread Index