On Thu, Apr 15, 2010 at 1:06 AM, Jongi <jongitech@gmail.com> wrote:
On 04/14/2010 11:53 PM, Jarod Wilson wrote:
On Wed, Apr 14, 2010 at 4:58 PM, Jongi <jongitech@gmail.com> wrote:
I am running Debian Unstable, kernel with lirc and
lirc-modules-source version (0.8.6-1~c0.sidux.13). This was done in order to
be able to compile lirc under the kernel.

This is the card in question -

lsusb reports it as follows:
Bus 003 Device 002: ID 185b:3020 Compro

So when I installed I decided to try modprobe lirc_mceusb2. lsmod reports

# lsmod | grep mce
lirc_mceusb            11881  0
lirc_dev                9749  1 lirc_mceusb
usbcore               137017  5 lirc_mceusb,usbhid,ohci_hcd,ehci_hcd

However there is no lircd.conf file for the remote.
You sure 'bout that? The standard mce config ought to work for just
about any rc6 mce remote.


Well thank you good sir. I suppose it makes sense that if a card is picked up by a certain module it makes sense to use the remote config for that module rather than for each individual card to its own conf file.

So I added /usr/sbin/lircd -d /dev/lirc0 to /etc/rc.local
I also copped /etc/lirc/lircd.conf to ~

But from the MCE MythTV wiki, it seems this may be an issue

Version 1

  • IR Receiver is supported
  • IR Transmitter is not supported

So I guess my question becomes can I use this as an lirc_mceusb2 device?


The above is obviously rubbish after thinking about it a bit more. irw sees the remote just fine. and i have also learnt that everything is now in lirc_mceusb.

i did a more extensive mplayer test. the arrow keys and ok button and the play/pause keys don't work in mplayer.

This got me thinking that maybe I need to replace some of the keywords in the lircd.conf file with the keywords I found when I ran irrecord -l. Does this make sense?