From owner-freebsd-current Wed Jan 22 5:29:59 2003 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 0301B37B401 for ; Wed, 22 Jan 2003 05:29:58 -0800 (PST) Received: from speechpro.com (crt-gw.infopro.spb.su [195.201.254.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FC1143ED8 for ; Wed, 22 Jan 2003 05:29:57 -0800 (PST) (envelope-from igorr@speechpro.com) Received: from igorr by sysadm.stc with local (Exim 3.36 #1) id 18bKx1-00047W-00 for freebsd-current@FreeBSD.ORG; Wed, 22 Jan 2003 16:29:55 +0300 Date: Wed, 22 Jan 2003 16:29:55 +0300 From: Igor Roboul To: freebsd-current@FreeBSD.ORG Subject: Re: PS/2 mouse problems with -CURRENT Message-ID: <20030122132955.GA15722@sysadm.stc> Reply-To: ir@hotbox.ru Mail-Followup-To: Igor Roboul , freebsd-current@FreeBSD.ORG References: <20030117132736.GB1201@sysadm.stc> <20030122063838.GA11430@sysadm.stc> <20030122064904.GG88085@arpa.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030122064904.GG88085@arpa.com> User-Agent: Mutt/1.3.99i Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Wed, Jan 22, 2003 at 12:49:04AM -0600, Chip Norkus wrote: > But try disabling ACPI and see if your PS/2 mouse suddenly works. ;) As you can see from my first post >> Same part of newer -CURRENT (I have disable ACPI, but I get same >> result with ACPI too): >> atkbdc0: at port 0x64,0x60 on isa0 >> atkbd0: flags 0x1 irq 1 on atkbdc0 >> kbd0 at atkbd0 >> psm0: irq 12 on atkbdc0 >> psm0: model NetMouse/NetScroll Optical, device ID 0 first thing I have tried was disabling ACPI :-(. I'll try today (maybe I have mistyped something). -- Igor Roboul, System administrator at Speech Technology Center http://www.speechpro.com http://www.speechpro.ru To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message