Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: CPU Usage of kdvb-fe



Am Die, 2003-06-10 um 20.39 schrieb Holger Waechtler:
> Dariush Forouher wrote:
> > Am Die, 2003-06-10 um 13.54 schrieb Holger Waechtler:
> > 
> >>Dariush Forouher wrote:
> >>
> >>>Hi,
> >>>
> >>>with the latest DVB driver package from Klaus Schmidinger the
> >>>kdvb-fe-1:0 process (Nova-S as secondary behind a DVB-S 1.3) takes
> >>>sometimes a lot of CPU usage while running VDR. Top shows a value of
> >>>30-40% on a P4-2GHz. As this is obviosly unnormal I hope somebody has a
> >>>clue what's going on here.
> >>
> >>adjust your antenna and check your cable installation. With a clean 
> >>signal the thread should need almost no CPU time.
> >>
> > 
> > I don't think that the signal is so bad that it causes this. Even while
> > hard raining there had been only few glitches while watching, if any at
> > all. Unfortunatly I have no tool installed that could show me the exact
> > signal strength values, but if you point me to one I'll try it.
> 
> try fe_mon.c from the DVB/apps/szap/ directory. It's accessing the 
> frontend device readonly, so you can run this in parallel with your main 
> DVB application.

Ok,

# ./femon -a 1 -f 0|tee nova.log

reports this:

using '/dev/dvb/adapter1/frontend0'
FE: STV0299/TSA5059/SL1935 based (SAT)
status 1f | signal b66d | snr db06 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b647 | snr d803 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal af01 | snr e04f | ber 00000200 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal af00 | snr e040 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal aef9 | snr e085 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal aefb | snr e07f | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal adc5 | snr e067 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal adc0 | snr e03d | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b03e | snr e070 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal af00 | snr e040 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal aefd | snr e079 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b03b | snr e06d | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal aef8 | snr e07c | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b03b | snr e05b | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b036 | snr e046 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal b03c | snr e091 | ber 00000000 | unc 00000000 |
FE_HAS_LOCK
status 1f | signal aef2 | snr e06a | ber 00000000 | unc 00000000 |
FE_HAS_LOCK

How can this values be interpreted?

ciao
Dariush
-- 
PGP Fingerprint: 0x886C99A1



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



Home | Main Index | Thread Index