On Thursday 25 September 2003 12:51, Martin Holst wrote: > Michael Hunold wrote: > > > I've installed dvb-kernel from today and noticed, that sometimes > > > when running ./insmod.sh load there won't be frontend0 in > > > /dev/dvb/adapter1. After several restarts (or a restart of the > > > machine) there appear frontend0 in the /dev/dvb/adapter directory. > > > > > > With the "normal" DVB-driver I've never had such effects. > > > > > > My system: > > > primary device: Hauppauge DVB-s 1.3 > > > secondary device: Hauppauge Nexus-s > > > Mandrake 9.1 with 2.4.21-0.13mdk-Kernel > > > > Perhaps something with the frontend detection is different in DVB and > > dvb-kernel. What frontends are one your cards? > > Sorrry, I've forgotten to write this: > primary device: Alps BSRV2 > secondary device: STV0299 (a Nexus-s rev. 2.1)
Yep, I can confirm this problem (single card system: DVB-S Nexus with stv0299 frontend). The problem can be easily reproduced with vdr. Unloading and reloading the driver fixes the problem. There are no error messages in syslog. > > You could try and use the "dvb-kernel" driver, but use your frontend > > driver from the DVB" tree. > > How? Simply copy the stv0299.c from dvb-driver to linux/... directory > of the dvb-kernel-driver? Simply use the compiled module (stv0299.o). I tested this and it does _not_ solve the problem. > I've read sth in the ML-archive, that the Grundig-frontend had a similar > problem. While reloading that frontend the chip/card/whatever is > powered down and so can't initialize while insmoding. > Is this behaviour in all frontends? (in the dvb-kernel-tree) Maybe! If you load dvb-core with parameter 'dvb_shutdown_timeout=0', the problem is gone! Oliver -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe linux-dvb" as subject.
