Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!sun-barr!cs.utexas.edu!wupost!newsfeed.rice.edu!rice!news.Rice.edu!rich From: rich@Rice.edu (& Murphey) Subject: Re: [386BSD] XFree86 doesn't start In-Reply-To: aki!wegmann's message of Sat, 12 Dec 1992 08:55:23 GMT Message-ID: <RICH.92Dec13025135@superego.Rice.edu> Sender: news@rice.edu (News) Reply-To: Rich@rice.edu Organization: Department of Electrical and Computer Engineering, Rice University References: <1992Dec12.085523.3828@aki.en.open.de> Date: Sun, 13 Dec 1992 08:51:35 GMT Lines: 28 >>>>> In article <1992Dec12.085523.3828@aki.en.open.de>, aki!wegmann (Frank Wegmann) writes: |> I'm posting this for a friend: |> I have problems running xfree86. When I try to run 'xinit' or 'X' |> my screen switches to graphics mode, displays some random dots in |> black and white and after a second or two I'll be back in text mode. |> Output of xinit >& err was: |> XFree86 Version 1.1 / X Window System |> (protocol Version 11, revision 0, vendor release 5000) |> Configured drivers: |> VGA256 (256 colour SVGA): |> et4000, et3000, pvga1, gvga, ati, tvga8900 |> VGA256: et4000 (mem: 1024k numclocks: 16) |> VGA256: clocks: 25 28 33 37 41 46 32 38 51 57 65 73 81 91 64 76 |> Caught signal 11. Server aborting This is a segmentation violation. It could mean a bug in the server or a corrupted executable. You can make certain that the server executable is not corruped by matching the checksum listed in the MANIFEST.core-server-1.1 file with that generated by 'cksum X386'. The distributed server executable isn't striped, so you may be able to get some information from the stack trace. You can use gdb on the core file generated by X386 to generate the backtrace. Rich