From owner-freebsd-questions Mon Nov 25 22:31:12 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id WAA13849 for questions-outgoing; Mon, 25 Nov 1996 22:31:12 -0800 (PST) Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id WAA13836 for ; Mon, 25 Nov 1996 22:31:06 -0800 (PST) Received: from localhost (dwhite@localhost) by gdi.uoregon.edu (8.8.3/8.6.12) with SMTP id WAA01903; Mon, 25 Nov 1996 22:32:16 -0800 (PST) Date: Mon, 25 Nov 1996 22:32:16 -0800 (PST) From: Doug White Reply-To: dwhite@resnet.uoregon.edu To: dhawley@el.nec.com cc: questions@FreeBSD.org Subject: Re: Can't run X86 Windows In-Reply-To: <329A385F.1F1A@el.nec.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-questions@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 25 Nov 1996, Nicholas G. Jourin wrote: > I'm getting the message, "Fatal Server Error: Cannot open mouse > (device not configured)". I have a PS2 mouse that worked just fine > before. I understand what's involved in getting it to work... > > I know how to include psm0 in the kernel (and exclude the other > choice). I know how to MAKEDEV psm0 in /dev. I know how to > select that mouse during the install (and I did all these things). > I know how to run /stand/sysinstall and configure X86... I chose > /dev/psm0, I chose "use META characters" (so i could emulate a > 3 button mouse). Again I had this all working before. What does your "Pointer" section in /etc/XF86Config read? > I had FreeBSD running just fine on a tiny little IDE drive, but > ever since I installed a fast/wide, new, improved, huge SCSI disk, > and 4X SCSI CD-ROM, I've been having lots of problems. I managed to > resolve all of them, *except* that I can no longer run X86Windows > (forgive me I don't remember what you call it). Before the SCSI > stuff I had it running, and I configured both twm and fvwm to work. > > I set things in the BIOS both on and off. I tried NumLock both > ways (after reading the FAQ). I turned off IDE in the BIOS. This is odd. Doug White | University of Oregon Internet: dwhite@resnet.uoregon.edu | Residence Networking Assistant http://gladstone.uoregon.edu/~dwhite | Computer Science Major