From owner-freebsd-questions Mon Jul 8 5:42:23 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4105437B400 for ; Mon, 8 Jul 2002 05:42:20 -0700 (PDT) Received: from mx1.eskimo.com (mx1.eskimo.com [204.122.16.48]) by mx1.FreeBSD.org (Postfix) with ESMTP id DA96443E5E for ; Mon, 8 Jul 2002 05:42:19 -0700 (PDT) (envelope-from ripper@eskimo.com) Received: from eskimo.com (ripper@eskimo.com [204.122.16.13]) by mx1.eskimo.com (8.9.1a/8.8.8) with ESMTP id FAA28766 for ; Mon, 8 Jul 2002 05:42:13 -0700 Received: (from ripper@localhost) by eskimo.com (8.9.1a/8.9.1) id FAA07451; Mon, 8 Jul 2002 05:42:13 -0700 (PDT) Date: Mon, 8 Jul 2002 05:42:13 -0700 (PDT) Message-Id: <200207081242.FAA07451@eskimo.com> From: Ross Lippert To: freebsd-questions@freebsd.org Subject: starting up usb mouse with vidcontrol Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG I just installed 4.6 on a system with a USB mouse, and one thing that was a bit confusing is that while usbd is starting moused in its 'attach' script, it is not starting vidcontrol. In fact, the only easy way I see to get both moused started right and to get vidcontrol going is to have moused_enable='YES' in rc.conf which results in an annoying error message during rc.syscons, because /dev/ums0 is in use, but does still start up vidcontrol -m on, making the pointer appear. I don't think there was this business before. Is vidcontrol's mouse stuff new? Did it used to get activated differently, or in a different order (like rc.syscons used to come before running usbd)? -r To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message