Hi Pavel, On Mon, Jun 10, 2013, Pavel Machek wrote: > root@amd:~# hciconfig hci0 up > Can't init device hci0: Operation not supported (95) > root@amd:~# hcitool inq > Inquiring ... > Inquiry failed.: No such device > root@amd:~# Could you take logs of the HCI traffic that happens when you try this. You can use the btmon tool from BlueZ for it. Based on a quick look at the code it seems like this particular error could only come if one of the HCI commands used for device initialization fails. The Bluetooth HCI init sequence is constructed using only commands that should be expected to work assuming the hardware follows the specification, but occasionally we do encounter Bluetooth hardware that is broken in one way or another and needs a work around to the sequence. E.g. recently we added a couple of extra commands to read some new parameters from the hardware, commands that are mandatory for hardware beyond a specific version (something we check for), but could be that the chip on the X60 doesn't support these. Anyway, once we see what exactly is failing in the HCI logs we can make an adjustment to the conditions that the failing commands depend on, which in the worst case will be a device specific quirk based on the USB id of your hardware. Johan -- 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
