After upgrading my Antec Fusion 430 based machine to kernel 2.6.42.7, my imon 0xffdc ir receiver stopped working. With the machine running the 2.6.42.7 kernel, irw and evtest show no scan codes or keys presses, though the log indicates that lirc is accepting clients. Here are the relevant log entries showing that lirc is accepting clients:
lircd-0.9.0[1113]: accepted new client on /var/run/lirc/lircd lircd-0.9.0[1113]: initializing '/dev/input/by-id/usb-15c2_ffdc-event-if00' lircd-0.9.0[1113]: removed client lircd-0.9.0[1113]: closing '/dev/input/by-id/usb-15c2_ffdc-event-if00'
Booting the machine to the 2.6.41.9 kernel restores lirc functionality. Here, inline, is the lirc config file for this machine:
/etc/sysconfig/lirc:
# Note: in addition to these parameters, you need to have working -*- sh -*- # configuration file for lircd (and lircmd if enabled).
# Options to lircd(8). Typically, this will be empty, as which driver to use # should be specified using the LIRC_DRIVER variable below. LIRCD_OPTIONS=""
# The infrared receiver (and/or transmitter) driver to be used by lircd(8), # similar to passing "-H driver" to lircd(8). # Run "/usr/sbin/lircd -H help" to get a listing of supported drivers. LIRC_DRIVER="devinput"
# Which lirc device will be used by lircd(8). # This is the same as passing "-d device" to lircd. # An empty value will use the default /dev/lirc0 device. LIRC_DEVICE="/dev/input/by-id/usb-15c2_ffdc-event-if00"
# If "yes", the init script will try to start lircmd(8) too. ENABLE_LIRCMD="no"
# Options to lircmd(8). LIRCMD_OPTIONS=""
Is anyone else seeing the same behavior? Am I missing something? Is this a known bug?
Rod
-
Rodney Morris