For some dongles (as my D-Link DBT-122), there little or no kernel problem, but a Bluez problem.
This is what I did concretely:
— display http://http.us.debian.org/debian/pool/main/b/bluez/
— click libbluetooth3_4.40-2_i386.deb and simply accept installation by GDebi
— idem with bluez_4.40-2_i386.deb and bluetooth_4.40-2_all.deb. (Others may have to make an other choice than i386.)
With Bluez 4.40, my problem was solved (after nearly eight months regression!)
It would be interesting that other people test Bluez 4.40 with the Broadcom or other dongles. It would be interesting to make this test with kernels 2.6.27 or 2.6.28. I installed 2.6.29 (with no improvement) before I heard of Bluez 4.40.
For some dongles (as my D-Link DBT-122), there little or no kernel problem, but a Bluez problem.
This is what I did concretely: http.us. debian. org/debian/ pool/main/ b/bluez/ 4.40-2_ i386.deb and simply accept installation by GDebi 40-2_i386. deb and bluetooth_ 4.40-2_ all.deb. (Others may have to make an other choice than i386.)
— display http://
— click libbluetooth3_
— idem with bluez_4.
With Bluez 4.40, my problem was solved (after nearly eight months regression!)
It would be interesting that other people test Bluez 4.40 with the Broadcom or other dongles. It would be interesting to make this test with kernels 2.6.27 or 2.6.28. I installed 2.6.29 (with no improvement) before I heard of Bluez 4.40.