https://bugzilla.kernel.org/show_bug.cgi?id=51221 --- Comment #11 from Paul Bolle <pebolle@xxxxxxxxxx> --- 0) Summary: perhaps this is not (only) a kernel problem, but (also) a bluez problem. 1) I ran into issues pairing the same bluetooth controller (0a5c:201e), also built into an (outdated) ThinkPad X41. But these issues were only seen when I tried to pair with a bluetooth headset. For some reason that headset aborts the pairing process after a few seconds. 2) Pairing with an (equally outdated) PDA did work. Pairing the troubling headset with some other Laptop I have lying around (which is using another Broadcom bluetooth controller) does work. 3) The current non working setup is Fedora 18, which is using bluez 4.101, and a locally built v3.12 kernel. 4) Quite a bit of testing with Fedora Live disks showed that the last working Live disk was Fedora 14, running a v2.6.35 kernel and bluez 4.71 The first Live disk with issues was Fedora 15, running a v2.6.38 kernel and bluez 4.87. 5) Downgrading bluez to Fedora 14's 4.71 on my Fedora 18 system seems to be enough to get pairing working again. (Downgrading to 4.71 required manually copying libudev.so.0.9.1 into /usr/lib/. Readers are warned!) I 6) I'm not sure I've correctly identified the problem. But my current thinking is that changes in bluez between 4.71 and 4.87 trigger issues in how this Broadcom controller and that headset behave during pairing. Does that make sense? -- You are receiving this mail because: You are the assignee for the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
