[mythtv-users] Joy and pain

[Daryl McDonald]

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
>
>>
>> I can tell you how I solved my same problem and I will provide my setup, udev and lirc files but
>> I use OpenSUSE, not ubuntu. The main difference in lirc is that in my distro there is no hardware.conf
>> file which I think controls blasting in *buntu, the only service config file for lirc is /etc/sysconfig/lirc.conf
>> I hope this won't confuse matters much. (There is a /etc/lirc/lircd.conf file, but it's used to define the remotes/protocols.)
>>
>> Anyway, I have a "Hauppauge Media Center Ed. eHome Infrared Remote Transceiver (0609:0334)", which I used
>> to have setup in lirc using the "devinput" driver, but that doesn't support blasting and I switched to the "default"
>> driver that does. It uses the mceusb kernel module, yours could be using a different one.
>>
>> I found the device name in /dev/input/by-id: (it's the last one)
>>
>> al2kpro:~ # la /dev/input/by-id/
>> σύνολο 0
>> drwxr-xr-x 2 root root 160 Νοέ   5 08:21 .
>> drwxr-xr-x 4 root root 560 Ιαν  24 14:21 ..
>> lrwxrwxrwx 1 root root   9 Ιαν  24 14:21 usb-05af_Rx504B_Ver:3.03-event-kbd -> ../event0
>> lrwxrwxrwx 1 root root   9 Ιαν  24 14:21 usb-05af_Rx504B_Ver:3.03-event-mouse -> ../event1
>> lrwxrwxrwx 1 root root   9 Ιαν  24 14:21 usb-05af_Rx504B_Ver:3.03-if01-event-mouse -> ../event1
>> lrwxrwxrwx 1 root root   9 Ιαν  24 14:21 usb-05af_Rx504B_Ver:3.03-if01-mouse -> ../mouse0
>> lrwxrwxrwx 1 root root   9 Ιαν  24 14:21 usb-05af_Rx504B_Ver:3.03-mouse -> ../mouse0
>> lrwxrwxrwx 1 root root   9 Ιαν  24 14:21 usb-SMK_CORPORATION_MCE_TRANCEIVR_Emulator_Device_2006_PA100707131807G-event-if00 -> ../event4
>
> daryl at daryl-A780L3C:~$ la /dev/input/by-id/
> usb-RCMCU_iPazzPort-event-kbd
> usb-SIGMACHIP_Usb_Mouse-event-mouse  usb-USB_USB_Keykoard-event-kbd
> usb-RCMCU_iPazzPort-if01-event-mouse  usb-SIGMACHIP_Usb_Mouse-mouse
> usb-RCMCU_iPazzPort-if01-mouse        usb-USB_USB_Keykoard-event-if01
>
> To me, the above is talking about one device, my "ipazzPort", a mini
> wireless keyboard/air mouse combo. I don't see anything about PCI IR
> devices or serial IR devices. My IR blaster has a RS232 serial port
> connector which is in turn connected to a 9 pin com on the mobo.
>>
>> then I found the udev info for the device:
>>
>> al2kpro:~ # udevadm info -a -p $(udevadm info -q path -n /dev/input/by-id/usb-
>
> So I am stymied as to what udevadm to search.
>>
>> Good luck on your new endeavour, ;)
>>
>> Yianni.
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>> http://wiki.mythtv.org/Mailing_List_etiquette
>> MythTV Forums: https://forum.mythtv.org
>
> Thanks Yianni and Hika.        Daryl

And from Hika's direction:

daryl at daryl-A780L3C:~$ (udevadm info --query path --name=/dev/input/event?)
device node not found
daryl at daryl-A780L3C:~$

I'm lost, but I don't give up!   Thanks again.     Daryl