I've posted more details here for userspace diagnosis/workaround, https://bugs.launchpad.net/ubuntu/+source/linux/+bug/377225 Some (older?) BT adapters don't support the commands 'Read Default Link Policy Settings' 'Write Default Link Policy Settings' as shown by # hciconfig hci0 commands This appears be one cause of the infamous kernel message: hci0: command tx timeout. This in turn causes bluetoothd to give up and take down the interface. If you kill bluetoothd, and manually # hciconfig hci0 up, you can discover and inq devices no problem. I made a patch to disable the offending command, and the above mentioned bug report I gave instructions to gather data on adapter BT version, supported features, and supported commands. Hopefully some user reports can be used to make use of the command conditional on actual adapter support. The question for kernel side is, regression, or corrected behaviour? -- Jeremy Jackson Coplanar Networks (519)489-4903 http://www.coplanar.net jerj@xxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
