[mythtv-users] LIRC config for a Hauppauge 350

[Harry Devine]

On 12/26/2010 04:09 PM, Boleslaw Ciesielski wrote:
> On 12/26/2010 03:31 PM, Harry Devine wrote:
>> My LIRC has been working for a while, but after my upgrade to 0.24, it
>> no longer does. I have my LIRC configured as an Hauppauge 350 remote. I
>> see the following in dmesg:
>>
>> hdevine at hdevine-desktop:/etc/lirc$ dmesg |grep lirc
>> [ 51.383125] lirc_dev: IR Remote Control driver registered, major 61
>> [ 51.428885] lirc_serial: port 03f8 already in use
>> [ 51.428888] lirc_serial: use 'setserial /dev/ttySX uart none'
>> [ 51.428890] lirc_serial: or compile the serial port driver as module 
>> and
>> [ 51.428891] lirc_serial: make sure this module is loaded first
>> [712154.214756] lirc_serial: port 03f8 already in use
>> [712154.214764] lirc_serial: use 'setserial /dev/ttySX uart none'
>> [712154.214768] lirc_serial: or compile the serial port driver as module
>> and
>> [712154.214772] lirc_serial: make sure this module is loaded first
>> [926311.764260] lirc_dev: IR Remote Control driver registered, major 61
>
> You are getting the wrong driver loaded. PVR-350 uses lirc_i2c, not 
> lirc_serial.
>
> I don't know about Ubuntu but on Fedora you need a file with .modules 
> extension in /etc/sysconfig/modules with a line like this in it:
>
> modprobe lirc-i2c
>
> Bolek
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
You were right in pointing out that the wrong driver was being loaded, 
but you had them reversed.  The hardware.conf had the line 
'REMOTE_MODULES="lirc_dev lirc_i2c"'.  Since my IR receiver is a serial 
device, the lirc_i2c needed to be lirc_serial.  Changing that to 
lirc_serial and restarting lirc fixed the issue.

Thanks for the shove in the right direction!
Harry