Nico Sabbi schrieb:
Il Tuesday 04 December 2007 08:10:26 Iilluzion Shadow ha scritto:
Hi there!
I appreciated for good staff you develop.
The question is:
is it a bug or feature that to be able to have dvbnet device
operational to be able to get traffic i need to have frontend
device to be held open by a user process?
env:
dvb card: TT-budget S-1401
budget module from kernel 2.6.22
linuxtv-dvb-apps-1.1.1
OK. some examples.
successful example 1
1. szap -n 1 - successfully locks a signal and continually
monitors signal strength
1.2 meanwhile [kdvb-fe-0] is being hold open
2. dvbnet - successfully makes a dvb0_0 device
3. ifconfig - successfully initializes dvb device
4. tcpdump - gives traffic
unsuccessful example 2
1. szap -n 1 -x - lock a signal and stops
2,3. dvbnet and ifconfig - make dvb0_0
4. tcpdump - shows NO traffic
reason: [kdvb-fe-0] is not being hold open
workaround: keep szap going placing it into background with &.
szap -n 1 > /dev/null 2>&1 &
so it seems i have to keep [kdvb-fe-0] making szap running
if you want to keep the frontend open load dvb_core with the parameter
dvb_shutdown_timeout=0
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
Is this module parameter still working in later releases ( e.g. current
CVS version ) ? It seems it is not. The parameter ist still defined but
not used anymore.
|
_______________________________________________
linux-dvb mailing list
linux-dvb@xxxxxxxxxxx
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
