From owner-freebsd-questions Thu Apr 6 17:41:40 2000 Delivered-To: freebsd-questions@freebsd.org Received: from wondermutt.net (host75-157.student.udel.edu [128.175.75.157]) by hub.freebsd.org (Postfix) with ESMTP id A79BD37B5C5 for ; Thu, 6 Apr 2000 17:41:30 -0700 (PDT) (envelope-from papalia@udel.edu) Received: from morgaine.udel.edu (morgaine.wondermutt.net [192.168.1.2]) by wondermutt.net (8.9.3/8.9.3) with ESMTP id UAA23729 for ; Thu, 6 Apr 2000 20:21:32 -0400 (EDT) (envelope-from papalia@udel.edu) Message-Id: <4.3.1.2.20000406201125.00ac3870@mail.udel.edu> X-Sender: papalia@mail.udel.edu X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Thu, 06 Apr 2000 20:14:40 -0400 To: freebsd-questions@freebsd.org From: John Subject: Mouse woes Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi all, It seems that some time this afternoon my mouse decided to go no vacation without me. My box has been up for (only) 30 days, and in that time, I've used X successfully dozens of times - including last night and this morning. This afternoon when I tried to start X up, I get the error Cannot open mouse (Device not configured). The only information I could find in the archives was regarding users who never even had the mouse working to start. The problem is that this mouse WAS working just 10 hours ago - and now it's not. I've checked the cabling, and all seems well. Any ideas short of rebooting? The mouse is a Logitech Trackman Marble (ps/2) running into an OmniCube 4-port KVM, and then into the FreeBSD (3.4-Stable) box. This configuration has given me no other troubles for the past 8 months that it's been running like this. Thanks in advance, John To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message