Michael Stearne wrote: > > The card is found. But the next problem is that it thinks the card has > a PAL tuner. Because of that (I think) I only get about an 1/8 of the > screen filled with static. Which should be filled playing a video from > the VCR I have hooked up. > > This is what I get from dmesg > > Linux video capture interface: v1.00 > i2c-core.o: i2c core module > i2c-algo-bit.o: i2c bit algorithm module > bttv: driver version 0.7.57 loaded > bttv: using 2 buffers with 2080k (4160k total) for capture > bttv: Host bridge needs ETBF enabled. > bttv: Bt8xx card found (0). > bttv0: Bt878 (rev 17) at 00:0f.0, irq: 11, latency: 64, memory: > 0xfc5fe000 > bttv0: subsystem: 0070:13eb => Hauppauge WinTV => card=10 > bttv0: model: BT878( *** UNKNOWN *** ) [insmod option] > bttv0: enabling 430FX/VP3 compatibilty > i2c-core.o: adapter bt848 #0 registered as adapter 0. > bttv0: i2c: checking for MSP34xx @ 0x80... not found > bttv0: i2c: checking for TDA9875 @ 0xb0... not found > bttv0: i2c: checking for TDA7432 @ 0x8a... not found > i2c-core.o: driver i2c TV tuner driver registered. > tuner: chip found @ 0x61 > bttv0: i2c attach [Temic PAL (4002 FH5)] > i2c-core.o: client [Temic PAL (4002 FH5)] registered to adapter [bt848 > #0](pos. 0). > i2c-core.o: driver i2c msp3400 driver registered. > > Any idea why I am only getting an 1/8 of the screen or why it thinks I > have a PAL tuner? There is a sticker on the card that says it's NTSC. That's quite odd. It's autodetecting it incorrectly, it would seem. I thought Hauppauge cards usually had a Philips tuner. Pull the card out, look at the tuner (the metal box), see what it really truly is, then compare that with the list of available tuner types. I forget which exact file that's in insmod-options or CARDLIST. Then force the tuner type on the bttv commandline - as in "modprobe bttv tuner=2" (I have to force tuner=2 for my STB Desktop TV) - Eric
