If this this is incorrect procedure, please forgive, as I'm new here. 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. Now, in a very rational sense, I believe I have hit the dead end. Which tells me that the AR3002 is still not "seen."Ĭan't init device hci0: Connection timed out (110) TX bytes:24 acl:0 sco:0 commands:8 errors:0 Now, when I launch blueman, I get no connection errors, or anything, but still no options to connect any devices.īD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0 I went ahead and added the natty packages to my repository, so that I could effectively install the bluez 4.87 and related packages. I would hope that "3002" is part of "300x," but I'm not sure. Very briefly, it says "Support for the Atheros AR300x chip." org/l2cap- extended- features- on-2-6- 36/ Go to the Bluez page, and search for "atheros," and you find this: So they say this device should support Bluez. All Bluetooth profiles in Blue Z are supported, including headset and hands-free profiles, A2DP, FTP, DUN, OPP, PAN, SPP and PBAP." "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. This is the device that Dell is putting into this Vostro V130, which Dell ships with Ubuntu 10.04 pre-loaded. The key is the device by Atheros Communications, Inc, which is their AR3002.
0 Comments
Leave a Reply. |