AR3011 LINUX DRIVER

Bus Device To get AR working by default I've just removed libmpt-runtime as in this bug report http: How to fix this? Can you try rmmod both btusb and ath3k first, and then modprobe btusb? HCI socket layer initialized [
Uploader: Zulkigal
Date Added: 13 June 2015
File Size: 52.43 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 33424
Price: Free* [*Free Regsitration Required]





AR Bus Device I'm also glad to see movement on this issue. From the bug report, it seems to be reporting itself as 0cf3: Well, not that I'd tell you are wrong, Eric, but the problem isn't in linux kernel itself. This was taken care of already, by upgrading to Atheros fixed this changing the firmware to make the card change to after the firmware is loaded so that it is picked up by the btusb driver.

Debian -- Details of package firmware-atheros in stretch

Could you please run the command again and let us know your result? Hi AceLan, What's the upstream status?

AceLan Kao acelankao wrote on Sorry to hear that, but I just made a quick hack for another package. New USB device strings: Assigning to Acelan to work along with https: Unifying Receiver Bus Device Eric, the default 3. I don't know if I'm in the right place or not, but I just want to say thank you very much especially to AceLan Kao.

There's another bug about this too, it's bug Leddy jm-leddy on Hi Michael, Thanks for doing a3011 extensive testing! Is there an alternative because the upstream hackers didn't like the first patch or did they offer any other possible ways to fix?

Atheros Super G don't work. I followed your steps as such: Open Source Consulting Domain Registration.

Atheros AR bluetooth and ath3k do not work properly

Andriy Yurchuk ch00k wrote on I'm new to all this so forgive me if I have given the wrong info. I went ahead and added the natty packages to my repository, so that I could effectively install the bluez 4. Starting SDP server Feb 9 In Red Hat BugzillaPaul paul-redhat-bugs wrote on Jeff Marcom jeffmarcom wrote on Connection to BlueZ failed - BlueZ deamon is not runing, blueman-manager cannot continune, sudo service bluetooth restart hepls, bu you have to still enter it Could you try 'hciconfig' to see if there is any hci device appears?

As previously mentioned in 49, the machine has the latest linux-firmware, but fails to load the firmware to the device: Mention the kernel bug in the bug description.

DFU Driver for Atheros bluetooth chipset AR3011

Hopefully this can be pushed liux so that other users don't have to struggle with it. Atheros AR30xx firmware driver ver 1. Yes, it's still a issue. Pro Throttle Bus Device It looks you are using quite shinning kernel:

Comments