no reaction with hauppage receiver...

[Thomas E. <Tho...@gm...>]

Hello,

I can't get lirc working with my hauppauge card. My config:

kernel: 2.4.1 (has bttv driver 0.7.50)
i2c package: from CVS (this morning)
lirc package: from CVS (this morning)

I do the following:

1. start kwintv in order to load the bttv drivers
2. modprobe lirc_i2c
3. lircd
4. irw
(I included the last messages of /var/log/messages below)

and then nothing happens if i press the buttons of the remote control.
The transmitter seems to be ok, I measured out that it sends out packets
with a digitally modulated carrier (looks like rc5).

by the way: is there anyone who can tell me if it is normal that the red
LED of the hauppauge's ir receiver is always on?

thanks,
   Thomas.

--- starting kwintv ---
> Feb 11 10:03:27 lisa kernel: Linux video capture interface: v1.00
> Feb 11 10:03:27 lisa kernel: bttv: driver version 0.7.50 loaded
> Feb 11 10:03:27 lisa kernel: bttv: using 2 buffers with 2080k (4160k total) for capture
> Feb 11 10:03:27 lisa kernel: bttv: Bt8xx card found (0).
> Feb 11 10:03:27 lisa kernel: PCI: Found IRQ 14 for device 00:08.0
> Feb 11 10:03:27 lisa kernel: PCI: The same IRQ used for device 00:08.1
> Feb 11 10:03:27 lisa kernel: bttv0: Bt878 (rev 2) at 00:08.0, irq: 14, latency: 32, memory: 0xdb002000
> Feb 11 10:03:27 lisa kernel: bttv0: subsystem: 0070:13eb  =>  Hauppauge WinTV  =>  card=10
> Feb 11 10:03:27 lisa kernel: bttv0: model: BT878(Hauppauge new (bt878)) [autodetected]
> Feb 11 10:03:27 lisa kernel: bttv0: Hauppauge msp34xx: reset line init
> Feb 11 10:03:27 lisa kernel: bttv0: i2c attach [EEPROM chip]
> Feb 11 10:03:27 lisa kernel: i2c-core.o: client [EEPROM chip] registered to adapter [bt848 #0](pos. 0).
> Feb 11 10:03:27 lisa kernel: i2c-core.o: adapter bt848 #0 registered as adapter 4.
> Feb 11 10:03:27 lisa kernel: bttv0: Hauppauge eeprom: model=61344, tuner=Philips FM1216 (5)
> Feb 11 10:03:27 lisa kernel: bttv0: i2c: checking for MSP34xx @ 0x80... found
> Feb 11 10:03:27 lisa kernel: i2c-core.o: driver i2c msp3400 driver registered.
> Feb 11 10:03:27 lisa kernel: msp34xx: init: chip=MSP3415D-B3, has NICAM support
> Feb 11 10:03:27 lisa kernel: msp3410: daemon started
> Feb 11 10:03:27 lisa kernel: bttv0: i2c attach [MSP3415D-B3]
> Feb 11 10:03:27 lisa kernel: i2c-core.o: client [MSP3415D-B3] registered to adapter [bt848 #0](pos. 1).
> Feb 11 10:03:27 lisa kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... not found
> Feb 11 10:03:27 lisa kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... not found
> Feb 11 10:03:27 lisa kernel: tvaudio: TV audio decoder + audio/video mux driver
> Feb 11 10:03:27 lisa kernel: tvaudio: known chips: tda9840,tda9873h,tda9850,tda9855,tea6300,tea6420,tda8425,pic16c54 (PV951)
> Feb 11 10:03:27 lisa kernel: i2c-core.o: driver generic i2c audio driver registered.
> Feb 11 10:03:27 lisa kernel: i2c-core.o: driver i2c TV tuner driver registered.
> Feb 11 10:03:27 lisa kernel: tuner: chip found @ 0x61
> Feb 11 10:03:27 lisa kernel: bttv0: i2c attach [Philips PAL]
> Feb 11 10:03:27 lisa kernel: i2c-core.o: client [Philips PAL] registered to adapter [bt848 #0](pos. 2).
> Feb 11 10:03:28 lisa kernel: bttv0: PLL: 28636363 => 35468950 ... ok

--- modprobe lirc_i2c ---
> Feb 11 10:03:49 lisa kernel: lirc_dev: IR Remote Control driver registered, at major 61 
> Feb 11 10:03:49 lisa kernel: i2c-core.o: driver i2c ir driver registered.
> Feb 11 10:03:49 lisa kernel: lirc_i2c: chip found @ 0x18 (Hauppauge IR)
> Feb 11 10:03:49 lisa kernel: bttv0: i2c attach [Hauppauge IR]
> Feb 11 10:03:49 lisa kernel: i2c-core.o: client [Hauppauge IR] registered to adapter [bt848 #0](pos. 3).
> Feb 11 10:03:49 lisa kernel: lirc_i2c: chip found @ 0x1a (Hauppauge IR)
> Feb 11 10:03:49 lisa kernel: bttv0: i2c attach [Hauppauge IR]
> Feb 11 10:03:49 lisa kernel: i2c-core.o: client [Hauppauge IR] registered to adapter [bt848 #0](pos. 4).

--- lircd ---
> Feb 11 10:04:00 lisa lircd-0.6.3[1234]: lircd(hauppauge) ready
> Feb 11 10:04:04 lisa lircd-0.6.3[1234]: accepted new client

then nothing happens...

-- 
________________________________________________________________________
Thomas Eschenbacher                           Tho...@gm...