From owner-freebsd-questions Thu Aug 31 11:48:25 2000 Delivered-To: freebsd-questions@freebsd.org Received: from relay.securify.com (relay.securify.com [207.5.63.61]) by hub.freebsd.org (Postfix) with ESMTP id 124C537B43E for ; Thu, 31 Aug 2000 11:48:24 -0700 (PDT) Received: by relay.securify.com; id LAA16757; Thu, 31 Aug 2000 11:47:51 -0700 (PDT) Received: from unknown(10.5.63.6) by relay.securify.com via smap (V5.5) id xma016732; Thu, 31 Aug 00 11:47:15 -0700 Received: from amnesiac (dude.securify.com [10.5.63.6]) by dude.securify.com (8.9.3/8.9.3) with SMTP id LAA57865 for ; Thu, 31 Aug 2000 11:47:15 -0700 (PDT) (envelope-from tomb@securify.com) Message-ID: <001601c0137d$347cfca0$1e05050a@amnesiac> From: "Tom Brown" To: Subject: Mouse inoperative after upgrade from RELEASE-4.0 to RELEASE-4.1 Date: Thu, 31 Aug 2000 11:56:43 -0700 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, Has anybody else had this problem. I upgraded my box from RELEASE-4.0 to RELEASE-4.1 using the cd-image from the ftp site. I tried X and it started fine but the mouse wasn't working at all. I decided to run through the stand/sysinstall menu to configure moused. The moused still wouldn't start. Just to make sure I tried booting the generic 4.1 kernel. Still nothing. I then tried to manually start moused and got the response: /dev/psm0 device not configured. just to make sure I went to /dev and ran ./MAKEDEV psm0 This had no effect. Checking systat -vm there is no activity on the device or IRQ 12 .\ Any ideas??? Thanks Tom Brown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message