From: "Stefan-W. Hahn" info@s-hahn.de
Did you also update the driver/kernel? Is it a Nova SE with s5h1420 Frontend? check with dmesg if both cards are initialized
There is a bug in the driver which was fixed a few days ago (still not in the man v4l-dvb hg): http://linuxtv.org/hg/~pb/v4l-dvb/rev/cd7eae82baf9 http://linuxtv.org/hg/~pb/v4l-dvb/rev/84530ecadf89
Also sprach Martin Dauskardt am Tue, 16 Sep 2008 at 15:12:10 +0200:
Hallo,
Are there any hints how to solve this problem?
Did you also update the driver/kernel?
No.
When changing the vdr software I didn't change the dvb driver. I'm using a 2.6.24 (commit 49914084e79) kernel.
Is it a Nova SE with s5h1420 Frontend? check with dmesg if both cards are initialized
It's a Nova CI.
Linux video capture interface: v2.00 saa7146: register extension 'dvb'. ACPI: PCI Interrupt 0000:00:08.0[A] -> GSI 16 (level, low) -> IRQ 20 saa7146: found saa7146 @ mem de8c0000 (revision 1, irq 20) (0x13c2,0x0003). DVB: registering new adapter (Technotrend/Hauppauge WinTV Nexus-S rev2.X) adapter has MAC addr = 00:d0:5c:20:30:52 dvb-ttpci: gpioirq unknown type=0 len=0 dvb-ttpci: info @ card 0: firm f0240009, rtsl b0250018, vid 71010068, app 80002622 dvb-ttpci: firmware @ card 0 supports CI link layer interface dvb-ttpci: adac type set to 0 @ card 0 saa7146_vv: saa7146 (0): registered device video0 [v4l2] saa7146_vv: saa7146 (0): registered device vbi0 [v4l2] DVB: registering frontend 0 (ST STV0299 DVB-S)... input: DVB on-card IR receiver as /class/input/input9 dvb-ttpci: found av7110-0. saa7146: register extension 'budget_ci dvb'. ACPI: PCI Interrupt 0000:00:09.0[A] -> GSI 17 (level, low) -> IRQ 19 saa7146: found saa7146 @ mem de94e000 (revision 1, irq 19) (0x13c2,0x100f). saa7146 (1): dma buffer size 192512 DVB: registering new adapter (TT-Budget/WinTV-NOVA-CI PCI) adapter has MAC addr = 00:d0:5c:21:fd:e0 input: Budget-CI dvb ir receiver saa7146 (1) as /class/input/input10 budget_ci: CI interface initialised DVB: registering frontend 1 (ST STV0299 DVB-S)...
If my described problem is a problem of the dvb driver, then the question is, what has been changed in vdr to display this faulty behaviour?
Stefan