>>> ivtv: ==================== START INIT IVTV ==================== >>> ivtv: version 0.4.3 (tagged release) loading >>> ivtv: Linux version: 2.6.15-1.1833_FC4 686 REGPARM 4KSTACKS gcc-4.0 >>> ivtv: In case of problems please include the debug info between >>> ivtv: the START INIT IVTV and END INIT IVTV lines, along with >>> ivtv: any module options, when mailing the ivtv-users mailinglist. >>> ivtv0: Autodetected WinTV PVR 350 card (cx23415 based) >>> ACPI: PCI Interrupt 0000:00:0d.0[A] -> Link [LNKD] -> GSI 11 (level, >>> low) -> IRQ 11 >>> saa7127 1-0044: saa7129 found @ 0x88 (ivtv i2c driver #0) >>> ivtv0: i2c attach to card #0 ok [client=saa7127, addr=44] >>> msp3400 1-0040: chip=MSP4448G-A2 +nicam +simple +simpler +radio >>> mode=simpler >>> ivtv0: i2c attach to card #0 ok [client=MSP4448G-A2, addr=40] >>> msp3400 1-0040: msp34xxg daemon started >>> tda9887 1-0043: (ivtv) chip found @ 0x86 (ivtv i2c driver #0) >>> ivtv0: i2c attach to card #0 ok [client=tda9887, addr=43] >>> tveeprom: ivtv version >>> tveeprom: Hauppauge: model = 48132, rev = K268, serial# = 8289714 >>> tveeprom: tuner = LG TAPE H001F MK3 (idx = 68, type = 47) >>> tveeprom: tuner fmt = NTSC(M) (eeprom = 0x08, v4l2 = 0x00001000) >>> tveeprom: audio processor = MSP4448 (type = 1b) >>> tveeprom: decoder processor = SAA7115 (type = 13) >>> ivtv0: i2c attach to card #0 ok [client=tveeprom, addr=50] >>> tuner (ivtv): chip found at addr 0xc2 i2c-bus ivtv i2c driver #0 >>> ivtv0: i2c attach to card #0 ok [client=(tuner unset), addr=61] >>> ivtv0 warning: i2c client addr: 0x21 not found for command 0x8004646b! >> >> This is your problem. The driver expects to find a saa7115 chip at >> address 0x21, but fails to. One possible reason is that the saa7115 >> module is failing to load - check to make sure you have one. Another >> possible reason is the saa7115 is damaged. Checking in Windows would >> verify this (or using i2cdetect in linux). >> >> Keith C > > Keith, > > Thanks for the info. I tried the following... > > modprobe i2c-dev > Then, I did i2cdetect -l and it returned: > i2c-1 unknown ivtv i2c driver #0 Algorithm > unavailable > i2c-0 unknown SiS96x SMBus adapter at 0x1080 Algorithm > unavailable > > Then I did a "i2cdetect 1" and this is what I got: > WARNING! This program can confuse your I2C bus, cause data loss and worse! > I will probe file /dev/i2c-1. > I will probe address range 0x03-0x77. > Continue? [Y/n] y > 0 1 2 3 4 5 6 7 8 9 a b c d e f > 00: XX XX XX XX XX XX XX XX XX XX XX XX XX > 10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 40: UU XX XX UU UU XX XX XX XX XX XX XX XX XX XX XX > 50: UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 60: XX UU XX XX XX XX XX XX XX XX XX XX XX XX XX XX > 70: XX XX XX XX XX XX XX XX > > I don't understand it really. Could anyone help me read this to find out > what might be the problem? I still have a fishy feeling about my Sis961 > Chipset. Can anyone confirm that? > > Thanks, > Nate > >
OK, I answered my own question. I noticed that there are busses on 40, 43, 44, 50, and 61 There is nothing registering at 0x21. I went ahead and did an i2cdump (i2cdump 1 0x40) of all the registers and I get response from the above list. Nothing is registering on 0x21. I have a Windows XP Box at home, and will try plugging it in there tonight. And make sure the card is not bad. I tried modprobe -v saa7115 and got this: insmod /lib/modules/2.6.15-1.1833_FC4/kernel/drivers/media/video/saa7115.ko So I am sure I have the module, and an lsmod shows the module loaded. Anyone else have any ideas? Thanks, Nate _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
