From owner-freebsd-current Thu Jan 22 17:23:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10985 for current-outgoing; Thu, 22 Jan 1998 17:23:29 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smokies.binc.net (root@smokies.binc.net [205.173.176.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10967 for ; Thu, 22 Jan 1998 17:23:24 -0800 (PST) (envelope-from subcero@binc.net) Received: from liquid.binc.net (msn-x2-1-25.binc.net [205.173.178.232]) by smokies.binc.net (8.8.5/8.8.5) with SMTP id TAA19174 for ; Thu, 22 Jan 1998 19:23:18 -0600 Date: Thu, 22 Jan 1998 19:23:14 -0600 (CST) From: Andrew Bazan To: FreeBSD-Current@FreeBSD.ORG Subject: PS/2 Mouse Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk Hi, I recently upgraded my system from 2.2.5-STABLE to 3.0-CURRENT -- did a complete harddrive flush (not really my choice) and reinstalled everything. Ever since I upgraded to -CURRENT, my PS/2 mouse has been giving me an immense amount of trouble. Basically, I don't usually run moused, and the first time I entered X and tried to move my mouse my harddrive made a bad crunching noise for a few seconds, and my mouse didn't move -- after awhile, I got a kernel error. I've CVSUP'd my sources, and I have the latest kernel as of about 3 this afternoon. I've had the problem with all the builds, and have no clue what's going on. I tried running moused to see if that would help anything, but it just crunched my harddrive when I moved the mouse and somehow (???) screwed up /proc so that I get a '/proc size mismatch' when I try to use a program that accesses it. I've tried all the easy solutions I can think of, and I'm wondering if this is a bug I haven't heard about in the kernel, or if it's just a new config issue I have to deal with. Thanks for your time, Andrew