On Wed, 2009-12-09 at 08:08 -0500, Robert wrote:
> On Tue, 08 Dec 2009 20:35:43 -0500 Andy wrote:
> AW> This second CX25843 chip has gone braindead or the I2C bus from the
> AW> second CX23416 chip isn't working. That's chip decodes analog video
> AW> signals into digital data. Until it responds no video will work.
> AW>
> AW> Check
> AW>
> AW> $ modinfo ivtv
> AW> $ modinfo cx25840
> AW>
> AW> and see what debugging options you can turn on in /etc/modprobe.conf for
> AW> these modules. It might give insight into what the problem is.
>
> Hi ANdy, thanks for responding.
>
> I turned on debug for both modules:
>
> # cat /etc/modprobe.d/mythtv.conf
> #parm: debug:Debug level (bitmask). Default: 0
> # 1/0x0001: warning
> # 2/0x0002: info
> # 4/0x0004: mailbox
> # 8/0x0008: ioctl
> # 16/0x0010: file
> # 32/0x0020: dma
> # 64/0x0040: irq
> # 128/0x0080: decoder
> # 256/0x0100: yuv
> # 512/0x0200: i2c
> # 1024/0x0400: high volume
> # 0x0208 = warning,info,ioctl,i2c
> option ivtv debug=0x020B
>
> #parm: debug:Debugging messages [0=Off (default) 1=On] (int)
> option cx25840 debug=1
>
>
> I've included more from dmesg below, but this looks relevant:
>
> [ 15.759140] cx25840 0-0044: firmware: requesting v4l-cx25840.fw
> [ 15.759167] cx25840 1-0044: firmware: requesting v4l-cx23885-avcore-01.fw
> [ 15.976478] cx25840 1-0044: firmware load i2c failure
> [ 19.814867] cx25840 0-0044: loaded v4l-cx23885-avcore-01.fw firmware (16382
> bytes)
Yes. This is further confirmation that communications with the second
CX25843 chip isn' working. The cx25840 module is misdetecting it as a
CX23885 A/V core - a fallback position.
> AW> Highest probability cause is that that CX25843 is dead.
>
> ugh. would this cause system instability? I've had some random reboots. If
> so, there is a module parameter to disable the 2nd tuner to restore stability?
Random reboots would be caused by PCI bus problems. That would be more
likely the fault of a defective CX23416 chip or bad interactions between
the PCI bridge on the PVR-500 and the motherboard chipset. (VIA chipset
are problems at times.)
So try
# modprobe ivtv cardtype=0,-1
to autodetect the first unit on the PVR-500 and to ignore the second
unit.
> AW> If you're lucky, it's only some Linux I2C subsystem problem in software.
>
> <crosses fingers>
You might have some luck with blacklisting the ivtv module so that it
doesn't load at boot and then modprobing it later when the flurry of PCI
bus activity at boot has died down. I wouldn't get my hopes up though.
You should try an test the board in a Windows machine. The I2C
subsystem debug messages are compiled out of the kernel by most distro's
by default. It's hard to see what is going on the i2c buses without
recompiling the kernel. :(
Regards,
Andy
_______________________________________________
ivtv-users mailing list
[email protected]
http://ivtvdriver.org/mailman/listinfo/ivtv-users
