<br>All,<br><br>I'm hoping someone can point me in the right direction. I have a serial receiver that I'm trying to get working with myth.<br><br>It does work on one of my systems with an identical setup, so I don't think the problem lies with lirc, lirc_serial, or the receiver itself. The problem is, I don't see errors anywhere, it just doesn't work. I'm running FC6 with kernel
2.6.20-1.2948.fc6.<br><br>Here are the relevant log entries:<br><br>[root@localhost ~]# dmesg | grep ttyS<br>serial8250: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A<br>00:09: ttyS0 at I/O 0x3f8 (irq = 4) is a NS16550A<br><br>
[root@localhost ~]#cat /var/log/messages | grep lirc<br>May 15 20:05:15 localhost kernel: lirc_dev: no version for "struct_module" found: kernel tainted.<br>May 15 20:05:15 localhost kernel: lirc_dev: IR Remote Control driver registered, at major 61
<br>May 15 20:05:15 localhost kernel: lirc_serial: auto-detected active low receiver<br>May 15 20:05:15 localhost kernel: lirc_dev: lirc_register_plugin: sample_rate: 0<br>May 15 21:19:40 localhost lircd-0.8.2-CVS[3756]: you should specify a valid gap value
<br>May 15 21:19:40 localhost lircd-0.8.2-CVS[3756]: lircd(userspace) ready<br>May 15 21:36:04 localhost lircd-0.8.2-CVS[3756]: caught signal<br><br><br>All of which is almost exactly the same as the working setups. And yet mode2 shows nothing on the receiver. I even went as far as to load XP on this machine and used WinLirc, which was fine. Only weird thing was that I had to use COM2, but with the same IRQ I/O settings. I assumed that was because of a built-in modem or something, but maybe it's screwing with linux?
<br><br>The only other oddity is that on my working system , the dmesg | grep ttyS shows the following:<br><br>00:0a: ttyS0 at I/0 0x3f8 (irq=4) is a NS16550A<br><br>A bit different, but still nothing that would indicate an error. Any suggestions on what I can do to troubleshoot?
<br><br>thanks,<br>matt<br><br><br><br>