Bug 1070287
| Summary: | [ath3k] Bluetooth adapter not recognized | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | francesco21 <francescospina22> |
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 20 | CC: | diego.ml, fadnix, gansalmon, itamar, jgrulich, jonathan, jreznik, kernel-maint, kevin, ltinkl, madhu.chinakonda, rdieter, redhat, than |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2014-12-10 14:58:44 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
francesco21
2014-02-26 14:48:47 UTC
[ 15.528479] ath3k: probe of 2-4:1.0 failed with error -110 → kernel (driver) bug, reassigning I have the same embedded bluetooth controller, with the same "failure to load firmware" issue.
I used the suggestion in the referenced thread to stop mtp from probing the card: at that point the device started working.
To summarize: I added this line to /lib/udev/rules.d/69-libmtp.rules:
ATTR{idVendor}=="13d3", ATTR{idProduct}=="3402", GOTO="libmtp_rules_end"
And the device started working.
Sorry but i don't understand where do you added this line, because if i open the file that you mentioned i have a lot of line but where i have to put this? Thank you. There are a few other lines in that file that have GOTO="libmtp_rules_end" in them (around line 22). Basically: add the id for your (our? :-) bluetooth adapter to that list; it says to avoid the rest of the file. As near as I can tell: the actual beneficial effect is to avoid the MTP autoprobe at the end of the file (look for the comment that starts with 'Autoprobe') You said that i have to change the line with this results?
# Some sensitive devices we surely don't wanna probe
# Color instruments
ATTR{idVendor}=="0670", GOTO="libmtp_rules_end"
ATTR{idVendor}=="0765", GOTO="libmtp_rules_end"
ATTR{idVendor}=="085c", GOTO="libmtp_rules_end"
ATTR{idVendor}=="0971", GOTO="libmtp_rules_end"
# Canon scanners that look like MTP devices (PID 0x22nn)
ATTR{idVendor}=="04a9", ATTR{idProduct}=="22*", GOTO="libmtp_rules_end"
# Canon digital camera (EOS 3D) that looks like MTP device (PID 0x3113)
ATTR{idVendor}=="04a9", ATTR{idProduct}=="3113", GOTO="libmtp_rules_end"
# Sensitive Atheros devices that look like MTP devices
ATTR{idVendor}=="13d3", ATTR{idProduct}=="3402", GOTO="libmtp_rules_end"
ATTR{idVendor}=="0cf3", GOTO="libmtp_rules_end"
But doen't work.
I'm sorry it didn't work for you; it did for me, but I guess your problem is different then. And just to ask the really obvious question: you power cycled your machine after you made the change, right? Yes i did this but doesn't work, i have the same problem some time works some time no, there is no reason about this :D *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.14.4-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those. I am on 3.14.5-200.fc20.x86_64 and still have this bug. Bluetooth used to work before, I don't use it much but when i needed it today it wasn't recognized with the same results as the bug reporter. I found a fix at http://wireless.kernel.org/en/users/Drivers/ath9k/btcoex which enables Bluetooth coexistence with WIFI and it works for me. I created a file [bluetooth-fix.conf] under /etc/modprobe.d with this line: options ath9k btcoex_enable=1 reboot and that is all. Hope it can be fixed so we don't need to do this. *********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 20 kernel bugs. Fedora 20 has now been rebased to 3.17.2-200.fc20. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 21, and are still experiencing this issue, please change the version to Fedora 21. If you experience different issues, please open a new bug report for those. This bug is being closed with INSUFFICIENT_DATA as there has not been a response in over 3 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously. This is still a problem on Fedora 20 with all updates as of 10 March 2015. # uname -a Linux localhost.localdomain 3.18.7-100.fc20.x86_64 #1 SMP Wed Feb 11 19:01:50 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux # lsusb -d 13d3:3402 Bus 001 Device 003: ID 13d3:3402 IMC Networks # modprobe -r ath3k [mar 9 06:11] usbcore: deregistering interface driver ath3k # modprobe ath3k [ +7,869333] Bluetooth: Error in firmware loading err = -110,len = 448, size = 4096 [ +0,000008] Bluetooth: Loading patch file failed [ +0,000006] ath3k: probe of 1-5:1.0 failed with error -110 [ +0,000044] usbcore: registered new interface driver ath3k |