<br><br>
<div><span class="gmail_quote">On 5/16/07, <b class="gmail_sendername">R. G. Newbury</b> <<a href="mailto:newbury@mandamus.org">newbury@mandamus.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">matt lutz wrote:<br>> All,<br>><br>> I'm hoping someone can point me in the right direction. I have a serial
<br>> 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<br>> the problem lies with lirc, lirc_serial, or the receiver itself. The
<br>> problem is, I don't see errors anywhere, it just doesn't work. I'm running<br>> 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"
<br>> found: kernel tainted.<br>> May 15 20:05:15 localhost kernel: lirc_dev: IR Remote Control driver<br>> registered, at major 61<br>> May 15 20:05:15 localhost kernel: lirc_serial: auto-detected active low<br>
> receiver<br>> May 15 20:05:15 localhost kernel: lirc_dev: lirc_register_plugin:<br>> sample_rate: 0<br>> May 15 21:19:40 localhost lircd-0.8.2-CVS[3756]: you should specify a valid<br>> 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<br>> mode2 shows nothing on the receiver. I even went as far as to load XP on
<br>> this machine and used WinLirc, which was fine. Only weird thing was that I<br>> had to use COM2, but with the same IRQ I/O settings. I assumed that was<br>> because of a built-in modem or something, but maybe it's screwing with
<br>> linux?<br>><br>> The only other oddity is that on my working system , the dmesg | grep ttyS<br>> 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
<br>> suggestions on what I can do to troubleshoot?<br>><br><br>2 things:<br>1 mode2 only works if lircd is NOT running. Run lsmodf and then<br>'modprobe -r lirc_your_driver' to make sure that mode2 can grab the
<br>hardware to see yo7ur keypresses.<br>2. Run mode2 with the -d option to point to the correct hardwarew point<br>in /dev. It is quite possible that mode2 is just looking in the wrong<br>place. Make a sym-link to /dev/lirc.
<br><br>Geoff<br><br><br><br>--<br> R. Geoffrey Newbury<br><br> Helping with the HTTP issue<br><a href="<a href="http://www.w3.org/Protocols/">http://www.w3.org/Protocols/</a>">HTTP</a>
<br>_______________________________________________<br>mythtv-users mailing list<br><a href="mailto:mythtv-users@mythtv.org">mythtv-users@mythtv.org</a><br><a href="http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users">
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users</a><br></blockquote></div>
<div> </div>
<div> </div>
<div> </div>
<div>Thanks for the reply. I definately do not have lircd running when I use mode2. I'm not sure why you want me to do a 'modprobe -r lirc_serial' though.. that removes the lirc module which definately causes mode2 to fail. Can you elaborate on that?
</div>
<div> </div>
<div>As for using the "-d" flag on mode2, I've definately done that. It's looking at the correct device.</div>
<div> </div>
<div>matt</div>
<div><br> </div>