problem starting X w/ Matrox Millennium G200 16MB and XSuSE XFCom_Matrox

problem starting X w/ Matrox Millennium G200 16MB and XSuSE XFCom_Matrox

Post by Mark Nippe » Fri, 13 Nov 1998 04:00:00

Okay, I've scoured and couldn't find anyone else
having a problem like this.  I also searched altavista and all the
relevant Matrox/X pages (,,

Anyway, here's the scoop:

XFCom_Matrox Version 2.2/ X Window System
(protocol Version 11, revision 0, vendor release 6300)
Release Date:  1 October 1998
        If the server is older than 6-12 months, or if your card is
        than the above date, look for a newer version before reporting

Operating System: Linux 2.1.51 i686 [ELF]
Configured drivers:
  SVGA: server for SVGA graphics adaptors (Patchlevel 0):
      mga2064w, mga1064sg, mga2164w, mga2164w AGP, mgag200, mgag100
(using VT number 7)

XF86Config: /etc/XF86Config
(**) stands for supplied, (--) stands for probed/default values
(**) XKB: keymap: "xfree86(us)" (overrides other XKB settings)
(**) Mouse: type: IMPS/2, device: /dev/mouse, buttons: 3
(**) SVGA: Graphics device ID: "Matrox Millennium G200 16MB"
(**) SVGA: Monitor ID: "My Monitor"
(--) SVGA: Mode "1600x1200" needs hsync freq of 87.50 kHz. Deleted.
(--) SVGA: Mode "1152x864" needs hsync freq of 89.62 kHz. Deleted.
(--) SVGA: Mode "1280x1024" needs hsync freq of 91.15 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 93.75 kHz. Deleted.
(--) SVGA: Mode "1600x1200" needs hsync freq of 105.77 kHz. Deleted.
(--) SVGA: Mode "1280x1024" needs hsync freq of 107.16 kHz. Deleted.
(--) SVGA: Mode "1800X1440" needs hsync freq of 96.15 kHz. Deleted.
(--) SVGA: Mode "1800X1440" needs hsync freq of 104.52 kHz. Deleted.
(**) FontPath set to

(--) SVGA: Linear framebuffer at 0xF0000000
(--) SVGA: MMIO registers at 0xD0200000
(--) SVGA: Video BIOS info block at 0x000c7a60
(--) SVGA: Found and verified enhanced Video BIOS info block
(!!) SVGA: reset VideoRAM to 2 MB for safety!
(--) SVGA: detected an SGRAM card
(--) SVGA: chipset:  mgag200
(--) SVGA: videoram: 16384k
(**) SVGA: Option "dac_8_bit"
(**) SVGA: Using 16 bpp, Depth 16, Color weight: 565
(--) SVGA: Maximum allowed dot-clock: 250.000 MHz
(**) SVGA: Mode "640x480": mode clock =  45.800
(**) SVGA: Mode "800x600": mode clock =  69.650
(**) SVGA: Mode "1024x768": mode clock = 115.500
(**) SVGA: Mode "1280x1024": mode clock = 135.000
(--) SVGA: Virtual resolution set to 1280x1024
(--) SVGA: SpeedUp code selection modified because virtualX != 1024
(--) SVGA: Read OPTION 0x4007cd21
(--) SVGA: Using XAA (XFree86 Acceleration Architecture)
(--) SVGA: XAA: Solid filled rectangles
(--) SVGA: XAA: Screen-to-screen copy
(--) SVGA: XAA: 8x8 color expand pattern fill
(--) SVGA: XAA: CPU to screen color expansion (TE/NonTE imagetext,
TE/NonTE polytext)
(--) SVGA: XAA: Using 10 128x128 areas for pixmap caching
(--) SVGA: XAA: Caching tiles and stipples
(--) SVGA: XAA: General lines and segments
(--) SVGA: XAA: Dashed lines and segments

Fatal server error:
Caught signal 11.  Server aborting

When reporting a problem related to a server crash, please send
the full server output, not just the last messages

_X11TransSocketUNIXConnect: Can't connect: errno = 111
giving up.
xinit:  Connection refused (errno 111):  unable to connect to X server
xinit:  No such process (errno 3):  Server error.

Is this related to the signal 11 problem that gcc has known to
report?  I've tried setting Option "no_accel" in XF86Config and it
makes no difference.  I've got symlinks in the right places and
I followed the instructions for XSuSE to a tee!

I guess I should also say I'm running a brand new Red Hat 5.2 release
with a 2.0.36 kernel (??? that's what it says!).  It's a Pentium II
based machine w/ 64Mb of RAM.  It is a MGA G200 with 16Mb SGRAM, so
that part is working okay.  I just can't figure out why it doesn't
go on from there.


problem starting X w/ Matrox Millennium G200 16MB and XSuSE XFCom_Matrox

Post by Valentin Guille » Sat, 14 Nov 1998 04:00:00


I have a couple of suggestions for you:

First.  Delete your current config file.  Now, I don't know which of the configuration utilities you are using, but I would suggest using the xf86Setup util.  The reason is
that this utility actually starts X running, and you do the configuration in a 16 color VGA X session!! No matter, use any of the other 3 utilities if you have a preference.
Next, select generic VGA as the type of video card.  Tell it you have 500k or 1 meg of vid mem on the card.  Nest select generic VGA monitor as your monitor, specifying
whatever screen size you actually have.  Next select 640x480 as the resolution to use.
Finish the configuration and start the X program.  You should now have a running X system!

What we want to do is get your system running, albeit minimally, to begin with.   Once you are successful in this, you can rename the working config file, and start the
process over again, using ONE (only!!) different parameter this time.  Keep this process going until you have maybe changed all the parameters to be how you actually want to
use X.  You wil want a decent refresh rate, resolution, optimized server, etc.  But it's obvious from seeing your errors log that you don't really understand what is
happening in your system.  If you had the expertise, doing it the above mentioned way wouldn't be neccessary, but if you can't just open the config file in vi and edit all
parameters to optimize it that way, you will need to do it this other way.

Your error log says that your config specifies resolutions like 1800x1440 and other such things.  You, or the config utility, have injected unheard of levels of complexity
into this config file.   And while I'm sure that you equipment is capable of such resolutions, you don't want any of this stuff artificially interjecting complexity into your
diagnostics.  To get it up and running, you want to use as simple a configuration as you can think of.  Once you have seen it actually running, you can save the config file,
and begin tweaking one parameter at a time, because you will know that you can always revert to a known level of performance, if something screws up.  Additionally, by
changing one parameter at a time and seeing the results, you will begin to understand what each item REALLY does.  I have no doubt that you can get this system up and
running.  I don't have your video card, so I am not certain exactly how high a performance level you will achieve with this card/monitor combo, but I know that it will be
servicable and impressive!!

Just start out with small steps and work you way into a "maxed out" configuration.  What will accelerate this process for you is to examine and become intimately familiar
with the XFree86 Config How To which is currently posted in this news group.  It is also available on your hard drive, as well as on your GNU/Linux distribution CD.  Your man
pages will assist you as will the XFree86Video Timings How To.

If you had posted the specifications of the monitor inquestion, as well as your current config file, etc., it would have been much faster and precise to zero in on the
error.  I am beginning to be hesitant to simply post working config files, because when I do that, people never actually learn how X works, and don't learn the configuration
methodology.  I have learned that if you point people in the right direction, instead of playing bill gates, and merely supplying them with everything, they actually learn

Best Regards,