[Karmic] Leadtek Winfast 2000XP remote not set up correctly
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mythbuntu-control-centre (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: mythbuntu-
I have a Leadtek Winfast 2000XP (card 34) with a remote Y0400046. The MCC remote generator does not make this remote work correctly. After using MCC and checking the "generate dynamic button mappings", I have to fix quite a number of things. I have set out the full instructions here (http://
A number of the configuration settings seem to be based on the assumption that the remote will be accessed directly, when the devinput method seems to be the best option for this remote. If devinput is used, the configuration needs to be for devinput, rather than remote-specific (I understand that the devinput driver already does the conversion from remote buttons to "keys" at a lower level).
1) use a UDEV rule to make a symlink for the event note as described here (http://
KERNEL=="event*", ATTRS{vendor}
2) the configuration file loaded into /etc/lirc/
lircd.
when it should be
include "/etc/lirc/
3) change /etc/lirc/
# /etc/lirc/
#
#Chosen Remote Control
REMOTE="Winfast TV2000/XP (card"
REMOTE_
REMOTE_
REMOTE_
REMOTE_SOCKET=""
REMOTE_
REMOTE_
MCC has a number of mistakes in its automatically generated one. The event will obviously need to match any udev rule symlink and the LIRCD_CONF was incorrect, from memory.
4) the ~/.lirc/mythtv file is *way* out and does nothing now that the devinput driver identifies presses as "linux-
Setting up this remote is quite an exercise at the moment, but it is just a series of fairly mechanical steps, so it would be great if MCC could do it for the user. Please let me know if I can be any further help!
Would it be helpful if I did a dpkg --reconfigure of LIRC and tell you how close it gets to the correct configuration options?
description: | updated |
Thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately the Mythbuntu team does not have the resources to handle the constant stream of new devices such as this. Since the lirc team does not have a bug tracker, the most efficient way to get the device supported would be for you to contact the lirc team on their mailng list and describe everything you know about the remote and any data that you have collected. If they do add support, please feel free to re-open this ticket with the information about what they called the device so that it can be considered for import into Mythbuntu as a patch.