[mythtv-users] Joy and pain

[Karl Newman]

On Wed, Feb 12, 2014 at 10:11 AM, Karl Newman <newmank1 at asme.org> wrote:

> On Wed, Feb 12, 2014 at 10:08 AM, Hika van den Hoven <hikavdh at gmail.com>wrote:
>
>>  Hoi Karl,
>>
>>
>> Wednesday, February 12, 2014, 7:02:19 PM, you wrote:
>>
>>
>>  On Wed, Feb 12, 2014 at 9:45 AM, Daryl McDonald <darylangela at gmail.com>
>> wrote:
>> On Wed, Feb 12, 2014 at 12:37 PM, Hika van den Hoven <hikavdh at gmail.com>
>> wrote:
>> > Hoi Daryl,
>> >
>> > Wednesday, February 12, 2014, 6:31:36 PM, you wrote:
>> >
>> >> On Wed, Feb 12, 2014 at 12:28 PM, Hika van den Hoven <
>> hikavdh at gmail.com> wrote:
>> >>> Hoi Daryl,
>> >>>
>> >>> Wednesday, February 12, 2014, 6:26:07 PM, you wrote:
>> >>>
>> >>>> On Wed, Feb 12, 2014 at 12:11 PM, Daryl McDonald <
>> darylangela at gmail.com> wrote:
>> >>>>> On Wed, Feb 12, 2014 at 12:02 PM, Daryl McDonald <
>> darylangela at gmail.com> wrote:
>> >>>>>> On Wed, Feb 12, 2014 at 3:53 AM, Yianni <yiannividalis at hotmail.com>
>> wrote:
>> >>>>>>> Hi, Daryl.
>> >>>>>>>
>> >>>>>>> I can see this turning into another udev-rules marathon!
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>> None of the cards are blaster capable, so I use a serial port IR
>> >>>>>>>> blaster. The new card is a PCTV 800i, I suppose pulling it would
>> test
>> >>>>>>>> if it is having an adverse effect on the IR baster, is there an
>> easier
>> >>>>>>>> way?
>> >>>>>>>
>> >>>>>>> I think Hika is right, most analog cards have ir (even without
>> the blasting capability)
>> >>>>>>> and your /dev/input/ devices must have changed their numbering,
>> possibly creating more than one /dev/lirc device
>> >>>>>>> (ls -lah /dev/lirc* ????????)
>> >>>>>>
>> >>>>>> daryl at daryl-A780L3C:~$ ls -lah /dev/lirc*
>> >>>>>> crw------- 1 root root 250, 0 Feb 12 11:05 /dev/lirc0
>> >>>>>> crw------- 1 root root 250, 1 Feb 12 11:05 /dev/lirc1
>> >>>>>> lrwxrwxrwx 1 root root     19 Feb 12 11:05 /dev/lircd ->
>> /var/run/lirc/lircd
>>
>> Hika,
>>
>> I think you're having Daryl looking for the wrong devices (in
>> /dev/input/XXX). I think you need to focus on the /dev/lirc0 and /dev/lirc1
>> and the associated lircd configuration. It would seem that the analog card
>> triggers the creation of /dev/lirc0, which bumps up the serial device Daryl
>> was using to /dev/lirc1. So you need to come up with a udev rule to create
>> a symlink for the device which is connected to /dev/lirc1 and then use that
>> symlink name in the command for the lircd daemon.
>> Karl
>>
>> /dev/lirc0 and /dev/lirc1 are created by the lird daemon. By instructing
>> the daemon properly you get only only /dev/lirc0 which is always the
>> right one.
>>
>>
> I think /dev/lirc0 and /dev/lirc1 are created by the modules or drivers.
> You have to connect the lircd daemon to the right device with the -d
> command line option.
>
> Karl
>

/dev/lircd *is* created by the daemon, however. That may be what you're
thinking of. Also I think the /dev/input/event... devices cannot take
output commands (i.e., I don't think you can't use those devices for
blasters).

Karl
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20140212/18e93a75/attachment.html>