<div class="gmail_quote">On Fri, Oct 23, 2009 at 10:38 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On 10/23/2009 09:42 AM, Larry K wrote:<br>
...<div class="im"><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Yes, lirc is working most of the time. It's just the occasional error<br>
that causes myth to weird out on me. If I press skip-ahead say 10 times<br>
repeatedly, I'll get maybe one bad code transmitted and then myth gets<br>
into the wrong menu and then the wife yells at me for it.<br>
<br>
I am using the Hauppauge PVR-250 IR receiver. I have a Xantech<br>
connecting block that I use to get the IR signal into my equipment<br>
cabinet. The emitter from the Xantech is positioned in close proximity<br>
to the Hauppauge IR receiver.<br>
<br>
All of this has worked fine for several years. The issues started after<br>
the fc10 upgrade.<br>
</blockquote>
<br></div>
I got nothin' on this front, lirc_i2c has changed some since what's in the F10 kernel, but only in the i2c client registration area, nothing significant I can think of in the signal processing area. Might try running with lirc_i2c loaded in debug mode, see what gets spit out into dmesg when the wackiness ensues.<br>
<font color="#888888">
<br>
-- </font><br></blockquote></div><br>Well, I ran in debug mode and I can see different hex codes reflected in the log when the spurious codes are received by irw , but the log gives no indication as to why....<br><br>Oh. I forgot to say that I have dual Hauppauge PVR-250s in this machine. I guess this shouldn't matter to lirc? It hasn't in the past.<br>