[mythtv-users] ATrpms 0.16-82.1.rhfc2.at -> No XvMC found +
ijr at po.cwru.edu
Sun Nov 28 01:57:59 UTC 2004
On Saturday 27 November 2004 08:45 pm, Jarod Wilson wrote:
> On Friday 26 November 2004 22:28, Isaac Richards wrote:
> > On Saturday 27 November 2004 01:20 am, Jarod C. Wilson wrote:
> > > On Nov 26, 2004, at 9:56 PM, Romain Kang wrote:
> > > > This morning, I used "apt-get upgrade" to bring my MythTV
> > > > installation to Axel's 0.16-82.1.rhfc2.at RPM set (aka
> > > > mythtv-suite-0.16-44.at). I used the updated installation to view
> > > > previously transcoded .nuv's. Then this evening, I tried to view
> > > > newly recorded captures from a PVR-350. This failed, with
> > > > mythfrontend producing messages about No XvMC found
> > > > followed by
> > > > Segmentation fault
> > > > and a core dump. This may be related to my Radeon 9200SE's lack of
> > > > support for XvMC.
> > > >
> > > > Rolling back to libmyth-0.16-81.rhfc2.at and keeping the rest of the
> > > > the updated packages appear to have restored normal operation.
> > >
> > > The new builds are the first to include full nVidia XvMC support, which
> > > I believe gets enabled by default when built into the package (at least
> > > that's the case w/my EPIA for Unichrome XvMC). Just go into the
> > > frontend settings and disable XvMC on the hardware decoding setup page,
> > > since no, your Radeon doesn't do XvMC, esp. the nVidia variant.
> > Please disable the xvmc by default in the rpms. I really don't want to
> > deal with the extra bug reports.
> Axel is rebuilding accordingly. We're discussing what to do about a
> unichrome build and an nvidia xvmc build...
Cool. Separate rpms makes sense to me..
More information about the mythtv-users