<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Oct 26, 2013 at 5:22 PM, Gabe Rubin <span dir="ltr"><<a href="mailto:gaberubin@gmail.com" target="_blank">gaberubin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Sat, Oct 26, 2013 at 3:37 PM, Gabe Rubin <span dir="ltr"><<a href="mailto:gaberubin@gmail.com" target="_blank">gaberubin@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div>Hi list,<br><br></div>I upgraded my mythbox, first from fedora17 to 18 and now to 19 using fed up. After the first upgrade, the remote stopped working properly. I used a harmony with a pvr-350 receiver (RC5).<br>
<br></div>The system is definitely recognizing keystrokes as verified by dmesg when I start the ir-kbd-i2c module in debug mode. I have verified that the keymap I am loading is fine and running ir-keytable -r shows keystrokes. I just no output when I run irw. I have stopped and restarted lirc plenty of of times, I have tried different lirc.conf files from the lirc-remotes package. I am just stumped here.<br>
<br>As an aside, some of the keys appear to be recognized as keyboard keystrokes if I use different keymaps than the custom one I have created (I can verify this by opening a text editor and inputting text with the remote). I would be fine just getting rid of lirc and using my harmony remote and receiver as a keyboard, but unsure how to do that.<br>
</div>
</blockquote></div><br><br></div></div></div><div class="gmail_extra">I figured out what may be the problem but unsure how to fix it. If I run the following command as root (after stopping lirc and removing the lircd lock file)<br>
lircd --device=/dev/input/remote --driver=devinput<br></div><div class="gmail_extra">I can then restart myth and have lirc work perfectly.<br><br>I thought it was an issue with my lirc config file, but this is what that file is:<br>
[root@localhost ~]# more /etc/sysconfig/lirc<br>LIRC_DRIVER="devinput"<br>LIRC_DEVICE="/dev/input/remote"<br><br><br></div><div class="gmail_extra">So I can use the remote, but I can't just restart the computer and have it work. I need to run this command first. I suppose I could not automatically start lirc and then call it from a startup script in rc.local, but it seems like I have my configuration done correctly, so I don't know why this is happening.<br>
</div></div></blockquote><div><br></div><div>Continuing to follow-up on this, it looks like it is a bug with the latest stable version of lirc where it won't read arguments from the /etc/sysconfig/lirc. I already have a script that takes care of some lirc related tasks on startup. I know have to add this command to the script:<br>
/usr/sbin/lircd --device=/dev/input/remote --driver=devinput<br><br></div><div>The bug report says that there is a new version that fixes this problem, but it was not working for me and I have already spent all day on this and don't want to diagnose further when I have a solution (albeit, very kludy). I did find another user reporting on this after spending a full day at it, but I am surprised no others are really having this issue. Kind of a big deal for lirc so I am also surprised there is not a stable version that fixes the problem.<br>
</div></div>
<br></div></div>