I have updated my kernel from 3.14 rc6 to the latest 3.15 code from Linus' tree. My bluetooth dongle that uses the ath3k driver no longer works. I am running the i386 (32 bit Intel) version of the kernel.
Same here, before 3.15 my bluetooth does not use ath3k driver. But with this commit https://github.com/torvalds/linux/commit/ca58e594da2486c1d28e7ad547d82266604ec4ce it is try to use ath3k module and failed with this error: "Can't get version to change to load ram patch err" blacklisting ath3k may help (does not try yet)
Hmm, I was wrong it uses ath3k on 3.14 too.
Ok my fault again, I was not wrong on 3.14 it use btusb. On 3.15 it is try to use ath3k
Created attachment 140051 [details] remove pid and vid from ath3k With this changes my bluetooth works again
So it seems that commit https://github.com/torvalds/linux/commit/ca58e594da2486c1d28e7ad547d82266604ec4ce is wrong, so could anyone revert it? Or what I could do for remove changes which comes with that commit?
Still affected on 3.15.2-1, using Arch. Same problem solved with given patch, thank you Daniel. Link to bugreport on archlinux: https://bugs.archlinux.org/task/40902
well apparently some people had dyslexia: From the commit == Bluetooth: Add a new PID/VID 0cf3/e005 for AR3012. == At the top of the original commit the VID clearly states 'e005'. So it starts with an 'e'. then why did this 'e' change into a '3' ?? Also the persons that signed off these commit also did not see the change from a 'e' to a '3'. PLease revert as soon as possible because this is holding me off from a kernel update.
Created attachment 141341 [details] ath3k&btusb USB_DEVICE(0x0cf3, 0x3005) --> USB_DEVICE(0x0cf3, 0xe005) sha256sum='e0c100fe0949a86088537c37e2e0e585730ab625e923efa5993467b80264e68c' Commit after good sleuthing from dutchman55.
It seems to me like this is already fixed in both bluetooth.git and bluetooth-next.git. The patch is called "Revert "Bluetooth: Add a new PID/VID 0cf3/e005 for AR3012." and it's also tagged to be backported to the 3.15.x stable tree.
@Johan, how long these things 'normally' take? I saw the revert on git. Running 3.15.3 right now, had to patch it myself, not a big deal, though.
Updated to 3.15.3 from 3.14.9 and noticed this problem either. In which revision the patch will be included?
Upgraded from 3.13.0 to 3.15.5 and even 3.16rc5 and lost bluetooth. My adapter is listed by lsusb as follows: Bus 003 Device 002: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
The patch in question has been in the net tree already for many weeks without the net maintainer making a new pull request for Linus (which would get it to the next 3.16-rc release as well as to the 3.15.x stable releases a bit later).
The patch has just hit Linus's mainline tree.