Linux Infrared Remote Control

On Apr 28, 2011, at 4:37 AM, Adrian C. wrote:

> Hello, 
> I have a home-made IR receiver which I used for 7-8 years. I built a new 
> machine for multimedia and lirc_serial is not functioning.
> 
> Here are the setups compared:
> 
> old: linux 2.6.18, lirc 0.8.0
> new: linux 2.6.38.4 lirc-utils 0.9.0
> 
> 
> I had some software trouble over the years, nothing I couldn't handle 
> tho, but this one really got me crazy. The receiver simply does not 
> receive any signals after everything I tried.
> 
> old serial port as seen in dmesg:
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 
> new serial port as seen in dmesg:
> serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
> 
> old modprobe.conf:
> options lirc_serial irq=4 io=0x3f8
> new modprobe.conf:
> identical to above
> 
> 
> old dmesg: 
> kernel: lirc_dev: IR Remote Control driver registered, at major 61 
> kernel: lirc_dev: lirc_register_plugin: sample_rate: 0
> kernel: lirc_serial: auto-detected active low receiver
> 
> new dmesg (with debug enabled): 
> [5.545067] lirc_dev: IR Remote Control driver registered, major 252 
> [12.462334] lirc_serial: module is from the staging directory, the quality is unknown, you have been warned.
> [12.463211] lirc_serial: in init_timing_params, freq=38000 pulse=3368, space=3368
> [12.463213] lirc_serial: Manually using active low receiver
> [12.463314] lirc_serial lirc_serial.0: lirc_dev: driver lirc_serial registered at minor = 0
> 
> I forced active low because it was reporting active high, which produced 
> no results with mode2, and from what I remember usually means no 
> receiver was detected.
> 
> 
> old device node:
> crw-rw---- 1 root root 61, 0 2009-01-02 01:32 /dev/lirc0
> 
> new device node:
> crw------- 1 root root 252, 0 Apr 28 10:08 /dev/lirc0
> 
> 
> I start mode2 and nothing happens. Blank. I re-connect the receiver to 
> the old machine and it gets the signals. I'm really stuck on this, it's 
> too important to get over it, I need a remote to watch TV. Please let me 
> know what else I can do to debug.

Not sure. I just tried one of my serial receivers with a 2.6.38.4
Fedora kernel, and it works just fine. Are you absolutely certain
on lircd version? (which lircd, lircd --version).

-- 
Jarod Wilson
jarod@...

On Thu, 28 Apr 2011, Jarod Wilson wrote:

> Are you absolutely certain on lircd version?

Yes.

Of course, this latest kernel has Lirc modules inclued, and where the 
old one has only lirc_dev and lirc_serial modules loaded this one has: 

lirc_serial             7742  3 
ir_lirc_codec           3727  0 
lirc_dev                7803  2 lirc_serial,ir_lirc_codec
rc_core                12840  7 
ir_lirc_codec,ir_sony_decoder,ir_jvc_decoder,ir_rc6_decoder,ir_rc5_decoder,ir_nec_decoder,mantis_core

For a moment I was thinking that rc and ir modules could be interfering, 
so I blacklisted them (which broke my DVB hardware btw), but it didn't 
help. mode2 was silent.

I have another receiver that plugs into DVB hardware. I was hoping I 
could use that as backup but it failed utterly. So I can only rely on 
the good old COM receiver.

On Thu, 28 Apr 2011, Jarod Wilson wrote:

> I just tried one of my serial receivers with a 2.6.38.4 Fedora kernel, 
> and it works just fine

Tested on latest SuSE, 11.4 with linux 2.6.37. It was no good, receiver 
is not detected.

On May 2, 2011, at 7:51 PM, Adrian C. wrote:

> On Thu, 28 Apr 2011, Jarod Wilson wrote:
> 
>> I just tried one of my serial receivers with a 2.6.38.4 Fedora kernel, 
>> and it works just fine
> 
> Tested on latest SuSE, 11.4 with linux 2.6.37. It was no good, receiver 
> is not detected.

I'm assuming there's some key difference between your hardware and mine
that I don't currently comprehend, but you could try a Fedora 15 live
image to be absolutely certain.

-- 
Jarod Wilson
jarod@...