Re: X server crashes everything
Andrew Varner wrote: Hi I have a problem with the X server. When I type 'X', the screen goes black and everything stops. SysRq+b doesn't even work. Is it likely that I am missing the driver? The video driver is where I would start. I'd shoot for the lowest common denominator to start, by "dpkg-reconfigure xserver-xorg" and choosing the vesa driver (or even the vga driver), then work up from there. -- Kent -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: X server crashes....
On Sun, 17 Oct 1999, Phil Brutsche wrote: > A long time ago, in a galaxy far, far way, someone said... > > Fatal server error: > > Caught signal 11. Server aborting > > Signal 11 is a segmentation fault. This is what I suggest: > > 1) Re-install the X server binary. It might have gotten munged somehow > 2) Check your memory, motherboard, and L2 cache, or a combination of the >above. Those are the three most common causes of a Sig11, especially >for 'no apparent reason'. > > Out of curiosity, have you tried recompiling the kernel recently? Hi, I reinstalled the X binaries (X, XF86_SVGA) again. The new X server is running and I'm keeping my fingers crossed... :) I updated my kernel to 2.2.12 from 2.0.36 about a month ago. why? Thanks for your help. Rajesh
Re: X server crashes....
A long time ago, in a galaxy far, far way, someone said... > Hi, > > My X server crashes on a consistent basis without any apparent > reason. > > Here is the output(useful parts) of my 'startx -- -bpp 16 >& errors' > command , [snip] > (--) SVGA: Virtual resolution set to 1152x864 > (--) SVGA: SpeedUp code selection modified because virtualX != 1024 > (--) 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 > poly > text) > (--) SVGA: XAA: Using 9 128x46 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 Signal 11 is a segmentation fault. This is what I suggest: 1) Re-install the X server binary. It might have gotten munged somehow 2) Check your memory, motherboard, and L2 cache, or a combination of the above. Those are the three most common causes of a Sig11, especially for 'no apparent reason'. Out of curiosity, have you tried recompiling the kernel recently? -- -- Phil Brutsche [EMAIL PROTECTED] "There are two things that are infinite; Human stupidity and the universe. And I'm not sure about the universe." - Albert Einstein
Re: X server crashes....
hi y.. the X messges is saying... a. it did not recognize any legal display for sync 1024x768, 1280x1024 800x600 etc... nothing... - you do NEED to know the horizontal sync and vertical refresh values ( or the manufacturers model number ) b. run Xconfigurator or XF86Setup or someother X11 setup tool... c. Check the errors again with the same method you used or X -probeonly have fun alvin > Hi, > > My X server crashes on a consistent basis without any apparent > reason. > > Here is the output(useful parts) of my 'startx -- -bpp 16 >& errors' > command , > > XFree86 Version 3.3.2.3 / X Window System > (protocol Version 11, revision 0, vendor release 6300) > Release Date: July 15 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. (see http://www.XFree86.Org/FAQ) > Operating System: Linux 2.0.36 i686 [ELF] > Configured drivers: > SVGA: server for SVGA graphics adaptors (Patchlevel 0): > NV1, STG2000, RIVA128, ET4000, ET4000W32, ET4000W32i, > ET4000W32i_rev_b, ET4000W32i_rev_c, ET4000W32p, ET4000W32p_rev_a, > > XF86Config: /etc/X11/XF86Config > (**) stands for supplied, (--) stands for probed/default values > (**) XKB: rules: "xfree86" > (**) XKB: model: "pc101" > (**) XKB: layout: "us" > (**) XKB: options: "ctrl:swapcaps" > (**) XKB: keymap: "xfree86(us)" (overrides other XKB settings) > (**) Mouse: type: PS/2, device: /dev/psaux, buttons: 3 > (**) SVGA: Graphics device ID: "matrox" > (**) SVGA: Monitor ID: "sa" > > > (--) SVGA: Virtual resolution set to 1152x864 > (--) SVGA: SpeedUp code selection modified because virtualX != 1024 > (--) 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 > poly > text) > (--) SVGA: XAA: Using 9 128x46 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 > > xinit: connection to X server lost.^M > > I don't know what to make of it. I have a Matrox Mystique (4MB) card. > > Any suggestions... > > Thanks > Rajesh > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
