lirc does not work with avermedia m115 card remote
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lirc (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: lirc
Hi,
I have an Avermedia M115 mini-pci-e TV card on an Acer Aspire 5652. The card has an infrared device which seems to work partially. I can get some of the keys like 1-2-3..
System is Ubuntu 9.04, newly installed. (i disabled the saa7134 module as it's buggy at the moment)
On the other hand, most of the special keys on the IR remote don't work, I receive such messages in dmesg output:
atkbd.c: Unknown key pressed (translated set 2, code 0x9e on isa0060/serio0).
atkbd.c: Use 'setkeycodes e01e <keycode>' to make it known.
I have the following device in the lshal output, which seems to be related to the tv card:
udi = '/org/freedeskt
info.
info.callouts.add = {'debian-
info.capabilities = {'input', 'input.keys', 'button'} (string list)
info.category = 'input' (string)
info.parent = '/org/freedeskt
info.product = 'Video Bus' (string)
info.subsystem = 'input' (string)
info.udi = '/org/freedeskt
input.device = '/dev/input/event6' (string)
input.product = 'Video Bus' (string)
input.x11_driver = 'evdev' (string)
input.xkb.layout = 'us' (string)
input.xkb.model = 'pc105' (string)
input.xkb.rules = 'evdev' (string)
linux.device_file = '/dev/input/event6' (string)
linux.
linux.subsystem = 'input' (string)
linux.sysfs_path = '/sys/devices/
cat /dev/input/event6 is always silent, except for the already recognized keys, which do write on the console:
root@enterprise:/# cat /dev/input/event6
1123560
1234567890
^C
I guess the first step is to get the kernel recognize those keys. But if it's going to be manual, that would be a hard work due to a total of 48 keys on the remote (some working).
Note: no input devices are configured in xorg.conf, nvidia driver is loaded to do it automatically. Xorg.0.log shows nothing about the remote getting configured.
Any clues?
If you are still interested in this bug, it needs to be tested with the new 0.9.4c release, basically on a zesty host.
In the updated package you could use mode2 using --driver devinput to check whether the kernel decodes the signals or not. If it doesn't, it might be perfectly possible to configure lirc to use the raw data instead of the /dev/input devices.
In short, here is not enough to qualify for a bug. If you are still interested in this please refer to the mailing list at http:// sf.net/ p/lirc for help configuring lirc in situations where the kernel decoding does not work. See also the configuration guide at http:// lirc.org/ html/configurat ion-guide. html.