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).
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)
> 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 [EMAIL PROTECTED]
>with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message