Re: Recent USB problems
I had no problem with kernel from February 14, but failed ums probes are happening very consistently with kernel from Feb 18. Kernels from dates earlier than Feb 14 failed to attach USB mouse most of the time but sometimes misteriously managed to work. No configuration was changing between successfull and unsuccessful boots, and there was no pattern whatsoever to hint why was that happening. By the way, the problem is related to the ums driver only, apparently. While I am having problems with the mouse, my USB scanner works absolutely reliably. > 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). I > will upgrade today and To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent USB problems
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 [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
Re: Recent USB problems
> > 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 [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent USB problems
On Sun, 17. Feb 2002, at 9:53 +0100, Michael Class wrote according to [Recent USB problems]: > usb1: on uhci1 > usb1: USB revision 1.0 > uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 > uhub1: 2 ports with 2 removable, self powered > > The system is a dual PIII Gigabyte system with VIA-Chipset. > > Any hints? 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 talked to the computer at great length and -- explained my view of the Universe to it" said Marvin. --- And what happened?" pressed Ford. "It committed suicide." said Marvin. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
