Joe Rutledge | 1 May 2003 13:33
Favicon

Bug Report: Mplayer crash using DGA2 with Sorenson Video and a GeForce 2

[Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
This was built using the most recent Gentoo ebuild and thus I had no 
control over configure or the make process, hence no debug output, 
sorry. It's fine using all other valid video drivers for my system. I'm 
also using the most recent nvidia X driver and the most recent ALSA 
drivers. I am using the most recent version of xfree86 as well.

The file in question is available online at

http://www.spoiler.nl/electrifying/movies/electrifying.mov

If you REALLY need the debug I'll do a download and hand build.

In other news, thanks for making the greatest media player I've come 
across, excellent work. I hope this bug report will help you continue to 
improve it.

Thanks,

Joe

------------------------------------------------------------------------

And now.... lots of info!

joeshmoe root # mplayer -vo dga /home/joe/downloads/electrifying.mov

MPlayer 0.90rc5-3.2.2 (C) 2000-2003 Arpad Gereoffy (see DOCS)

CPU: Intel Pentium 4 Willamette (Family: 8, Stepping: 7)
(Continue reading)

Jonathan Rogers | 1 May 2003 17:55

Re: Bug Report: Mplayer crash using DGA2 with Sorenson Video and a GeForce 2

[Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
Joe Rutledge wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> This was built using the most recent Gentoo ebuild and thus I had no 
> control over configure or the make process, hence no debug output, 
> sorry. It's fine using all other valid video drivers for my system. I'm 
> also using the most recent nvidia X driver and the most recent ALSA 
> drivers. I am using the most recent version of xfree86 as well.
> 
> The file in question is available online at
> 
> http://www.spoiler.nl/electrifying/movies/electrifying.mov

The problem seems to be with DGA video. I also get a signal 11 with -vo dga:
-----------------------------snip-----------------------------
VO: [dga] 352x208 => 352x208 BGR 32-bit
vo_dga: DGA 2.0 available :-) Can switch resolution AND depth!
vo_dga: Selected hardware mode  400 x  300  <at>   75 Hz  <at>  depth 24, bitspp 32.
vo_dga: Video parameters by codec: 352 x 208, depth 24, bitspp 32.
vo_dga: Framebuffer mapping failed!!!
FATAL: Cannot initialize video driver.
init_vo failed

MPlayer interrupted by signal 11 in module: decode_video
- MPlayer crashed by bad usage of CPU/FPU/RAM.
   Recompile MPlayer with --enable-debug and make a 'gdb' backtrace and
   disassembly. For details, see DOCS/bugreports.html#crash.b.
- MPlayer crashed. This shouldn't happen.
   It can be a bug in the MPlayer code _or_ in your drivers _or_ in your gcc
   version. If you think it's MPlayer's fault, please read 
(Continue reading)

Jonathan Rogers | 1 May 2003 17:27

Re: Bug Report: Mplayer crash using DGA2 with Sorenson Video and a GeForce 2

[Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
Joe Rutledge wrote:
> [Automatic answer: RTFM (read DOCS, FAQ), also read DOCS/bugreports.html]
> This was built using the most recent Gentoo ebuild and thus I had no 
> control over configure or the make process, hence no debug output, 
> sorry. It's fine using all other valid video drivers for my system. I'm 
> also using the most recent nvidia X driver and the most recent ALSA 
> drivers. I am using the most recent version of xfree86 as well.

Perhaps you already figured this out, but there is an easy way to get 
output from Portage builds: set the PORT_LOGDIR variable in 
/etc/make.conf. For instance, I just uncommented the line already there 
(PORT_LOGDIR=/var/log/emerge). Also, make sure the directory exists. 
Make sure you have portage-2.0.48_pre3 or newer (though it's not 
unmasked yet), as there seems to be a bug related to logfiles in earlier 
ones.

How could you say that you "had no control over configure or the make 
process?" ;) Gentoo is the most configurable and easily tweakable distro 
I've used. Just edit the ebuild to have control over the configure and 
make process. I've found the PORTDIR_OVERLAY mechanism to be most 
helpful. I just set PORTDIR_OVERLAY to a directory in my home directory. 
Then, I can tweak existing ebuilds or write entirely new ones without 
stepping on /usr/portage and without doing anything as root except the 
actual build.

Before I started using Gentoo, I always had the dilemna of having to 
either stick to the packages available for the distribution (Redhat, 
Mandrake, or Debian) or install other packages from source, with no 
system or tracking of what was installed where. Now, I usually write a 
(Continue reading)


Gmane