[vdr] Re: some observations and problems with 1.2.0

[Gregor Lawatscheck <gpel@mpex.net>]

At 22:37 01/06/2003, you wrote:
> 1. The linux-dvb.2003-05-24 firmware seems not so utterly stable. I've seen
> many artifacts especially around fast moving persons and patterns, and in
> one case the firmware froze entirely, with lots of error messages in the
> syslog, like,
>
> Jun  1 18:18:57 linvdr kernel: OutCommand: timeout waiting for COMMAND idle
> Jun  1 18:18:57 linvdr kernel: SOutCommand error
> Jun  1 18:18:57 linvdr kernel: outcom error
> Jun  1 18:18:58 linvdr kernel: OutCommand: timeout waiting for COMMAND idle
> Jun  1 18:18:58 linvdr kernel: SOutCommand error
> Jun  1 18:18:58 linvdr kernel: outcom error
> Jun  1 18:18:59 linvdr kernel: OutCommand: timeout waiting for COMMAND idle
> Jun  1 18:18:59 linvdr kernel: CommandRequest error
> Jun  1 18:18:59 linvdr kernel: StopHWFilter error
>
> etc. Well this is probabliy more DVB than VDR related.
Indeed. What driver have you been using before? 0.9.4? It performs nicely 
here. With what channels are you using vdr? Astra Sat? DVB-T in the UK or 
elsewhere? Transfermode to from budget card to watch TV?

There is still something wrong with the firmware. Increasing video memory 
size in latest CVS (as of 1.6.) is a step in the right direction but I'm at 
a loss why it locks up with OutCom errors.


>5. A suggestion: If there is a double entry in channels.conf, is it
>possible to gracefully ignore the problem? There is an error message like
>
>Jun 1 17:44:13 linvdr vdr[23927]: ERROR: channel data not unique!
>Jun 1 17:44:13 linvdr vdr[23927]: ERROR: error in /video/channels.conf, 
line222
>
>but all programs then have number 0 (zero), and you cannot switch channels
>and more. I can deal with it but this is not very mother-in-law friendly
>if you know what I mean.

Agreed, it shouldn't lock up the channels list like that if possible, but I 
guess it's  minor point. 


--
Info:
To unsubscribe send a mail to ecartis@linuxtv.org with "unsubscribe vdr" as subject.