[mythtv-users] Joy and pain

Karl Newman newmank1 at asme.org
Wed Feb 12 19:26:29 UTC 2014


On Wed, Feb 12, 2014 at 10:25 AM, Hika van den Hoven <hikavdh at gmail.com>wrote:

>  Hoi Karl,
>
>
> Wednesday, February 12, 2014, 7:21:43 PM, you wrote:
>
>
>  On Wed, Feb 12, 2014 at 10:16 AM, Hika van den Hoven <hikavdh at gmail.com>
> wrote:
> Hoi Karl,
>
>
> Wednesday, February 12, 2014, 7:11:10 PM, you 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
>
>
>
> You might be right there. I forgot the exact sequence about
> /var/run/lirc/lirc? and /dev/lirc?.
> But the /dev/lirc? device only contains information about the driver used,
> not about the physical device.
> So if both use the same driver... Also driver names can change with an
> upgrade.
>
> Well that's unfortunate. However, I'm nearly positive he is using
> different drivers (one is serial, the other is ...not serial--whatever the
> analog card uses) so you should still be able to create a unique symlink
> based on that, right? If not, he might just need to use /dev/lirc1 and hope
> the lirc device nodes are always created in that order...!
>
> Karl
>
>
> As I use Gentoo my simplest solution would be to remove unwanted drivers
> from both the kernel and lirc.
> But we will see. If it doesn't work we can try with rules on /dev/lirc?.
>

I forgot to add--I'm also on Gentoo but I believe Daryl is on Mythbuntu and
doesn't compile his own kernel, so it's probably not as simple as that for
him. Especially when it comes to eventual system upgrades which will likely
restore the removed driver... I think a more durable solution is required.

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


More information about the mythtv-users mailing list