From owner-freebsd-questions Tue May 5 17:44:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18399 for freebsd-questions-outgoing; Tue, 5 May 1998 17:44:35 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA17544 for ; Tue, 5 May 1998 17:41:08 -0700 (PDT) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA14934; Wed, 6 May 1998 10:05:45 +0930 (CST) (envelope-from grog) Message-ID: <19980506100544.C14746@freebie.lemis.com> Date: Wed, 6 May 1998 10:05:44 +0930 From: Greg Lehey To: Stumpie , freebsd-questions@FreeBSD.ORG Subject: Re: Still trying to get X-Windows going References: <354F49D6.6983@edu.gte.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <354F49D6.6983@edu.gte.net>; from Stumpie on Tue, May 05, 1998 at 10:18:14AM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 5 May 1998 at 10:18:14 -0700, Stumpie wrote: > Hi, > > I reloaded FreeBSD in an attempt to get this going. That's not the way to approach software installation. > I am now able to get into the graphical configuration file which I > wasn't able to do before. > > But now I have two new problems. > > 1. I can't seem to find a mouse driver that works. I've tried all the > selections with a common 2 button and 3 button serial mouse, but my mouse > won't 'squeak'. Well, it you've told it as much information as you've told us, that's not surprising. What kind of mouse do you have? How is it connected? > 2. I get an error message when I type in startx. > > xinit: no such file or directory (errno 2) no server X in path. > > I'm using the Leahy book as a crutch here to look up items. Maybe you'd be better off reading the chapter. > If there is a discussion of how to create paths and put programs in > correct paths, then it's not obvious to me. What do you make of this? It's the lower half of page 106: Configuring X for Your Hardware _______________________________ After installing the X software, you will need to customize the file /usr/X11R6/lib/X11/XF86Config, which tells the X server about your hardware and how you want to run it. The format of XF86Config has changed since version 2 of XFree86. If you are upgrading from version 2, use the reconfig utility to perform a partial translation of the old XConfig file to the new format. You'll still need to make some changes manually. # reconfig < Xconfig > XF86Config The man page XF86Config (on page 1533) and the file /usr/X11R6/lib/X11/XF86Config.eg will help you complete the changes. In order to set up XF86Config, you'll need the following hardware information: o Your mouse type, the bit rate if it's a serial mouse, and the name of the device to which it is connected. This will typically be /dev/ttyd0 or /dev/ttyd1 for a serial mouse, or /dev/psm0 or /dev/mse0 for a bus mouse. o The type of the video board and the amount of display memory. If it's a no- name board, establish what VGA chip set it uses. o The parameters of your monitor: vertical and horizontal frequency. On page 105, you'll find: Then check that the directory /usr/X11R6/bin is in the default path for sh in /etc/profile and for csh in /etc/csh.login, and add it if it is not. It's best to do this with an editor, but if you want to take a short cut, you can enter: # echo 'set path = ($path /usr/X11R6/bin)' >>/etc/csh.login # echo 'PATH=$PATH:/usr/X11R6/bin' >>/etc/profile Alternatively, make sure everybody who uses X puts /usr/X11R6/bin in their shell's PATH variable. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message