inputlirc: zeroconf LIRC daemon using Linux input event devices

[Guus Sliepen-2]

Hello,

I have some remote controls that are handled by the USB HID driver and
the AT keyboard driver. These are hard to get working with LIRC. Even
though recent versions of LIRC can read /dev/input/eventX devices, you
still need to use irrecord to painstakingly create a suitable
configuration file. However, the kernel's input layer already assigns
appropriate symbolic names to multimedia keys. To make life easy, I have
written a small daemon that acts like a LIRC daemon, but only processes
/dev/input/eventX files and translates events directly to useful
symbolic names, without any further configuration necessary. I have
tested this with a few keyboards with multimedia keys, an USB remote
control dongle that acts like a HID, and another remote control that is
handled by the AT keyboard driver.

You can download the software from the following subversion repository:

http://svn.sliepen.eu.org/inputlirc/trunk/

You need to have /usr/include/linux/input.h present. To compile and run:

make
./inputlircd /dev/input/event*

All LIRC clients should work with inputlircd. Use irw or input-events
from the input-utils package to find out the names of the buttons, and
write your .lircrc accordingly.

Comments are welcome.

--
Met vriendelijke groet / with kind regards,
    Guus Sliepen <guus@...>

[Christoph Bartelmus]

Hi!

Guus Sliepen "guus@..." wrote:
[...]
> appropriate symbolic names to multimedia keys. To make life easy, I have
> written a small daemon that acts like a LIRC daemon, but only processes
> /dev/input/eventX files and translates events directly to useful
> symbolic names, without any further configuration necessary. I have

Why don't we simply auto-generate a lircd.conf file. I have been  
wondering for a long time why the dev/input guys havn't submitted  
anything suitable yet.

Christoph


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

[Buzz-8]

Christoph,
I don't know why this hasn't been done.   But then again, I don't know how
to do this either.... So maybe everyone else is in the same boat?

Suggestions on how it might be do-able?.... There is a ever-growning number
of USB dev/input compatible devices out there?

Ideas:
*  I expect you need to know what "keycodes" a particular dev/input device
is capable of emitting (since a 20button remote won't have a full AT 105 key
keyboard set of keycodes, let alone multimedia keys  - my keyboard has 17
"multimedia" keys),
* from there you just directly map those keys (in lircd.conf) that are
available to the same-named X keyboard event with irxevent?

Anyone care to comment?

Buzz.

> -----Original Message-----
> From: lirc-list-admin@...
> [mailto:lirc-list-admin@...] On Behalf Of
> Christoph Bartelmus
> Sent: Friday, 10 February 2006 7:38 AM
> To: lirc-list@...
> Subject: Re: inputlirc: zeroconf LIRC daemon using Linux
> input event devices
>
> Hi!
>
> Guus Sliepen "guus@..." wrote:
> [...]
> > appropriate symbolic names to multimedia keys. To make life easy, I
> > have written a small daemon that acts like a LIRC daemon, but only
> > processes /dev/input/eventX files and translates events directly to
> > useful symbolic names, without any further configuration
> necessary. I
> > have
>
> Why don't we simply auto-generate a lircd.conf file. I have
> been wondering for a long time why the dev/input guys havn't
> submitted anything suitable yet.
>
> Christoph
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep
> through log files for problems?  Stop!  Download the new AJAX
> search engine that makes searching your log files as easy as
> surfing the  web.  DOWNLOAD SPLUNK!
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&
> dat=121642
>

-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642

[gphelan]

Guus Sliepen-2 wrote:

but only processes /dev/input/eventX files and translates events directly to useful symbolic names

Hello all - I also have a USB remote control that acts like a HID.
However, my problem is that it gets split into two separate event devices - /dev/input/event1 and /dev/input/event2.
All the remote keys map to KEY_* codes.
The keys (e.g. the numeric keys and up/down/left/right) from the first event device (1) have the same X key codes as their corresponding keys on the keyboard, so if I press a numeric key on the remote, X receives it the same as if I had pressed the key on the keyboard.
The keys for the second device have no effect, presumably because I have not configured X to be aware of them?

I wanted to use inputlircd to grab these event devices and pass their input to VDR.
user@host # ./inputlircd -gf /dev/input/event1 /dev/input/event2
The problem is that VDR will only pick up keys from event2. (X gets the event1 keys first?)

Does anyone know if it is possible to configure inputlirc to 'roll' two event devices into a single virtual device?

This is the relevant section from lsinput (input-utils):

/dev/input/event1
   bustype : BUS_USB
   vendor  : 0x766
   product : 0x204
   version : 1
   name    : "TopSeed Tech Corp. USB IR Combo "
   phys    : "usb-0000:00:07.2-2/input0"
   uniq    : ""
   bits ev : EV_SYN EV_KEY EV_LED EV_REP

/dev/input/event2
   bustype : BUS_USB
   vendor  : 0x766
   product : 0x204
   version : 1
   name    : "TopSeed Tech Corp. USB IR Combo "
   phys    : "usb-0000:00:07.2-2/input1"
   uniq    : ""
   bits ev : EV_SYN EV_KEY EV_REL EV_REP

And from cat /proc/bus/input/devices:

I: Bus=0003 Vendor=0766 Product=0204 Version=0001
N: Name="TopSeed Tech Corp. USB IR Combo Device "
P: Phys=usb-0000:00:07.2-2/input0
S: Sysfs=/class/input/input1
H: Handlers=kbd event1
B: EV=120003
B: KEY=10000 7 ff87207a c14057ff febeffdf ffefffff ffffffff fffffffe
B: LED=1f

I: Bus=0003 Vendor=0766 Product=0204 Version=0001
N: Name="TopSeed Tech Corp. USB IR Combo Device "
P: Phys=usb-0000:00:07.2-2/input1
S: Sysfs=/class/input/input2
H: Handlers=kbd mouse1 event2 ts1
B: EV=100007
B: KEY=42c03b2 20d0400 0 0 70000 4 18000 21f8 d001d006 9e0040 0 0 0
B: REL=103

[dishbert]

Thanks for the great little app, I found it with Synaptic from Ubuntu 8.04 when I was just about to pull my hair out trying to get lirc to work with Mythtv.  At last irw and input-events will work for me, (though not irrecord) but I'm not quite there yet.

I'm trying to get a Twinhan DVB remote to work properly. It shows up fine:

chris@PC-Linux:~$ lsusb
...
Bus 001 Device 003: ID 6253:0100 TwinHan Technology Co., Ltd Ir reciver f. remote control
Bus 001 Device 001: ID 0000:0000

and here:

/dev/input/event2
  bustype : BUS_USB
  vendor  : 0x6253
  product : 0x100
  version : 272
  name    : "Twinhan Tech Remote Control"
  phys    : "usb-0000:00:10.0-1/input0"
  uniq    : "1111111"
  bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP

/dev/input/event3
  bustype : BUS_USB
  vendor  : 0x6253
  product : 0x100
  version : 272
  name    : "Twinhan Tech Remote Control"
  phys    : "usb-0000:00:10.0-1/input1"
  uniq    : "1111111"
  bits ev : EV_SYN EV_KEY EV_REL EV_MSC

And some keys have worked fine from the begining with no adjustment whatever:  Enter, Exit, the number keys etc.  But the main keys I need to control Myth are Guide and the up and down arrow keys, and I can't make them work for the life of me.

irw shows them like this when I press Guide, Up, Down: (the "e" is from the "Guide" keypress)

e68 0 KEY_PAGEUP event2
^[[5~6d 0 KEY_PAGEDOWN event2
^[[6~

And input-event like this:

11:26:16.594274: EV_MSC code=4 value=458760
11:26:16.594291: EV_KEY KEY_E pressed
11:26:16.594294: EV_SYN code=0 value=0
e11:26:16.602269: EV_MSC code=4 value=458760
11:26:16.602284: EV_KEY KEY_E released
11:26:16.602286: EV_SYN code=0 value=0

11:26:18.673984: EV_SYN code=0 value=0
11:26:18.785973: EV_MSC code=4 value=458827
11:26:18.785990: EV_KEY KEY_PAGEUP pressed
11:26:18.785993: EV_SYN code=0 value=0
^[[5~11:26:18.793972: EV_MSC code=4 value=458827
11:26:18.793988: EV_KEY KEY_PAGEUP released
11:26:18.793990: EV_SYN code=0 value=0

11:26:19.569858: EV_SYN code=0 value=0
11:26:19.737844: EV_MSC code=4 value=458830
11:26:19.737860: EV_KEY KEY_PAGEDOWN pressed
11:26:19.737862: EV_SYN code=0 value=0
^[[6~11:26:19.753838: EV_MSC code=4 value=458830
11:26:19.753853: EV_KEY KEY_PAGEDOWN released
11:26:19.753856: EV_SYN code=0 value=0

But when I go to edit my lircrc file, I can only get certain keys to work to open the guide, and "Guide" is not one of them.  If I map the Myth command "m" to the "Stop" button or the "Up" keys, which irw says are KEY_TAB and KEY_HOME, it works fine.  But if I map it to the "Guide" button, which input-events says is KEY_E(or to e), it doesn't work and that key does what it always did, which is to bring up the Channel Editor.  Remapping the Up and Down keys does not stop them from performing the PageUp and PageDown functions either

I've stripped my lircrc down to nothing to try to diagnose this, but no joy yet.  When I start mythfrontend I can see it pointing the correct lircrc file.

I can't understand why changes to that file work for some keys and not others.

Guus Sliepen-2 wrote:

Hello,

I have some remote controls that are handled by the USB HID driver and
the AT keyboard driver. These are hard to get working with LIRC. Even
though recent versions of LIRC can read /dev/input/eventX devices, you
still need to use irrecord to painstakingly create a suitable
configuration file. However, the kernel's input layer already assigns
appropriate symbolic names to multimedia keys. To make life easy, I have
written a small daemon that acts like a LIRC daemon, but only processes
/dev/input/eventX files and translates events directly to useful
symbolic names, without any further configuration necessary. I have
tested this with a few keyboards with multimedia keys, an USB remote
control dongle that acts like a HID, and another remote control that is
handled by the AT keyboard driver.

You can download the software from the following subversion repository:

http://svn.sliepen.eu.org/inputlirc/trunk/

You need to have /usr/include/linux/input.h present. To compile and run:

make
./inputlircd /dev/input/event*

All LIRC clients should work with inputlircd. Use irw or input-events
from the input-utils package to find out the names of the buttons, and
write your .lircrc accordingly.

Comments are welcome.

--
Met vriendelijke groet / with kind regards,
    Guus Sliepen <[e-mail]>

 

[Anders Eriksson-2]

dishbert@... said:
> e68 0 KEY_PAGEUP event2
> ^[[5~6d 0 KEY_PAGEDOWN event2
> ^[[6~

Those ^[[ things are usually a sign thatthe kernel lacks guidance on the
keypress.

Have a look at showkey(1) and use setkeycodes(1) to tell the kernel to emit
the right keycodes for your scan codes. Works for my multimedia keys on my
keyboard...

/Anders



------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

[Yan Seiner]

dishbert wrote:

> Thanks for the great little app, I found it with Synaptic from Ubuntu 8.04
> when I was just about to pull my hair out trying to get lirc to work with
> Mythtv.  At last irw and input-events will work for me, (though not
> irrecord) but I'm not quite there yet.
>
> I'm trying to get a Twinhan DVB remote to work properly. It shows up fine:
>
> chris@PC-Linux:~$ lsusb
> ...
> Bus 001 Device 003: ID 6253:0100 TwinHan Technology Co., Ltd Ir reciver f.
> remote control
> Bus 001 Device 001: ID 0000:0000
>
> and here:
>
> /dev/input/event2
>   bustype : BUS_USB
>   vendor  : 0x6253
>   product : 0x100
>   version : 272
>   name    : "Twinhan Tech Remote Control"
>   phys    : "usb-0000:00:10.0-1/input0"
>   uniq    : "1111111"
>   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
>
> /dev/input/event3
>   bustype : BUS_USB
>   vendor  : 0x6253
>   product : 0x100
>   version : 272
>   name    : "Twinhan Tech Remote Control"
>   phys    : "usb-0000:00:10.0-1/input1"
>   uniq    : "1111111"
>   bits ev : EV_SYN EV_KEY EV_REL EV_MSC
>
> And some keys have worked fine from the begining with no adjustment
> whatever:  Enter, Exit, the number keys etc.  But the main keys I need to
> control Myth are Guide and the up and down arrow keys, and I can't make them
> work for the life of me.
>
> irw shows them like this when I press Guide, Up, Down: (the "e" is from the
> "Guide" keypress)
>
> e68 0 KEY_PAGEUP event2
> ^[[5~6d 0 KEY_PAGEDOWN event2
> ^[[6~
>
> And input-event like this:
>
> 11:26:16.594274: EV_MSC code=4 value=458760
> 11:26:16.594291: EV_KEY KEY_E pressed
> 11:26:16.594294: EV_SYN code=0 value=0
> e11:26:16.602269: EV_MSC code=4 value=458760
> 11:26:16.602284: EV_KEY KEY_E released
> 11:26:16.602286: EV_SYN code=0 value=0
>
> 11:26:18.673984: EV_SYN code=0 value=0
> 11:26:18.785973: EV_MSC code=4 value=458827
> 11:26:18.785990: EV_KEY KEY_PAGEUP pressed
> 11:26:18.785993: EV_SYN code=0 value=0
> ^[[5~11:26:18.793972: EV_MSC code=4 value=458827
> 11:26:18.793988: EV_KEY KEY_PAGEUP released
> 11:26:18.793990: EV_SYN code=0 value=0
>
> 11:26:19.569858: EV_SYN code=0 value=0
> 11:26:19.737844: EV_MSC code=4 value=458830
> 11:26:19.737860: EV_KEY KEY_PAGEDOWN pressed
> 11:26:19.737862: EV_SYN code=0 value=0
> ^[[6~11:26:19.753838: EV_MSC code=4 value=458830
> 11:26:19.753853: EV_KEY KEY_PAGEDOWN released
> 11:26:19.753856: EV_SYN code=0 value=0
>
> But when I go to edit my lircrc file, I can only get certain keys to work to
> open the guide, and "Guide" is not one of them.  If I map the Myth command
> "m" to the "Stop" button or the "Up" keys, which irw says are KEY_TAB and
> KEY_HOME, it works fine.  But if I map it to the "Guide" button, which
> input-events says is KEY_E(or to e), it doesn't work and that key does what
> it always did, which is to bring up the Channel Editor.  Remapping the Up
> and Down keys does not stop them from performing the PageUp and PageDown
> functions either
>
> I've stripped my lircrc down to nothing to try to diagnose this, but no joy
> yet.  When I start mythfrontend I can see it pointing the correct lircrc
> file.
>
> I can't understand why changes to that file work for some keys and not
> others.
>  

See if this discussion helps.

http://sourceforge.net/mailarchive/forum.php?thread_name=497B3A7A.7060801%40seiner.com&forum_name=lirc-list

--Yan

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

[dishbert]

Thanks Yan, I gave irexec a try, but still nothing, I just tried the basics in lircd using the examples in the link, the  rest is a little over my head at this point.  In the meantime, I installed a Hauppage  Nexus S that had been lying around, and I'm hoping for an easier time setting up it's remote.  It has some working examples of .conf files available.  Thanks for your help, don't be surprised to see me back here soon with other issues.  Mythtv is a great program, but almost useless if you can't get the remote to work.

Yan Seiner wrote:

dishbert wrote:
> Thanks for the great little app, I found it with Synaptic from Ubuntu 8.04
> when I was just about to pull my hair out trying to get lirc to work with
> Mythtv.  At last irw and input-events will work for me, (though not
> irrecord) but I'm not quite there yet.
>
> I'm trying to get a Twinhan DVB remote to work properly. It shows up fine:
>
> chris@PC-Linux:~$ lsusb
> ...
> Bus 001 Device 003: ID 6253:0100 TwinHan Technology Co., Ltd Ir reciver f.
> remote control
> Bus 001 Device 001: ID 0000:0000
>
> and here:
>
> /dev/input/event2
>   bustype : BUS_USB
>   vendor  : 0x6253
>   product : 0x100
>   version : 272
>   name    : "Twinhan Tech Remote Control"
>   phys    : "usb-0000:00:10.0-1/input0"
>   uniq    : "1111111"
>   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
>
> /dev/input/event3
>   bustype : BUS_USB
>   vendor  : 0x6253
>   product : 0x100
>   version : 272
>   name    : "Twinhan Tech Remote Control"
>   phys    : "usb-0000:00:10.0-1/input1"
>   uniq    : "1111111"
>   bits ev : EV_SYN EV_KEY EV_REL EV_MSC
>
> And some keys have worked fine from the begining with no adjustment
> whatever:  Enter, Exit, the number keys etc.  But the main keys I need to
> control Myth are Guide and the up and down arrow keys, and I can't make them
> work for the life of me.
>
> irw shows them like this when I press Guide, Up, Down: (the "e" is from the
> "Guide" keypress)
>
> e68 0 KEY_PAGEUP event2
> ^[[5~6d 0 KEY_PAGEDOWN event2
> ^[[6~
>
> And input-event like this:
>
> 11:26:16.594274: EV_MSC code=4 value=458760
> 11:26:16.594291: EV_KEY KEY_E pressed
> 11:26:16.594294: EV_SYN code=0 value=0
> e11:26:16.602269: EV_MSC code=4 value=458760
> 11:26:16.602284: EV_KEY KEY_E released
> 11:26:16.602286: EV_SYN code=0 value=0
>
> 11:26:18.673984: EV_SYN code=0 value=0
> 11:26:18.785973: EV_MSC code=4 value=458827
> 11:26:18.785990: EV_KEY KEY_PAGEUP pressed
> 11:26:18.785993: EV_SYN code=0 value=0
> ^[[5~11:26:18.793972: EV_MSC code=4 value=458827
> 11:26:18.793988: EV_KEY KEY_PAGEUP released
> 11:26:18.793990: EV_SYN code=0 value=0
>
> 11:26:19.569858: EV_SYN code=0 value=0
> 11:26:19.737844: EV_MSC code=4 value=458830
> 11:26:19.737860: EV_KEY KEY_PAGEDOWN pressed
> 11:26:19.737862: EV_SYN code=0 value=0
> ^[[6~11:26:19.753838: EV_MSC code=4 value=458830
> 11:26:19.753853: EV_KEY KEY_PAGEDOWN released
> 11:26:19.753856: EV_SYN code=0 value=0
>
> But when I go to edit my lircrc file, I can only get certain keys to work to
> open the guide, and "Guide" is not one of them.  If I map the Myth command
> "m" to the "Stop" button or the "Up" keys, which irw says are KEY_TAB and
> KEY_HOME, it works fine.  But if I map it to the "Guide" button, which
> input-events says is KEY_E(or to e), it doesn't work and that key does what
> it always did, which is to bring up the Channel Editor.  Remapping the Up
> and Down keys does not stop them from performing the PageUp and PageDown
> functions either
>
> I've stripped my lircrc down to nothing to try to diagnose this, but no joy
> yet.  When I start mythfrontend I can see it pointing the correct lircrc
> file.
>
> I can't understand why changes to that file work for some keys and not
> others.
>  

See if this discussion helps.

http://sourceforge.net/mailarchive/forum.php?thread_name=497B3A7A.7060801%40seiner.com&forum_name=lirc-list

--Yan

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

[dishbert]

Thanks for the responses, sorry I'm slow to respond, my main board died and I'm just now getting back on line with a new one!  

I'll try Anders suggestions as soon as I get Linux back up and running and let you know how it turns out.  Maybe the new hardware alone will solve it.

Anders Eriksson-2 wrote:

[e-mail] said:
> e68 0 KEY_PAGEUP event2
> ^[[5~6d 0 KEY_PAGEDOWN event2
> ^[[6~

Those ^[[ things are usually a sign thatthe kernel lacks guidance on the
keypress.

Have a look at showkey(1) and use setkeycodes(1) to tell the kernel to emit
the right keycodes for your scan codes. Works for my multimedia keys on my
keyboard...

/Anders



------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword

[dishbert]

I installed the new hardware and was still having a terrible time with the remote until I came across this

http://www.doctort.org/adam/general/update-on-twinhan-remote-for-mythbuntu-810.html 

I followed those steps and the remote worked immediately.  Hopefully this can help others as well.



Thanks Yan, I gave irexec a try, but still nothing, I just tried the basics in lircd using the examples in the link, the  rest is a little over my head at this point.  In the meantime, I installed a Hauppage  Nexus S that had been lying around, and I'm hoping for an easier time setting up it's remote.  It has some working examples of .conf files available.  Thanks for your help, don't be surprised to see me back here soon with other issues.  Mythtv is a great program, but almost useless if you can't get the remote to work.

Yan Seiner wrote:

dishbert wrote:
> Thanks for the great little app, I found it with Synaptic from Ubuntu 8.04
> when I was just about to pull my hair out trying to get lirc to work with
> Mythtv.  At last irw and input-events will work for me, (though not
> irrecord) but I'm not quite there yet.
>
> I'm trying to get a Twinhan DVB remote to work properly. It shows up fine:
>
> chris@PC-Linux:~$ lsusb
> ...
> Bus 001 Device 003: ID 6253:0100 TwinHan Technology Co., Ltd Ir reciver f.
> remote control
> Bus 001 Device 001: ID 0000:0000
>
> and here:
>
> /dev/input/event2
>   bustype : BUS_USB
>   vendor  : 0x6253
>   product : 0x100
>   version : 272
>   name    : "Twinhan Tech Remote Control"
>   phys    : "usb-0000:00:10.0-1/input0"
>   uniq    : "1111111"
>   bits ev : EV_SYN EV_KEY EV_MSC EV_LED EV_REP
>
> /dev/input/event3
>   bustype : BUS_USB
>   vendor  : 0x6253
>   product : 0x100
>   version : 272
>   name    : "Twinhan Tech Remote Control"
>   phys    : "usb-0000:00:10.0-1/input1"
>   uniq    : "1111111"
>   bits ev : EV_SYN EV_KEY EV_REL EV_MSC
>
> And some keys have worked fine from the begining with no adjustment
> whatever:  Enter, Exit, the number keys etc.  But the main keys I need to
> control Myth are Guide and the up and down arrow keys, and I can't make them
> work for the life of me.
>
> irw shows them like this when I press Guide, Up, Down: (the "e" is from the
> "Guide" keypress)
>
> e68 0 KEY_PAGEUP event2
> ^[[5~6d 0 KEY_PAGEDOWN event2
> ^[[6~
>
> And input-event like this:
>
> 11:26:16.594274: EV_MSC code=4 value=458760
> 11:26:16.594291: EV_KEY KEY_E pressed
> 11:26:16.594294: EV_SYN code=0 value=0
> e11:26:16.602269: EV_MSC code=4 value=458760
> 11:26:16.602284: EV_KEY KEY_E released
> 11:26:16.602286: EV_SYN code=0 value=0
>
> 11:26:18.673984: EV_SYN code=0 value=0
> 11:26:18.785973: EV_MSC code=4 value=458827
> 11:26:18.785990: EV_KEY KEY_PAGEUP pressed
> 11:26:18.785993: EV_SYN code=0 value=0
> ^[[5~11:26:18.793972: EV_MSC code=4 value=458827
> 11:26:18.793988: EV_KEY KEY_PAGEUP released
> 11:26:18.793990: EV_SYN code=0 value=0
>
> 11:26:19.569858: EV_SYN code=0 value=0
> 11:26:19.737844: EV_MSC code=4 value=458830
> 11:26:19.737860: EV_KEY KEY_PAGEDOWN pressed
> 11:26:19.737862: EV_SYN code=0 value=0
> ^[[6~11:26:19.753838: EV_MSC code=4 value=458830
> 11:26:19.753853: EV_KEY KEY_PAGEDOWN released
> 11:26:19.753856: EV_SYN code=0 value=0
>
> But when I go to edit my lircrc file, I can only get certain keys to work to
> open the guide, and "Guide" is not one of them.  If I map the Myth command
> "m" to the "Stop" button or the "Up" keys, which irw says are KEY_TAB and
> KEY_HOME, it works fine.  But if I map it to the "Guide" button, which
> input-events says is KEY_E(or to e), it doesn't work and that key does what
> it always did, which is to bring up the Channel Editor.  Remapping the Up
> and Down keys does not stop them from performing the PageUp and PageDown
> functions either
>
> I've stripped my lircrc down to nothing to try to diagnose this, but no joy
> yet.  When I start mythfrontend I can see it pointing the correct lircrc
> file.
>
> I can't understand why changes to that file work for some keys and not
> others.
>  

See if this discussion helps.

http://sourceforge.net/mailarchive/forum.php?thread_name=497B3A7A.7060801%40seiner.com&forum_name=lirc-list

--Yan

------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword