Try using 'evtest' to get diagnostic information on what driver is providing the events to /dev/input/event5, and what events are being generated.

On 10 April 2011 16:42, John Doe <> wrote:
, Jarod Wilson.
08.04.2011 23:56
> On Apr 5, 2011, at 1:11 AM, john.99.doe wrote:
>> lircd 0.9.0 configured devinput
>> why not exist /var/run/lirc after restart? witch script must create this?
>> /usr/local/sbin/lircd --nodaemon --driver=devinput
>> --output=/var/run/lirc/lircd --device=/dev/input/event5
>> lircd: lircd(devinput) ready, using /var/run/lirc/lircd
>> in other console start irw
>> in first console answer
>> lircd: accepted new client on /var/run/lirc/lircd
>> lircd: initializing '/dev/input/event5'
>> lircd: WARNING: can't get exclusive access to events coming from
>> `/dev/input/event5' interface
>> irw has no reaction to key press
> Are you sure event5 is the right device? Your prior mail had event8.
> I suggest using the /dev/input/by-id/<foo> symlink instead.
Yes. /dev/input/event5 and /dev/input/event8 right device.
At first to adjust a chain.(lircd+irw=reactions ) Then correctly to
specify options in hardware.conf.

Forrester Wave Report - Recovery time is now measured in hours and minutes
not days. Key insights are discussed in the 2010 Forrester Wave Report as
part of an in-depth evaluation of disaster recovery service providers.
Forrester found the best-in-class provider in terms of services and vision.
Read this report now!