On Fri, 2005-04-15 at 23:15 -0400, Alan Stern wrote: > It would help if you set CONFIG_USB_DEBUG and provided a system log > showing what happens when the bluetooth device is enumerated.
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. johannes
dmesg.tar.gz
Description: application/compressed-tar
signature.asc
Description: This is a digitally signed message part
