hmm, on Tue, Dec 01, 2009 at 09:02:36PM +0000, Jacob Meuser said that
> now, go read the mplayer manual and see what options are available for
> -vo xv. there are several. first try changing the xv adaptor, if
> possible. xvinfo(1) is probably useful as well. but don't just send us
> the dump of xvinfo.
-vo xv:adaptor=0 X crashes
-vo xv:adaptor=1 plays the movie
xvinfo lines:
X-Video Extension version 2.2
screen #0
Adaptor #0: "Intel(R) Textured Video"
number of ports: 16
port base: 70
...
Adaptor #1: "Intel(R) Video Overlay"
number of ports: 1
port base: 86
> oh, and since you mention fullscreen. does it only crash/reboot if you
> put it in fullscreen mode? what if you remove the pp filter?
no, fullscreen is not required for the crash.
removing the filter does not change the outcome (-noconfing all).
> some other things: BIOS settings? can you change the amount of video
> memory? this is an eeepc netbook, right? what are the screen
> dimensions? are the video dimensions larger than your screen? if you
> use mencoder to reencode it to a smaller frame size, does it still crash?
there are no bios settings regarding the video memory.
the screen dimensions are 800x480.
yes, the video is bigger than screensize: 852x480.
do you still want me to resize the video?
with the parameters mencoder has, that looks like
quite a daunting task...
> I'm sorry if it sounds like I'm being harsh, or asking for a lot, but
> imo, just because we're talking about a "multimedia" application,
> there's no extra excuses for not trying to understand the tools
> you're using.
but of course, by all means. you tell me what to do, i do it :]
it's not like there is a list of what-to-do's for debugging issues
like this. or if there is, and it is common knowledge, i have
some catching up to do...
-f
--
i could prove god statistically. -- george gallup
