On Tue, 24 May 2011, Paulo Edgar Castro wrote: > > Unfortunately that's not too helpful either. I suspect some other part > > of the system is supposed to turn on the Bluetooth device but is > > failing to do so. > > > > Here's something else you can try, under 2.6.39. Do this (as root): > > > > echo 0000:00:1a.0>/sys/bus/pci/drivers/uhci_hcd/unbind > > dmesg -c>/dev/null > > echo 0000:00:1a.0>/sys/bus/pci/drivers/uhci_hcd/bind > > dmesg>dmesg.out > > > > and then post the contents of dmesg.out. > > > > Another thing that might help: Collect a usbmon trace for bus 0 while > > doing the above experiment. Instructions are in > > Documentation/usb/usbmon.txt; basically all you need to do is mount a > > debugfs filesystem on /sys/kernel/debug and then do: > > > > cat /sys/kernel/debug/usb/usbmon/0u>usbmon.out > > > > in a separate window before running the commands above. When the other > > commands are finished, kill the "cat" program and post the usbmon.out > > file. > > > > Alan Stern > Hi Alan. > > I'm attaching the outputs. This confirms what I thought earlier: The Bluetooth device simply isn't connected to the USB bus. It may need to be powered on or enabled in some other way. In any event, this isn't a problem in the USB stack -- the problem lies somewhere else. Maybe in ACPI, as Oliver suggested... Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
