From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from webmail.icp-qv1-irony-out1.iinet.net.au ([203.59.1.146]) by www.linuxtv.org with esmtp (Exim 4.63) (envelope-from ) id 1LHrhW-00018U-GV for linux-dvb@linuxtv.org; Wed, 31 Dec 2008 04:24:56 +0100 MIME-Version: 1.0 From: "sonofzev@iinet.net.au" To: sonofzev@iinet.net.au, 'Devin Heitmueller' Date: Wed, 31 Dec 2008 12:24:47 +0900 Message-Id: <61079.1230693887@iinet.net.au> Cc: linux-dvb@linuxtv.org Subject: Re: [linux-dvb] DVICO dual express incorrect readback of firmware message (2.6.28 kernel) Reply-To: sonofzev@iinet.net.au List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0952977434==" Mime-version: 1.0 Sender: linux-dvb-bounces@linuxtv.org Errors-To: linux-dvb-bounces+mchehab=infradead.org@linuxtv.org List-ID: --===============0952977434== Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset="iso-8859-1"



On Wed Dec 31 13:58 , "Devin Heitmueller= " sent:

On Tue, Dec 30, 2008 at 9:55 PM, sonofzev@iinet.n= et.au
<sonofzev@iinet.net.au> wrote:
> Upgrade to latest hg...
>
> Issue is still occurring.
>
> I also noticed some other messages in dmesg that I didn't see before t= hat
> hopefully may help.
>
> cheers
> Allan
>
> Here is the output..
>
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> zl10353: write to reg 5f failed (err =3D -5)!
> zl10353: write to reg 71 failed (err =3D -5)!
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 4)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> zl10353: write to reg 5f failed (err =3D -5)!
> zl10353: write to reg 71 failed (err =3D -5)!
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> zl10353_read_register: readreg error (reg=3D6, ret=3D=3D-5)
> zl10353: write to reg 55 failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg 56 failed (err =3D -5)!
> zl10353: write to reg 5e failed (err =3D -5)!
> zl10353: write to reg 5c failed (err =3D -5)!
> zl10353: write to reg 64 failed (err =3D -5)!
> zl10353: write to reg cc failed (err =3D -5)!
> zl10353: write to reg 65 failed (err =3D -5)!
> zl10353: write to reg 66 failed (err =3D -5)!
> zl10353: write to reg 6c failed (err =3D -5)!
> zl10353: write to reg 6d failed (err =3D -5)!
> zl10353: write to reg 6e failed (err =3D -5)!
> zl10353: write to reg 6f failed (err =3D -5)!
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> zl10353: write to reg 5f failed (err =3D -5)!
> zl10353: write to reg 71 failed (err =3D -5)!
> zl10353_read_register: readreg error (reg=3D6, ret=3D=3D-5)
> zl10353: write to reg 55 failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 4-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 4-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 4)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> zl10353: write to reg 5f failed (err =3D -5)!
> zl10353: write to reg 71 failed (err =3D -5)!
> zl10353_read_register: readreg error (reg=3D6, ret=3D=3D-5)
> zl10353: write to reg 55 failed (err =3D -5)!
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg 56 failed (err =3D -5)!
> zl10353: write to reg 5e failed (err =3D -5)!
> zl10353: write to reg 5c failed (err =3D -5)!
> zl10353: write to reg 64 failed (err =3D -5)!
> zl10353: write to reg cc failed (err =3D -5)!
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> zl10353: write to reg 65 failed (err =3D -5)!
> zl10353: write to reg 66 failed (err =3D -5)!
> zl10353: write to reg 6c failed (err =3D -5)!
> zl10353: write to reg 6d failed (err =3D -5)!
> zl10353: write to reg 6e failed (err =3D -5)!
> zl10353: write to reg 6f failed (err =3D -5)!
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> zl10353: write to reg 5f failed (err =3D -5)!
> zl10353: write to reg 71 failed (err =3D -5)!
> zl10353_read_register: readreg error (reg=3D6, ret=3D=3D-5)
> zl10353: write to reg 55 failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg ea failed (err =3D -5)!
> zl10353: write to reg 56 failed (err =3D -5)!
> zl10353: write to reg 5e failed (err =3D -5)!
> zl10353: write to reg 5c failed (err =3D -5)!
> zl10353: write to reg 64 failed (err =3D -5)!
> zl10353: write to reg cc failed (err =3D -5)!
> zl10353: write to reg 65 failed (err =3D -5)!
> zl10353: write to reg 66 failed (err =3D -5)!
> zl10353: write to reg 6c failed (err =3D -5)!
> zl10353: write to reg 6d failed (err =3D -5)!
> zl10353: write to reg 6e failed (err =3D -5)!
> zl10353: write to reg 6f failed (err =3D -5)!
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 4-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 4-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 4-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 4-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 4)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: i2c output error: rc =3D -5 (should be 64)
> xc2028 4-0061: -5 returned from send
> xc2028 4-0061: Error -22 while loading base firmware
> zl10353: write to reg 5f failed (err =3D -5)!
> zl10353: write to reg 71 failed (err =3D -5)!
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 4-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 4-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 3-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 3-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 3-0061: Incorrect readback of firmware version.
> xc2028 4-0061: Loading firmware for type=3DD2633 DTV7 (90), id
> 0000000000000000.
> xc2028 4-0061: Loading SCODE for type=3DDTV6 QAM DTV7 DTV78 DTV8 ZARLI= NK456
> SCODE HAS_IF_4760 (620003e0), id 0000000000000000.
> xc2028 4-0061: Incorrect readback of firmware version.
> xc2028 3-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.
> xc2028 4-0061: Loading firmware for type=3DBASE F8MHZ (3), id
> 0000000000000000.

Do me a favor and please stop top posting. It's a violation of list policy= .

Were those there before you upgraded to the latest hg?

I suspect that perhaps the components are powered down, which is why
the i2c calls are failing. Very strange.

--
Devin J. Heitmueller
http://www.devinheitmueller.com
AIM: devinheitmueller
)


------------------------------------------------------------------
Hi Devin
 

I did not see the messages before upgrading. However, I cannot confirm if t= hey weren't there and I suspect they actually were. As the dmesg buffer is = being constantly overwritten by these errors, and after more recent checks = these more detailed messages aren't showing up any more.  I believe I = just missed them.

I will also enable the timing messages in my next kernel build but this pro= bably won't be for a couple of days. If I get a chance before NYE celebrati= ons tonight I will disable the option in MythTV that releases the adaptors = when not in use. I don't really need this option as there are no other TV a= pplications that will access these tuners. I will also check for any powers= aving options both in the kernel and in the PCIe configuration of the mobo.=


cheers

Allan





 








= --===============0952977434== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ linux-dvb mailing list linux-dvb@linuxtv.org http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb --===============0952977434==--