Hi Keith, > > A consequence is that you'll need to use newer version of bluez, at least 4.99. > > Or call the bluetooth daemon (from a pre 4.99 version) with a parameter to > > disable the new interface: > > That's not OK -- you're breaking user space with this kernel change. I > know I get bashed every time I suggest that we 'fix' the kernel and > require new user space X bits... I think we actually have a broken user space in this case. I do have a hunch on what went wrong. It is not the kernel's fault here. If I am anywhere right, then bluetoothd fails to bring up the device. That is why you don't see anything with "hcitool dev", but the device should be present. Check "hciconfig -a". Check your bluetoothd startup line and add "-P mgmtops". That will disable the broken plugin. Regards Marcel -- 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
