On Monday 12 June 2006 04:22, Aristedes Maniatis wrote:
> On 12/06/2006, at 12:10 AM, Hans Verkuil wrote:
> > 'didn't work' as in: it refused to load, or as in: nothing appeared
> > in the log? The modprobe.conf options line is correct.
>
> The logs show the drivers loading, but then these errors at the end:
>
> 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 0xc0045627!
> ivtv0: i2c addr 0x44 not found for command 0x40345622!
> 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
>
> Other than this all the associated modules appear to load fine:
> tuner, tveeprom, wm8775 and tda9887.
>
> > Try two things:
> >
> > First load ivtv with the newi2c=0 option.
>
> That seemed to make no difference except "i2cdetect -l" showed it
> loading in i2c-3 and i2c-4 after the NVIDIA device. With the option
> removed, it loads as i2c-0 and i2c-1 and the NVIDIA driver after.
>
> > If that still gives the same
> > problems, then use 'i2cdetect -a 0' to see if the cx25840 is even
> > detected on the i2c bus. If not (you get 'XX' for address 0x44)
> > then it
> > is likely to be a hardware problem.
>
> 0x43 shows UU, but 0x44 shows XX. So this means the card itself is
> being detected, but a particular address mapped to the card is
> faulty? I guess it is possible that this was just coincidental to my
> upgrade of the kernel. Perhaps I need to purchase another card to
> test for sure.
>
> If it is important, my working card (PVR 250) at ivtv1 shows XX in
> that address as well, but it isn't trying to use cx25840.
Just checking: you are using the correct i2c bus number with
i2cdetect -a? E.g. the same one as reported by i2cdetect -l for your
card.
Everything points strongly towards a broken cx25840. Several people are
having problems reading the eeprom, but for them the eeprom is still
clearly visible on the i2c bus, so that seems to be a true software bug
somewhere (kernel or driver, that's yet to be determined). Whereas here
it looks to be broken hardware.
If you discover that it works fine in another computer (Windows or
linux), then I'm very interested of course. But until now whenever a
chip doesn't show up on an i2cdetect -a, then the card was broken.
It's rare for this to happen to a PVR150, the PVR500 seems to be more
fragile in that respect.
Sorry, I wish I had better news...
Regards,
Hans
_______________________________________________
ivtv-devel mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-devel
