<p>More details about ubuntu lirc init.d script problem? (I'm currently working on translating into init [upstart] scripts and want to avoid/fix problems while I'm at it ;-)</p>
<p>Craig.</p>
<div class="gmail_quote">On May 23, 2011 9:58 AM, "Jarod Wilson" <<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>> wrote:<br type="attribution">> On May 19, 2011, at 6:18 PM, John McFadden wrote:<br>
> <br>>> On Tue, May 17, 2011 at 12:23 PM, Jarod Wilson <<a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a>> wrote:<br>>>> On May 15, 2011, at 7:39 PM, John McFadden wrote:<br>>>> <br>
>>>> I have an mceusb receiver (/dev/lircd) and a USB FTDI blaster<br>>>>> (/dev/lircd1) with LIRC 0.9.0 and I can't seem to find the right way<br>>>>> to tell LIRC that the FTDI is the blaster and the mceusb is the<br>
>>>> receiver.<br>>>>> <br>>>>> When I use<br>>>>> irsend -d /dev/lircd SEND_ONCE DTA100 KEY_1<br>>>>> nothing happens as lircd is only a receiver, but I do not get an error message.<br>
>>>> <br>>>>> When I use<br>>>>> irsend -d /dev/lircd1 SEND_ONCE DTA100 KEY_1<br>>>>> I receive<br>>>>> irsend: command failed: SEND_ONCE DTA100 KEY_1<br>>>>> irsend: hardware does not support sending<br>
>>>> <br>>>>> <br>>>>> I can use other scripts to make the blaster transmit test patterns, so<br>>>>> it seems to be only an LIRC configuration issue.<br>>>>> <br>
>>>> Can anyone suggest a path forward?<br>>>> <br>>>> Output of the following, please:<br>>>> <br>>>> # ls -l /dev/lirc*<br>>>> <br>>>> Need to know how you're launching your two lircd instances too. Distro<br>
>>> and kernel version would be useful to know.<br>>>> <br>>>> <br>>> john@AMDQuad:~/Desktop$ ls -l /dev/lirc*<br>>> crw-rw---- 1 root root 61, 0 2011-05-15 12:44 /dev/lirc0<br>>> lrwxrwxrwx 1 root root 19 2011-05-15 19:28 /dev/lircd -> /var/run/lirc/lircd<br>
>> lrwxrwxrwx 1 root root 21 2011-05-15 19:28 /dev/lircd1 -><br>>> /var/run/lirc/lircd11<br>>> <br>>> I'm not sure what you mean by launching the two lircd instances, I<br>>> used the built-in Mythbuntu LIRC configuration generator to set it for<br>
>> my remote and a different blaster/STB combo and then changed<br>>> hardware.conf and lircd.conf to reflect my blaster and STB<br>>> <br>>> The system is running Mythbuntu 10.04, kernal 2.6.32-31-generic<br>
> <br>> <br>> In which case, you're launching lircds by way of the ubuntu lirc initscript,<br>> as configured by hardware.conf, which has been known to screw things up from<br>> time to time...<br>> <br>
> Halt the initscript, and try starting up two lircd instances by hand with<br>> all the necessary args passed to them, see if things behave any better.<br>> <br>> -- <br>> Jarod Wilson<br>> <a href="mailto:jarod@wilsonet.com">jarod@wilsonet.com</a><br>
> <br>> <br>> <br>> <br>> ------------------------------------------------------------------------------<br>> What Every C/C++ and Fortran developer Should Know!<br>> Read this article and learn how Intel has extended the reach of its <br>
> next-generation tools to help Windows* and Linux* C/C++ and Fortran <br>> developers boost performance applications - including clusters. <br>> <a href="http://p.sf.net/sfu/intel-dev2devmay">http://p.sf.net/sfu/intel-dev2devmay</a><br>
</div>