[mythtv-users] LIRC on FC14 Mythtv .24 Both LIRC and Built In Running - Help?

[Michael Jones]

>-----Original Message-----
>From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
>bounces at mythtv.org] On Behalf Of Don Lewis
>Sent: Tuesday, February 22, 2011 2:56 PM
>To: mythtv-users at mythtv.org
>Subject: Re: [mythtv-users] LIRC on FC14 Mythtv .24 Both LIRC and Built In
>Running - Help?
>
>On 22 Feb, Michael Jones wrote:
>> In efforts to get current, add a few capabilities to my system and gain a
>> little more stability I've recently wiped my MythTV BE system and
installed
>> FC14 (2.6.35.11-83.fc14.i686.PAE) and MythTV .24. from ATRPMS    So far I
>> have "almost" everything working.
>>
>>
>>
>> One of the misbehaving components is LIRC .. Whenever I press a remote
>key,
>> I get at least 2 keypresses in the UI.  I'm guessing this is due to both
the
>> imbedded LIRC support in .24 and LIRC running together?  How do I turn
the
>> imbedded version off?
>>
>>
>> I've tried:
>>
>>
>>
>> echo none +lirc > /sys/class/rc/rc0/protocols
>
>This worked for me:
>
>  echo lirc > /sys/class/rc/rc0/protocols
>


Nope, Still not working.. I've now tried both +lirc and lirc in that command
and neither produces the correct result.   I've also made a link in the /dev
directory from lirc to /dev/lircd but that doesn't help either. 

How can I tell if the MythTV imbedded lirc support is turned off or ignored?


Any other ideas.    It seems that the imbedded version is a little cranky so
I'd rather use lirc until it's all ironed out.   -- Unless of course I'm
doing something wrong with my configuration. 

I have the lircd.conf in the /etc/lirc directory and the .lircrc file in the
/home/mythtv/.mythtv with a link by the same name in the /home/mythtv
directory.   I haven't found a good resource yet on how this is supposed to
be set up so this is just a guess from the "old methods". 

If I press the buttons on the remote 2x quickly, sometimes I can get it to
work properly, but that's a pain and takes a VERY heavy toll on the WAF.  

Ideas? 

Thanks, 

Michael