From: "Timothy D. Lenz" <tlenz@vorgon.com>
To: linux-media@vger.kernel.org
Subject: Re: DViCO FusionHDTV7 Dual Express I2C write failed
Date: Mon, 17 Jan 2011 16:12:54 -0700 [thread overview]
Message-ID: <4D34CCF6.5040603@vorgon.com> (raw)
In-Reply-To: <20101207190753.GA21666@io.frii.com>
I just tried to update from kernel 2.6.34 and in doing so had to switch
to git for v4l. I noticed the chip in this this post and saved it to
look at latter. now I'm glad I did. I ran into the same problem. Driver
seems to load ok, but when I try to start vdr I get thet same messages
in syslog.
Jan 16 21:50:48 LLLx64-32 vdr: [6170] saved setup to
/usr/local/dvb/VDR/config/setup.conf
Jan 16 21:50:49 LLLx64-32 kernel: xc5000: waiting for firmware upload
(dvb-fe-xc5000-1.6.114.fw)...
Jan 16 21:50:49 LLLx64-32 kernel: xc5000: firmware read 12401 bytes.
Jan 16 21:50:49 LLLx64-32 kernel: xc5000: firmware uploading...
Jan 16 21:50:49 LLLx64-32 vdr: [6176] section handler thread ended
(pid=6170, tid=6176)
Jan 16 21:50:49 LLLx64-32 kernel: xc5000: I2C write failed (len=3)
Jan 16 21:50:49 LLLx64-32 kernel: xc5000: firmware upload complete...
Jan 16 21:50:50 LLLx64-32 vdr: [6175] tuner on frontend 0/0 thread ended
(pid=6170, tid=6175)
Jan 16 21:50:50 LLLx64-32 kernel: xc5000: waiting for firmware upload
(dvb-fe-xc5000-1.6.114.fw)...
Jan 16 21:50:50 LLLx64-32 kernel: xc5000: firmware read 12401 bytes.
Jan 16 21:50:50 LLLx64-32 kernel: xc5000: firmware uploading...
Jan 16 21:50:50 LLLx64-32 vdr: [6174] CI adapter on device 0 thread
ended (pid=6170, tid=6174)
.......
On 12/7/2010 12:07 PM, Mark Zimmerman wrote:
> Greetings:
>
> I have a DViCO FusionHDTV7 Dual Express card that works with 2.6.35 but
> which fails to initialize with the latest 2.6.36 kernel. The firmware
> fails to load due to an i2c failure. A search of the archives indicates
> that this is not the first time this issue has occurred.
>
> What can I do to help get this problem fixed?
>
> Here is the dmesg from 2.6.35, for the two tuners:
>
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
> xc5000: firmware read 12401 bytes.
> xc5000: firmware uploading...
> xc5000: firmware upload complete...
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
> xc5000: firmware read 12401 bytes.
> xc5000: firmware uploading...
> xc5000: firmware upload complete..
>
> and here is what happens with 2.6.36:
>
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
> xc5000: firmware read 12401 bytes.
> xc5000: firmware uploading...
> xc5000: I2C write failed (len=3)
> xc5000: firmware upload complete...
> xc5000: Unable to initialise tuner
> xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
> xc5000: firmware read 12401 bytes.
> xc5000: firmware uploading...
> xc5000: I2C write failed (len=3)
> xc5000: firmware upload complete...
>
> -- Mark
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2011-01-17 23:13 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20101207190753.GA21666@io.frii.com>
2011-01-10 2:14 ` DViCO FusionHDTV7 Dual Express I2C write failed Mark Zimmerman
2011-01-19 15:59 ` VDR User
2011-01-19 16:13 ` Devin Heitmueller
2011-01-19 17:22 ` VDR User
2011-01-19 17:39 ` Mark Zimmerman
2011-01-24 15:49 ` Mark Zimmerman
2011-01-24 15:57 ` Devin Heitmueller
2011-01-25 14:27 ` Mark Zimmerman
2011-01-19 19:01 ` Timothy D. Lenz
2011-01-17 23:12 ` Timothy D. Lenz [this message]
2011-02-12 15:29 ` [get-bisect results]: " Mark Zimmerman
2011-02-12 16:27 ` Andy Walls
2011-02-12 16:36 ` Mark Zimmerman
2011-02-12 16:46 ` Andy Walls
2011-02-12 17:03 ` Mark Zimmerman
2011-02-12 19:05 ` Mark Zimmerman
2011-02-12 20:48 ` Andy Walls
2011-02-13 14:47 ` [corrected get-bisect " Mark Zimmerman
2011-02-13 14:52 ` Devin Heitmueller
2011-02-13 20:26 ` Mark Zimmerman
2011-02-13 21:26 ` Andy Walls
2011-02-14 0:16 ` Andy Walls
2011-02-14 14:29 ` Devin Heitmueller
2011-02-14 0:37 ` Mark Zimmerman
2011-02-14 8:05 ` Jean Delvare
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D34CCF6.5040603@vorgon.com \
--to=tlenz@vorgon.com \
--cc=linux-media@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox