Date: Fri, 22 Feb 2002 19:51:20 +0100 From: Michael Class <michael_class@gmx.net> To: Alexander Kabaev <ak03@gte.com> Cc: current@freebsd.org Subject: Re: Recent USB problems Message-ID: <3C769328.1090908@gmx.net> References: <3C6F6F85.4050300@gmx.net> <20020222181428.GA8774@f113.hadiko.de> <20020222133629.15316a9f.ak03@gte.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, with current of yesterday everything seems to be ok for me again. But I do not see any reason for this (code has not changed inbetween). Michael Alexander Kabaev wrote: >>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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3C769328.1090908>