From: linux-media@jd67.de
To: linux-kernel@vger.kernel.org
Subject: Nova-T USB-Stick Model 1277: DiB0070 I2C read / write failed
Date: Fri, 16 Apr 2010 19:26:16 +0200 [thread overview]
Message-ID: <201004161926.17040.linux-media@jd67.de> (raw)
Hi,
I have some trouble with a Nova-T USB-Stick.
It's a "WinTV NOVA-T Stick Value, Model 1277" USB-ID:2040:7070.
I use three of it with an ASRock 939A785GMH/128M Mainboard (AMD A785 / SB710) as an Myth-Server.
Currently everything running fine after following all advices found at:
http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-NOVA-T-Stick (Making it Work).
At the modules
* Disabled dvb-rec-polling
* Enabled LNA
* Additional Disabled usb-suspend.
At Myth-Backend
* Disabled all EIT-scans
* set an tuning delay to 1000ms.
Before I changing mythtv, I had errors like:
Apr 13 15:58:07 vdr1 kernel: [ 1887.816045] dvb-usb: error while stopping stream.
Apr 13 15:58:13 vdr1 kernel: [ 1893.137037] dvb-usb: error while enabling fifo.
Apr 13 15:59:38 vdr1 kernel: [ 1978.672048] dvb-usb: error while stopping stream.
Apr 13 16:00:18 vdr1 kernel: [ 2018.165037] DiB0070 I2C write failed
Apr 13 16:00:23 vdr1 kernel: [ 2023.176044] DiB0070 I2C read failed
Apr 13 16:00:26 vdr1 kernel: [ 2026.468132] DiB0070 I2C write failed
Before I disabled the dvb-rec-polling, I had usb-fullstops:
ehci_hcd 0000:00:13.2: force halt; handhake f804c424 00004000 00000000 -> -110
I tested with ubuntu-kernels 2.6.31, 32 and 33.
I can live with this settings, but I have some bad feeling going in holiday for a longer while, leaving the system
alone. Is there anything I can do, help fixing this issues. Enable debug options, sending logs?
Would it help, to use an other usb-chipset (VIA, etc)?
Greetings from Frankfurt
Jan
reply other threads:[~2010-04-16 17:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201004161926.17040.linux-media@jd67.de \
--to=linux-media@jd67.de \
--cc=linux-kernel@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 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.