I've been reading up on i2c. http://www.robot-electronics.co.uk/htm/using_the_i2c_bus.htm
My errors on the i2c debug: Jun 6 01:28:22 media kernel: ivtv0 i2c: i2c init Jun 6 01:28:22 media kernel: ivtv0 i2c: setting scl and sda to 1 Jun 6 01:28:23 media kernel: ivtv0 i2c: SCL stuck low at start Jun 6 01:28:23 media kernel: ivtv0 i2c: SCL could not be set high Jun 6 01:28:23 media kernel: ivtv0 i2c: SDA was low at start Jun 6 01:28:23 media kernel: ivtv0 i2c: SCL stuck low at start Jun 6 01:28:23 media kernel: ivtv0 i2c: SCL could not be set high The I2C protocol specification states that the IC that initiates a data transfer on the bus is considered the Bus Master. Consequently, at that time, all the other ICs are regarded to be Bus Slaves. So why is the bus stuck low? ----- Original Message ----- From: "Simon Baxter" <[EMAIL PROTECTED]> To: "User discussion about IVTV" <[email protected]> Sent: Tuesday, June 06, 2006 3:53 PM Subject: Re: [ivtv-users] FC5 or FC4 ? > Well, I would. But I'm getting mixed results and posting all the > variations > based on what kernel I'm running, ivtv0.6.2 unpatched, then patched with > an > newi2c patch from Hans, then the same for 0.8.1 - all getting slightly > different results, would over complicate things. > > At the moment things are looking very poor. > > This (below) is modprobing with: > options tveeprom debug=1 > options ivtv newi2c=0 tuner=50,-1 > > for some reason it's taking AGES to comeback - and is now failing, where > it > was previously working. This delay is causing udev all sorts of problems > on > boot up. > > It's also reporting i2c_adapter i2c-1: as finding i2c 0x44, but then > ivtv0: > cannot. > > > > ivtv: ==================== START INIT IVTV ==================== > ivtv: version 0.8.0 (development revision 3310M) loading > ivtv: Linux version: 2.6.17-rc5 mod_unload 686 REGPARM 4KSTACKS gcc-4.1 > 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 Hauppauge WinTV PVR-150 card (cx23416 based) > ACPI: PCI Interrupt 0000:00:0a.0[A] -> GSI 17 (level, low) -> IRQ 21 > i2c_adapter i2c-1: adapter [ivtv i2c driver #0] registered > i2c-dev: adapter [ivtv i2c driver #0] registered as minor 1 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x50 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x50, len=0 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x50, len=1 > tveeprom 1-0050: Huh, no eeprom present (err=-121)? > tveeprom 1-0050: Encountered bad packet header [00]. Corrupt or not a > Hauppauge eeprom. > ivtv0: No tuner detected, default to NTSC > i2c-core: driver [tuner] registered > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x42 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x42, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x43 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x43, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x4a > i2c_adapter i2c-1: master_xfer[0] W, addr=0x4a, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x4b > i2c_adapter i2c-1: master_xfer[0] W, addr=0x4b, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x60 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x60, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x61 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x61, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x62 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x62, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x63 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x63, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x64 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x64, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x65 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x65, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x66 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x66, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x67 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x67, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x68 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x68, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x69 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x69, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x6a > i2c_adapter i2c-1: master_xfer[0] W, addr=0x6a, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x6b > i2c_adapter i2c-1: master_xfer[0] W, addr=0x6b, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x6c > i2c_adapter i2c-1: master_xfer[0] W, addr=0x6c, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x6d > i2c_adapter i2c-1: master_xfer[0] W, addr=0x6d, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x6e > i2c_adapter i2c-1: master_xfer[0] W, addr=0x6e, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x6f > i2c_adapter i2c-1: master_xfer[0] W, addr=0x6f, len=0 > i2c-core: driver [tda9887] registered > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x42 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x42, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x43 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x43, len=0 > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x4b > i2c_adapter i2c-1: master_xfer[0] W, addr=0x4b, len=0 > i2c-core: driver [cx25840] registered > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x44 > i2c_adapter i2c-1: master_xfer[0] W, addr=0x44, len=0 > i2c-core: driver [wm8775] registered > i2c_adapter i2c-1: found normal entry for adapter 1, addr 0x1b > i2c_adapter i2c-1: master_xfer[0] W, addr=0x1b, len=0 > ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes) > ivtv0: Encoder revision: 0x02050032 > ivtv0: Allocate DMA encoder MPEG stream: 128 x 32768 buffers (4096KB > total) > ivtv0: Allocate DMA encoder YUV stream: 194 x 10800 buffers (2048KB total) > ivtv0: Allocate DMA encoder VBI stream: 120 x 17472 buffers (2048KB total) > ivtv0: Allocate DMA encoder PCM audio stream: 455 x 4608 buffers (2048KB > total) > ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! > ivtv0: i2c addr 0x44 not found for command 0x40045613! > ivtv0: i2c addr 0x44 not found for command 0x4008646f! > ivtv0: i2c hardware 0x00000020 not found for command 0x4008646d! > ivtv0: i2c hardware 0x00000001 not found for command 0x4008646d! > ivtv0: i2c addr 0x44 not found for command 0x40045612! > ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! > ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! > ivtv0: i2c addr 0x44 not found for command 0x40045613! > ivtv0: i2c addr 0x44 not found for command 0x40045612! > ivtv0: i2c hardware 0x00000001 not found for command 0xc008561c! > ivtv0: Initialized Hauppauge WinTV PVR-150, card #0 > ivtv: ==================== END INIT IVTV ==================== > > > The attached file is with: > options tveeprom debug=1 > options ivtv newi2c=1 ivtv_debug=33 > > > ----- Original Message ----- > From: "Kevin J. Cummings" <[EMAIL PROTECTED]> > To: "User discussion about IVTV" <[email protected]> > Sent: Tuesday, June 06, 2006 2:38 PM > Subject: Re: [ivtv-users] FC5 or FC4 ? > > >> Simon Baxter wrote: >>> I've been struggling with a fresh install of Fedora Core 5, and getting >>> everything to work with my new PVR-150 card. Most of the problems have >>> been >>> around i2c device naming and handling. After installing several kernel >>> versions, various versions of ivtv and various versions of lirc, i2c is >>> again giving me grief with slowness in reading addresses on the PVR bus >>> which result in udev failing and many many other problems. >>> >>> I'm about to blitz the box again and go for a fresh install (why does >>> this >>> starting to feel more and more like microsoft). >>> >>> Should I stick to my guns and have another go with FC5, or is FC4 going >>> to >>> be better? Perhaps all my i2c problems are because of new 2.6.16/17 >>> kernels >>> and not the distro? Should I contemplate a completely new distro (new >>> ground for me) >>> >>> whaddayareckon? >> >> I'd be surprised if we can't get it to work with you having to >> re-install FC5 from scratch. But, without the messages from your >> /var/log/messages file, were just guessing as to what's wrong here. >> >> Can you post all of the IVTV initialization messages? >> >> -- >> Kevin J. Cummings >> [EMAIL PROTECTED] >> [EMAIL PROTECTED] >> [EMAIL PROTECTED] >> Registered Linux User #1232 (http://counter.li.org) >> >> _______________________________________________ >> ivtv-users mailing list >> [email protected] >> http://ivtvdriver.org/mailman/listinfo/ivtv-users > > > > -------------------------------------------------------------------------------- > > > _______________________________________________ > ivtv-users mailing list > [email protected] > http://ivtvdriver.org/mailman/listinfo/ivtv-users _______________________________________________ ivtv-users mailing list [email protected] http://ivtvdriver.org/mailman/listinfo/ivtv-users
