From owner-freebsd-current Fri Feb 22 10:36:37 2002 Delivered-To: freebsd-current@freebsd.org Received: from h132-197-179-27.gte.com (h132-197-179-27.gte.com [132.197.179.27]) by hub.freebsd.org (Postfix) with ESMTP id E3A2137B405 for ; Fri, 22 Feb 2002 10:36:30 -0800 (PST) Received: from kanpc.gte.com (localhost [127.0.0.1]) by h132-197-179-27.gte.com (8.12.2/8.12.2) with SMTP id g1MIaTJR006951; Fri, 22 Feb 2002 13:36:29 -0500 (EST) (envelope-from ak03@gte.com) Date: Fri, 22 Feb 2002 13:36:29 -0500 From: Alexander Kabaev To: "Thomas E. Zander" Cc: current@FreeBSD.ORG Subject: Re: Recent USB problems Message-Id: <20020222133629.15316a9f.ak03@gte.com> In-Reply-To: <20020222181428.GA8774@f113.hadiko.de> References: <3C6F6F85.4050300@gmx.net> <20020222181428.GA8774@f113.hadiko.de> Organization: Verizon Data Services X-Mailer: Sylpheed version 0.7.2claws1 (GTK+ 1.2.10; i386--freebsd5.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit 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 > > Sorry, no hint by my side, but I can report exactly the same problem > on an Athlon-C System equipped with a VIA-KT133A chipset. > (actually it has the same USB controller, so it was expectable) > > Riggs I am seeing the same symptoms while using Microsoft USB mouse with KT133A-based computer. In my case, initial probe for ums, uhid and then ugen fails. This is not consistent, though. Sometimes, probe will report failing ums attach, sometimes it will not even detect device as mouse and will start probing uhid or even ugen instead. Later in the boot process, right after the "Waiting for SCSI messages to settle" message, ums gets probed again and this time it attaches and works flawlessly 100% of the time. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message