Re: Problem with Hauppauge WinTV

[Volker Drewer-G. <vol...@gm...>]

On Wednesday 05 September 2001 23:22, Eric Jorgensen wrote:
> Volker Drewer-Gutland wrote:
> > On Wednesday 05 September 2001 22:05, Eric Jorgensen wrote:
> > > Volker Drewer-Gutland wrote:
> > > > On Tuesday 04 September 2001 22:01, Eric Jorgensen wrote:
> > > > > Volker Drewer-Gutland wrote:
> > > > > > Hi All!
> > > > > >
> > > > > > After reading all sorts of documentation and checking log files,
> > > > > > I finally send a message to this mailing list because I ran out
> > > > > > of ideas on what's going wrong:
> > > > > > I have a WinTV card and I'd like to use the onboard IR receiver
> > > > > > with LIRC. However, it just doesn't work. I'm running the 2.4.5
> > > > > > kernel on a SuSE 7.0 system. I configured (lirc_i2c) and compiled
> > > > > > the latest lirc package (version 0.6.4).
> > > > > > When I try to run the test program (xmode2) I get the error
> > > > > > message: xmode2: error opening /dev/lirc
> > > > > > xmode2: No such device
> > > > > >
> > > > > > Basically the same errors are reported when I try to use lircd
> > > > > > and irexec.
> > > > >
> > > > >       Simple questions first:
> > > > >
> > > > >       Does /dev/lirc exist?
> > > > >
> > > > >       Also, I have found that the hauppauge ir reciever won't work
> > > > > if it wasn't plugged into the card at reset time - that is, when
> > > > > you turned it on, or when you last rebooted your computer.
> > > > >
> > > > >  - Eric
> > > >
> > > > Eric,
> > > >
> > > > thanks for your hints! Hoyever, /dev/lirc exists and I believe it has
> > > > the right major and minor number (61,0). The receiver is also plugged
> > > > in....
> > >
> > >       Well, the point was that if it wasn't plugged in when you turned
> > > on the computer, it won't work until you reset the computer.
> > >
> > >       Anyway, I think the point that someone else made - that lirc_i2c
> > > isn't shown anywhere in your logs - is more relivant.
> > >
> > >  - Eric
> >
> > OK! I understand that, but according to lsmod the lirc_i2c module is
> > loaded. What messages should appear in the log if the module is working
> > properly?
>
> 	Mine says the following, with lirc 0.6.3:
>
> lirc_dev: IR Remote Control driver registered, at major 61
> i2c-core.o: driver i2c ir driver registered
> lirc_i2c: chip found @ 0x18 (Hauppauge IR)
> bttv0: i2c attach [Hauppauge IR]
> i2c-core.o: client [Hauppauge IR] registered to adapter [bt848 #0](pos.
> 2).
>
>  - Eric

hmm....I checked my log file again:

Sep  5 23:26:03 haeuptling kernel: lirc_dev: IR Remote Control driver 
registered, at major 61
Sep  5 23:26:03 haeuptling kernel: bttv: driver version 0.7.57 loaded
Sep  5 23:26:03 haeuptling kernel: bttv: using 2 buffers with 2080k (4160k 
total) for capture
Sep  5 23:26:03 haeuptling kernel: bttv: Bt8xx card found (0).
Sep  5 23:26:03 haeuptling kernel: bttv0: Bt878 (rev 2) at 00:0a.0, irq: 11, 
latency: 64, memory: 0xebdfd000
Sep  5 23:26:03 haeuptling kernel: bttv0: subsystem: 0070:13eb  =>  Hauppauge 
WinTV  =>  card=10
Sep  5 23:26:03 haeuptling kernel: bttv0: model: BT878(Hauppauge new (bt878)) 
[insmod option]
Sep  5 23:26:03 haeuptling kernel: bttv0: Hauppauge msp34xx: reset line init
Sep  5 23:26:03 haeuptling kernel: tuner: chip found @ 0x61
Sep  5 23:26:03 haeuptling kernel: bttv0: i2c attach [i2c tv tuner chip]
Sep  5 23:26:03 haeuptling kernel: i2c-core.o: client [i2c tv tuner chip] 
registered to adapter [bt848 #0](pos. 0).
Sep  5 23:26:03 haeuptling kernel: i2c-core.o: adapter bt848 #0 registered as 
adapter 1.
Sep  5 23:26:03 haeuptling kernel: bttv0: Hauppauge eeprom: model=61294, 
tuner=Philips FI1216 MK2 (5), radio=no
Sep  5 23:26:03 haeuptling kernel: bttv0: i2c: checking for MSP34xx @ 0x80... 
not found
Sep  5 23:26:03 haeuptling kernel: bttv0: i2c: checking for TDA9875 @ 0xb0... 
not found
Sep  5 23:26:03 haeuptling kernel: bttv0: i2c: checking for TDA7432 @ 0x8a... 
not found
Sep  5 23:26:03 haeuptling kernel: i2c-core.o: driver i2c ir driver 
registered.

It also tells me something about registering the drivers and stuff like this. 
Just like your log file...

Volker