[mythtv-users] Hauppauge PVR 350 and LIRC setting up

Thu Apr 1 00:42:39 UTC 2010

On 3/31/2010 5:20 PM, Marc Chamberlin wrote:
> On 3/31/2010 2:54 PM, Jarod Wilson wrote:
>> On Wed, Mar 31, 2010 at 5:22 PM, Marc Chamberlin
>> <marc at marcchamberlin.com>  wrote:
>>> On 3/31/2010 1:11 PM, Jarod Wilson wrote:
>>>> On Wed, Mar 31, 2010 at 3:36 PM, Scott<pickle136 at sbcglobal.net>    
>>>> wrote:
>>>>
>>>>> On 3/31/2010 3:27 PM, Marc Chamberlin wrote:
>>>>>
>>>>>>   From my searching around on the internet, and looking through 
>>>>>> this and
>>>>>> other mail lists, I suspect this may have been answered 
>>>>>> somewhere, but I
>>>>>> was
>>>>>> not able to find any answers that I could grok.. (but lots of 
>>>>>> chatter
>>>>>> about
>>>>>> this remote!)  So with possible apologies in advance, I wonder if 
>>>>>> some
>>>>>> kind
>>>>>> guru could help me get my Hauppauge PVR-350 (gray) remote completely
>>>>>> communicating with my media computer? I am running SuSE 11.2 
>>>>>> x86-64 and
>>>>>> I
>>>>>> have installed version 0.8.5.4.1 of lirc and version
>>>>>> 0.8.5_2.6.31.5_0.1-4.4
>>>>>> of the LIRC kernel modules. Following instructions I have also 
>>>>>> installed
>>>>>> the
>>>>>> kernel modules for lirc-i2c and lirc-dev.
>>>>>>
>>>>>> I am headed towards getting this working for mythTV. I have 
>>>>>> installed
>>>>>> and
>>>>>> configure the .lircrc, lircd.conf and the lirc file in 
>>>>>> /etc/sysconfig/
>>>>>> following instructions as best as I could. I have got it going 
>>>>>> partially
>>>>>> in
>>>>>> that using ircat I can see the number keys are being recognized, 
>>>>>> as well
>>>>>> as
>>>>>> the volume up/down button but nothing else.
>>>>>>
>>>>>> I dunno what files or command outputs I should include so will wait
>>>>>> until
>>>>>> I hear further.. So anyone willing to guide me out of these 
>>>>>> woods? Or
>>>>>> point
>>>>>> me to a good website that explains in easy to understand terms 
>>>>>> what to
>>>>>> do?
>>>>>> Thanks in advance...
>>>>>>
>>>>>>
>>>>>>   Marc..
>>>>>>
>>>>>>
>>>>> what do you get from IRW?
>>>>> most likely you see some keys but not other than the button 
>>>>> definitions
>>>>> in
>>>>> the lircd.conf arnt right. Install and look in the lirc remotes 
>>>>> package
>>>>> you
>>>>> might find the right remote info in there. (FYI theres an newer lirc
>>>>> 0.8.6
>>>>> in a repo called vdr, but you your case that 0.8.5 should work)
>>>>> lircrc only matter once you want to use the remote in lirc
>>>>>
>>>> Not so sure about lirc 0.8.5 working here. I believe there were
>>>> numerous i2c changes in 2.6.31 that made lirc_i2c non-functional, and
>>>> they weren't fixed until after lirc 0.8.5 was released. I could be
>>>> misremembering though. dmesg output from lirc_i2c module load time
>>>> would likely say for sure.
>> I also fail at reading. You said you were getting key presses, just
>> not into mythtv. However...
> Sorry for the confusion Jarod - I haven't gotten as far as getting 
> mythtv configured for running from a remote yet... Trying to take baby 
> steps to get there, so right now I am focused on getting the lirc 
> daemon to at least recognize the key presses from my Hauppauge 
> remote... And so far, using either ircat or irw I can only see that it 
> is responding to just the numeric and volume up/down keys. None of the 
> other keys, for example channel up/down produce any response yet...
>
> (This project will get even more interesting too... I got two other 
> remotes that I am going to want lirc to handle for me as well, but one 
> remote at a time....)
>> ...your dmesg output shows ir-kbd-i2c binding to the ir receiver, not
>> lirc_i2c. That makes a significant difference. The
>> lircd.conf.hauppauge config file is for use with lirc_i2c. For
>> ir-kbd-i2c, assuming the key map is correct for your remote, you'd
>> need to use lircd.conf.devinput, and tell lircd to use its devinput
>> driver mode pointed at the appropriate /dev/input/foo, rather than
>> using its default driver mode (lirc kernel driver) pointed at
>> /dev/lirc0.
>>
> Ok now you lost me! And I apologize for my beginners ignorance.  What 
> is a key map?  Is that the .lircrc file that I have to set up for 
> mythTV?   Over in the /usr/share/lirc/remotes/devinput directory I 
> found a file named lircd.conf.devinput, is this the file I should copy 
> to /etc/lirc/lircd.conf?
>
> I am using SuSE 11.2 which comes with a tool called YaST that has a 
> utility to configure the TV card and part of that sets up the 
> configuration for the lirc daemon. This configuration file is located 
> at /etc/sysconfig/lirc  and I noted that YaST configured the 
> LIRC_MODULE="ir_kbd_i2c" but it sets the LIRCD_DRIVER="/dev/lircd"   
> Under /dev I see a link for lircd -> /var/run/lirc/lircd and  under 
> /dev/input I see a number of devices (event0 event1 ... event7 ir (ir 
> is a link to event7) mice mouse) and sub directories (by-id by-path) 
> whose purpose I don't comprehend....  Should I point the LIRCD_DRIVER 
> to one of these?
>
> Thanks again for your patience and help...   Marc..
>

Oh boy, now my confusion level just deepened! I thought I was getting 
output indications from my Hauppauge remote when I was running IRCAT or 
IRW...  But I just accidentally discovered that in fact I get these 
indications of a key press from the remote in a plain shell. In other 
words the few keys that seem to work, act as if they are simply the same 
as pressing the corresponding key on a real keyboard! So I am guessing 
that this "key map" config file, whatever that is (help?) must somehow 
map all the buttons of the Hauppauge remote into either simple keys or 
possibly strings? I think I need a pointer to some documentation that 
describes this... And on how these "key map(s)" gets mapped to different 
applications, such as for mythTV or xine or....

    Marc..

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6464 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mythtv.org/pipermail/mythtv-users/attachments/20100331/6dfc8e97/attachment-0001.bin>