From owner-freebsd-questions Tue Jan 13 16:34:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA00734 for questions-outgoing; Tue, 13 Jan 1998 16:17:43 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from random.tpgi.com.au (random.tpgi.com.au [203.12.160.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00540 for ; Tue, 13 Jan 1998 15:52:05 -0800 (PST) (envelope-from eirvine@tpgi.com.au) Received: (from smtpd@localhost) by random.tpgi.com.au (8.8.4/8.8.6) id RAA25324; Tue, 13 Jan 1998 17:29:31 +1100 (EST) Received: from tar-ppp-162.tpgi.com.au(203.26.26.162), claiming to be "gretchen" via SMTP by random.tpgi.com.au, id smtpdAAAa006BO; Tue Jan 13 17:29:23 1998 From: "Eddie Irvine" To: , Subject: Re: moused and x Date: Tue, 13 Jan 1998 17:31:01 +1100 Message-ID: <01bd1fec$d0f06400$a21a1acb@gretchen> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-questions@freebsd.org Precedence: bulk OK. I have a ps/2 mouse and it works fine with X. First, on bootup, go to the visual configure mode. You want to enable an input device called psm0 - this is the ps/2 mouse device. It present a conflict with the keyboard or console but that is OK. Now, in XF86Config, DON'T TOUCH THE MOUSE until you have selected a ps/2 mouse and the psm0 input device, and tabbed over and hit the "apply" button. Getting the mouse to work on the console is more involved ... Eddie.