<div class="gmail_quote">On Mon, Aug 27, 2012 at 5:13 AM, Igor Cicimov <span dir="ltr"><<a href="mailto:icicimov@gmail.com" target="_blank">icicimov@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Mon, Aug 27, 2012 at 12:47 PM, Kenneth Emerson <span dir="ltr"><<a href="mailto:kenneth.emerson@gmail.com" target="_blank">kenneth.emerson@gmail.com</a>></span> wrote:<br></div>
</div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
<div class="gmail_quote"><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div>> REMOTE_LIRCD_CONF="" should be pointing to your remote settings file for your remote, you know one that has "begin remote" and "end remote" lines inside and all the hex codes mapped to keys inbetween. Also you need to have lircd autostart set to yes its couple of lines bellow not shown in your print.<br>
</div></div>
Once you have your hauppauge remote working use it to train your harmony remote. Thats what i did with my harmony 700.<p></p>
<br></blockquote></div><div>Thanks for the pointer, but that didn't help. At this point, I'm just trying to find the connections between the devinput driver and lirc so that I can see something come out of irw. I should also mention that I do not have a device "/dev/lirc0" which I thought was necessary for the magic to work.</div>
<div><br></div><div>-- Ken E. </div></div>
<br></div></div><div class="im">_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org" target="_blank">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></div></blockquote></div><br>Does the device "/dev/input/event11" exist? Do you see anything with:<br>$ cat /dev/input/event11<br>when pressing remote buttons? You should see some gibberish if it is working. If not then your driver is not getting loaded which for your remote should be<font color="black" face="Verdana,Arial,Helvetica"> "<font color="black" face="Verdana,Arial,Helvetica">ir-kbd-i2c". So check with:<br>
$ lsmod | grep ^ir<br>if the module is loaded.<br><br>Also this thread might help too: <a href="http://ubuntuforums.org/showthread.php?t=1846070" target="_blank">http://ubuntuforums.org/showthread.php?t=1846070</a><br>The guy had same problem as you after upgrade to 12.04.<br>
<br> </font></font>
<br>_______________________________________________<br>
mythtv-users mailing list<br>
<a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br>
<a href="http://www.mythtv.org/mailman/listinfo/mythtv-users" target="_blank">http://www.mythtv.org/mailman/listinfo/mythtv-users</a><br>
<br></blockquote></div><br>I'm no expert but i did the same thing yesterday. It took a while to figure out. But since i'm no expert i can't tell you what to do since i did so many things that i don't know what worked in the end =)<br>
<br>But the first thing i should suggest you to do is to install ir-keytable. When you run ir-keytable you can see what inputdevices you have, and on what event they are. With ir-keytable -t you get something that is like irw, but for devinput. So you should see key press output when you press the remote. And if this dont work it is the first step before you try to connect devinput with lirc.<br>
<br>This is how the first part of my hardware.conf looks like:<br><br>REMOTE="Linux input layer (/dev/input/eventX)"<br>REMOTE_MODULES=""<br>REMOTE_DRIVER="devinput"<br>REMOTE_DEVICE="/dev/input/event`grep -A3 Phys="i2c" /proc/bus/input/devices | grep "Handlers=" | sed 's/.*event\([0-9]\+\)/\1/'`"<br>
REMOTE_SOCKET=""<br>REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput"<br>REMOTE_LIRCD_ARGS=""<br><br>The strange line on REMOTE_DEVICE is because my remote change event number when i reboot. With that line the number is figured out on runtime (found that solution on internet)<br>
<br>I hope this could be a start for you.<br><br><br><br>