Atheros Bluetooth AR3011 not working {AMD64}

[Ray Whatman]

I've installed Oneiric on my laptop{it originally came with Natty pre-installed} and I have lost the bluetooth. bluetooth will work if I dual boot linux mint or ubuntu 11.04 then shutdown I get no bluetooth in oneiric, but if I reboot{restart} bluetooth is working fine in oneiric. I'm new to all this so forgive me if I have given the wrong info. I have asked in the ubuntu forums but as always no one cares to help so I'm posting this as a bug as I not sure what else it could be and as a new user if I don't get help how can I know what is right or wrong? I have just done a full clean install of oneiric alpha 3 and I still get no bluetooth I will be happy to install ubuntu 11.04 or linux mint as a dual boot if it will help to resolve this issue and get the bluetooth working again all you have to do is ask. and here is the thread on the ubuntu forums http://ubuntuforums.org/showthread.php?t=1808143

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: bluetooth (not installed)
ProcVersionSignature: Ubuntu 3.0.0-7.9-generic 3.0.0
Uname: Linux 3.0.0-7-generic x86_64
Architecture: amd64
Date: Sun Aug 7 10:49:24 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
InterestingModules: rfcomm bnep bluetooth
MachineType: Kogan Kogan Agora
ProcEnviron:
 LANGUAGE=en_AU:en
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-7-generic root=UUID=ccefc5bc-7fb6-4ed5-b7ed-bf523da84391 ro quiet splash vt.handoff=7
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/05/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 080016
dmi.board.name: Kogan Agora
dmi.board.vendor: Kogan
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: Kogan
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd05/05/2011:svnKogan:pnKoganAgora:pvr1.0:rvnKogan:rnKoganAgora:rvr1.0:cvnKogan:ct10:cvr1.0:
dmi.product.name: Kogan Agora
dmi.product.version: 1.0
dmi.sys.vendor: Kogan
hciconfig:

rfkill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
syslog:

[Gendre (gendre-redhat-bugs)]

Description of problem:
The system can't load the firmware for Atheros AR3011 Bluetooth chip.

dmesg return:
[ 26.117905] ath3k_load_firmware: Can't change to loading configuration err
[ 26.117978] ath3k: probe of 1-1.3:1.0 failed with error -5
[ 26.118051] usbcore: registered new interface driver ath3k

Version-Release number of selected component (if applicable):
2.6.38.5-22.fc15.x86_64

[Chuck (chuck-redhat-bugs)]

Note the upstream bug is closed even though it's not fixed.

Please attach the output of the command 'lsusb -nn' so we can see exactly which device you have.

[Chuck (chuck-redhat-bugs)]

(In reply to comment #1)

> Please attach the output of the command 'lsusb -nn' so we can see exactly which
> device you have.

That should just be 'lsusb'.

[Gendre (gendre-redhat-bugs)]

$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 017: ID 0cf3:3005 Atheros Communications, Inc.
Bus 002 Device 004: ID 174f:1420 Syntek
Bus 002 Device 010: ID 046d:c03e Logitech, Inc. Premium Optical Wheel Mouse (M-BT58)

[Pavel (pavel-redhat-bugs)]

I'm also having this trouble with F15 (F14 was working fine).

My Bluetooth:
Bus 006 Device 002: ID 0cf3:3000 Atheros Communications, Inc. AR3011

[Diego (diego-redhat-bugs)]

I've got the same problem, but this is what I experience:

First time plug:
[ 2057.518106] usb 7-2: new full speed USB device number 5 using uhci_hcd
[ 2057.657083] usb 7-2: New USB device found, idVendor=0cf3, idProduct=3000
[ 2057.657095] usb 7-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2058.938405] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[ 2063.987087] ath3k_load_firmware: Can't change to loading configuration err
[ 2063.987157] ath3k: probe of 7-2:1.0 failed with error -110
[ 2063.987209] usbcore: registered new interface driver ath3k

lsusb:
Bus 007 Device 005: ID 0cf3:3000 Atheros Communications, Inc. AR3011

Unplug and replug:

lsusb just after replug:
Bus 007 Device 005: ID 0cf3:3000 Atheros Communications, Inc. AR3011

lsusb ~1 second after replug:
nothing

lsusb ~2 seconds after replug:
Bus 007 Device 007: ID 0cf3:3005 Atheros Communications, Inc.

Infact I get:
[ 2408.824090] usb 7-2: new full speed USB device number 10 using uhci_hcd
[ 2408.962120] usb 7-2: New USB device found, idVendor=0cf3, idProduct=3000
[ 2408.962126] usb 7-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 2409.454142] usb 7-2: USB disconnect, device number 10
[ 2410.693058] usb 7-2: new full speed USB device number 11 using uhci_hcd
[ 2410.832130] usb 7-2: New USB device found, idVendor=0cf3, idProduct=3005
[ 2410.832134] usb 7-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

and now (after replugging the adapter) Bluetooth works. By the way this is an ASUS USB-BT211.

[Gendre (gendre-redhat-bugs)]

If I turn Gnome to Airplane-Mode On and Off, the bluetooth work. But never at boot.

[Anthony Wong (anthonywong)]

Assigning to Acelan to work along with https://bugs.launchpad.net/ubuntu/+source/linux/+bug/714862.

[Vladimir (vladimir-redhat-bugs)]

Upgrade to linux-firmware-20110731-2 rebuilt from fedora rawhide seems to help out with AR3011-based ASUS USB-BT211 dongle on fedora 14/15 with stock 2.6.38.2-13.fc15.i686.PAE kernel

[Josh (josh-redhat-bugs)]

(In reply to comment #6)
> If I turn Gnome to Airplane-Mode On and Off, the bluetooth work. But never at
> boot.

That sounds like something is booting up and causing rfkill to disable it.

Can you run 'rfkill list' before and after you toggle the Airplane mode and provide the output?

[Gendre (gendre-redhat-bugs)]

Before:

0: cmpc_rfkill: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no

After:

0: cmpc_rfkill: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

[Paul (paul-redhat-bugs)]

Confirming the results reported by Vladimir in Comment 7. Updating to linux-firmware-20110731-2 got the ASUS USB-BT211 working for me in Fedora 15.

[Vladimir (vladimir-redhat-bugs)]

So, the suggested fix is to upgrade to Fedora 16

[Gendre (gendre-redhat-bugs)]

(In reply to comment #11)
> So, the suggested fix is to upgrade to Fedora 16

I upgrade to F16: problem don't fixed.

[Vladimir (vladimir-redhat-bugs)]

I'm able to talk through my Sennheiser MM550 BT headset on Fedora 16 with ASUS USB-BT211 dongle. So please check your hardware. If you are sure you've got hardware, based on Atheros AR3011 Bluetooth chip, please make sure your upgrade process went off well enough.. Anyways, please make sure you've got linux-firmware-20110731-2 intalled, it is in the official F16 repo by now. If you've got stale linux-firmare package, you should probably run software update utility, either install it by hand directly from http://kojipkgs.fedoraproject.org/packages/linux-firmware/20110731/2.fc16/noarch/linux-firmware-20110731-2.fc16.noarch.rpm

[Diego (diego-redhat-bugs)]

(In reply to comment #12)
> (In reply to comment #11)
> > So, the suggested fix is to upgrade to Fedora 16
>
> I upgrade to F16: problem don't fixed.

Same here: Fedora 16.

$ rpm -q linux-firmware
linux-firmware-20110731-2.fc16.noarch

$ rpm -q kernel
kernel-3.1.2-1.fc16.x86_64

dmesg (151 first insertion, 180 second insertion):
[ 151.055020] usb 4-2: new full speed USB device number 2 using uhci_hcd
[ 151.193037] usb 4-2: New USB device found, idVendor=0cf3, idProduct=3000
[ 151.193040] usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 152.452308] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[ 157.467038] Bluetooth: Can't change to loading configuration err
[ 157.467069] ath3k: probe of 4-2:1.0 failed with error -110
[ 157.467095] usbcore: registered new interface driver ath3k
[ 171.704053] usb 4-2: USB disconnect, device number 2
[ 171.910024] usb 4-2: new full speed USB device number 3 using uhci_hcd
[ 172.024017] hub 4-0:1.0: unable to enumerate USB device on port 2
[ 180.357017] usb 4-2: new full speed USB device number 4 using uhci_hcd
[ 180.495035] usb 4-2: New USB device found, idVendor=0cf3, idProduct=3000
[ 180.495038] usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 180.954058] usb 4-2: USB disconnect, device number 4
[ 182.461017] usb 4-2: new full speed USB device number 5 using uhci_hcd
[ 182.601042] usb 4-2: New USB device found, idVendor=0cf3, idProduct=3005
[ 182.601045] usb 4-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 182.615538] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 182.617965] usbcore: registered new interface driver btusb
[ 183.739009] Bluetooth: RFCOMM TTY layer initialized
[ 183.739013] Bluetooth: RFCOMM socket layer initialized
[ 183.739015] Bluetooth: RFCOMM ver 1.11

[Vladimir (vladimir-redhat-bugs)]

Ok. As to my ASUS USB-BT211 dongle, it has the id of 0xf3:3005 and F16 appears to handle it with btusb driver. When I blacklisted btusb and tried to make ath3k handle the device, I got the same fault in firmware loader

Dec 2 02:24:48 ted kernel: [ 143.857509] Bluetooth: Atheros AR30xx firmware driver ver 1.0
Dec 2 02:24:48 ted kernel: [ 143.886726] Bluetooth: Can't change to loading configuration err
Dec 2 02:24:48 ted kernel: [ 143.894563] ath3k: probe of 5-2:1.0 failed with error -71

Both EPROTO(71) and ETIMEDOUT(110) status codes from uhci controller mean that the device refuses to switch to DFU mode, so it doesn't seem to be an issue with Atheros firmware but rather with ath3k driver itself.

When I loaded btusb module by hand, it worked just fine

Dec 2 02:27:52 ted kernel: [ 327.980026] usb 5-2: new full speed USB device number 3 using uhci_hcd
Dec 2 02:27:52 ted kernel: [ 328.118955] usb 5-2: New USB device found, idVendor=0cf3, idProduct=3005
Dec 2 02:27:52 ted kernel: [ 328.118960] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Dec 2 02:27:52 ted bluetoothd[1451]: HCI dev 0 registered

So, I have to apologize. It's me who has got different hardware. But I should confirm that in F15 my device used to be handled with ath3k driver and I was much impressed by the results of the firmware upgrade...

[Gendre (gendre-redhat-bugs)]

This is my log when I boot in Fedora 16:

Dec 5 14:53:54 Aragorn kernel: [ 46.849283] Bluetooth: Core ver 2.16
Dec 5 14:53:54 Aragorn kernel: [ 46.849331] NET: Registered protocol family 31
Dec 5 14:53:54 Aragorn kernel: [ 46.849335] Bluetooth: HCI device and connection manager initialized
Dec 5 14:53:54 Aragorn kernel: [ 46.849342] Bluetooth: HCI socket layer initialized
Dec 5 14:53:54 Aragorn kernel: [ 46.849346] Bluetooth: L2CAP socket layer initialized
Dec 5 14:53:54 Aragorn kernel: [ 46.849360] Bluetooth: SCO socket layer initialized
Dec 5 14:53:54 Aragorn kernel: [ 46.850236] Bluetooth: Atheros AR30xx firmware driver ver 1.0
Dec 5 14:53:54 Aragorn kernel: [ 51.850430] Bluetooth: Can't change to loading configuration err
Dec 5 14:53:54 Aragorn kernel: [ 51.850523] ath3k: probe of 1-1.3:1.0 failed with error -110
Dec 5 14:53:54 Aragorn kernel: [ 51.850591] usbcore: registered new interface driver ath3k

[AceLan Kao (acelankao)]

Hi,

Is it still a issue on 11.10?
Could you please try this dkms package to see if it do anything help if this is still a issue.

[Ray Whatman (roo79x)]

@AceLan Kao, thanks for trying to help but no good installed in ubuntu 11.10 and Linux mint 12 but it didn't work, I'm going to throw this laptop out because of this and the other compatibility problems it has. {So much for ubuntu friendly hey?}... but keep up the great work maybe it will help someone else.

[AceLan Kao (acelankao)]

Ray,

Sorry to hear that, but I just made a quick hack for another package.
Please give it a try if you have not thrown you laptop away.
Remember to remove the previous dkms package before installing this one.

[Ray Whatman (roo79x)]

hey thanks for the update I will try it I salvaged the laptop from the trash in the shed before it was thrown out so I will test your fixes. it would be nice to have the laptop usable again if it works. I've seen heaps of posts on google with people with this same issue but most get fixed by the manufacturer... this is not the case with kogan though and I'm not smart enough to know how to fix it. I am starting to wonder if it has more to do with the kernel packages and not just bluez but I have no idea if that is right.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/714862

http://<email address hidden>/msg3345735.html

http://us.generation-nt.com/answer/bug-641749-bug-641749-update-help-205360731.html

these are just some of the threads I've found using google are they relevant to my issue?

[Ray Whatman (roo79x)]

@AceLan Kao, just tried your latest fix with no luck. It did not work for me :-(. I've included dmesg results for you if that helps at all?

also I found this while I was googling >> http://permalink.gmane.org/gmane.linux.debian.devel.bugs.general/898794

[AceLan Kao (acelankao)]

Ray,

Happy New Year.
The "firmware loading failed" problem should be fixed by ar3011 dkms package, but it seems not work for you.
So, I need more logs from you to dig into the problem.

1. install ar3011-dkms_1.1ryu2.4_all.deb, please remove dw1703-dkms_1.2_all.deb if you have installed it.
2. dkms status > dkms.log
3. add btusb, ath3k in /etc/modprobe.d/blacklist.conf
   % head /etc/modprobe.d/blacklist.conf

   # This file lists those modules which we don't want to be loaded by
   # alias expansion, usually so some other driver will be loaded for the
   # device instead.

   blacklist ath3k
   blacklist btusb

   # evbug is a debug tool that should be loaded explicitly
   blacklist evbug
4. reboot, then lsusb > lsusb-1.log
5. modprobe ath3k, then lsusb > lsusb-2.log

Upload those logs here to see if I can find anything different.

[Ray Whatman (roo79x)]

I will get straight onto it and get the info you need. I have had windows installed but will take no time at all to install ubuntu again.

also I'd like to say a very big thank you, as I have posted about this problem on many forums and you have been the only one to help. it's a real credit to you.!!!

[BrianBehlendorf (brian-hyperreal)]

I have this issue as well. I've installed AceLan's dkms package, and then do a:

modprobe -r ath3k
modprobe ath3k

I get (from the syslog):

Feb 5 11:01:01 buzz kernel: [59150.042608] Bluetooth: Atheros AR30xx firmware driver ver 1.0
Feb 5 11:01:06 buzz kernel: [59155.046021] ath3k_load_firmware: Can't change to loading configuration err
Feb 5 11:01:06 buzz kernel: [59155.046082] ath3k: probe of 1-1.3:1.0 failed with error -110
Feb 5 11:01:06 buzz kernel: [59155.046145] usbcore: registered new interface driver ath3k

which was the same problem as before (and still no bt device found). lsusb shows the AR3011 both before and after the modprobe. DKMS status is:

ar3011, 1.1ryu2.4, 3.0.0-16-generic, x86_64: installed
ar3011, 1.1ryu2.4, 3.2.0-5-generic, x86_64: built

[Anthony Wong (anthonywong)]

Hi Brian,

The theory of the ar3011-dkms is a bit convoluted and hence it doesn't make use of ath3k to make the bluetooth work, but instead it loads the necessary firmware from btusb. Can you try rmmod both btusb and ath3k first, and then modprobe btusb?

Please provide lsusb output before and after loading btusb.

From dkms status output, there are two kernels, which one are you using now?

[BrianBehlendorf (brian-hyperreal)]

root@buzz:~# uname -a
Linux buzz 3.0.0-16-generic #28-Ubuntu SMP Fri Jan 27 17:44:39 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
root@buzz:~# rmmod btusb ath3k
ERROR: Module btusb does not exist in /proc/modules
root@buzz:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 004: ID 174f:1420 Syntek
root@buzz:~# modprobe btusb
root@buzz:~# lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 003: ID 0cf3:3000 Atheros Communications, Inc. AR3011
Bus 002 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 004: ID 174f:1420 Syntek
root@buzz~# tail -4 /var/log/syslog
Feb 6 15:48:59 buzz kernel: [77082.537235] usbcore: deregistering interface driver ath3k
Feb 6 15:49:02 buzz kernel: [77085.975173] Bluetooth: Firmware load driver init. Version:1.0
Feb 6 15:49:02 buzz kernel: [77085.981174] Bluetooth: Generic Bluetooth USB driver ver 0.6.1
Feb 6 15:49:02 buzz kernel: [77085.981280] usbcore: registered new interface driver btusb

Looks like success - however, neither the bluetooth settings panel, or the blueman interface, can find the device.

Brian

[AceLan Kao (acelankao)]

Brian,

Looks like the firmware loaded successfully.
Could you try 'hciconfig' to see if there is any hci device appears?
And try to restart bluetooth daemon
   sudo service bluetooth restart

Try to use the newer ath3k firmware if above steps won't work
   sudo cp /lib/firmware/ath3k-3.fw /lib/firmware/ath3k-3.fw.orig
   sudo cp /lib/firmware/ath3k-1.fw /lib/firmware/ath3k-3.fw
And then reboot

And be aware of that ath3k should not be loaded if you use this dkms,
if your system will load ath3k after booting up, please add ath3k in the /etc/modprobe.d/blacklist.conf

[Ray Whatman (roo79x)]

Sorry for the ultra late reply but I have been tied up with work... AceLan Kao here are the logs you asked for. I followed what you said to do to the letter and these are what I ended up with

[Ray Whatman (roo79x)]

lsusb-1.log

[Ray Whatman (roo79x)]

lsusb-2.log

[Ray Whatman (roo79x)]

this is an lsusb I did with the AR3011 bluetooth showing but not working.

[Anthony Wong (anthonywong)]

Hi Ray,

There is a slight mistake in step 5 in comment #8, the command should be "modprobe btusb" instead of "modprobe ath3k". Could you please run the command again and let us know your result? Thanks.

[BrianBehlendorf (brian-hyperreal)]

Feb 9 15:14:04 buzz kernel: [ 157.428648] Bluetooth: Firmware load driver init. Version:1.0

Following instructions in comment #13,

>Could you try 'hciconfig' to see if there is any hci device appears?

Nothing.

> And try to restart bluetooth daemon
> sudo service bluetooth restart

Nothing.

> Try to use the newer ath3k firmware if above steps won't work
> sudo cp /lib/firmware/ath3k-3.fw /lib/firmware/ath3k-3.fw.orig
> sudo cp /lib/firmware/ath3k-1.fw /lib/firmware/ath3k-3.fw
> And then reboot

There was no /lib/firmware/ath3k-3.fw, only a /lib/firmware/ath3k-1.fw. There was a /var/lib/dkms/ar3011/1.1ryu2.4/build/ath3k-3.fw however, so I swapped that in:

cp /lib/firmware/ath3k-1.fw /lib/firmware/ath3k-1.fw-bak
cp /var/lib/dkms/ar3011/1.1ryu2.4/build/ath3k-3.fw /lib/firmware/

[added btusb and ath3k to modprobe.d/blacklist, and reboot]

Same as before:

root@buzz# modprobe btusb
Feb 9 15:14:04 buzz kernel: [ 157.429864] Bluetooth: Generic Bluetooth USB driver ver 0.6.1
Feb 9 15:14:04 buzz kernel: [ 157.429956] usbcore: registered new interface driver btusb

root@buzz:~# hciconfig
(nothing)

root@buzz:~# sudo service bluetooth restart
Feb 9 15:14:41 buzz bluetoothd[1309]: Stopping SDP server
Feb 9 15:14:41 buzz bluetoothd[1309]: Exit
Feb 9 15:14:42 buzz bluetoothd[2678]: Bluetooth daemon 4.96
Feb 9 15:14:42 buzz bluetoothd[2678]: Starting SDP server
Feb 9 15:14:42 buzz NetworkManager[687]: <warn> bluez error getting default adapter: No such adapter
Feb 9 15:14:42 buzz dbus[657]: [system] Activating service name='org.blueman.Mechanism' (using servicehelper)
Feb 9 15:14:42 buzz blueman-mechanism: Starting blueman-mechanism
Feb 9 15:14:42 buzz dbus[657]: [system] Successfully activated service 'org.blueman.Mechanism'
Feb 9 15:14:42 buzz blueman-mechanism: loading Config
Feb 9 15:14:42 buzz blueman-mechanism: loading Network
Feb 9 15:14:42 buzz blueman-mechanism: loading Ppp
Feb 9 15:14:42 buzz blueman-mechanism: loading RfKill
root@buzz:~# hciconfig
(nothing)

[Serge (serge-redhat-bugs)]

inserting trust bt dongle on f16:
[777840.144046] usb 5-2: new full-speed USB device number 2 using ohci_hcd
[777840.289047] usb 5-2: New USB device found, idVendor=0cf3, idProduct=3000
[777840.289057] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[777841.853933] Bluetooth: Core ver 2.16
[777841.854220] NET: Registered protocol family 31
[777841.854226] Bluetooth: HCI device and connection manager initialized
[777841.854233] Bluetooth: HCI socket layer initialized
[777841.854238] Bluetooth: L2CAP socket layer initialized
[777841.855619] Bluetooth: SCO socket layer initialized
[777841.865135] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[777846.880902] Bluetooth: Can't change to loading configuration err
[777846.881025] ath3k: probe of 5-2:1.0 failed with error -110
[777846.881105] usbcore: registered new interface driver ath3k

[Anthony Wong (anthonywong)]

An updated firmware has recently been posted upstream (ath3k-1.fw) which we have had a preliminary look at and appears to correct the issues here specific to AR3011:

http://permalink.gmane.org/gmane.linux.kernel/1262485

May I ask you who currently have AR3011 to give it a test, by putting the attached ath3k-1.fw firmware file in /lib/firmware. Remember to first remove the ar3011 dkms if you have installed it before testing.

Thanks!

[Anthony Wong (anthonywong)]

This issue should now be fixed for Precise, according to bug 714862.

[Gendre (gendre-redhat-bugs)]

The problem seems to be resolved on Fedora 17.

[James (james-redhat-bugs)]

(In reply to comment #18)
> The problem seems to be resolved on Fedora 17.

Not for me with 13d3:3304, an internal IMC Networks adapter. Loading ath3k fails for me with

  Bluetooth: Can't change to loading configuration err
  [ 935.527588] ath3k: probe of 1-1.2:1.0 failed with error -110

Works find in Windows 7. (It's odd -- once got it to work, but can't recall how. Running lsusb -v on this device seems to pause briefly at the end.) Might be a different bug, though.

[Dave (dave-redhat-bugs)]

James, that seems like a separate problem. Can you file a new bug on that if it's still happening with the 3.4 update ?

thanks.

[Vladimir (vladimir-redhat-bugs)]

(In reply to comment #17)
> inserting trust bt dongle on f16:
> [777840.144046] usb 5-2: new full-speed USB device number 2 using ohci_hcd
> [777840.289047] usb 5-2: New USB device found, idVendor=0cf3, idProduct=3000

My ASUS USB-BT211 dongle (0cf3:3005) works just fine with stock f16 btusb:

Jun 19 02:34:56 ted kernel: [187877.956040] usb 5-2: new full-speed USB device number 4 using uhci_hcd
Jun 19 02:34:57 ted kernel: [187878.094619] usb 5-2: New USB device found, idVendor=0cf3, idProduct=3005
Jun 19 02:34:57 ted kernel: [187878.094625] usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jun 19 02:34:57 ted kernel: [187878.171351] usbcore: registered new interface driver btusb