On Mon, 18 Apr 2005, Johannes Berg wrote: > I have attached a three startup logs (dmesg) with CONFIG_USB_DEBUG. The > relevant device is on 0001:10:1a.0/usb1/1-1/1-1:1.0 (or :1.1 or both, > not sure). On the same bus there's the keyboard/trackpad/eject button > device, so I can't really give you something that shows *just* the > bluetooth device. > The three different logs are > * newscheme - only new scheme > * newscheme.both - new, with usb_both_schemes=1 > * oldscheme.both - old, with usb_both_schemes=1 > > The device works in newscheme.both and oldscheme.both, but not if I > don't fall back to the old scheme. > > So maybe this is less interesting in the light of your following remark: > > > P.S.: If it isn't already, usb_both_schemes=1 will soon be the default. > > It isn't already, but thanks for the note. And indeed, this seems to > 'fix' it as well.
All I can is, this seems to be a pretty finicky device. Of course, it's always possible that the problem lies not in the device but in the host controller. Have you tried plugging it into any of the other controllers on your computer? Better yet, have you tried plugging it into a different computer? And does the device work when plugged into a machine running Windows? The "new" scheme is a copy of what Windows does; if the device doesn't like it one would think it wouldn't be able to work with Windows at all. For solving problems like this it really helps to have a USB bus analyzer available... Well, at least you _can_ get it to work on your Powerbook. Alan Stern ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
