Bluetooth connection problem after R1 upgrage

Hello!
I use BT5, and bluetooth works fine. (2.6.38)
I`ve upgraded it to R1 (2.6.39.4), and that caused trouble with my bluetooth connections.
When I run hciconfig -a hci0 - ok, I see the device, it`s up and working
hcitool scan --all - ok, I can see the device I`m trying to connect with. But when I run sdptool browse %bd_addr% - I see this error

Failed to connect to SDP server on %bd_addr%: Protocol not supported

So, the question is - how to fix this? I`d like 2 use R1, but with working bluetooth...

I have this same problem :/ Has anyone found a solution to this?

Is anyone else having this issue? I need a fix :/

Perhaps it has something to do with this: http://blog.projectnibble.org/2010/08/08/how-ubuntus-broken-bluetooth-support-came-to-be/

last link nobacktrackt working!

Hi,

unfortunately - and for some reason unknown to me - Redmine doesn't let me register a new account. Thus I try to comment on http://redmine.backtrack-linux.org:8080/issues/269 in the related forums thread. That said, is there any plan to release an updated kernel for BT5r1 with l2cap support at some point in time? I mean, Bluetooth in BT5r1 is essentially useless atm.

Thanks,
orange

Yes, too bad if you suddenly discover than if you want to set up Kismet + Kismon + GPS share with Android phone over Bluetooth you need to downgrade kernel.

Quote:

---

Originally Posted by MI1c00k

Yes, too bad if you suddenly discover than if you want to set up Kismet + Kismon + GPS share with Android phone over Bluetooth you need to downgrade kernel.

---

Hi
Is there a posted fix for this that others could follow >? Or is the solution to use an older version of Backtrack ?

Cheers

The BT team just recently upgraded bluez, obex, and bluez-hcidump to the latest versions. Try apt-get update && apt-get dist-upgrade to get the latest versions of those software packages and see if Bluetooth works for you.

Yeppers. Kernel 3.2.6 has a kernel config which brings back the bluez :)
Please report any bluetooth issues you may have with the 3.2.6 kernel in a new thread.