<br><br>
<div><span class="gmail_quote">On 9/22/07, <b class="gmail_sendername">Michael T. Dean</b> <<a href="mailto:mtdean@thirdcontact.com">mtdean@thirdcontact.com</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">On 09/22/2007 01:27 AM, David Shay wrote:<br>><br>> On 9/21/07, Robert Johnston <<a href="mailto:anaerin@gmail.com">
anaerin@gmail.com</a>> wrote:<br>>><br>>> On 9/21/07, David Shay <<a href="mailto:david@shay.net">david@shay.net</a>> wrote:<br>>>><br>>>> I'm using SVN 14510 with a Via EX10000EG. Openchrome drivers.
<br>>>> All was working fine before this last SVN upgrade (which was<br>>>> pre-mythtv-vid merge). I went in and set up a new video profile,<br>>>> and to make things simple, created one which just used Via XVMC
<br>>>> all of the time. This box only watches MPEG2 recordings that are<br>>>> 720x480, so this should be fine.<br>>>><br>>>> Mythfrontend shows this error:<br>>>><br>>>> <datetime> VideoOutputXv: XvMC Adaptor Name: 'XV_SWOV' Unable to
<br>>>> create XvMC surface<br>>>><br>>>> CPU utilization then goes to about 96%.<br>>>><br>>>> Anything I did wrong here? What other debugging info is needed?<br>>><br>
>> From the looks of it, you don't have Xv or XvMC support in your<br>>> kernel/setup (I'm presuming XV_SWOV means something along the lines<br>>> of XVideo SoftWare Overlay Video).<br>>><br>
>> Check that your openchrome drivers are working AOK (Try using<br>>> mplayer with -vo XvMC and see if that works before trying to blame<br>>> Myth).<br>><br>> Not it. As I said, Myth before the mythtv-vid merge was working fine.
<br>> Xine -V xxmc works just fine too.<br><br>Did you do a make distclean? I've heard reports of mmx being disabled<br>until the user did a make distclean. (Also, knowing it worked before<br>doesn't prove that it was enabled by configure. Check the configure
<br>output.)<br><br>Mike</blockquote>
<div> </div>
<div>
<div>Well, this is now "solved" in the sense that I don't think it was really a problem in the first place. The CPU problem was a red herring. The error message that I found when attempting to track down the cause of the CPU problem (which must have been something other than reverting to software decoding...) was apparently not a real problem, either, according to danielk. Essentially, chalk it up to user error...
</div></div><br> </div>