Torgeir Veimo wrote: > > (resend with correct from address) > > I have just gotten a used voodo tv fm card and I am having trouble > getting the tuner to respond. The cover/heatsink over the tuner chip is > very hot, making me suspect this card might be broken(?). It gets hot here, too ! Nevertheless it works. The datasheet has: - 2.8W power dissipation - junction temperature 96 Celsius - 10 years lifetime at ambient temp. 55 Celsius, with correct heatsink only ! > > When I start a windows pctv app called Sattelite (just to check if the > bt878 video input is working ok) I get a lot of entries in the log that > indicates activity on the i2c bus. > > 19:03:46.870:00000430 - gpioremote-thread: key=0ff000 > 19:03:46.920:00000430 - gpioremote-thread: key=0ff000 > 19:03:46.970:00000430 - gpioremote-thread: key=0ff003 > 19:03:47.020:00000430 - gpioremote-thread: key=0ff000 Ask whoever wrote this windows app what this means. > From my logfile when loading the modules; > > Sep 23 21:46:23 atlantis kernel: Linux video capture interface: v1.00 > Sep 23 21:46:23 atlantis kernel: i2c-core.o: i2c core module > Sep 23 21:46:23 atlantis kernel: i2c-algo-bit.o: i2c bit algorithm module > Sep 23 21:46:23 atlantis kernel: bttv: driver version 0.7.80 loaded ... > Sep 23 21:46:23 atlantis kernel: bttv0: detected: 3Dfx VoodooTV FM/ > VoodooTV 200 [card=68], PCI subsystem ID is 121a:3000Sep 23 21:46:23 > atlantis kernel: bttv0: using: BT878(3Dfx VoodooTV FM (Euro)) > [card=68,insmod option] > Sep 23 21:46:23 atlantis kernel: bttv0: enabling ETBF (430FX/VP3 > compatibilty) > Sep 23 21:46:23 atlantis kernel: bttv0: Hauppauge/Voodoo msp34xx: reset > line init [20] ... > Sep 23 21:46:23 atlantis kernel: i2c-core.o: adapter bt848 #0 registered > as adapter 0. Here msp should be detected (with latest patch)!!! Make sure you load the newly compiled module. You should see "bttv0: i2c: checking for MSP34xx @ 0x80... found"... > Sep 23 21:46:23 atlantis kernel: bttv0: i2c: checking for TDA9875 @ > 0xb0... not found > Sep 23 21:46:23 atlantis kernel: bttv0: i2c: checking for TDA7432 @ > 0x8a... not found > Sep 23 21:46:23 atlantis kernel: i2c-core.o: driver i2c TV tuner driver > registered. > Sep 23 21:46:23 atlantis kernel: tuner: chip found @ 0xc0 > Sep 23 21:46:23 atlantis kernel: bttv0: i2c attach [client=MT2032 > universal,ok] > Sep 23 21:46:23 atlantis kernel: i2c-core.o: client [MT2032 universal] > registered to adapter [bt848 #0](pos. 0). > Sep 23 21:46:23 atlantis kernel: devfs: devfs_register(): device already > registered: "v4l/video0" > Sep 23 21:46:23 atlantis kernel: devfs: devfs_register(): device already > registered: "v4l/vbi0" > Sep 23 21:46:23 atlantis kernel: devfs: devfs_register(): device already > registered: "v4l/radio0" I dont know what the last 3 messages mean. Tried without devfs ? > When I try to scan using scantv I get these; > > Sep 23 22:06:26 atlantis kernel: tuner: tv freq set to 0.00 > Sep 23 22:06:26 atlantis kernel: tuner: TV freq (0.00) out of range (44-958) > Sep 23 22:06:26 atlantis kernel: mt2032: rfin=0 lo1=207 lo1n=25 lo1a=7 > sel=4, lo1freq=1086750000 These are fine (debug=1). Freq out of range is just temporary when you start scanning... > Actually, with the latest patch, I now get sound, and I can hear that > the card kindof mutes when I change channel in xawtv. It's like if the > antenna input is broken or something. (Yes the cable is ok... :) Recently there was a report from somebody needing to warmboot from windows to get the card working correctly. However, is the sound correct (or noise only) ? Add "debug=1" for the "msp3400"-module to see the sound carrier values.
