have you checked that you're on the right PID? Do you see network typical sections when you run DVB/apps/test/test_sections on this PID?
Holger
David Vidal Rodr�guez wrote:
Holger Waechtler wrote:
Just use e.g. tzap for tuning, everything else should work as above. On the wen you also find some HOWTOs which describe how to set up a network connection over DVB.
In order to use tzap I have to generate a channel list with the scan program, isn't it? Well, I get the following output:
# dvbtune -c 0 -f 650000000 -tm 8 -qam 16 -cr 2_3 -gi 8 -bw 8 -n 16978
Using DVB card "TechnoTrend/Hauppauge DEC-2000-t Frontend"
tuning DVB-T (in United Kingdom) to 650000000 Hz
polling....
Getting frontend event
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Bit error rate: 0
Signal strength: 255
SNR: 0
FE_STATUS: FE_HAS_SIGNAL FE_HAS_LOCK FE_HAS_CARRIER FE_HAS_VITERBI FE_HAS_SYNC
Successfully opened network device, please configure the dvb interface
# scan using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
>>> tune to:
658000000:INVERSION_AUTO:BANDWIDTH_8_MHZ:FEC_2_3:FEC_NONE:QAM_16:TRANSMISSION_MODE_8K:GUARD_INTERVAL_1_8:HIERARCHY_NONE
Frontend can not do requested INVERSION_AUTO, trying INVERSION_OFF instead >>> tuning status == 0x1f!!! start filter pid 0x0000 table_id 0x00 start filter pid 0x0011 table_id 0x42 start filter pid 0x0010 table_id 0x40 filter timeout pid 0x0011 remove filter pid 0x0011 filter timeout pid 0x0000 remove filter pid 0x0000 filter timeout pid 0x0010 remove filter pid 0x0010 dumping lists (0 services) Done.
...which leads me to think that there is still something wrong there. First of all, that "658000000" number, or the "Signal strength: 255" line from the dvbtune command.
It is proven that I receive the DVB-T signal because I can watch TV with the same dec.
Let's go on:
# ifconfig dvb0_0 dvb0_0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 BROADCAST NOARP MULTICAST MTU:4096 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Base address:0x4252
# ifconfig dvb0_0 hw ether 11:12:13:14:15:16 # ifconfig dvb0_0 192.168.0.1 # ifconfig dvb0_0 promisc # ifconfig dvb0_0 dvb0_0 Link encap:Ethernet HWaddr 11:12:13:14:15:16 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0 UP BROADCAST RUNNING NOARP MULTICAST MTU:4096 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) Base address:0x4252
Neither iptraf nor tcpdump show activity of any class in dvb0_0. Luckily I don't get panics any more, or at least I can't reproduce such a situation.
I'm using (in this order) dvb-core, dvb-ttusb-dec, and dec2000_frontend.
What's going on here? Thanks! David.
-- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
