The configuration menu only lets you select one of the two drivers, but
I don't see a reason the two should conflict as long as you only allow
one of them to load.

Switching to the older driver is more of a workaround than a solution.
The new driver needs to be fixed one way or another, and once we have
the fix, we can backport it.

But anyone who wants working Bluetooth today can build a custom kernel
with hci_usb instead of btusb.

-- 
Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/268502
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to