Date: Wed, 06 Nov 2002 09:10:47 -0800 From: Maksim Yevmenkin <myevmenk@exodus.net> To: Josef Karthauser <joe@FreeBSD.ORG> Cc: current@FreeBSD.ORG Subject: Re: USB problem (Who owns USB code in -current?) Message-ID: <3DC94D17.DC5D8D6@exodus.net> References: <3DC6BD74.25097511@exodus.net> <20021106130658.GB8523@genius.tao.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
Josef, > > This problem is FreeBSD-specific and seems related to > > Bluetooth USB dongles only. I have been contacted by other > > people who have the same problem. I do not know what is so > > special about Bluetooth USB dongles. USB mouse, for example, > > works fine. Can it be power related? Both Windows and > > Linux do not have this problem which makes me think that > > there is something different about FreeBSD way of doing > > things. > > Compile the kernel with 'option USB_DEBUG' and then tweak the hw.usb > sysctls to get debug output for your controller, the usb stack and the > uhub. Maybe this will shed some light on the problem. i *did* compile my kernel with USB_DEBUG and *did* tweak sysctl's. i even attached the dump to my previous message. it seems there is some kind of communication error on the bus and stack can not get device descriptor. i need to know what might cause these communication errors. thanks, max 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?3DC94D17.DC5D8D6>