mythbuntu-bugs team mailing list archive

[Mario Limonciello <superm1@xxxxxxxxxx>]

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.


** Changed in: mythbuntu-control-centre (Ubuntu)
       Status: New => Won't Fix

-- 
[Karmic] Leadtek Winfast 2000XP remote not set up correctly
https://bugs.launchpad.net/bugs/482961
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythbuntu-control-centre in ubuntu.

Status in “mythbuntu-control-centre” package in Ubuntu: Won't Fix

Bug description:
Binary package hint: mythbuntu-control-centre

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://www.linuxtv.org/wiki/index.php/Leadtek_WinFast_2000#Setting_up_the_remote ) and here (http://www.mythtv.org/wiki/Leadtek_WinFast#Remote )

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://ubuntuforums.org/showthread.php?t=222672), to stop the remote changing its device node on boot. My rule is:
KERNEL=="event*", ATTRS{vendor}=="0x109e", ATTRS{device}=="0x036e", ATTRS{modalias}=="pci:v0000109Ed0000036Esv0000107Dsd00006606bc04sc00i00", SYMLINK+="input/bttv_remote"

2) the configuration file loaded into /etc/lirc/lircd.conf is
  lircd.conf.RM-0010
when it should be
include "/etc/lirc/linux-input-layer-lircd.conf"

3) change /etc/lirc/hardware.conf to read:

# /etc/lirc/hardware.conf
#
#Chosen Remote Control
REMOTE="Winfast TV2000/XP (card"
REMOTE_MODULES="bttv"
REMOTE_DRIVER="devinput"
REMOTE_DEVICE="/dev/input/bttv_remote"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="devinput/lircd.conf.devinput"
REMOTE_LIRCD_ARGS=""

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-input-layer".  My config file is at http://pastebin.com/f62afb3cf but is specifically to get the most out of the Y0400046 remote, so may not cover (or use optimally) the buttons on other 2000XP bttv cards.

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?