I'm using a universal remote programmed with Hauppauge codes with the 
MCEUSB2 receiver.  It works fine.

Ian Service wrote:
> If you're using the MCE IR receiver, you have to use the MCE remote.  
> You can get the codes to install into your /etc/lircd.conf by getting 
> this file: http://www.lirc.org/remotes.tar.bz2 
> <http://www.lirc.org/remotes.tar.bz2> and roaming through to find the 
> best match.
>
> In all of my testing I've found that only MCE remotes work with MCE 
> receivers and Hauppauge remotes with Hauppauge cards, unless you can 
> get a universal to impersonate those remotes.
>
> - Ian
>
> On 11/28/06, *David Fishburn* <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
>
>
>     Ubuntu Edgy
>     Kernel 2.6.18.1 <http://2.6.18.1>
>     Ivtv 0.8.1
>     Lirc lirc-0.8.1pre2
>
>     I have been trying to get the remote up and running.
>
>     I had a different thread attempting to use lirc_i2c:
>     
> http://www.gossamer-threads.com/lists/ivtv/users/33057?search_string=whistle
>     %20sound;#33057
>
>
>     The problem with using lirc_i2c resulted in:
>     [ 44.670400] lirc_dev: IR Remote Control driver registered, at
>     major 61
>     [ 44.681445] lirc_i2c: no version for "lirc_unregister_plugin"
>     found: kernel
>     tainted.
>
>     I could never modprobe anything.
>
>
>     My current attempt is to use lirc_mceusb2.  I have seen other people
>     indicate they are using it with success.  The HowTo I am following is:
>     http://www.mythtv.org/wiki/index.php/LIRC_on_Ubuntu_Edgy_Eft
>
>
>     modprobe lirc_mceusb2
>     dmesg | tail
>
>     [   33.489434] lirc_dev: IR Remote Control driver registered, at
>     major 61
>     [   33.497416] lirc_mceusb2: no version for "lirc_get_pdata"
>     found: kernel
>     tainted.
>     [   33.497831] lirc_mceusb2: USB remote driver for LIRC v0.23
>     [   33.497834] lirc_mceusb2: Martin Blatter
>     <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>,
>     Daniel Melander < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>>
>     [   33.874817] lirc_dev: lirc_register_plugin: sample_rate: 0
>     [   33.880644] lirc_mceusb2[2]: SMK eHome Infrared Transceiver on
>     usb1:2
>     [   33.880672] usbcore: registered new driver lirc_mceusb2
>
>
>     [EMAIL PROTECTED]:/etc/X11# ls -la /dev/lirc*
>     crw-rw---- 1 root root 61, 0 2006-11-28 06:49 /dev/lirc0
>     srw-rw-rw- 1 root root     0 2006-11-28 07:04 /dev/lircd
>     prw-r--r-- 1 root root     0 2006-11-28 06:49 /dev/lircm
>
>
>     mode2 -d /dev/lirc0
>
>     Pressing a key:
>     [EMAIL PROTECTED]:/etc/X11# mode2 -d /dev/lirc0
>     space 95250
>     pulse 2750
>     space 750
>     pulse 550
>     ...
>
>
>     Edit /modprobe/aliases
>
>     vim /etc/modprobe.d/aliases
>     alias char-major-61 lirc_mceusb2
>
>
>     Given my machine uses /dev/lirc0 not /dev/lirc/0, I added:
>
>     vim /usr/src/lirc-0.8.1pre2/contrib/lirc.rules
>     KERNEL="lirc[0-9]*",    NAME="lirc%n", MODE="0666"
>
>
>     mv /usr/src/lirc-0.8.1pre2/contrib/lirc.rules
>     /etc/udev/rules.d/90-lirc.rules
>     mv /etc/lircmd.conf /etc/lirc/
>     mv /etc/lircd.conf /etc/lirc/
>
>
>     Any reason for 90-lirc.rules?  Thought it might have been
>     61-lirc.rules?
>
>
>
>     [EMAIL PROTECTED]:/etc/X11# /etc/init.d/lirc start
>     Starting lirc daemon: lircd lircmd.
>
>     [EMAIL PROTECTED]:/etc/X11# ps ax |grep lirc
>     31918 ?        Ss     0:00 /usr/sbin/lircd --device=/dev/lirc0
>     31920 ?        Ss     0:00 /usr/sbin/lircmd
>     31932 pts/0    R+     0:00 grep lirc
>
>
>     [EMAIL PROTECTED]:/etc/X11# irw
>
>     Pressing any keys results in nothing.  CTRL-C to quit.
>
>
>     Any ideas on why irw does not respond?
>
>     I am not positive what entries to use in /etc/lircd.conf, I used
>     this entry:
>     
> http://lirc.cvs.sourceforge.net/lirc/lirc/remotes/hauppauge/lircd.conf.haupp
>     
> <http://lirc.cvs.sourceforge.net/lirc/lirc/remotes/hauppauge/lircd.conf.haupp>
>     auge?revision=5.4&view=markup
>
>     But I am not sure if I should use something else since I went the
>     mceusb2
>     instead of the i2c route.
>
>
>     [EMAIL PROTECTED]:/etc# less /etc/lirc/hardware.conf
>     # /etc/lirc/hardware.conf
>     #
>     # Arguments which will be used when launching lircd
>     LIRCD_ARGS=""
>
>     #Don't start lircmd even if there seems to be a good config file
>     #START_LIRCMD=false
>
>     #Try to load appropriate kernel modules
>     LOAD_MODULES=true
>
>     # Run "lircd --driver=help" for a list of supported drivers.
>     DRIVER=""
>     # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc0 will be
>     # If DEVICE is set to /dev/lirc and devfs is in use /dev/lirc/0
>     will be
>     # automatically used instead
>     DEVICE=""
>     MODULES="lirc_mceusb2"
>     # MODULES="lirc_i2c"
>
>     # Default configuration files for your hardware if any
>     LIRCD_CONF=""
>     LIRCMD_CONF=""
>
>
>     I also have the lircd.conf file in /etc/lirc and /etc.  Not sure
>     why it is
>     in both or which should be the correct location.
>
>
>
>
>     Not sure how to move forward from here.
>
>     TIA,
>     Dave
>
>
>
>
>
>
>     _______________________________________________
>     ivtv-users mailing list
>     [email protected] <mailto:[email protected]>
>     http://ivtvdriver.org/mailman/listinfo/ivtv-users
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> ivtv-users mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-users


_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users

Reply via email to