Bug 73981 - ath3k: Trust Bluetooth dongle does not work anymore
Summary: ath3k: Trust Bluetooth dongle does not work anymore
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Bluetooth (show other bugs)
Hardware: i386 Linux
: P1 blocking
Assignee: linux-bluetooth@vger.kernel.org
Depends on:
Reported: 2014-04-14 07:41 UTC by Dylan Borg
Modified: 2016-02-15 21:42 UTC (History)
10 users (show)

See Also:
Kernel Version: 3.15
Tree: Mainline
Regression: Yes

remove pid and vid from ath3k (1.68 KB, patch)
2014-06-17 06:21 UTC, Daniel Kozák
Details | Diff
ath3k&btusb USB_DEVICE(0x0cf3, 0x3005) --> USB_DEVICE(0x0cf3, 0xe005) (1.72 KB, patch)
2014-06-29 15:14 UTC, mark
Details | Diff

Description Dylan Borg 2014-04-14 07:41:27 UTC
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.
Comment 1 Daniel Kozák 2014-06-09 16:40:11 UTC
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)
Comment 2 Daniel Kozák 2014-06-10 06:16:37 UTC
Hmm, I was wrong it uses ath3k on 3.14 too.
Comment 3 Daniel Kozák 2014-06-10 06:24:58 UTC
Ok my fault again, I was not wrong on 3.14 it use btusb. On 3.15 it is try to use ath3k
Comment 4 Daniel Kozák 2014-06-17 06:21:26 UTC
Created attachment 140051 [details]
remove pid and vid from ath3k

With this changes my bluetooth works again
Comment 5 Daniel Kozák 2014-06-18 13:12:34 UTC
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?
Comment 6 mark 2014-06-28 19:03:26 UTC
Still affected on 3.15.2-1, using Arch.
Same problem solved with given patch, thank you Daniel.

Link to bugreport on archlinux:
Comment 7 dutchman55 2014-06-29 12:24:41 UTC
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.
Comment 8 mark 2014-06-29 15:14:38 UTC
Created attachment 141341 [details]
ath3k&btusb USB_DEVICE(0x0cf3, 0x3005) --> USB_DEVICE(0x0cf3, 0xe005)


Commit after good sleuthing from dutchman55.
Comment 9 Johan Hedberg 2014-06-30 07:53:17 UTC
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.
Comment 10 mark 2014-07-01 10:25:51 UTC
@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.
Comment 11 careca 2014-07-09 17:18:49 UTC
Updated to 3.15.3 from 3.14.9 and noticed this problem either.
In which revision the patch will be included?
Comment 12 nortexoid 2014-07-16 13:19:08 UTC
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
Comment 13 Johan Hedberg 2014-07-16 13:34:38 UTC
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).
Comment 14 Dylan Borg 2014-07-17 13:44:29 UTC
The patch has just hit Linus's mainline tree.

Note You need to log in before you can comment on or make changes to this bug.