> > --Message-Boundary-7696 > Content-type: text/plain; charset=US-ASCII > Content-transfer-encoding: 7BIT > Content-description: Mail message body > > Hi, > > Can anyone help me how I have to interpret the output of the > (Matrox) X-server. I start but crashes. but how to interpret all the > messages it produces?. Is there a document that explains this ?? > > I have attached the output of my Matrox X-server as an example. > > Many thanks. > Regards, > Marc > ____________________________________________________ > > ir. Marc Fleureck [EMAIL PROTECTED] > tel: +32-(0)2-2085311 fax: +32-(0)2-2085320 > ____________________________________________________ > > > > > --Message-Boundary-7696 > Content-type: text/plain; charset=US-ASCII > Content-transfer-encoding: 7BIT > Content-description: Text from file 'report' > > > > 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 newer > than the above date, look for a newer version before reporting > problems. Please report problems to [EMAIL PROTECTED] > 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(fr)" (overrides other XKB settings) > (**) Mouse: type: Busmouse, device: /dev/mouse, buttons: 3 > (**) Mouse: 3 button emulation (timeout: 50ms) > (**) SVGA: Graphics device ID: "Matrox Millennium G200 8MB" > (**) SVGA: Monitor ID: "CPD-200GST" > (--) SVGA: Mode "640x480" needs vert refresh rate of 100.02 Hz. Deleted. > (--) SVGA: Mode "800x600" needs vert refresh rate of 100.03 Hz. Deleted. > (--) SVGA: Mode "1024x768" needs hsync freq of 80.21 kHz. Deleted. > (--) SVGA: Mode "1280x1024" needs hsync freq of 81.13 kHz. Deleted. > (--) 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 > "/usr/X11R6/lib/X11/fonts/misc/,/usr/X11R6/lib/X11/fonts/100dpi/:unscaled,/usr/X11R6/lib/X11/fonts/100dpi/" > (--) SVGA: PCI: Matrox MGA G200 AGP rev 1, Memory @ 0xcf000000, 0xce000000 > (--) SVGA: Linear framebuffer at 0xCF000000 > (--) SVGA: MMIO registers at 0xCE000000 > (--) SVGA: Video BIOS info block at 0x000c7a60 > (--) SVGA: Found and verified enhanced Video BIOS info block > (--) SVGA: detected an SGRAM card > (--) SVGA: chipset: mgag200 > (**) SVGA: videoram: 8192k > (**) SVGA: Option "dac_8_bit" > (**) SVGA: Using 8 bits per color component > (**) SVGA: Using 8 bpp, Depth 8, Color weight: 888 > (--) SVGA: Maximum allowed dot-clock: 250.000 MHz > (**) SVGA: Mode "640x480": mode clock = 31.500 > (**) SVGA: Mode "800x600": mode clock = 60.750 > (**) SVGA: Mode "1024x768": mode clock = 98.900 > (**) 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 > > waiting for X server to shut down FreeFontPath: FPE > "/usr/X11R6/lib/X11/fonts/misc/" refcount is 2, should be 1; fixing.
I got an almost identical result as you (after I reduced the number of
fonts listed in XF86Config, since I had originally included more font
packages whether needed or not).
The last three lines
SVGA ...
waiting for X server to shut down FreeFontPath: ...
I got identically when I quit my X session.
While I didn't try a few things, here are a couple probably irrelevant
to your problem but useful when you get X-windows working.
Above, you had the line, " Using 8 bpp, Depth 8", for only 8 bits of color.
This probably works fine for getting things going.
Since your matrox G200 can handle all of 32 bits color,
eventually try
startx -- :1 -bpp 16
or better yet
startx -- :2 -bpp 32
You can leave the :1 and :2 off also;
these nifty numbers indicate which DISPLAY displays.
:1 corresponds to ctrl-alt-F7
:2 corresponds to ctrl-alt-F8
You might search some places for errors.
I run xdm, so I get some X errors in .xsession-errors of my home directory.
For startx, rather than using the startup programs you put in .xsession,
you put them in .xinitrc (though maybe startx uses .xsession now).
Maybe there is a .xinitrc-errors (I don't know).
See what files were created in your home directory in the last few minutes with
ls -tla |head -15
You might also check, though probably to no avail, for errors in
/var/log/messages
You might more explain "I start but crashes".
Did you see for a few seconds a colorful screen, a finely gray hashed
screen?
Did your screen return to
login:
If your screen remained a blank gray hash, you just had no
.xinitrc (though there may be a default .xinitrc), in which case
you can find some programs by clicking your left mouse button.
You might check that /etc/X11/window-managers has some window
manager listed (fvwm2, fvwm, twm, fvwm95, or some such);
these are entered when the corresponding package is installed and
you need one or more such entries.
You might see if you get the same failure both as root and as an ordinary user
when running startx.
I notice you have a " Busmouse, device: /dev/mouse".
Most computers sold in the US have a PS/2 mouse, though
many mice recognize a couple protocols.
For a PS/2, my /dev/mouse is
/dev/mouse -> psaux
If you have a mouse problem, perhaps gpm-mouse-test,
xmseconfig (probably requires X running),
"gpm -t ..." with different arguments, "mev -i" to see if mouse is understood
can help.
I believe you need PS/2 protocol compiled in the kernel (if you have
a PS/2 only mouse) for it to work;
you can get your mouse working with "gpm" in an ascii screen
without having a full X-windows session running;
I have in /usr/src/linux/.config the line (with "y" for "yes")
CONFIG_PSMOUSE=y
CONFIG_UMISC=y
from running a kernel configuration.
A bad mouse configuration may not even cause your X-windows to halt anyway.
Hopefully, you needn't compile a new kernel, since you have
enough to do already.
Other people can better help you recognize your current startx problems;
I am mostly flailing in the wind.
I attach a copy of my "startx" output and of my XF86Config (for Matrox G200),
though yours needn't at all be the same as mine.
Excuse me for using so much band width with attachments.
xstart-font.out
Description: xstart-font.out
XF86Config
Description: XF86Config
