[mythtv-users] Trouble with lirc and HD-PVR on Fedora 12

Tue Apr 13 14:18:36 UTC 2010

On 04/12/2010 10:08 PM, John Welch wrote:
> On Mon, Apr 12, 2010 at 9:57 PM, richard Woelk<richardwoelk at gmail.com>  wrote:
>> On 04/12/2010 13:37, John Welch wrote:
>>>
>>> On Sat, Apr 10, 2010 at 4:36 PM, John Welch<jrw3319 at gmail.com>    wrote:
>>>
>>>>
>>>> I have a Fedora 12 Mythtv back-end system with myth packages coming
>>>> from the ATrpms repo.  Around the turn of the year I had my HD-PVR
>>>> fully operational, including IR transmitter, using the info from the
>>>> MythTV wiki.  For various reasons I haven't used the HD-PVR for a
>>>> while, but now that I am trying to use it again I am having some
>>>> problems with lirc and the IR transmitter.  Per the HD-PVR wiki
>>>> instructions I have the lirc_zilog (and lirc_dev) modules loaded, but
>>>> yet no lirc devices exists under /dev.
>>>>
>>>> Trying to troubleshoot the issue I unloaded the lirc_zilog module and
>>>> stopped the lirc service; then I tried starting from scratch.  When I
>>>> manually load the lirc_zilog module I see the following in
>>>> /var/log/messages:
>>>> Apr 10 15:58:47 localhost kernel: lirc_dev: IR Remote Control driver
>>>> registered, major 249
>>>> Apr 10 15:58:47 localhost kernel: lirc_zilog: Zilog/Hauppauge IR
>>>> driver initializing
>>>> Apr 10 15:58:47 localhost kernel: lirc_zilog: initialization complete
>>>>
>>>> To me this seems to indicate that the module(s) loaded successfully
>>>> and if I run an lsmod the lirc_zilog and lirc_dev modules do appear.
>>>> However, I'm still not seeing an lirc device showing up in /dev.
>>>> Continuing on I restarted the lirc service.  When I do this I get
>>>> several thousand messages like the following showing up in
>>>> /var/log/messages:
>>>>
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: "2195390513" is out of range
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: error in configfile line
>>>> 30938:
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: "2195390514" is out of range
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: error in configfile line
>>>> 30940:
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: "2195390515" is out of range
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: error in configfile line
>>>> 30942:
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: "2195390541" is out of range
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: error in configfile line
>>>> 30944:
>>>> Apr 10 16:02:01 localhost lircd-0.8.6[6055]: "2195390542" is out of range
>>>>
>>>> These messages are apparently being generated due to an issue with my
>>>> lircd.conf file.  The thing is I haven't made any changes to this file
>>>> at all since I had things working.  I also re-downloaded the
>>>> lircd.conf referenced in the MythTV HD-PVR wiki page, and verified
>>>> that it is the same one that I am using.
>>>>
>>>> At this point I am stumped.  Since the time I had things working there
>>>> have been a few kernel updates and also mythtv package updates, so I
>>>> guess it is possible that one of these updates is causing the problem.
>>>>   But I haven't been able to find any info on this issue, and I have to
>>>> believe others have a similar setup.
>>>>
>>>> Any help would be appreciated.
>>>>
>>>> Thanks,
>>>> John
>>>>
>>>>
>>>
>>> Sorry to reply to my own post, but I'm still having issues with this.
>>> Can anyone at least confirm that they have this modules (lirc_zilog)
>>> and this device (the IR transmitter of the HD-PVR) working on an F12
>>> system with the latest kernel (2.6.32.11-99)?  The fact that the
>>> module appears to load OK based on the messages I am seeing seems to
>>> indicate a problem with the module and/or kernel.  But I really have
>>> no idea what I am talking about, so maybe I'm out to lunch on this
>>> assessment.  Shouldn't the lirc device be created when the module
>>> loads?  If not, is it typically created when the service is started?
>>> In either case I had this working with minimal effort with the help of
>>> the directions in the HD-PVR wiki page.  So unless the wiki is
>>> outdated something appears to be amiss.
>>>
>>> Thanks again,
>>> John
>>>
>>
>> John,
>>     I did experience this as well when I tried to set up the blaster, The big
>> remote ID numbers in lircd.conf are too big for lircd, and the daemon will
>> stop loading when it encounters these. I don't know how big is too big, but
>> removing all the the 10 digit numbers fixed it. My problem is that most of
>> the choices for my motorola STB were big numbers. I went back to my MCE USB
>> device.
>>     I also found a connection issue with the newer version of lirc. The
>> /dev/lirc0 device is created by the module loading, but what used to be
>> /dev/lircd, is now /var/run/lirc/lircd. This is created after lircd runs.
>>
>> - Richard
>>
>>
>>
>>
> Richard,
>
> Thanks you so much for the response.  I was beginning to think I was
> alone with this problem.  I don't have anything fixed yet, but at
> least you've given me a few leads to explore.  Obviously something has
> changed in the kernel module or the lirc package because as I have
> stated I did have this all working.
>
> Thanks again,
> John

This problem was raised on the lirc list a couple of weeks ago. The 
variable which holds the key code is inadvertently defined as a small 
'int'. This might well already be fixed in the lirc cvs.

For more info, check the list-list archives at:

http://sourceforge.net/mailarchive/forum.php?forum_name=lirc-list

Geoff

          Tux says: "Be regular. Eat cron flakes."