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

[Joerg Riechardt <J.Riechardt@gmx.de>]

Oliver Endriss wrote:

> On Friday 30 July 2004 11:26, Joerg Riechardt wrote:
>
> > Oliver Endriss wrote:
> >
> >
> > > > > > event2 which usually belongs to the DVB on-card IR receiver isn't there
> > > > > 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?)
> > > > I indeed use the hotplug firmware loader, is that not recommended?
> > >
> > > I never used the hotplug firmware loader because it slows down driver
> > > loading. The event interface is registered as the last step during
> > > driver initialization.
> > what kind of driver are you using?
>
> - dvb-kernel branch linux_2_4 with vanilla kernel 2.4.26
> - dvb-kernel with vanilla kernel 2.6.7
>
>
> > dvb-kernel with makelinks? but then you have to recompile your kernel 
> > every time you do a new cvs checkout for the dvb-kernel, don't you?
>
> No, there is another way:
> Simply compile dvb-kernel in the build-2.6 directory of the driver.
> The kernel sources will not be touched, and you can easily test
> different drivers using the same kernel.
Hm, that's what I do, so I think I didn't get the difference to hotplug 
firmware loader. Would you explain?
> > > > P.S. when I insert a "sleep 10" between driver start and vdr start 
> > > > everything is fine
> > > > ...
> > > > ERROR: /dev/input/event2: No such file or directory
> > > > ...
> > > Strange. According to the log the device node does not exist!
> > > Are you using devfs?
> > no
> >
> >
> > > Maybe it takes some time until the device node
> > > shows up in the file system.
> > sometimes it happens after several loadings and unloadings of the 
> > driver, that the IR events are on event3 instead of event2, in that case 
> > there is nothing on event2. I had that during my experiments from time 
> > to time.
>
> Strange, the event interface should change only if you add or remove
> drivers or hardware, for example USB devices.
For sure I didn't do that (except reload of dvb-kernel driver).
Jörg