[mythtv-users] Several lirc devices

[Fredrik Hallgarde]

Joacim J skrev:

> On Jan 27, 2008 4:34 PM, Fredrik Hallgarde <mythtv at tedde.nu 
> <mailto:mythtv at tedde.nu>> wrote:
>
>     Joacim J skrev:
>     > Hello,
>     >
>     > I have a Microsoft MCE remote which I like and it's working fine
>     with
>     > MythTV (running in production mode).
>     >
>     > However when I reboot the frontend (backend on a server) I often
>     > (always?!) gets a non working remote and checking the irw I can not
>     > get any response. Seraching for lirc devices I get two devices:
>     >
>     > ~$ ls -al /dev/lirc*
>     > crw-rw---- 1 root root 61, 0 2008-01-25 19:18 /dev/lirc0
>     > crw-rw---- 1 root root 61, 1 2008-01-25 19:18 /dev/lirc1
>     > srw-rw-rw- 1 root root     0 2008-01-25 19:25 /dev/lircd
>     >
>     > Then if I modify the "/etc/lirc/hardware.conf" to point to the other
>     > device (the one that was not used)
>     > E.g. switching from:
>     > DEVICE="/dev/lirc0"
>     > to
>     > DEVICE="/dev/lirc1"
>     >
>     > and restart the daemon it works again...
>     >
>     > I am using Ubuntu Gutsy (32-bit).
>     >
>     > Why do I get two devices?
>     > Will the line "MODULES="lirc_mceusb2"" in "/etc/lirc/hardware.conf"
>     > cause dual lirc devices?
>     >
>     > Any idea?
>     >
>     > --
>     > Regards
>     > Joacim
>     Do you have any other LIRC hardware in your box? I am thinking of
>     Hauppauge cards, integrated LCDs with a remote receiver, maybe another
>     receiver (i.e. Mac mini). All of these could cause you to have a
>     second
>     entry.
>     Did you install a cvs version of lirc without removing/disabling the
>     existing?
>
>     just a few thoughts...
>
>     Fredrik
>
>
> Yes, it seems to be the integrated remote receiver in the LCD that are 
> causing this....I am using the MCE remote receiver sine it has a 
> transmitter as well (not using it yet though)
>
> ~$ dmesg | grep lirc
> [   13.836000] lirc_dev: IR Remote Control driver registered, at major 61
> [   13.848000] lirc_mceusb2: Philips eHome USB IR Transciever and 
> Microsoft MCE 2005 Remote Control driver for LIRC $Revision: 1.33 $
> [   13.848000] lirc_mceusb2: Daniel Melander <lirc at rajidae.se 
> <mailto:lirc at rajidae.se>>, Martin Blatter <martin_a_blatter at yahoo.com 
> <mailto:martin_a_blatter at yahoo.com>>
> [   13.872000] 
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/media/lirc/lirc_imon/lirc_imon.c: 
> Driver for Soundgraph iMON MultiMedian IR/VFD, v0.3
> [   13.872000] 
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/media/lirc/lirc_imon/lirc_imon.c: 
> Venky Raju <dev at venky.ws <mailto:dev at venky.ws>>
> [   14.220000] lirc_dev: lirc_register_plugin: sample_rate: 0
> [   14.228000] lirc_mceusb2[2]: Philips eHome Infrared Transceiver on 
> usb2:2
> [   14.228000] 
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/media/lirc/lirc_imon/lirc_imon.c: 
> imon_probe: found IMON device
> [   14.228000] usbcore: registered new interface driver lirc_mceusb2
> [   14.228000] lirc_dev: lirc_register_plugin: sample_rate: 0
> [   14.228000] 
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/media/lirc/lirc_imon/lirc_imon.c: 
> imon_probe: Registered iMON plugin (minor:1)
> [   14.228000] 
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/media/lirc/lirc_imon/lirc_imon.c: 
> imon_probe: iMON device on usb<2:4> initialized
> [   14.228000] usbcore: registered new interface driver lirc_imon
> [   21.904000] 
> /build/buildd/linux-ubuntu-modules-2.6.22-2.6.22/debian/build/build-generic/media/lirc/lirc_imon/lirc_imon.c: 
> VFD port opened
>
>
>
>
> -- 
> Regards
> Joacim
Try blacklisting the lirc_imon driver (for now at least) or set up udev 
rules to ensure you know what lirc-device is which...
See previous discussion about tv-cards not appearing in the same order 
each boot etc...

Fredrik