Hello,
I use vdr-1.7.9, v4l-dvb from http://linuxtv.org/hg/v4l-dvb and femon 1.7.4
When I start the plugin I don't get any output on my tv and see the following messages in my logfile:
--snip-- Sep 15 08:37:36 video vdr: [17541] ERROR: cOsd::SetAreas returned 6 Sep 15 08:37:36 video vdr: [18523] femon receiver thread started (pid=17541, tid=18523) Sep 15 08:37:36 video vdr: [18524] receiver on device 1 thread started (pid=17541, tid=18524) Sep 15 08:37:36 video vdr: [18525] TS buffer on device 1 thread started (pid=17541, tid=18525) Sep 15 08:37:36 video vdr: [18526] femon osd thread started (pid=17541, tid=18526) Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:37 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:37 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:38 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented Sep 15 08:37:38 video vdr: [18526] femon osd thread ended (pid=17541, tid=18526) Sep 15 08:37:38 video vdr: [18523] femon receiver thread ended (pid=17541, tid=18523) Sep 15 08:37:38 video vdr: [18525] TS buffer on device 1 thread ended (pid=17541, tid=18525) Sep 15 08:37:38 video vdr: [18524] buffer stats: 114304 (5%) used Sep 15 08:37:38 video vdr: [18524] receiver on device 1 thread ended (pid=17541, tid=18524) --snip--
does anybody know what is wrong with my setup ?
PS.: via svdr I can get some infos:
--snip-- video:~ # svdrpsend.pl plug femon info 220 video SVDRP VideoDiskRecorder 1.7.9; Tue Sep 15 08:41:59 2009; ANSI_X3.4-1968 900-CARD:0 900-TYPE:0 900-NAME:ST STV0299 DVB-S 900-STAT:1F 900-SGNL:E11E 900-SNRA:EC1F 900-BERA:00000000 900-UNCB:00000000 900 CHAN:Das Erste;ARD:11836:hC34M2O0S0:S19.2E:27500:101=2:102=deu,103=2ch;106=dd:104:0:28106:1:1101:0 221 video closing connection video:~ # --snip--
On Tue, 15 Sep 2009, Dieter Bloms wrote:
Sep 15 08:37:36 video vdr: [17541] ERROR: cOsd::SetAreas returned 6
Your OSD is running out of memory. The only cure is to shrink your current OSD size.
Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented
Your DVB driver doesn't provide the FE_READ_UNCORRECTED_BLOCKS ioctl - it shouldn't be fatal.
BR, -- rofa
Rolf Ahrenberg wrote:
Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented
Your DVB driver doesn't provide the FE_READ_UNCORRECTED_BLOCKS ioctl - it shouldn't be fatal.
Hm, wouldn't it be better to display something like 'n/a' in the osd instead of logging an error?
CU Oliver
Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB.
On 9/15/09, Oliver Endriss o.endriss@gmx.de wrote:
Rolf Ahrenberg wrote:
Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented
Your DVB driver doesn't provide the FE_READ_UNCORRECTED_BLOCKS ioctl - it shouldn't be fatal.
Hm, wouldn't it be better to display something like 'n/a' in the osd instead of logging an error?
CU Oliver
--
VDR Remote Plugin 0.4.0: http://www.escape-edv.de/endriss/vdr/ 4 MByte Mod: http://www.escape-edv.de/endriss/dvb-mem-mod/ Full-TS Mod: http://www.escape-edv.de/endriss/dvb-full-ts-mod/
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Wed, 16 Sep 2009, Theunis Potgieter wrote:
Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB.
The "osOutOfMemory" error comes from the VDR - not from the plugin. Of course you could log another more detailed error message in plugins, but it would be just redundant information to fill up your syslog. IMO, if you want more detailed error messages, you should modify VDR's cOsd::SetAreas() method rather than plugins.
BR, -- rofa
Would you care to write such a patch for vdr? In a way that Klaus could simply include in future releases. I think it would help a lot for end-users, trying figure out what possible causes are.
On 9/16/09, Rolf Ahrenberg rahrenbe@cc.hut.fi wrote:
On Wed, 16 Sep 2009, Theunis Potgieter wrote:
Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB.
The "osOutOfMemory" error comes from the VDR - not from the plugin. Of course you could log another more detailed error message in plugins, but it would be just redundant information to fill up your syslog. IMO, if you want more detailed error messages, you should modify VDR's cOsd::SetAreas() method rather than plugins.
BR,
rofa
vdr mailing list vdr@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/vdr
On Wed, Sep 16, 2009 at 3:58 AM, Theunis Potgieter theunis.potgieter@gmail.com wrote:
Would you care to write such a patch for vdr? In a way that Klaus could simply include in future releases. I think it would help a lot for end-users, trying figure out what possible causes are.
I agree. Detailed error messages are the only ones worth printing/logging, especially when it comes to end-users trying to figure out why their box isn't working properly.
Hi,
please re-read my message. I was not referring to the osd size stuff, but to this error message:
| Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented
femon must not assume that drivers support all ioctls...
CU Oliver
Theunis Potgieter wrote:
Why not state the real error which is not enough ram on device X for osd? with a hint message like: Require xyz KB, only have 2048KB.
On 9/15/09, Oliver Endriss o.endriss@gmx.de wrote:
Rolf Ahrenberg wrote:
Sep 15 08:37:36 video vdr: [18526] ERROR (femonosd.c,504): Function not implemented
Your DVB driver doesn't provide the FE_READ_UNCORRECTED_BLOCKS ioctl - it shouldn't be fatal.
Hm, wouldn't it be better to display something like 'n/a' in the osd instead of logging an error?
-
Dieter Bloms -
Oliver Endriss -
Rolf Ahrenberg -
Theunis Potgieter -
VDR User