Atheros AR3011 cannot be turned up/is not recognized.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
Linux |
Confirmed
|
Medium
|
|||
Debian |
Fix Released
|
Unknown
|
|||
linux-firmware (Ubuntu) |
Fix Released
|
High
|
AceLan Kao | ||
Maverick |
Won't Fix
|
High
|
Unassigned | ||
Natty |
Won't Fix
|
High
|
AceLan Kao | ||
Oneiric |
Won't Fix
|
High
|
AceLan Kao | ||
Precise |
Fix Released
|
High
|
AceLan Kao |
Bug Description
The key is the device by Atheros Communications, Inc, which is their AR3002.
This is the device that Dell is putting into this Vostro V130, which Dell ships with Ubuntu 10.04 pre-loaded.
Atheros indicates that:
"As a proponent of open software, Atheros provides its own Bluetooth stack for easy portability and also supports standard Bluetooth stacks such as Blue Z on Linux, Chrome OS, and Android OS. All Bluetooth profiles in Blue Z are supported, including headset and hands-free profiles, A2DP, FTP, DUN, OPP, PAN, SPP and PBAP.."
So they say this device should support Bluez.
Go to the Bluez page, and search for "atheros," and you find this:
http://
Very briefly, it says "Support for the Atheros AR300x chip."
I would hope that "3002" is part of "300x," but I'm not sure. I went ahead and added the natty packages to my repository, so that I could effectively install the bluez 4.87 and related packages.
Well, this ends a lot of errors. Now, when I launch blueman, I get no connection errors, or anything, but still no options to connect any devices.
This still happens:
sudo hciconfig:
hci0: Type: BR/EDR Bus: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:24 acl:0 sco:0 commands:8 errors:0
Which tells me that the AR3002 is still not "seen."
sudo hciconfig hci0 up yields:
Can't init device hci0: Connection timed out (110)
Now, in a very rational sense, I believe I have hit the dead end. The device is simply too new, I guess, to be supported(?) Turning in bug request in hope of future support, and as question has no activity on it. If this this is incorrect procedure, please forgive, as I'm new here.
Related branches
tags: | added: blocks-hwcert |
Changed in linux (Ubuntu Natty): | |
assignee: | nobody → AceLan Kao (acelankao) |
importance: | Undecided → High |
status: | New → In Progress |
tags: | added: oneiric |
tags: | added: blocks-hwcert-enablement |
tags: | added: rls-mgr-o-tracking |
Changed in linux: | |
importance: | Unknown → Medium |
status: | Unknown → Confirmed |
Changed in linux (Ubuntu Oneiric): | |
milestone: | none → oneiric-updates |
Changed in linux (Ubuntu Precise): | |
status: | New → In Progress |
importance: | Undecided → High |
tags: |
added: rls-mgr-p-tracking removed: rls-mgr-o-tracking |
Changed in linux (Ubuntu Maverick): | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in linux (Ubuntu Precise): | |
assignee: | nobody → AceLan Kao (acelankao) |
Changed in linux (Ubuntu Maverick): | |
status: | In Progress → Fix Committed |
status: | Fix Committed → Won't Fix |
summary: |
- Atheros AR3002 cannot be turned up/is not recognized. + Atheros AR3011 cannot be turned up/is not recognized. |
tags: | added: precise |
affects: | linux (Ubuntu Precise) → linux-firmware (Ubuntu Precise) |
Changed in linux-firmware (Ubuntu Precise): | |
status: | In Progress → Fix Committed |
Changed in debian: | |
status: | Unknown → Confirmed |
tags: | added: kernel-wifi |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in debian: | |
status: | Confirmed → Fix Released |
I have found a dkms-driver for the Atheros chipset on the recovery image which I created from the pre-installed Ubuntu 10.04. Thus, I tried to install it under Ubuntu 10.10 (64 Bit). The BT Device was recognized immediately after the installation and still works fine for me.