[linux-dvb] Hauppauge NOVA-T-500 USB Disconnect with *-03-pre1.fw

Andy Thomas alt at picnic.demon.co.uk
Fri Aug 10 01:19:07 CEST 2007


Eduard Huguet wrote:
>
>     ---------- Missatge reenviat ----------
>     From: Nicolas Will < nico at youplala.net <mailto:nico at youplala.net>>
>     To: linux-dvb at linuxtv.org <mailto:linux-dvb at linuxtv.org>
>     Date: Thu, 09 Aug 2007 10:19:24 +0100
>     Subject: Re: [linux-dvb] Hauppauge NOVA-T-500 USB Disconnect with
>     *-03-pre1.fw
>     On Sun, 2007-08-05 at 00:53 +0100, Andy Thomas wrote:
>     >
>     > Unfortunately I'm still seeing the "USB disconnects" even with
>     the new
>     > firware and drivers on a new Hauppauge NOVA-T-500.
>
>
>     oooooh... <insert despair cry of your choice>
>
>     Got it too...
>
>
>             Aug  8 05:31:07 favia kernel: [35836.965561] usb 10-1: USB
>     disconnect, address 2
>             Aug  8 05:31:07 favia kernel: [35836.965568 ] ehci_hcd
>     0000:06:01.2: qh ffff810037bb80a0 (#00) state 4(has tds)
>             Aug  8 05:31:07 favia kernel: [35836.965784] mt2060 I2C
>     write failed (len=2)
>             Aug  8 05:31:07 favia kernel: [35836.965787] mt2060 I2C
>     write failed (len=6)
>             Aug  8 05:31:07 favia kernel: [35836.965790] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia lircd-0.8.2[4954]: error reading
>     '/dev/input/event4'
>             Aug  8 05:31:07 favia lircd-0.8.2[4954]: caught signal
>             Aug  8 05:31:07 favia lircd-0.8.2[4954]: closing
>     '/dev/input/event4'
>             Aug  8 05:31:07 favia kernel: [35836.973490] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35836.981548 ] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35836.989674] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35836.997752] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [ 35837.005851] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35837.013958] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35837.022052] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [ 35837.030165] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35837.038258] mt2060 I2C
>     read failed
>             Aug  8 05:31:07 favia kernel: [35837.184367] mt2060 I2C
>     write failed
>             Aug  8 05:32:55 favia kernel: [ 35945.471227] dvb-usb:
>     error while stopping stream.
>             Aug  8 05:32:55 favia kernel: [35945.472993] mt2060 I2C
>     write failed (len=2)
>             Aug  8 05:32:55 favia kernel: [35945.472996] mt2060 I2C
>     write failed (len=6)
>             Aug  8 05:32:55 favia kernel: [35945.472998] mt2060 I2C
>     read failed
>             Aug  8 05:32:55 favia kernel: [35945.479290] mt2060 I2C
>     read failed
>             Aug  8 05:32:55 favia kernel: [35945.487364] mt2060 I2C
>     read failed
>             Aug  8 05:32:55 favia kernel: [35945.495660] mt2060 I2C
>     read failed
>
>
>     tree from 2 days ago, *03-pre1.fw.
>
>     Nico
>
>
>
> Same here. It seems to happen very ocasionally (as before...), but 
> they still happens.
>
> Cheers,
>   Eduard
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

Are you using the remote control with the NOVA-T-500 (looks like its on 
input 4 in your listing)?  When I get these errors lircd dies as well.

I've tried with the latest kernel 2.6.22-9-generic but still get the 
same problem.

However if I use a keyboard and not the remote then the system seems to 
be much more stable - the remote usage seems to provoke these errors.
Also the remote does not allow key repeats (only one "event per key press").

Regards,

Andy.




More information about the linux-dvb mailing list