Brian Rogers wrote: > 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.
Thanks for finding that, but it didn't help. I've tried hci_usb with Jaunty's 2.6.28-7, and it didn't solve my problem. My next attempt will be to try and build the entire Bluetooth stack from 2.6.24 grafted into the newer kernel, and see if that works... (I suspect my problem is a different bug.) -- Jamie -- 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
