[mythtv-users] PVR-350 displays OSD but not video - .17
apt-getupgrade
John Harvey
john.p.harvey at btinternet.com
Mon Apr 11 19:31:54 UTC 2005
I believe this is caused by blt_fill code in the firmware crashing
occasionally. I was working on some changes and managed to get to a point
where this was very reproducible (though not every time).
In libs/libmythtv/videout_ivtv.cpp in the function ClearOSD() there is some
code that looks something like
if (version > 0x00000????)
{
Clear using old method
} else
{
Clear using BLTFILL;
}
If you change this so it always uses the old method you might find it fixes
the problem. Easiest way is to just make the number being compared against
larger termporarily.
I spent ages looking at this and came to the conclusion that the firmware is
broken in some way or there is a horrible interaction with the dma code.
John
> -----Original Message-----
> From: mythtv-users-bounces at mythtv.org [mailto:mythtv-users-
> bounces at mythtv.org] On Behalf Of Darren Hart
> Sent: 11 April 2005 19:52
> To: Dave; Discussion about mythtv
> Subject: Re: [mythtv-users] PVR-350 displays OSD but not video - .17 apt-
> getupgrade
>
> Dave wrote:
> > On Feb 23, 2005 10:58 PM, Mark Matula <mmatula at ratula.net> wrote:
> >
> >>On Tue, 22 Feb 2005, Mark Matula wrote:
> >>
> >>
> >>>I've seen a lot of different issues with the 350 since folks have
> upgraded
> >>>but none of them exactly match what happened to my box. I've search
> the
> >>>archives since the .17 release, but haven't wrapped my mind around a
> >>>solution.
> >>>
> >>>My 350 TV out was working fine with .16 installed on Debian unstable
> from
> >>>the .debs on
> http://dijkstra.csh.rit.edu/~mdz/debian/dists/unstable/mythtv/
> >>
> >>[. . .]
> >>
> >>>Before I do anything drastic, I was looking for input on how to
> troubleshoot
> >>>this.
> >>>- Upgrade ivtv?
> >>>- Un-reinstall the .17 debs?
> >>>- Uninstall .17 and try to roll back to .16?
> >>
> >>Turns out an ivtv driver update was in order. I'm at version 0.2.0-rc3
> >>right now, and all seems well.
> >>
> >>--
> >>Mark Matula
> >>Mikey, you will be missed:
> >>http://eblo.ratula.net/mikey.html
> >>
> >>
> >>_______________________________________________
> >>mythtv-users mailing list
> >>mythtv-users at mythtv.org
> >>http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
> >>
> >>
> >>
> >
> >
> > Hi Mark,
> > I'm in a similar situation as you - I was using IVTV .19, but after
> > upgrading Myth to .17, it appears I need to upgrade IVTV.
> > I tried upgrading to IVTV 0.2.0, but ran into major problems
> > (system freezes, etc).
> > Did you follow a specific set of instructions to do the IVTV upgrade?
> > Did you have any major issues/problems during the IVTV upgrade?
> >
>
> Has anyone solved the myth 0.17 + ivtv 0.[23].* issues? I still get:
>
> Mar 11 19:06:53 leeloo kernel: ivtv: 1000 ms time out waiting for firmware
> Mar 11 19:06:53 leeloo kernel: ivtv: Failed api call 0x00000015 with
> result 0xfffffff0
> Mar 11 19:06:53 leeloo kernel: ivtv: DEC: couldnt read clock
>
> in the logs when the playback locks up (usually when seeking). Sound is
> still often very deep (like a slow playback, but the speed seems right).
>
> I haven't been getting any feedback on these problems from here of ivtv,
> is there another list I should try?
>
> --Darren
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
More information about the mythtv-users
mailing list