> Mar 26 14:11:43 linvdr user.info kernel: input: i2c IR (Hauppauge) as > /class/input/input2 > Mar 26 14:11:43 linvdr user.warn kernel: ir-kbd-i2c: i2c IR (Hauppauge) > detected at i2c-1/1-0018/ir0 [ivtv i2c driver #0] > > The machine has a PVR350 and an Avermedia 771. The Avermedia seems to be > input0, but why is the Hauppauge card detected twice (input1 and input2) > > With old driver 0.4.x it looks like this: > > Mar 27 11:54:42 linvdr user.warn kernel: lirc_i2c: chip found @ 0x18 > (Hauppauge IR) > Mar 27 11:54:42 linvdr user.info kernel: ivtv0: i2c attach to card #0 ok > [client=Hauppauge IR, addr=18] > Mar 27 11:54:43 linvdr user.warn kernel: lirc_dev: lirc_register_plugin: > sample_rate: 10 > > ... and the remote control works with lircd. > > With the new driver and automatic use of ir-kbd-i2c only the numbers 1-9 > work. What is the trick to get it work with all keys like before?
Either use the dev/input driver in lirc and remap your keys, or unload/blacklist ir-kbd-i2c and let lirc_i2c do the work as before. Key #s can be found with modprobe evdev && evtest /dev/input/eventX. HTH, Mark _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
