It would be better to file a new bug for another chip, but I think I can give you the answer right away. Atheros’s engineer had tried to propose this way to upstream but be rejected. However, this is still a “bug” right? So I go to the Bluez page, and search for “atheros,” and you find this: To post a comment you must log in. The information about this bug in Launchpad is automatically pulled daily from the remote bug.
|Date Added:||24 January 2013|
|File Size:||51.18 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
USB lnux, device number 3 [ Ok, looks like the dkms package didn’t install correctly and I think you might want to try It only works if I star Windows and then reboot to Ubuntu. I found this helpful in getting that to show up: Type “lsusb”, if you got this line you probably are:.
I’m having trouble with an AR under Oneric amd The following is from a scan with 4 BT devices advertising themselves a mono headset, an Android phone, BT audio headphones, and BT speakers: So it seams that the device presents itself a total of 3 times, once initially when there is no firmware, then two more times after the firmware loads. I followed AceLan Kao’s steps and got the bluetooth service working on my V, but the bluetooth applet icon in the panel was not visible.
Atheros AR3002 cannot be turned up/is not recognized.
Maintenance out of tree might get expensive after a while. I’ve modified the upstream drivers a little bit and managed to get it working, but the changes are so ulgy they’ll never make into upstream.
Just noting the final few comments in: Leddy jm-leddy wrote on Can you help with this problem? If you got the following output you’re good: Chris, Yes, it’s still a issue.
[Bug 714862] Re: Atheros AR3002 cannot be turned up/is not recognized.
Thanks for posting that. The bug is partly solved in 2. Or do I turn in a bug notice to the bluez developer? Jeff Blanchard j-d-blanchard wrote on I’m also glad to see movement on this issue. Moving this task to ‘In Progress’ linx keep track of the upstream bug.
Bluetooth AR hciattach ath3k fail | NXP Community
I could live without bluetooth, but blacklisting ath3k does not solve this problem. Yes, it’s still a issue. And you’ve done more than just removing libmtp, i. linx
This is really annoying, as it renders standby unusable. On Wed, Jun 13, at 9: You can find it on the right side. This information was last pulled 22 hours ago.
Andriy Yurchuk ch00k wrote on On a separate page, Atheros indicates that: To make it usable on The issue is not in bluez but in the kernel drivers, so I’m reassigning this to the right package. Sorry, I didn’t followup this issue for a while.
New USB device strings: