6:27 p.m.
I've recently purchased a ir remote (for use with MythTV) and it's
designed for Windows Media Center, which means is should work fine with
the lirc_mceusb2 drivers. In fact, the manufacturers seem so confident
it just works, that they don't include drivers (for Windows). Whether
or not this means it's safe to assume that it will work with lirc is
open for debate, but for the moment is irrelevant.
The receiver is USB based, but when I plug it in, it doesn't
automatically load the lirc_mceusb2 modules. (I've another UCB based IR
receiver that when plugged in see the the lirc modules loaded, so I'm
pretty confident that this should happen).
What part of fedora (should) tell the system to load the modules when
this device is plugged in? I'm keen to test this device and see if I
can get it working.
When I plug the device in /var/log/messages shows:
Jul 13 09:25:09 moose kernel: usb 5-1: new full speed USB device using uhci_hcd and
address 5
Jul 13 09:25:09 moose kernel: usb 5-1: New USB device found, idVendor=147a,
idProduct=e03c
Jul 13 09:25:09 moose kernel: usb 5-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Jul 13 09:25:09 moose kernel: usb 5-1: Product: eHome Infrared Transceiver
Jul 13 09:25:09 moose kernel: usb 5-1: Manufacturer: Formosa21
Jul 13 09:25:09 moose kernel: usb 5-1: SerialNumber: 00100186
Jul 13 09:25:09 moose kernel: usb 5-1: configuration #1 chosen from 1 choice
Jul 13 09:25:19 moose kernel: generic-usb 0003:147A:E03C.0008: timeout initializing
reports
Jul 13 09:25:19 moose kernel: generic-usb 0003:147A:E03C.0008: hiddev97,hidraw2: USB HID
v1.00 Device [Formosa21 eHome Infrared Transceiver] on usb-0000:00:1d.3-1/input1
hope someone can help me test this device. If the manufacturers claims
are correct, it shouldn't take too much to get this device working, and
then I'd be happy to contact various upstreams to let them know that the
deivce works and what is needed to get it working.
regards
Rodd
6:44 p.m.
On Mon, 2009-07-13 at 09:27 +1000, Rodd Clarkson wrote:
I've recently purchased a ir remote (for use with MythTV) and
it's
designed for Windows Media Center, which means is should work fine with
the lirc_mceusb2 drivers. In fact, the manufacturers seem so confident
it just works, that they don't include drivers (for Windows). Whether
or not this means it's safe to assume that it will work with lirc is
open for debate, but for the moment is irrelevant.
The receiver is USB based, but when I plug it in, it doesn't
automatically load the lirc_mceusb2 modules. (I've another UCB based IR
receiver that when plugged in see the the lirc modules loaded, so I'm
pretty confident that this should happen).
What part of fedora (should) tell the system to load the modules when
this device is plugged in? I'm keen to test this device and see if I
can get it working.
When I plug the device in /var/log/messages shows:
Jul 13 09:25:09 moose kernel: usb 5-1: new full speed USB device using uhci_hcd and
address 5
Jul 13 09:25:09 moose kernel: usb 5-1: New USB device found, idVendor=147a,
idProduct=e03c
Jul 13 09:25:09 moose kernel: usb 5-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
Jul 13 09:25:09 moose kernel: usb 5-1: Product: eHome Infrared Transceiver
Jul 13 09:25:09 moose kernel: usb 5-1: Manufacturer: Formosa21
Jul 13 09:25:09 moose kernel: usb 5-1: SerialNumber: 00100186
Jul 13 09:25:09 moose kernel: usb 5-1: configuration #1 chosen from 1 choice
Jul 13 09:25:19 moose kernel: generic-usb 0003:147A:E03C.0008: timeout initializing
reports
Jul 13 09:25:19 moose kernel: generic-usb 0003:147A:E03C.0008: hiddev97,hidraw2: USB HID
v1.00 Device [Formosa21 eHome Infrared Transceiver] on usb-0000:00:1d.3-1/input1
hope someone can help me test this device. If the manufacturers claims
are correct, it shouldn't take too much to get this device working, and
then I'd be happy to contact various upstreams to let them know that the
deivce works and what is needed to get it working.
I should add, that I've downloaded the SRPM for lirc and added the
following UCB identifiers to drivers/lirc_mceusb2/lirc_mceusb2.c
/* Formosa Industrial Computing / Beanbag Emulation Device */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe018) },
+ /* Formosa Industrial Computing / Aim IR605A */
+ { USB_DEVICE(VENDOR_FORMOSA, 0xe03c) },
/* Fintek eHome Infrared Transceiver */
{ USB_DEVICE(VENDOR_FINTEK, 0x0602) },
and installed the resulting build.
The problem is (for the moment) getting fedora to see that the device is
a lirc_mceusb2 device and load the module.
R.
8:35 p.m.
On Mon, 2009-07-13 at 09:44 +1000, Rodd Clarkson wrote:
On Mon, 2009-07-13 at 09:27 +1000, Rodd Clarkson wrote:
>
> When I plug the device in /var/log/messages shows:
>
> Jul 13 09:25:09 moose kernel: usb 5-1: new full speed USB device using uhci_hcd and
address 5
> Jul 13 09:25:09 moose kernel: usb 5-1: New USB device found, idVendor=147a,
idProduct=e03c
> Jul 13 09:25:09 moose kernel: usb 5-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
> Jul 13 09:25:09 moose kernel: usb 5-1: Product: eHome Infrared Transceiver
> Jul 13 09:25:09 moose kernel: usb 5-1: Manufacturer: Formosa21
> Jul 13 09:25:09 moose kernel: usb 5-1: SerialNumber: 00100186
> Jul 13 09:25:09 moose kernel: usb 5-1: configuration #1 chosen from 1 choice
> Jul 13 09:25:19 moose kernel: generic-usb 0003:147A:E03C.0008: timeout initializing
reports
> Jul 13 09:25:19 moose kernel: generic-usb 0003:147A:E03C.0008: hiddev97,hidraw2: USB
HID v1.00 Device [Formosa21 eHome Infrared Transceiver] on usb-0000:00:1d.3-1/input1
>
> hope someone can help me test this device. If the manufacturers claims
> are correct, it shouldn't take too much to get this device working, and
> then I'd be happy to contact various upstreams to let them know that the
> deivce works and what is needed to get it working.
I should add, that I've downloaded the SRPM for lirc and added the
following UCB identifiers to drivers/lirc_mceusb2/lirc_mceusb2.c
/* Formosa Industrial Computing / Beanbag Emulation Device */
{ USB_DEVICE(VENDOR_FORMOSA, 0xe018) },
+ /* Formosa Industrial Computing / Aim IR605A */
+ { USB_DEVICE(VENDOR_FORMOSA, 0xe03c) },
/* Fintek eHome Infrared Transceiver */
{ USB_DEVICE(VENDOR_FINTEK, 0x0602) },
and installed the resulting build.
The problem is (for the moment) getting fedora to see that the device is
a lirc_mceusb2 device and load the module.
Yeah, I know, responding to you own thread is terrible, but I have more
information.
modinfo lirc_mceusb2 (below) shows that there's no alias for my usb ir
receiver in the list. How would I add it to the list. Does this
require a kernel rebuild, or can I just do some alias magic from the
command line.
I'm guessing I could need to see something like:
alias: usb:v147ApE03Cd*dc*dsc*dp*ic*isc*ip*
in the list.
R.
[rodd@moose modprobe.d]$ modinfo lirc_mceusb2
filename:
/lib/modules/2.6.29.5-191.fc11.i686.PAE/kernel/drivers/input/lirc/lirc_mceusb2.ko
license: GPL
author: Daniel Melander <lirc(a)rajidae.se>, Martin Blatter
<martin_a_blatter(a)yahoo.com>
description: Philips eHome USB IR Transceiver and Microsoft MCE 2005
Remote Control driver for LIRC
srcversion: 95945ED64B98983B457F9A4
alias: usb:v185Bp3020d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0FB8p0002d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1019p0F38d*dc*dsc*dp*ic*isc*ip*
alias: usb:v2304p0225d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1934p0702d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1934p0602d*dc*dsc*dp*ic*isc*ip*
alias: usb:v147ApE018d*dc*dsc*dp*ic*isc*ip*
alias: usb:v147ApE017d*dc*dsc*dp*ic*isc*ip*
alias: usb:v147ApE016d*dc*dsc*dp*ic*isc*ip*
alias: usb:v147ApE015d*dc*dsc*dp*ic*isc*ip*
alias: usb:v045Ep00A0d*dc*dsc*dp*ic*isc*ip*
alias: usb:v043Ep9803d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1509p9242d*dc*dsc*dp*ic*isc*ip*
alias: usb:v195Dp7002d*dc*dsc*dp*ic*isc*ip*
alias: usb:v179Dp0010d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0008d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0007d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0006d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1784p0001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v03EEp2501d*dc*dsc*dp*ic*isc*ip*
alias: usb:v107Bp3009d*dc*dsc*dp*ic*isc*ip*
alias: usb:v051CpC001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1308pC001d*dc*dsc*dp*ic*isc*ip*
alias: usb:v1460p9150d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p0334d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p0322d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0609p031Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p0815d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p0613d*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p060Fd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p060Dd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p060Cd*dc*dsc*dp*ic*isc*ip*
alias: usb:v0471p0608d*dc*dsc*dp*ic*isc*ip*
depends: lirc_dev
vermagic: 2.6.29.5-191.fc11.i686.PAE SMP mod_unload 686
parm: debug:Debug enabled or not (bool)
5:28 a.m.
On Mon, Jul 13, 2009 at 11:35:47AM +1000, Rodd Clarkson wrote:
modinfo lirc_mceusb2 (below) shows that there's no alias for my usb ir
receiver in the list. How would I add it to the list.
You are rebuilding a driver module from a source with added required
identifiers.
Does this
require a kernel rebuild,
No; you just need 'kernel-devel' installed. The only thing is that
you would need "clobber" with your module the original one which
came with a kernel package.
One source of exampled which need be done in detail would be srpms
for various "extra" modules which you can find on rpmfusion.
Write a bugzilla report describing what exactly is missing for your
device.
Michal
5439
days inactive
5440
days old
3 comments
2 participants
participants (2)
-
Michal Jaegermann -
Rodd Clarkson