From owner-freebsd-current@FreeBSD.ORG Thu Dec 18 11:22:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A39716A4CE for ; Thu, 18 Dec 2003 11:22:45 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 4E70B43D4C for ; Thu, 18 Dec 2003 11:22:44 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 74204 invoked by uid 1000); 18 Dec 2003 19:22:45 -0000 Date: Thu, 18 Dec 2003 11:22:45 -0800 (PST) From: Nate Lawson To: acpi-jp@jp.FreeBSD.org In-Reply-To: <1071527493.1620.22.camel@hunter.muc.eu.mscsoftware.com> Message-ID: <20031218112214.V74190@root.org> References: <1071506783.25341.11.camel@bigboot.humphrey.world> <1071527493.1620.22.camel@hunter.muc.eu.mscsoftware.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-current@freebsd.org cc: "Georg-W. Koltermann" Subject: Re: [acpi-jp 2913] Re: Compaq Presario 2105US ACPI = NO MOUSE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Dec 2003 19:22:45 -0000 On Mon, 15 Dec 2003, Georg-W. Koltermann wrote: > On Mo, 2003-12-15 at 17:46, Brendon and Wendy wrote: > > Greetings to you also. > > > > Thanks for your ASL patch suggestion - that worked perfectly. I now have > > a PS/2 mouse being detected with ACPI on on my Compaq Presario 2100 > > latop. Woohoo. > > I have a Compaq N800w and see the same problem: 5.2-RC1 + ACPI = NO > MOUSE. It works just fine in 5.1R, with ACPI enabled. > > The problem is, I don't see a snippet like Device (MSE0) in my asl, so I > cannot apply the fix. > > I'll send my AML off-list, if one of you would kindly take a look and > help me. FYI, I also get a bunch of errors from iasl, even after > removing the '*' from all the ids. I already have the latest ROM :-( Please cvsup and try again. I committed code last nigh that should fix this problem. -Nate