[mythtv-users] Hauppauge grey remote with homemade serial IR receiver in MythTV 0.26 and Fedora 19

[Bob Shanteau]

On 9/1/2013 3:55 PM, Stephen Worthington wrote:
> On Sun, 01 Sep 2013 12:59:03 -0700, you wrote:
>> On 26 August 2013 04:54, Bob Shanteau <rmshant at gmail.com> wrote:
>>> I have installed MythTV in Fedora 19 on a test box mostly following 
>>> these instructions, except using RPM Fusion and the Software Install 
>>> GUI instead of yum:
>>> <http://www.mythtv.org/wiki/Installing_MythTV_on_Fedora>
>>>
>>> Now I want to get my Hauppauge grey remote working with a homemade 
>>> serial receiver, which are currently working in MythDora 12.23, but 
>>> I have not been successful. I copied lircd.conf and .lircrc from the 
>>> MythDora installation to /etc/lirc and ~, respectively, on the test 
>>> box, but what now? (I've listed those files below my signature.)
>>>
>>> The documentation on the lirc.org page is not working right now, so 
>>> I installed lirc-docs. Those instructions assume you are compiling 
>>> LIRC from scratch, which I am not. According to this page, the LIRC 
>>> modules are already in the kernel.
>>> <http://www.mythtv.org/wiki/LIRC>
>>
>> Could we please get back on-topic? I am using a serial homemade 
>> receiver, not an MCE receiver, and I am using Fedora 19, not Ubuntu. 
>> So all this stuff about hardware.conf and so forth does not apply to 
>> my problem. And does Fedora even use ir-keytables?
>>
>> I have installed LIRC, but  I just tried running "ls -la /dev/lirc*" 
>> and there were no such files. So I'm not even getting to first base.
>
> Yes, Fedora too has had the IR drivers move into the kernel, so it 
> will be using ir-keytable (or some equivalent software).
>
> So what driver does your IR receiver use?  Can you see it loading in 
> the log files?  In Mythbuntu, that would be in dmesg or kern.log, but 
> I have no idea how Fedora does its log files these days.
>
>  You mentioned doing:
>
>    modprobe lirc_serial
>
> When you do that, if lirc_serial is the driver, then you should see 
> new lines in the log files saying what device the lirc_serial driver 
> created.
>
> Or if lirc_serial is loading already at boot time, the log lines from 
> it may be hard to find, so if your IR receiver is a USB one, just 
> unplug it and plug it in again to get it to log what it does again. If 
> it is not a USB device, you can get the same effect by unloading and 
> reloading the driver:
>
>   modprobe -r lirc_serial
>   modprobe lirc_serial

Here is my output:

---
[root at localhost ~]# dmesg | grep lirc
[root at localhost ~]# modprobe lirc_serial
[root at localhost ~]# dmesg | grep lirc
[  257.347777] lirc_dev: IR Remote Control driver registered, major 248
[  257.379360] lirc_serial: module is from the staging directory, the 
quality is unknown, you have been warned.
[  257.380159] lirc_serial lirc_serial.0: port 03f8 already in use
[  257.380167] lirc_serial lirc_serial.0: use 'setserial /dev/ttySX uart 
none'
[  257.380172] lirc_serial lirc_serial.0: or compile the serial port 
driver as module and
[  257.380177] lirc_serial lirc_serial.0: make sure this module is 
loaded first
[  257.380196] lirc_serial: probe of lirc_serial.0 failed with error -16
[  257.381092] platform lirc_serial.0: lirc_dev: driver lirc_serial 
registered at minor = 0
[root at localhost ~]# setserial /dev/ttyS0 uart none
bash: setserial: command not found...
[root at localhost ~]# ir-keytables
bash: ir-keytables: command not found...
---

Bob Shanteau