linux-kernel - Nova-T USB-Stick Model 1277: DiB0070 I2C read / write failed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Fri, 16 Apr 2010 19:26:16 +0200
From:	linux-media@...7.de
To:	linux-kernel@...r.kernel.org
Subject: Nova-T USB-Stick Model 1277: DiB0070 I2C read / write failed

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/