[linux-dvb] Re: Hauppauge Nova-T and dual Athlon MP

[Holger Waechtler <holger@convergence.de>]

Atish Nazir wrote:
> Thanks Justin & Gavin
> 
> -->
> 
>> yes. dvbstream has a -o option that sends to standard out, so you can 
>> pipe
>> it into mplayer for example.
> 
> <--
>     Dave Chapman (the author of dvbstream) kindly directed me to the CVS 
> repository of dvbstream and that compiles nicely against the latest 
> drivers.
> 
>     Still having problemas.  Trying for BBC1 (was hoping to crontab a 
> pipe to a file for weekdays at 17:34):
> 
> 
> BBC-1:554000000:INVERSION_OFF:BANDWIDTH_8_MHZ:FEC_2_3:FEC_NONE:QAM_64:TRANSMISSION_MODE_2K:GUARD_INTERVAL_1_32:HIERARCHY_NONE:600:601 
> 
> 
> hashaday@necromancer:~$ tzap  BBC-1
> using '/dev/dvb/adapter0/frontend0' and '/dev/dvb/adapter0/demux0'
> tuning to 554000000 Hz
> status 01 | signal 2020 | snr 0000 | ber 0000ffff | unc 00000000 |
> status 01 | signal 3131 | snr 0000 | ber 0000ffff | unc 00000000 |
> 
> 
> should I be worrying about that signal strength -- my roof aerial feed 
> is coming via booster in the attic, maybe it's acting as a bandpass?

check your antenna installation.



> hashaday@necromancer:/usr/src/dvb/dvbstream$ ./dvbstream 600 601 -o
> dvbstream v0.4pre3 - (C) Dave Chapman 2001
> Released under the GPL.
> Latest version available from http://www.linuxstb.org/
> Output to stdout
> Streaming 2 streams
> 
> 
> I really had my fingers crossed for a load of gibberish and a corrupted 
> console :o\  No hay nada :o(
> 
> 
> What I found more worrying is that none the obvious modules were being 
> used (I simply used "make insmod"):
> 
> root@necromancer:/usr/src/dvb/DVB/driver# lsmod
> Module                  Size  Used by    Tainted: P
> dvb-ttpci              74816   0  (unused)
> evdev                   4224   0  (unused)
> input                   3552   0  [dvb-ttpci evdev]
> ves1820                 3776   0
> grundig_29504-491       3296   0
> grundig_29504-401       3424   1
> alps_bsrv2              3488   0
> alps_bsru6              5312   0
> dvb-core               45636   6  [dvb-ttpci ves1820 grundig_29504-491 
> grundig_29504-401 alps_bsrv2 alps_bsru6]
> tuner                   8804   1  (autoclean)
> tvaudio                11424   0  (autoclean) (unused)
> bttv                   70624   0
> i2c-algo-bit            7180   1  [bttv]
> i2c-core               13216   0  [tuner tvaudio bttv i2c-algo-bit]
> NVdriver              988864  10
> rio500                  4128   0  (unused)

They are only marked as 'used' when you open an associated device. The 
dvb-ttpci module registers only a videodevice, when you don't open this 
it won't increase it's use count. The demux, frontend and dvr devices 
are provided by dvb-core. grundig_29504-401 has a use count of 1 because 
dvb_i2c keeps some pointer references into this driver.


>> dont worry, its not much time. My machine has been recording for a few 
>> days
>> running now and kdvb-fe has used 35:48 min of cpu time, as against 
>> 191:17 m
>> for the program to read the transport stream, 185:20m for the buffer, and
>> 2688:21 m for the tcp server. Since Thursday or so. (I have now
>> recorded 187GB of the all the BBC channels to exercise my disks). SO the
>> kernel process is not very significant
> 
> <--
>     Still, I'm rather scared of the fact that it's using almost 40% of 
> one of my Athlons!
> 
>   PID USER     PRI  NI  SIZE  RSS SHARE STAT %CPU %MEM   TIME COMMAND
>   523 root      16   0     0    0     0 SW   39.4  0.0  92:46 kdvb-fe

Like mentioned before, this is only the case when the signal is bad. 
Check your antenna installation.

Anyway, the frontend thread should only take idle time. Check this by 
giving some load on your box and check if the CPU usage of kdvb-fe goes 
down.

Holger



-- 
Info:
To unsubscribe send a mail to listar@linuxtv.org with "unsubscribe linux-dvb" as subject.