From owner-freebsd-mobile@FreeBSD.ORG Thu Oct 25 18:33:27 2007 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3CF0C16A421 for ; Thu, 25 Oct 2007 18:33:27 +0000 (UTC) (envelope-from nate@root.org) Received: from root.org (root.org [67.118.192.226]) by mx1.freebsd.org (Postfix) with ESMTP id F114C13C48E for ; Thu, 25 Oct 2007 18:33:26 +0000 (UTC) (envelope-from nate@root.org) Received: (qmail 57063 invoked from network); 25 Oct 2007 18:06:47 -0000 Received: from unknown (HELO ?192.168.1.77?) (nate-mail@71.141.139.72) by root.org with ESMTPA; 25 Oct 2007 18:06:47 -0000 Message-ID: <4720DB2F.3060006@root.org> Date: Thu, 25 Oct 2007 11:06:39 -0700 From: Nate Lawson User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Tom Judge References: <471CCA24.4080400@tomjudge.com> <200710232328.18947.jhb@freebsd.org> <471FCE4C.70303@tomjudge.com> <200710251234.59272.jhb@freebsd.org> <4720D21F.7050909@tomjudge.com> In-Reply-To: <4720D21F.7050909@tomjudge.com> X-Enigmail-Version: 0.95.3 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: freebsd-mobile@freebsd.org Subject: Re: ACPI Attach (acpi_ibm) stops mouse from working X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 25 Oct 2007 18:33:27 -0000 Tom Judge wrote: > John Baldwin wrote: >> The linux acpi_ibm driver only attaches to IBM0068 FWIW. You can try >> removing "IBM0057" from the ID list in acpi_ibm.c, that should fix >> your mouse issue. >> > The only bios settings relevent to the mouse are whether to disable it, > or have it automatically disabled if an external mouse is detected, > presumable connected to the dock mouse port (which I don't have). > > Why would the psm/ibm_acpi attach order be changed by where abouts > acpi_ibm_load is in loader.conf? Don't worry about it. John just checked in a fix in -current. If you run that, you can cvsup and test, otherwise wait for the MFC. -- Nate