From owner-freebsd-current  Thu Sep  6  4:42:12 2001
Delivered-To: freebsd-current@freebsd.org
Received: from nasu.utsunomiya-u.ac.jp (nasu.utsunomiya-u.ac.jp [160.12.128.3])
	by hub.freebsd.org (Postfix) with ESMTP id C461637B403
	for <current@freebsd.org>; Thu,  6 Sep 2001 04:42:07 -0700 (PDT)
Received: from nantai.utsunomiya-u.ac.jp by nasu.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/26Jan01-1134AM)
	id f86Bg15422906; Thu, 6 Sep 2001 20:42:01 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp by nantai.utsunomiya-u.ac.jp (8.11.2/1.1.29.3/30Jan01-0241PM)
	id f86Bg1u260325; Thu, 6 Sep 2001 20:42:01 +0900 (JST)
Received: from zodiac.mech.utsunomiya-u.ac.jp (IDENT:MKmdhAJn0jZc1uUDhzFcbAVKgJueb072@zodiac.mech.utsunomiya-u.ac.jp [160.12.43.7])
	by zodiac.mech.utsunomiya-u.ac.jp (8.9.3+3.2W/3.7W/zodiac-May2000) with ESMTP id UAA20428;
	Thu, 6 Sep 2001 20:51:45 +0900 (JST)
Message-Id: <200109061151.UAA20428@zodiac.mech.utsunomiya-u.ac.jp>
To: current@freebsd.org
Cc: acpi-jp@jp.freebsd.org, yokota@zodiac.mech.utsunomiya-u.ac.jp
Subject: ACPI and PS/2 mouse problem
Date: Thu, 06 Sep 2001 20:51:44 +0900
From: Kazutaka YOKOTA <yokota@zodiac.mech.utsunomiya-u.ac.jp>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

As reported in this list by several people, you may be seeing that
your PS/2 mouse is not detected after the recent ACPI update.

This seems to be caused by ACPI in some BIOS assigns IRQ 12 (mouse
interrupt) to both the PS/2 mouse device node and the system reserved
resource node.

To see if this is to be your case, put the following line in
/boot/device.hints and reboot.

debug.acpi.disable="sysresource"

If this brings your mouse back, I recommend you to keep that line
there until the proper fix is committed.

If it doesn't solve the problem, there must be other causes ;-( 
You had better contact the FreeBSD ACPI developers
(acpi-jp@jp.freebsd.org) ML.

Kazu

PS: I am going to commit some update to the psm driver shortly.
But, that alone won't fix the problem. Sorry...


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message