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