Launchpad has imported 22 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=702375.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2011-05-05T13:46:22+00:00 Gendre wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/0 ------------------------------------------------------------------------ On 2011-05-06T11:52:49+00:00 Chuck wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/1 ------------------------------------------------------------------------ On 2011-05-06T11:53:57+00:00 Chuck wrote: (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'. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/2 ------------------------------------------------------------------------ On 2011-05-20T14:54:10+00:00 Gendre wrote: $ 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) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/3 ------------------------------------------------------------------------ On 2011-07-12T16:59:30+00:00 Pavel wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/4 ------------------------------------------------------------------------ On 2011-08-12T07:58:00+00:00 Diego wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/7 ------------------------------------------------------------------------ On 2011-08-12T11:50:52+00:00 Gendre wrote: If I turn Gnome to Airplane-Mode On and Off, the bluetooth work. But never at boot. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/8 ------------------------------------------------------------------------ On 2011-10-03T19:08:57+00:00 Vladimir wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/10 ------------------------------------------------------------------------ On 2011-10-07T13:59:01+00:00 Josh wrote: (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? Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/11 ------------------------------------------------------------------------ On 2011-10-08T11:27:17+00:00 Gendre wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/12 ------------------------------------------------------------------------ On 2011-10-19T20:13:12+00:00 Paul wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/13 ------------------------------------------------------------------------ On 2011-11-09T18:15:58+00:00 Vladimir wrote: So, the suggested fix is to upgrade to Fedora 16 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/14 ------------------------------------------------------------------------ On 2011-11-28T13:29:38+00:00 Gendre wrote: (In reply to comment #11) > So, the suggested fix is to upgrade to Fedora 16 I upgrade to F16: problem don't fixed. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/15 ------------------------------------------------------------------------ On 2011-11-28T16:18:19+00:00 Vladimir wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/16 ------------------------------------------------------------------------ On 2011-11-29T12:18:15+00:00 Diego wrote: (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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/17 ------------------------------------------------------------------------ On 2011-12-02T00:49:56+00:00 Vladimir wrote: 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... Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/18 ------------------------------------------------------------------------ On 2011-12-05T14:00:07+00:00 Gendre wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/19 ------------------------------------------------------------------------ On 2012-02-27T23:22:14+00:00 Serge wrote: 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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/37 ------------------------------------------------------------------------ On 2012-05-05T09:31:26+00:00 Gendre wrote: The problem seems to be resolved on Fedora 17. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/40 ------------------------------------------------------------------------ On 2012-05-05T10:27:07+00:00 James wrote: (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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/41 ------------------------------------------------------------------------ On 2012-06-18T21:46:47+00:00 Dave wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/42 ------------------------------------------------------------------------ On 2012-06-18T22:55:05+00:00 Vladimir wrote: (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 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux- firmware/+bug/822128/comments/43 ** Changed in: bluez Status: Unknown => Fix Released ** Changed in: bluez Importance: Unknown => Undecided -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/822128 Title: Atheros Bluetooth AR3011 not working {AMD64} Status in Bluez Utilities: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Bug description: 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: To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/822128/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
