All of lore.kernel.org
 help / color / mirror / Atom feed
From: "petercarm" <linuxtv@hotair.fastmail.co.uk>
To: linux-dvb@linuxtv.org
Subject: Re: [linux-dvb] Nova-TD and I2C read/write failed
Date: Tue, 04 Nov 2008 15:40:23 +0000	[thread overview]
Message-ID: <1225813223.7609.1282933233@webmail.messagingengine.com> (raw)
In-Reply-To: <e28a31000811040730qef2d86bsf04cc389c3800c1e@mail.gmail.com>

Thanks for the quick replies. I'll give that a try.

On Tue, 4 Nov 2008 15:30:22 +0000, "Greg Thomas"
<Greg@thethomashome.co.uk> said:
> 2008/11/4 petercarm <linuxtv@hotair.fastmail.co.uk>
> 
> > My build is gentoo with 2.6.25 kernel and mercurial V4L using
> > dvb-usb-dib0700-1.10.fw   The Hauppauge Nova-TD USB stick shows a USB ID
> > of 2040:5200.
> >
> > The card works for a few hours and then floods dmesg with "DiB0070 I2C
> > write failed" messages.
> >
> > I've found plenty of passing references to this problem, but what do I
> > need to do to get this working?
> >
> > Do I need to change to the 1.20 firmware?
> >
> 
> FWIW, I suffered from the same problem, and found that simply blatting
> the
> 1.20 firmware from
> http://www.linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-TD-Stick#Firmwareover
> the 1.10 firmware solved it for me.
> 
> Greg

_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

      parent reply	other threads:[~2008-11-04 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-03 21:11 [linux-dvb] [PATCH] Add suport for AverMedia Volar X remote Jose Alberto Reguero
2008-11-04 13:12 ` Antti Palosaari
2008-11-04 15:14   ` [linux-dvb] Nova-TD and I2C read/write failed petercarm
2008-11-04 15:24     ` Devin Heitmueller
     [not found]     ` <e28a31000811040730qef2d86bsf04cc389c3800c1e@mail.gmail.com>
2008-11-04 15:40       ` petercarm [this message]

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=1225813223.7609.1282933233@webmail.messagingengine.com \
    --to=linuxtv@hotair.fastmail.co.uk \
    --cc=linux-dvb@linuxtv.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.