Mar 26 14:11:42 linvdr user.info kernel: bttv0: registered device vbi0 Mar 26 14:11:42 linvdr user.info kernel: ok Mar 26 14:11:42 linvdr user.warn kernel: bttv0: add subdevice "dvb0" Mar 26 14:11:42 linvdr user.info kernel: input: bttv IR (card=123) as /class/input/input0 Mar 26 14:11:42 linvdr user.warn kernel: bttv-input: bttv IR (card=123) detected at pci-0000:00:0a.0/ir0 Mar 26 14:11:43 linvdr user.info kernel: input: i2c IR (Hauppauge) as /class/input/input1 Mar 26 14:11:43 linvdr user.warn kernel: ir-kbd-i2c: i2c IR (Hauppauge) detected at i2c-0/0-001a/ir0 [bt878 #0 [hw]] Mar 26 14:11:43 linvdr user.info kernel: ivtv: ==================== START INIT IVTV ==================== Mar 26 14:11:43 linvdr user.info kernel: ivtv: version 0.7.0 (v4l-dvb + ivtv virtual merge) Revision: 3228 loading Mar 26 14:11:43 linvdr user.info kernel: ivtv: Linux version: 2.6.16 386 gcc-3.3 Mar 26 14:11:43 linvdr user.info kernel: ivtv: In case of problems please include the debug info between Mar 26 14:11:43 linvdr user.info kernel: ivtv: the START INIT IVTV and END INIT IVTV lines, along with Mar 26 14:11:43 linvdr user.info kernel: ivtv: any module options, when mailing the ivtv-users mailinglist. Mar 26 14:11:43 linvdr user.info kernel: ivtv0: Autodetected Hauppauge WinTV PVR-350 card (cx23415 based) Mar 26 14:11:43 linvdr user.info kernel: ACPI: PCI Interrupt 0000:00:08.0[A] -> Link [LNKA] -> GSI 11 (level, low) -> IRQ 11 Mar 26 14:11:43 linvdr user.info kernel: ivtv0: Unreasonably low latency timer, setting to 64 (was 32) Mar 26 14:11:43 linvdr user.info kernel: tuner 1-0061: chip found @ 0xc2 (ivtv i2c driver #0) 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? _______________________________________________ ivtv-devel mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-devel
