Red Hat Bugzilla – Bug 52553
Trouble getting latest MPlayer to use DGA mode
Last modified: 2007-04-18 12:36:35 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.01; Windows NT 5.0)
Description of problem:
I'm compiled the latest CVS version of MPlayer on the second roswell
release and cannot get it to display anything but a blank screen when
switching to DGA mode.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Compile and Install MPlayer
DGA implementation is hardware dependant. Please provide more information
as to the exact hardware you are using. Also attach a copy of your
XFree86 log, and your XF86Config-4 config file uncompressed using the
Also, did this _ever_ work? If so, which XFree86 release(s) did it work
on, and was it the same video hardware you're using now as back then?
I've not tried it on any other release version. The system is a Gateway Solo
2500 with the NeoMagic 128XD chipset with 2MB RAM.
Created attachment 29794 [details]
Created attachment 29795 [details]
Further investigation indicates that there is a bug in the neomagic driver that
is causing this problem. A patch is making its way into the CVS version of
XFree86 to correct it. The patch is as follows:
retrieving revision 1.56
diff -u -r1.56 neo_driver.c
2001/08/07 07:04:48 1.56
@@ -2156,8 +2156,8 @@
* This function handles restoring the generic VGA registers. */
- VGA_SR_MODE | VGA_SR_CMAP
- | (restoreFonts ? VGA_SR_FONTS : 0));
+ | (restoreFonts ? (VGA_SR_FONTS | VGA_SR_CMAP) : 0));
Will this patch be incorporated into the RedHat version of XFree86 soon?
If you attach the patch as a file attachment, I will add it to the
next build I make. Cut and pasted patches are always badly broken.
As stated above, this is fixed in upstream XFree86 CVS. It
will appear in a future release of Red Hat Linux.
OK, here is the patch in an attachment.
Created attachment 36501 [details]
neomagic DGA fix patch
Added to XFree86-4.1.0-6.0.1, will appear in 4.1.0-7 test release
sometime this week. If this works ok, it will appear in any
future erratum that may be released. Thanks.