Re: [vdr] VDR logs and logwatch
Hi Kartsa, please find attached the files. They go into /etc/logwatch on a Debian system. Please let me know if you have improvements, comments, bugfixes... Best regards, Reiner. On 14.11.2011 08:02, Kartsa wrote: Yes please :) Probably I will be able to develop it the way it is suitable for my needs :) \\Kartsa -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Reiner Buehl Sent: 14. marraskuuta 2011 0:20 To: vdr@linuxtv.org Subject: Re: [vdr] VDR logs and logwatch I have created a first draft version of logwatch scripts for vdr.log. If you want, I can send them to you. I am still extending it. Best regards, Reiner. On 13.11.2011 22:25, Kartsa wrote: Hi Has anyone built a script for logwatch to get VDR messages from the logs? I am not familiar with perl which is mostly used with logwatch scripts. I assume it is possible to use any other language as well but thought that I would ask here if anyone has already a solution :) \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr logwatch_vdr.tar.gz Description: GNU Zip compressed data ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
Re: [vdr] VDR logs and logwatch
Thanx Reiner As soon as I have the time I will take a look at this. And yes as soon as I have time to get to know perl I may even have some comments :) Thanx again. \\Kartsa On 14.11.2011 21:35, Reiner Buehl wrote: Hi Kartsa, please find attached the files. They go into /etc/logwatch on a Debian system. Please let me know if you have improvements, comments, bugfixes... Best regards, Reiner. On 14.11.2011 08:02, Kartsa wrote: Yes please :) Probably I will be able to develop it the way it is suitable for my needs :) \\Kartsa -Original Message- From: vdr-boun...@linuxtv.org [mailto:vdr-boun...@linuxtv.org] On Behalf Of Reiner Buehl Sent: 14. marraskuuta 2011 0:20 To: vdr@linuxtv.org Subject: Re: [vdr] VDR logs and logwatch I have created a first draft version of logwatch scripts for vdr.log. If you want, I can send them to you. I am still extending it. Best regards, Reiner. On 13.11.2011 22:25, Kartsa wrote: Hi Has anyone built a script for logwatch to get VDR messages from the logs? I am not familiar with perl which is mostly used with logwatch scripts. I assume it is possible to use any other language as well but thought that I would ask here if anyone has already a solution :) \\Kartsa ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr ___ vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
[vdr] VDR and Hybrid DVB Cards ( was "HVR 4000 drivers broken - adapter0/frontend1 busy" in linux-media list )
Lars, Thanks for the reply. Output of ls -la /dev/dvb/adapter0: root@Nutrigrain:/home/digitalTV/vdr-1.7.21# ls -la /dev/dvb/adapter0/* crw-rw 1 root video 212, 1 Nov 14 19:20 /dev/dvb/adapter0/demux0 crw-rw 1 root video 212, 5 Nov 14 19:20 /dev/dvb/adapter0/demux1 crw-rw 1 root video 212, 2 Nov 14 19:20 /dev/dvb/adapter0/dvr0 crw-rw 1 root video 212, 6 Nov 14 19:20 /dev/dvb/adapter0/dvr1 crw-rw 1 root video 212, 0 Nov 14 19:20 /dev/dvb/adapter0/frontend0 crw-rw 1 root video 212, 4 Nov 14 19:20 /dev/dvb/adapter0/frontend1 crw-rw 1 root video 212, 3 Nov 14 19:20 /dev/dvb/adapter0/net0 crw-rw 1 root video 212, 7 Nov 14 19:20 /dev/dvb/adapter0/net1 root@Nutrigrain:/home/digitalTV/vdr-1.7.21# As you can see there is a demux1 and dvr1 but all hung off adapter0 which is presumably the problem. I actually want to use both the DVB-S2 and the DVB-T frontends, though not concurrently. Happy to work with you on developing the required patch. If as you suggest that this is actually a VDR problem then I'll also post this reply in the VDR mailing list and we can take it from there. Regards, Mark. -Original Message- From: linux-media-ow...@vger.kernel.org [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of L. Hanisch Sent: Tuesday, 15 November 2011 5:35 AM To: linux-me...@vger.kernel.org Subject: Re: HVR 4000 drivers broken - adapter0/frontend1 busy Hi, Am 14.11.2011 04:14, schrieb Hawes, Mark: > Hi, > > I have just acquired a Hauppauge HVR 4000 hybrid DVB-S2 / DVB-T / > Analogue card > which I am trying to use with VDR 1.7.21 on the latest Slackware stable release > using kernel 2.6.37.6. vdr doesn't know anything about hybrid cards where you can access only one frontend at the same time. On startup vdr opens all frontends, so when accessing the second one this is blocked. Since I don't know this card exactly, what devices does it create? Is there also a demux[01] and dvr[01] or just a demux0 and dvr0? Which frontend do you want to use? For now you have to choose one and start vdr with the "-D" parameter to tell it which to use. If there's no demux1 and dvr1 and you want to use frontend1 you'll have the next problem since vdr asumes that every frontend has its own demux/dvr. I wrote a patch, so vdr uses demux0 with frontend1. http://linuxtv.org/pipermail/vdr/2011-November/025411.html Soon I will have some DVB-C/T hybrid device so I will try to extend the patch so both frontends can be used (not at the same time of course). It would be nice if you can send me the output of "ls -la /dev/dvb/adapter0/*". I don't know exactly what the dvb/v4l spec is saying about hybrid devices and how they should expose their capabilities but it seems to me there's some discussion about this topic from time to time. After all this is a problem at application level, not driver level. If I'm wrong please correct me. And maybe you want to read the vdr mailing list... Regards, Lars. > > The drivers seem to detect the card OK as seen in dmesg output: > > [7.501729] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.9 loaded > [7.503174] cx88[0]: subsystem: 0070:6902, board: Hauppauge WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected], frontend(s): 2 > [7.503373] cx88[0]: TV tuner type 63, Radio tuner type -1 > [7.551718] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 > [7.551788] i915 :00:02.0: setting latency timer to 64 > [7.564218] i915 :00:02.0: irq 41 for MSI/MSI-X > [7.564399] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem > [7.564825] [drm] initialized overlay support > [7.579830] cx88/0: cx2388x v4l2 driver version 0.0.9 loaded > [7.583007] No connectors reported connected with modes > [7.583077] [drm] Cannot find any crtc or sizes - going 1024x768 > [7.588874] Console: switching to colour frame buffer device 128x48 > [7.591121] fb0: inteldrmfb frame buffer device > [7.591144] drm: registered panic notifier > [7.591174] No ACPI video bus found > [7.591316] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 > [7.617097] cx88[0]: i2c init: enabling analog demod on HVR1300/3000/4000 tuner > [7.702578] IR RC5(x) protocol handler initialized > [7.728589] IR RC6 protocol handler initialized > [7.730628] cx2388x alsa driver version 0.0.9 loaded > [7.746096] IR JVC protocol handler initialized > [7.749962] IR Sony protocol handler initialized > [7.918601] IR MCE Keyboard/mouse protocol handler initialized > [7.980484] lirc_dev: IR Remote Control driver registered, major 243 > [7.994039] IR LIRC bridge handler initialized > [7.994767] tda9887 15-0043: creating new instance > [7.994795] tda9887 15-0043: tda988[5/6/7] found > [7.995608] tuner 15-0043: Tuner 74 found with type(s) Radio TV. > [7.997560] tuner 15-0061: Tuner -1 found with type(s) Radio TV. > [
Re: [vdr] VDR and Hybrid DVB Cards ( was "HVR 4000 drivers broken - adapter0/frontend1 busy" in linux-media list )
On Tue, 15 Nov 2011 14:08:24 +1100 "Hawes, Mark" wrote: > Lars, > > Thanks for the reply. > > Output of ls -la /dev/dvb/adapter0: > > root@Nutrigrain:/home/digitalTV/vdr-1.7.21# ls -la /dev/dvb/adapter0/* > crw-rw 1 root video 212, 1 Nov 14 19:20 /dev/dvb/adapter0/demux0 > crw-rw 1 root video 212, 5 Nov 14 19:20 /dev/dvb/adapter0/demux1 > crw-rw 1 root video 212, 2 Nov 14 19:20 /dev/dvb/adapter0/dvr0 > crw-rw 1 root video 212, 6 Nov 14 19:20 /dev/dvb/adapter0/dvr1 > crw-rw 1 root video 212, 0 Nov 14 > 19:20 /dev/dvb/adapter0/frontend0 crw-rw 1 root video 212, 4 Nov > 14 19:20 /dev/dvb/adapter0/frontend1 crw-rw 1 root video 212, 3 > Nov 14 19:20 /dev/dvb/adapter0/net0 crw-rw 1 root video 212, 7 > Nov 14 19:20 /dev/dvb/adapter0/net1 > root@Nutrigrain:/home/digitalTV/vdr-1.7.21# > > As you can see there is a demux1 and dvr1 but all hung off adapter0 > which is presumably the problem. Not that on itself, but possibly the implications. Can you try to start the vdr with -D 1 to start the vdr only at the second card ? Assumption would be, that you can use each individually, if you not filter for a device you get a busy device on the second. What i got from previous discussions on linux-media is, that if the device nodes are created within one adapter, an application needs to assume that the devices can not be used concurrently and needs to close one "device node group" before opening the other one. > I actually want to use both the DVB-S2 and the DVB-T frontends, though > not concurrently. > > Happy to work with you on developing the required patch. > > If as you suggest that this is actually a VDR problem then I'll also > post this reply in the VDR mailing list and we can take it from there. > > Regards, > > Mark. > > -Original Message- > From: linux-media-ow...@vger.kernel.org > [mailto:linux-media-ow...@vger.kernel.org] On Behalf Of L. Hanisch > Sent: Tuesday, 15 November 2011 5:35 AM > To: linux-me...@vger.kernel.org > Subject: Re: HVR 4000 drivers broken - adapter0/frontend1 busy > > Hi, > > Am 14.11.2011 04:14, schrieb Hawes, Mark: > > Hi, > > > > I have just acquired a Hauppauge HVR 4000 hybrid DVB-S2 / DVB-T / > > Analogue card > > which I am trying to use with VDR 1.7.21 on the latest Slackware > stable release > using kernel 2.6.37.6. > > vdr doesn't know anything about hybrid cards where you can access > only one frontend at the same time. > On startup vdr opens all frontends, so when accessing the second one > this is blocked. > > Since I don't know this card exactly, what devices does it create? > Is there also a demux[01] and dvr[01] or just a > demux0 and dvr0? Which frontend do you want to use? For now you have > to choose one and start vdr with the "-D" parameter to tell it which > to use. > If there's no demux1 and dvr1 and you want to use frontend1 you'll > have the next problem since vdr asumes that every frontend has its own > demux/dvr. I wrote a patch, so vdr uses demux0 with frontend1. > > http://linuxtv.org/pipermail/vdr/2011-November/025411.html > > Soon I will have some DVB-C/T hybrid device so I will try to extend > the patch so both frontends can be used (not at the same time of > course). > > It would be nice if you can send me the output of "ls -la > /dev/dvb/adapter0/*". > > I don't know exactly what the dvb/v4l spec is saying about hybrid > devices and how they should expose their capabilities but it seems to > me there's some discussion about this topic from time to time. > > After all this is a problem at application level, not driver level. > If I'm wrong please correct me. > And maybe you want to read the vdr mailing list... > > Regards, > Lars. > > > > > The drivers seem to detect the card OK as seen in dmesg output: > > > > [7.501729] cx88/2: cx2388x MPEG-TS Driver Manager version 0.0.9 > loaded > > [7.503174] cx88[0]: subsystem: 0070:6902, board: Hauppauge > WinTV-HVR4000 DVB-S/S2/T/Hybrid [card=68,autodetected], frontend(s): 2 > > [7.503373] cx88[0]: TV tuner type 63, Radio tuner type -1 > > [7.551718] i915 :00:02.0: PCI INT A -> GSI 16 (level, low) > > -> > IRQ 16 > > [7.551788] i915 :00:02.0: setting latency timer to 64 > > [7.564218] i915 :00:02.0: irq 41 for MSI/MSI-X > > [7.564399] vgaarb: device changed decodes: > PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem > > [7.564825] [drm] initialized overlay support > > [7.579830] cx88/0: cx2388x v4l2 driver version 0.0.9 loaded > > [7.583007] No connectors reported connected with modes > > [7.583077] [drm] Cannot find any crtc or sizes - going 1024x768 > > [7.588874] Console: switching to colour frame buffer device > > 128x48 [7.591121] fb0: inteldrmfb frame buffer device > > [7.591144] drm: registered panic notifier > > [7.591174] No ACPI video bus found > > [7.591316] [drm] Initialized i915 1.6.0 20080730 for > > :00:02.0 > on minor 0 > >
