[mythtv-users] will Nova-T 500 work?

[Henrik Beckman]

On the pre hotplug driver i was, 'Hauppauge Nova-T 500 Dual DVB-T
successfully deinitialized and disconnected' and then after a while you got
an oops.

On the newer hotplug drivers you get an write failed for mt2060 error
message, I don´t have the exact message at hand right now.

The newer driver as said has hotplug and requier a restart of
mythtv-backend, I think this disconnect soon will be handled by the
  backend and only be a few seconds long gap in the recording.

There is work being done but since the error seems to be connected to the
USB layer rather than the DVB layer i is hard to track down. The linux-dvb
mailinglist has more information about the problem and what improvments that
have been done, it seems like it is more or less stable on tmessagehe latest
kernel if you don´t use EIT.

If anyone could spare time to snoop the usb traffic while using the card in
windows let the DVB list know.

For me the card is stable but I don´t use EIT, can´t realy remeber last time
a recording failed.

/Henrik


On 5/25/07, Leigh Porter <leigh at leighporter.org> wrote:
>
>
>
> Does anybody here know what the status of a real fix for this is? There is
> loads and loads of archived talk about the Nova-T 500 on various lists, but
> I have never found anything that actually details what causes these
> problems...
>
>
> Is it being worked on or should all the Nova-T 500 users give up and get
> something else?
>
>
> --
> Leigh
>
>
>
>
>
>  On 24 May 2007, at 13:08, Eduard Huguet wrote:
>
>   Hi,
>     You get now a trace of errors about reading and/or writing to mt2060
> device (can't remember exactly how the trace looks, but it's for sure about
> these device).
>
> Cheers
>   Eduard
>
>
>
>
> ---------- Missatge reenviat ----------
> > From: "Paul Mason" < latepaul at gmail.com>
> > To: "Discussion about mythtv" <mythtv-users at mythtv.org>
> > Date: Thu, 24 May 2007 12:47:07 +0100
> > Subject: Re: [mythtv-users] will Nova-T 500 work?
> >
> >
> > On 26/04/07, Henrik Beckman <henrik.list at gmail.com > wrote:
> > >
> > >
> > > I wrote a small script the ran in cron every minute, the script itself
> > > looped every 10 seconds.
> > > Checking messages for the disconnect message,  made a date stamped
> > > copy of messages and cp  /dev/null  to the message file then rebooted,  my
> > > recordings  start 3 minutes ahead to  be able to do a reboot since my
> > > disconnects only/mostly occured while "opening" a channel, haven´t had any
> > > disconnects for a long while though.
> >
> >
> >
> > I have a script that does something like this. At the moment I'm running
> > MythTV 0.20 and 2.6.20.
> >
> >
> > I would be simple to have a script running through messages each minute
> > > and restarting myth-backend in case of a disconnect. The oopses where
> > > much worse since the occasionaly needed a hard reset.
> >
> >
> >
> > How do you detect the disconnects? I haven't been able to identify a
> > message in the  mythbackend log (perhaps I need to run with more verbose
> > output?). Now that I'm in a position to do so (finally got broadband at
> > home) I'm intending to upgrade to 0.20-fixes and probably a 2.6.21kernel. However I'm concerned that without an Oops to grep for in
> > /var/log/messages I'm not going to know how to detect when a disconnect has
> > occurred.
> >
> >
> >
> > --
> > Paul Mason
> >
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mythtv.org/pipermail/mythtv-users/attachments/20070525/084f59a0/attachment-0001.htm