[vdr] Re: vdr-remote doesn't find event after vdr restart due to emergency exit

[Oliver Endriss <o.endriss@gmx.de>]

On Thursday 22 July 2004 22:31, Joerg Riechardt wrote:
> the situation was:
> one recording going on
> a second recording starting
> UPT, emergency exit, restart of vdr by runvdr
> event2 which usually belongs to the DVB on-card IR receiver isn't there
> vdr stops
> How can I improve that? Is that a driver problem?
> Should I check in runvdr if event2 is there, and restart the driver if not?
> Jörg
> 
> Jul 21 23:26:19 vdr vdr[6144]: starting plugin: remote
> Jul 21 23:26:19 vdr vdr[6144]: remote: using '/dev/input/event2'
> 
> Jul 22 00:40:02 vdr vdr[6745]: ERROR: unknown picture type '4'
> Jul 22 00:40:02 vdr vdr[6745]: initiating emergency exit
> 
> Jul 22 00:40:16 vdr vdr[7016]: starting plugin: remote
> Jul 22 00:40:16 vdr vdr[7016]: remote: unable to open '/dev/input/event2': No such file or directory
> Jul 22 00:40:16 vdr vdr[7016]: ERROR: /dev/input/event2: No such file or directory
> Jul 22 00:40:18 vdr vdr[7016]: ERROR: /dev/input/event2: No such file or directory
> Jul 22 00:40:20 vdr vdr[7016]: remote: fatal error - unable to open input device

Please check your system logfile for messages from the DVB driver.
Imho this could only happen if evdev or dvb-ttpci have not been loaded.
Maybe vdr started *before* the driver was completely initialized
(hotplug firmware loader?)

Oliver