On Thursday 14 December 2006 19:13, Rich wrote:
> Thanks Dirk, that worked.
> Note for others: newi2c=1 not i2cnew=false
Rich,
Can you do a test for me? I'm surprised that it failed with the default
autodetect setting.
First load tveeprom with: modprobe tveeprom debug=1
Then load ivtv with modprobe ivtv newi2c=1.
Please post the INIT IVTV messages.
Thanks,
Hans
>
> Rich
>
> > I had a similar problem, try to set a module paramter
> > "i2cnew=false" because
> > also with my card the I2C code doesn't work!
> >
> > Am Donnerstag, 14. Dezember 2006 17:36 schrieb Rich:
> >> Does this mean something fatal has happend to this card?
> >>
> >> The card had been working for well over a year now. After moving
> >> from FC5
> >> ivtv v7.2 to FC6 ivtv v8.2 I am getting errors. The PVR500 card
> >> in this system loads find. The other system that I have with a
> >> PVR-350 now running FC6 ivtv v8.2 works fine.
> >>
> >> Thanks,
> >> Rich
> >>
> >> ivtv: ==================== START INIT IVTV ====================
> >> ivtv: version 0.8.2 (tagged release) loading
> >> ivtv: Linux version: 2.6.18-1.2849.fc6 SMP mod_unload 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. sd 0:0:0:0: Attached scsi generic sg0 type 0
> >> sd 1:0:0:0: Attached scsi generic sg1 type 0
> >> eth1: forcedeth.c: subsystem: 01462:0300 bound to 0000:00:05.0
> >> ACPI: PCI Interrupt Link [APCJ] enabled at IRQ 21
> >> ACPI: PCI Interrupt 0000:00:06.0[A] -> Link [APCJ] -> GSI 21
> >> (level, high)
> >> -> IRQ 193
> >> PCI: Setting latency timer of device 0000:00:06.0 to 64
> >> intel8x0_measure_ac97_clock: measured 51586 usecs
> >> intel8x0: clocking to 46867
> >> ivtv0: Autodetected Hauppauge card (cx23415 based)
> >> i2c_adapter i2c-0: nForce2 SMBus adapter at 0x4c00
> >> i2c_adapter i2c-1: nForce2 SMBus adapter at 0x4c40
> >> ACPI: PCI Interrupt 0000:02:07.0[A] -> Link [APC2] -> GSI 17
> >> (level, low)
> >> -> IRQ 209
> >> ivtv0: Unreasonably low latency timer, setting to 64 (was 32)
> >> ieee1394: Host added: ID:BUS[0-00:1023] GUID[0010dc00006baf5b]
> >> ivtv0: loaded v4l-cx2341x-enc.fw firmware (262144 bytes)
> >> ivtv0: loaded v4l-cx2341x-dec.fw firmware (262144 bytes)
> >> tveeprom 2-0050: Huh, no eeprom present (err=-121)?
> >> tveeprom 2-0050: Encountered bad packet header [01]. Corrupt or
> >> not a Hauppauge eeprom.
> >> ivtv0: Invalid EEPROM
> >> ivtv0: Encoder revision: 0x02050032
> >> ivtv0: Decoder revision: 0x02020023
> >> ivtv0: Registered device video0 for encoder MPEG
> >> ivtv0: Registered device video32 for encoder YUV
> >> ivtv0: Registered device vbi0 for encoder VBI
> >> ivtv0: Registered device video24 for encoder PCM audio
> >> ivtv0: Registered device radio0 for encoder radio
> >> ivtv0: Registered device video16 for decoder MPEG
> >> ivtv0: Registered device vbi8 for decoder VBI
> >> ivtv0: Registered device vbi16 for decoder VOUT
> >> ivtv0: Registered device video48 for decoder YUV
> >> ivtv0: loaded v4l-cx2341x-init.mpg firmware (155648 bytes)
> >> ivtv0: i2c hardware 0x00000008 (msp3400) not found for command
> >> 0xc008561c!
> >> ivtv0: i2c addr 0x21 not found for command 0x4008646f!
> >> ivtv0: i2c hardware 0x00000008 (msp3400) not found for command
> >> 0x4008646d!
> >> ivtv0: i2c hardware 0x00000008 (msp3400) not found for command
> >> 0xc008561c!
> >> ivtv0: i2c hardware 0x00000008 (msp3400) not found for command
> >> 0xc008561c!
> >> ivtv0: i2c hardware 0x00000008 (msp3400) not found for command
> >> 0xc008561c!
> >> ivtv0: Initialized Hauppauge WinTV PVR-350, card #0
> >> ivtv: ====================== NEXT CARD ======================
> >>
> >>
> >> _______________________________________________
> >> ivtv-devel mailing list
> >> [email protected]
> >> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
> >
> > _______________________________________________
> > ivtv-devel mailing list
> > [email protected]
> > http://ivtvdriver.org/mailman/listinfo/ivtv-devel
>
> _______________________________________________
> ivtv-devel mailing list
> [email protected]
> http://ivtvdriver.org/mailman/listinfo/ivtv-devel
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
