<br><br><div class="gmail_quote">On Sat, Jun 20, 2009 at 10:20 PM, Jarod Wilson <span dir="ltr"><<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 06/20/2009 11:06 PM, Richard Shaw wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
and now my<br>
remote doesn't work. This configuration has worked flawlessly since<br>
Fedora 8. I'm now getting some output from dmesg I don't<br>
remember seeing<br>
before:<br>
<br>
[root@calvin ~]# dmesg | grep lirc<br>
lirc_dev: IR Remote Control driver registered, major 61<br>
lirc_serial: auto-detected active low receiver<br>
<br>
<br>
Do you know if it was auto-detected as active low previously?<br>
Definitely makes a difference... You could try forcing it to active<br>
high as a test. (add modparam 'sense=0')<br>
<br>
<br>
Not sure but tried sense=0 (i.e. "modprobe lirc_serial sense=0" if<br>
that's the correct way to do it) and didn't see anything different in<br>
dmesg. It still said "low".<br>
</blockquote>
<br></div>
Hrm. That certainly shouldn't be the case... You did unload the lirc_serial module before that, right? What you should be seeing (in dmesg) is:<br>
<br>
lirc_serial: Manually using active high receiver</blockquote><div><br>Yup, did a rmmod lirc_serial (but I didn't unload lirc_dev) the first time, but as you saw in the lines below I did a modprobe -r which did unload both. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Load lirc_serial with the module param 'debug=1', see what else it<br>
says. You can try fiddling with other module options as well.<br>
<br>
<br>
I didn't see anything helpful but here's the output:<br>
</blockquote>
<br></div>
The output from modprobe isn't what's interesting, its the stuff that gets spewed into dmesg afterwards when trying to use it. :)</blockquote><div><br>It doesn't look like the module parameters are either getting passed to lirc_serial or that they're not being accepted. I'm not seeing any additional output from dmesg. Is that something I could put in my modprobe.conf configuration? <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">
Since "irw" didn't work I tried stopping the service and running<br>
irrecord to make sure it wasn't my remote config but it had an issue as<br>
well:<br>
<br>
[root@calvin modprobe.d]# irrecord test<br>
<br>
irrecord - application for recording IR-codes for usage with lirc<br>
<br>
Copyright (C) 1998,1999 Christoph Bartelmus(<a href="mailto:lirc@bartelmus.de" target="_blank">lirc@bartelmus.de</a><br></div>
<mailto:<a href="mailto:lirc@bartelmus.de" target="_blank">lirc@bartelmus.de</a>>)<div class="im"><br>
<br>
irrecord: could not get hardware features<br>
irrecord: this device driver does not support the LIRC ioctl interface<br>
irrecord: make sure you use a current version of the driver<br>
irrecord: could not init hardware (lircd running ? --> close it, check<br>
permissions)<br>
</div></blockquote>
<br>
Hrm... That's not looking particularly good... I may have vague recollections of Janne saying that was known to be busted though, even when the receiver is working properly. I really do need to dive into lirc_serial code again, but its... grotty...<br>
<br>
For the record, what kernel version is this with? Need to compare the lirc_serial code in it w/current cvs and git trees...</blockquote><div><br>2.6.27.24-170.2.68.fc10.x86_64 <br><br>I also have a Fedora 11 install running 2.6.29.4-167.fc11.x86_64 which I could move the receiver to for comparison testing if it would be helpful.<br>
</div><br></div>Thanks,<br>Richard<br>