It is likely your lircd or lircrc file that is at fault.
I have a mceusb2 and have a working lircd and lircrc file. However the double and sometimes triple entries for me were because the mceusb was trying to act as a keyboard. Once I disabled that it behaved and worked as it always had in numerous kernel releases.
If adding that file disables the whole thing my guess is your lircd file is not complete.
Can you post it and I can have a look and compare it to mine.
I went back and looked at my first post and can’t edit that post. In it I said you needed a lircrc in /etc/lirc That should have read you need a lircrd.conf file in /etc/lirc
You then of course will need a lircrc in your mythtv hidden directory and a .lircrc in your home directory.
I wouldn’t call the efforts of compiling heroic - writing the manual was more work
You are correct, lirc-0.9.0-pre1 is not really necessary. I got confused by some thread were it stated that lirc-0.9.0 better supports the now built-in support for lirc in the kernel. This may or may not be the case, I can not tell for sure.
However, the lirc package included in openSUSE 11.4 (0.8.7) works just fine with my manual steps 1.6 and 2.1 (just as you said).
However, kremotecontrol does not work - but the problem could be unrelated. See also Bug 260271 - Kremotecontrol daemon not working
kremotecontrol works fine - I mis-configured XBMC: I set “Remote control sends keyboard presses” to yes - which prevents
kremotecontrol from picking up any of the key-presses from the remote.
So for the iMON-Pad (Device ID 15c2:ffdc) I can now say:
LIRC: working
irw: working
kremotecontrol: working
XBMC: working
The only things I had to do were configure lirc in /etc/sysconfig/lirc and copy the correct lircd.conf to /etc/lirc/
Thanks for all your help in understanding lirc a little better.
This is true, (as far as I can tell at least) version 0.9.0 is being developed with the understanding that the LIRC kernel modules that used to be compiled with LIRC (and technically still can be) are merged in to the kernel and 0.9.0 is utilizing the lirc.h header file as merged into the kernel source. However, given that, the driver you are using (devinput) does not use kernel modules–it is implemented in userspace, so 0.8.7 should be just as good in your case, and in fact might be a tad more stable than the development version of 0.9.0.
Not only am I up and running, but I learned some new Linux stuff from Martin and Poorboy Willy. In the end Bruce was the man for me. Bruce, your quirks.conf file came through in eliminating the double command mess. And it worked all along. :)I’ve been testing this on a slow Atom/Ion system and the clue was patience. After a reboot there was no LIRC . . . for about 15 seconds or so. If I wait a bit before I start up MythTV, it works like a charm.
I want to thank you all you for the friendly support. Linux Rocks!
I’ve tried many tips I found in this topic but it still does not work with my Philips SRM 7500. I came a little further but still no succes. If I start irw lirc starts dumping errors:
/usr/local/sbin/lircd --nodaemon --output=/var/run/lirc/lircd --device=macShortAddress=12:34,remoteShortAddress=56:78,macPANId=9a:bc
lircd: lircd(srm7500libusb) ready, using /var/run/lirc/lircd
lircd: accepted new client on /var/run/lirc/lircd
lircd: initializing driver
lircd: 802.15.4 network parameters
lircd: macShortAddress 12:34
lircd: macPANId 9a:bc
lircd: LogicalChannel 19
lircd: remoteShortAddress 56:78
lircd: macBeaconPayload PHILIPSlinux-sxua
lircd: initializing Philips USB receiver
lircd: could not detach kernel driver: No such file or directory
lircd: initializing Philips USB receiver
lircd: could not detach kernel driver: No such file or directory
lircd: initializing Philips USB receiver
lircd: could not detach kernel driver: No such file or directory
lircd: initializing Philips USB receiver
lircd: could not detach kernel driver: No such file or directory
lircd: initializing Philips USB receiver
lircd: could not detach kernel driver: No such file or directory
[etc etc]
Hi, I tried your trick, but I still get double and triple keys from the remote. Don’t know much about X, so any ideas on how to debug why the quirks file is not working in my setup?
I get this in my boot sequence, so I believe your trick should work:
<6> 5.508035] Registered IR keymap rc-rc6-mce
<6> 5.508303] input: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/rc/rc0/input3
<6> 5.508461] rc0: Media Center Ed. eHome Infrared Remote Transceiver (0471:0815) as /devices/pci0000:00/0000:00:02.0/usb3/3-1/3-1:1.0/rc/rc0
<6> 5.508574] mceusb 3-1:1.0: Registered Philips eHome Infrared Transceiver on usb3:2
<6> 5.508686] usbcore: registered new interface driver mceusb
<6> 5.518271] lirc_dev: IR Remote Control driver registered, major 251
<6> 5.520352] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
<6> 5.520452] IR LIRC bridge handler initialized
I’ve been having similar issues with the MCE remote and found this thread very interesting to read. Hopefully it’s ok to add my questions to the thread rather than starting a new one.
I’ve been using Suse and Myth for years now and recently bought some new hardware to be able to use DVB-T in HD. One thing i’ve been holding off on is getting the MCE remote(s) to work but the day has finally come
It seems that LIRC is recognizing the USB receiver fine, and can load all the modules and start lirc. Logs indicate it is recognized but have not been able to get any meaningful output. I think my problem is that suse 11.4 recognized the keyboard as a HID and might prevent Lirc from using it? The silver arrow keys work, and the volume but that even when I do not run lirc (hence me thinking it’s seen as a HID). I’ve tried the 10-quirks.conf trick, but that does not seem to do anything. (no errors in the log either)
irw starts with no errors (also when I point it to /dev/lirc0) but no output whatsoever.
I was hoping there’s another way to prevent the remote being recognized as HID. Or is this not supposed to interfere?
all lirc modules are loaded fine (usbmce, lirc_dev). dmesg lists Media Centre Ed. eHome Infrared Remote Tranciever as registered with no errors in the logs anywhere.
Eventually, I’d like to have the keyboard working outside Myth too, so I can do some surfing etc…
So in order to follow your recommendations and fill up the configuration in /etc/sysconfig/lirc (LIRCD_DRIVER and LIRCD_DEVICE) I need to know which is the device driver. That by the way are empty fields in Suse 11.3 (but works)
