[Kernel-packages] [Bug 714862] Re: Atheros AR3011 cannot be turned up/is not recognized.
** Changed in: debian Status: Confirmed => Fix Released -- 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/714862 Title: Atheros AR3011 cannot be turned up/is not recognized. Status in HWE Next: Fix Released Status in Linux: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Maverick: Won't Fix Status in linux-firmware source package in Natty: Won't Fix Status in linux-firmware source package in Oneiric: Won't Fix Status in linux-firmware source package in Precise: Fix Released Status in Debian: Fix Released 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://www.bluez.org/l2cap-extended-features-on-2-6-36/ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/714862/+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
[Kernel-packages] [Bug 714862] Re: Atheros AR3011 cannot be turned up/is not recognized.
** Also affects: hwe-next Importance: Undecided Status: New ** Changed in: hwe-next Status: New = Fix Released -- 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/714862 Title: Atheros AR3011 cannot be turned up/is not recognized. Status in HWE Next Project: Fix Released Status in The Linux Kernel: Confirmed Status in “linux-firmware” package in Ubuntu: Fix Released Status in “linux-firmware” source package in Maverick: Won't Fix Status in “linux-firmware” source package in Natty: Won't Fix Status in “linux-firmware” source package in Oneiric: Won't Fix Status in “linux-firmware” source package in Precise: Fix Released Status in Debian GNU/Linux: Confirmed 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://www.bluez.org/l2cap-extended-features-on-2-6-36/ 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. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/714862/+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
