Red Hat Bugzilla – Bug 811087
atheros ar3012 bluetooth in asus ux31e/ux21e not recognized (reopening)
Last modified: 2012-04-26 00:29:17 EDT
Description of problem:
(this bug duplicates #808650 to reopen it since 3.3.1 doesn't have the patch)
Bluetooth on an ASUS UX31E (tested) refuses to discover devices during pairing.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. boot fedora 16 with patches to linux-3.3.1-3.fc16.x86_64 into gnome-3
2. choose "set up a new device..." from the bluetooth menu > continue to device
3. push the "pairing" button on your keyboard
4. be disappointed when your keyboard (in my case, a microsoft bluetooth
keyboard 6000) doesn't show up
no pairing. no keyboard. no love.
still, even since 3.3.1 and #80650
keyboard discovery and typing glory.
Patch at http://thread.gmane.org/gmane.linux.bluez.kernel/18801
applied in Ubunutu https://help.ubuntu.com/community/AsusZenbook
as of 2012-03-22.
The web says the patch is in linux-next.
I thought it was in 3.3.1 (according to the changelog).
But 3.3.1-3.fc16 still leaves me heartbroken.
I don't know how much pain it is to get a patch into the fedora kernel, but
it'd be nice to see this in until the Mainline Kernel catches up.
(I've updated my patch to have a proper name, none of this linux-2.6 junk.)
Created attachment 576376 [details]
kernel patch from http://article.gmane.org/gmane.linux.bluez.kernel/18830
Created attachment 576377 [details]
kernel spec patch, now with more sensible filename and patchno
OK, the patch went into 3.4-rc1. I'll get this into Fedora shortly.
Applied to F15-F17. Will be in the next submitted update. Bodhi will leave a comment here when that has been pushed to the repos.
kernel-184.108.40.206-2.fc15 has been submitted as an update for Fedora 15.
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing kernel-220.127.116.11-2.fc15'
as soon as you are able to, then reboot.
Please go to the following url:
then log in and leave karma (feedback).
Wrt comment #4, the ath3k patch doesn't seem to be in kernel-3.3.1-5.
(But not clear to me what "next submitted update" is exactly.)
Comment #6 speaks only of fc15, and I'm running f16, so perhaps it's
still working its way through?
(In reply to comment #7)
> Wrt comment #4, the ath3k patch doesn't seem to be in kernel-3.3.1-5.
> (But not clear to me what "next submitted update" is exactly.)
> Comment #6 speaks only of fc15, and I'm running f16, so perhaps it's
> still working its way through?
I'm submitting an update today that should cover this in F16.
kernel-3.3.2-1.fc16 has been submitted as an update for Fedora 16.
kernel-3.3.2-1.fc17 has been submitted as an update for Fedora 17.
kernel-3.3.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.
kernel-18.104.22.168-6.fc15 has been submitted as an update for Fedora 15.
kernel-3.3.2-1.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
kernel-22.214.171.124-6.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
I can confirm that kernel-3.3.2-6.fc16 Works For Me.
(I think 3.3.2-1 also did, but that's already history)