I had a similar problem where the lirc-imon module wasn't loading
although lirc-dev was. I then tried to manually load lirc-imon by
Then by looking at dmesg it implied that I had a bad option. It turned
out that I had two copies of the lirc-dev module. One was in
/lib/modules/(kernel version)/misc and the other in
/lib/modules/(kernel version)/kernel/drivers/media/IR. By removing both
of them and then re-installing the lirc drivers from source the problem
was fixed. I'm not sure if the latter was installed as part of the
openSUSE package or when I recompiled the kernel and erroneously had the
lirc modules compiled too. (Bound to be one of them).
Until the lirc-imon driver is loaded you won't see it listed under
and the directory may not exist at all.
On 01/29/11 12:58, Jarod Wilson wrote:
> On Jan 28, 2011, at 4:48 PM, Cory Coager wrote:
>> On Fri, Jan 28, 2011 at 04:37:44PM -0500, Jarod Wilson wrote:
>>> Are you sure /dev/input/event5 is the imon device? Its actually better to
>>> use /dev/input/by-id/<imon description>-if00 if I'm thinking clearly.
>>> The imon driver definitely does work with 0.9.0-pre1 though, I have five
>>> different imon devices and they all function. :)
>> I can tell by process of elimination:
>> mythtv ~ # ls -l /dev/input/by-id/
>> lrwxrwxrwx 1 root root 9 Jan 28 02:49 usb-1430_RedOctane_USB_pad-event-joystick -> ../event1
>> lrwxrwxrwx 1 root root 6 Jan 28 02:49 usb-1430_RedOctane_USB_pad-joystick -> ../js0
>> lrwxrwxrwx 1 root root 9 Jan 28 02:49 usb-Logitech_USB_Receiver_1C9DDB-event-kbd -> ../event2
>> lrwxrwxrwx 1 root root 9 Jan 28 02:49 usb-Logitech_USB_Receiver_1C9DDB-event-mouse -> ../event3
>> lrwxrwxrwx 1 root root 9 Jan 28 02:49 usb-Logitech_USB_Receiver_1C9DDB-mouse -> ../mouse0
>> lrwxrwxrwx 1 root root 9 Jan 28 02:49 usb-RedOctane_RedOctane_USB_Pad-event-joystick -> ../event4
>> lrwxrwxrwx 1 root root 6 Jan 28 02:49 usb-RedOctane_RedOctane_USB_Pad-joystick -> ../js1
>> I don't see a device for imon in /dev/input/by-id
> That's a problem. What do you see in dmesg wrt the imon device? Looks to
> me like the driver isn't properly loading or binding to anything.