From owner-freebsd-questions Tue Oct 7 02:21:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA11807 for questions-outgoing; Tue, 7 Oct 1997 02:21:03 -0700 (PDT) (envelope-from owner-freebsd-questions) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA11790 for ; Tue, 7 Oct 1997 02:20:56 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id SAA27231; Tue, 7 Oct 1997 18:50:40 +0930 (CST) Message-ID: <19971007185040.58580@lemis.com> Date: Tue, 7 Oct 1997 18:50:40 +0930 From: Greg Lehey To: beef@tht.net Cc: questions@FreeBSD.ORG, support@cdrom.com Subject: Re: Xwindows won't run after complete re-install References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: ; from Lanny Baron on Tue, Oct 07, 1997 at 02:05:22AM +0000 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Oct 07, 1997 at 02:05:22AM +0000, Lanny Baron wrote: > Hi again, > > Unfortunately, it has been a month since i ordered FreeBSD 2.2.2 and > have always to reinstall over the net (4-6 hrs each time). This time, > after doing the Xwindows setup (graphically), if i type startx, I get > no command found. If I go into /usr/X11R6/bin and type X i get the > grey screen This is a sure indication that you don't have /usr/X11R6/bin in your PATH. > but no windows. None at all? > I copied xinitrc for .../xinit/xinitrc and copied to > /home/beef/.xinitrc and did chown to myself. But that did not help. I > am at a loss as what the problem is. I have an ATI mach 64 with 4 > megs ram and basically did same setup as before. I tried it as root > and myself. All fails and gives some type of message about SHVSYM or > something like that. Ah. Why don't you write down the message exactly? That will help us understand the problem. In this case, though, I'd guess that you've built a kernel without SYSVSHM. Add this line to your kernel config file and try again: options SYSVSHM # Include System V shared memory emulation Greg