← Back to team overview

mythbuntu-bugs team mailing list archive

[Bug 660185] Re: Issues with Generic Mceusb receiver after upgrade to 10.10

 

** Description changed:

  Binary package hint: lirc
  
  Issues with Generic Mceusb receiver after upgrade to 10.10
  
  I've upgraded a 10.04 system to 10.10 and seem to have problems with my
  generic mceusb receiver (the receiver works fine in 10.04)
  
  dmesg | grep lirc
  [   17.618734] lirc_dev: IR Remote Control driver registered, major 249
  [   17.630203] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
+ 
+ dmesg | grep mceusb
+ [   17.630203] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
+ [   17.630222] mceusb 2-9:1.0: Registered Formosa21 SnowflakeEmulation on usb2:2
+ [   17.630241] usbcore: registered new interface driver mceusb
  
  cat /proc/bus/input/devices
  ...
  I: Bus=0000 Vendor=0000 Product=0000 Version=0000
  N: Name="Media Center Ed. eHome Infrared Remote Transceiver (147a:e017)"
  P: Phys=usb-0000:00:04.0-9/input0
  S: Sysfs=/devices/virtual/rc/rc0/input4
  U: Uniq=
  H: Handlers=kbd event4
  B: EV=100003
  B: KEY=fff 0 108fc326 217604100000000 0 118000 418000100001 9e968000000000 10000000
  
  The device seems to be recognised and /dev/lirc0 is created but irw does
  not respond to any buttons. Using 'sudo mode2 - d /dev/lirc0' I do get
  output when buttons are pressed.
  
  cat /etc/lirc/hardware.conf
  REMOTE="Windows Media Center Transceivers/Remotes (all)"
  TRANSMITTER="None"
  REMOTE_MODULES="lirc_dev mceusb"
  REMOTE_DRIVER=""
  REMOTE_DEVICE="/dev/lirc0"
  REMOTE_SOCKET=""
  REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
  REMOTE_LIRCD_ARGS=""
  TRANSMITTER_MODULES=""
  TRANSMITTER_DRIVER=""
  TRANSMITTER_DEVICE=""
  TRANSMITTER_SOCKET=""
  TRANSMITTER_LIRCD_CONF=""
  TRANSMITTER_LIRCD_ARGS=""
  START_LIRCD="true"
  START_LIRCMD=""
  LOAD_MODULES=""
  LIRCMD_CONF=""
  FORCE_NONINTERACTIVE_RECONFIGURATION="false"
  
  Connecting a genuine Microsoft receiver to the machine using the same
  config works fine.

-- 
Issues with Generic Mceusb receiver after upgrade to 10.10
https://bugs.launchpad.net/bugs/660185
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to lirc in ubuntu.

Status in “lirc” package in Ubuntu: New

Bug description:
Binary package hint: lirc

Issues with Generic Mceusb receiver after upgrade to 10.10

I've upgraded a 10.04 system to 10.10 and seem to have problems with my generic mceusb receiver (the receiver works fine in 10.04)

dmesg | grep lirc
[   17.618734] lirc_dev: IR Remote Control driver registered, major 249
[   17.630203] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0

dmesg | grep mceusb
[   17.630203] rc rc0: lirc_dev: driver ir-lirc-codec (mceusb) registered at minor = 0
[   17.630222] mceusb 2-9:1.0: Registered Formosa21 SnowflakeEmulation on usb2:2
[   17.630241] usbcore: registered new interface driver mceusb

cat /proc/bus/input/devices
...
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="Media Center Ed. eHome Infrared Remote Transceiver (147a:e017)"
P: Phys=usb-0000:00:04.0-9/input0
S: Sysfs=/devices/virtual/rc/rc0/input4
U: Uniq=
H: Handlers=kbd event4
B: EV=100003
B: KEY=fff 0 108fc326 217604100000000 0 118000 418000100001 9e968000000000 10000000

The device seems to be recognised and /dev/lirc0 is created but irw does not respond to any buttons. Using 'sudo mode2 - d /dev/lirc0' I do get output when buttons are pressed.

cat /etc/lirc/hardware.conf
REMOTE="Windows Media Center Transceivers/Remotes (all)"
TRANSMITTER="None"
REMOTE_MODULES="lirc_dev mceusb"
REMOTE_DRIVER=""
REMOTE_DEVICE="/dev/lirc0"
REMOTE_SOCKET=""
REMOTE_LIRCD_CONF="mceusb/lircd.conf.mceusb"
REMOTE_LIRCD_ARGS=""
TRANSMITTER_MODULES=""
TRANSMITTER_DRIVER=""
TRANSMITTER_DEVICE=""
TRANSMITTER_SOCKET=""
TRANSMITTER_LIRCD_CONF=""
TRANSMITTER_LIRCD_ARGS=""
START_LIRCD="true"
START_LIRCMD=""
LOAD_MODULES=""
LIRCMD_CONF=""
FORCE_NONINTERACTIVE_RECONFIGURATION="false"

Connecting a genuine Microsoft receiver to the machine using the same config works fine.







References