Bluetooth on Atheros AW-NB100H, no devices shown after scan.

Question

I bought a halfmini pci card with the atheros chipset for adding bluetooth to my netbook the chipsets are
are AR1111 + AR1005. AR1005 being the bluetooth side which shows up as usb device and so far nothing is turning up any errors yet when i try to scan for devices to pair with using hcitool or blueman nothing shows and on the other side when set to visable my android also doen't detect the netbook. Wifi/wlan works fine. no issues there. I seem to be able to manipulate settings and modes for that part of the card with the hci... commmands as well as rfkill yet nothing seems to make a difference. Also the bios registers it fine as well. I have a usb dongle that I know works as I was previously using it for my bluetooth needs so as far as my setup with bluetooth everything seems to be in order. I've gathered a lot of info on the hardware but there's little info out on the net about this particular internal card. Heres the output(trimmed down to the specifics relating to the device):
The following was used to get this information:
hwinfo --pci (and --usb)
lsmod
lsusb
lspci -vnn
rfkill list all
jounalctl -n
iwconfig
ifconfig
hwinfo --pci (specifically the pci card)
24: PCI 200.0: 0280 Network controller
[Created at pci.319]
Unique ID: y9sn._O8iZVphHCE
Parent ID: hoOk.4aTjYoti5oD
SysFS ID: /devices/pci0000:00/0000:00:1c.2/0000:02:00.0
SysFS BusID: 0000:02:00.0
Hardware Class: network
Model: "Atheros Network controller"
Vendor: pci 0x168c "Atheros Communications Inc."
Device: pci 0x0037
SubVendor: pci 0x1a3b
SubDevice: pci 0x2100
Revision: 0x01
Driver: "ath9k"
Driver Modules: "ath9k", "ath9k"
Device File: wlan0
Memory Range: 0xf9f80000-0xf9ffffff (rw,non-prefetchable)
Memory Range: 0xf9f70000-0xf9f7ffff (ro,non-prefetchable,disabled)
IRQ: 18 (no events)
HW Address: dc:85:de:82:89:67
Module Alias: "pci:v0000168Cd00000037sv00001A3Bsd00002100bc02sc80i00"
Driver Info #0:
Driver Status: ath9k is active
Driver Activation Cmd: "modprobe ath9k"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #13 (PCI bridge)
#hwinfo --usb (specifically the bluetooth entry)
05: USB 00.0: 11500 Bluetooth Device
[Created at usb.122]
Unique ID: wn1q.caWM9jujblA
Parent ID: 2XnU.CCckIHJirFC
SysFS ID: /devices/pci0000:00/0000:00:1d.3/usb5/5-2/5-2:1.0
SysFS BusID: 5-2:1.0
Hardware Class: bluetooth
Model: "Atheros Bluetooth USB Host Controller"
Hotplug: USB
Vendor: usb 0x0cf3 "Atheros Communications, Inc."
Device: usb 0x3008 "Bluetooth USB Host Controller"
Revision: "0.01"
Serial ID: "Alaska Day 2006"
Driver: "btusb"
Driver Modules: "btusb"
Speed: 12 Mbps
Module Alias: "usb:v0CF3p3008d0001dcE0dsc01dp01icE0isc01ip01in00"
Driver Info #0:
Driver Status: btusb is active
Driver Activation Cmd: "modprobe btusb"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #4 (Hub)
#lsmod (excluding some totally unrelated modules from my knowedge)
btusb 12341 0
rfcomm 34304 8
arc4 2008 2
bnep 9210 2
ath9k 99149 0
ath9k_common 2097 1 ath9k
ath9k_hw 356012 2 ath9k_common,ath9k
ath 15362 3 ath9k_common,ath9k,ath9k_hw
mac80211 434959 1 ath9k
cfg80211 180203 3 ath,ath9k,mac80211
iTCO_wdt 5224 0
bluetooth 195418 22 bnep,btusb,rfcomm
rfkill 16029 5 cfg80211,bluetooth,asus_wmi
pci_hotplug 22989 1 asus_wmi
usbhid 37196 0
lpc_ich 11346 0
crc16 1360 2 ext4,bluetooth
uhci_hcd 23501 0
ahci 21393 3
libahci 21003 1 ahci
libata 169219 2 ahci,libahci
ehci_hcd 42393 0
usbcore 153813 5 btusb,uhci_hcd,uvcvideo,ehci_hcd,usbhid
usb_common 955 1 usbcore
#lsusb
Bus 005 Device 002: ID 0cf3:3008 Atheros Communications, Inc.
#lspci
02:00.0 Network controller: Atheros Communications Inc. Device 0037 (rev 01)
#hciconfig
hci0: Type: BR/EDR Bus: USB
BD Address: DC:85:DE:82:82:1E ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING PSCAN ISCAN
RX bytes:575 acl:0 sco:0 events:37 errors:0
TX bytes:1381 acl:0 sco:0 commands:35 errors:0
#ifconfig
wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
ether dc:85:de:82:89:67 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
#iwconfig
wlan0 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=16 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:on
#rfkill list all
0: asus-wlan: Wireless LAN
Soft blocked: no
Hard blocked: no
2: asus-bluetooth: Bluetooth
Soft blocked: no
Hard blocked: no
3: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
5: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
#journalctl -n
bluetoothd[334]: bluetoothd[334]: Stopping discovery
bluetoothd[334]: Stopping discovery
sudo[27501]: maat : TTY=pts/1 ; PWD=/home/maat ; USER=root ; COMMAND=/bin/su
sudo[27501]: pam_unix(sudo:session): session opened for user root by maat(uid=0)
su[27506]: (to root) maat on /dev/pts/1
su[27506]: pam_unix(su:session): session opened for user root by maat(uid=0)
bluetoothd[334]: bluetoothd[334]: Discovery session 0x7f81c3c85430 with :1.25 activated
bluetoothd[334]: Discovery session 0x7f81c3c85430 with :1.25 activated
bluetoothd[334]: bluetoothd[334]: Stopping discovery
bluetoothd[334]: Stopping discovery
Oh found this as well with "hciconfig -a"
hci0: Type: BR/EDR Bus: USB
BD Address: DC:85:DE:82:82:1E ACL MTU: 1022:8 SCO MTU: 183:5
UP RUNNING PSCAN ISCAN
RX bytes:1010 acl:0 sco:0 events:117 errors:0
TX bytes:1829 acl:0 sco:0 commands:100 errors:0
Features: 0xff 0xfe 0x0d 0xfe 0xd8 0x7f 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF
Link mode: SLAVE ACCEPT
Name: 'Asus1018p-0'
Class: 0x580100
Service Classes: Capturing, Object Transfer, Telephony
Device Class: Computer, Uncategorized
HCI Version: 3.0 (0x5) Revision: 0x102
LMP Version: 4.0 (0x6) Subversion: 0x1
Manufacturer: Atheros Communications, Inc. (69)
Last edited by Thme (2012-12-22 03:05:43)

Answer 1

I want to know how these particular devices in the list work in relation to streaming media to devices I know of around the house, and weather leaving their 'Allowed' boxes checked is particularly a good idea.
Once you choose Local or All networks, it should reveal all machines that have successfully connected to the HomeGroup network, you should allow only the trusted networks to access your shared media. if you don't trust it or have some confusion, it's recommended
to remove\block the devices under Media Streaming Options.
Yolanda Zhu
TechNet Community Support