ukungfu, Some time ago I remember I tried to workaround this, l2ping did work but the connection was not reliable at all, since the card could not signal if its buffer was empty, so the driver would continue sending tx packets continuously even with the tx buffer full. At the moment I cannot find the testing tree I was using at the time, so I can't tell more for now...
After testing in an WinXP virtual machine and sniffing the USB traffic as in comment #11, I could conclude that the problem is not in the bluetooth stack but in the method/init parameters/something like that the btusb driver and/or the usb driver use to initialize the usb communication with the bluetooth card. The only sensible difference between the WinXP dump and the btusb dump was the maximum size of the usb packets sent and received on the wire. I also tried to manually replace the btusb initialization messages with the sniffed ones from WinXP, and it did not work. (P.s. As a quick fix I'd suggest you to buy or borrow a $10 CSR dongle as I've done when I was in a hurry and needed bluetooth on this pc some time ago, this fixed the problem very well. ;) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/950413 Title: Bluetooth connections stalling with some Broadcom cards from year 2005 To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/950413/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
