Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 882693 - Atheros Bluetooth is not starting...
Summary: Atheros Bluetooth is not starting...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 18
Hardware: i686
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-02 17:23 UTC by Iosif Bancioiu
Modified: 2013-07-27 15:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-27 15:23:10 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Comment (139.45 KB, text/plain)
2013-01-07 21:47 UTC, Iosif Bancioiu
no flags Details

Description Iosif Bancioiu 2012-12-02 17:23:20 UTC
Description of problem:
The system can't load the firmware for Atheros AR9285 Bluetooth chip.

dmesg return:
[   60.320181] Bluetooth: Can't change to loading configuration err
[   60.320225] ath3k: probe of 4-1:1.0 failed with error -110

rfkill list return:
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no

So it can't see the adapter

Additional info:
1) The Bluetooth is working in Windows 7 @ 32 BIT
2) I use Dell Vostro 1015
3) The WiFi is working.

Comment 1 Iosif Bancioiu 2012-12-02 18:21:52 UTC
Also, in win 7 the adapter name is dell  1702 bluetooth driver, but i'm sure that the adapter is AR9285 because in windows i use fn+f11to disable the wifi and the bluetooth, so is on the same channel and is the same device....

Comment 2 Josh Boyer 2013-01-07 19:43:25 UTC
Please attach the full dmesg output from a boot.

Also, please attach the output of lspci -nnvv and 'lsusb -v'.

Comment 3 Josh Boyer 2013-01-07 19:44:33 UTC
Also, is the bluetooth service running on this machine?

Comment 4 Iosif Bancioiu 2013-01-07 21:47:52 UTC
Created attachment 915651 [details]
Comment

(This comment was longer than 65,535 characters and has been moved to an attachment by Red Hat Bugzilla).

Comment 5 Josh Boyer 2013-03-11 20:04:04 UTC
Are you still seeing this with 3.7.9 or 3.8.2?

Also, it' isn't the AR9285 device that's failing.

Comment 6 Iosif Bancioiu 2013-03-13 13:59:34 UTC
(In reply to comment #5)
> Are you still seeing this with 3.7.9 or 3.8.2?
> 
> Also, it' isn't the AR9285 device that's failing.

Hi, i have kernel 3.8.1 f18 kde 4.9.5 and the problem is still here :(

Comment 7 Iosif Bancioiu 2013-03-18 17:51:08 UTC
the bug is still here, on 3.8.3

Comment 8 Josh Boyer 2013-06-03 19:09:40 UTC
Are you still seeing this with the 3.9.4 kernel in updates-testing?

Comment 9 Iosif Bancioiu 2013-06-04 15:39:52 UTC
(In reply to Josh Boyer from comment #8)
> Are you still seeing this with the 3.9.4 kernel in updates-testing?

No, no result. Could it be an KDE problem?

Comment 10 Iosif Bancioiu 2013-06-08 09:56:53 UTC
I mean yes, the problem is still here

Comment 11 Iosif Bancioiu 2013-06-08 09:59:58 UTC
(In reply to Iosif Bancioiu from comment #10)
> I mean yes, the problem is still here

and the bug is present in F18 + KDE too

Comment 12 Fedora End Of Life 2013-07-03 23:33:40 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.


Note You need to log in before you can comment on or make changes to this bug.