Anycom USB-250 unseen by hcitool

Hello. I recently bought an Anycom USB-250 Bluetooth adapter, and I'm trying to get it to work with my Palm Tungsten E2 so that I can get online on the E2.

However, I can't get it to work. When I run "hcitool scan", I get this error message: "Device is not available: No such device."

This confuses me because I seem to have plenty of devices in /dev:

crw-rw---- 1 root dialout 10, 250 2008-05-12 17:53 vhci

crw-rw---- 1 root dialout 216,   3 2008-05-12 17:53 ttyUB3
crw-rw---- 1 root dialout 216,   2 2008-05-12 17:53 ttyUB2
crw-rw---- 1 root dialout 216,   1 2008-05-12 17:53 ttyUB1
crw-rw---- 1 root dialout 216,   0 2008-05-12 17:53 ttyUB0
crw-rw---- 1 root dialout 216,   9 2008-05-12 17:53 rfcomm9
crw-rw---- 1 root dialout 216,   8 2008-05-12 17:53 rfcomm8
crw-rw---- 1 root dialout 216,   7 2008-05-12 17:53 rfcomm7
crw-rw---- 1 root dialout 216,   6 2008-05-12 17:53 rfcomm6
crw-rw---- 1 root dialout 216,   5 2008-05-12 17:53 rfcomm5
crw-rw---- 1 root dialout 216,   4 2008-05-12 17:53 rfcomm4
crw-rw---- 1 root dialout 216,  31 2008-05-12 17:53 rfcomm31
crw-rw---- 1 root dialout 216,  30 2008-05-12 17:53 rfcomm30
crw-rw---- 1 root dialout 216,   3 2008-05-12 17:53 rfcomm3
crw-rw---- 1 root dialout 216,  29 2008-05-12 17:53 rfcomm29
crw-rw---- 1 root dialout 216,  28 2008-05-12 17:53 rfcomm28
crw-rw---- 1 root dialout 216,  27 2008-05-12 17:53 rfcomm27
crw-rw---- 1 root dialout 216,  26 2008-05-12 17:53 rfcomm26
crw-rw---- 1 root dialout 216,  25 2008-05-12 17:53 rfcomm25
crw-rw---- 1 root dialout 216,  24 2008-05-12 17:53 rfcomm24
crw-rw---- 1 root dialout 216,  23 2008-05-12 17:53 rfcomm23
crw-rw---- 1 root dialout 216,  22 2008-05-12 17:53 rfcomm22
crw-rw---- 1 root dialout 216,  21 2008-05-12 17:53 rfcomm21
crw-rw---- 1 root dialout 216,  20 2008-05-12 17:53 rfcomm20
crw-rw---- 1 root dialout 216,   2 2008-05-12 17:53 rfcomm2
crw-rw---- 1 root dialout 216,  19 2008-05-12 17:53 rfcomm19
crw-rw---- 1 root dialout 216,  18 2008-05-12 17:53 rfcomm18
crw-rw---- 1 root dialout 216,  17 2008-05-12 17:53 rfcomm17
crw-rw---- 1 root dialout 216,  16 2008-05-12 17:53 rfcomm16
crw-rw---- 1 root dialout 216,  15 2008-05-12 17:53 rfcomm15
crw-rw---- 1 root dialout 216,  14 2008-05-12 17:53 rfcomm14
crw-rw---- 1 root dialout 216,  13 2008-05-12 17:53 rfcomm13
crw-rw---- 1 root dialout 216,  12 2008-05-12 17:53 rfcomm12
crw-rw---- 1 root dialout 216,  11 2008-05-12 17:53 rfcomm11
crw-rw---- 1 root dialout 216,  10 2008-05-12 17:53 rfcomm10
crw-rw---- 1 root dialout 216,   1 2008-05-12 17:53 rfcomm1
crw-rw---- 1 root dialout 216,   0 2008-05-12 17:53 rfcomm0
crw-rw---- 1 root dialout 217,   3 2008-05-12 17:53 ccub3
crw-rw---- 1 root dialout 217,   2 2008-05-12 17:53 ccub2
crw-rw---- 1 root dialout 217,   1 2008-05-12 17:53 ccub1
crw-rw---- 1 root dialout 217,   0 2008-05-12 17:53 ccub0

This is what I get when I do an strace on "hcitool scan":

execve("/usr/bin/hcitool", ["hcitool", "scan"], [/* 40 vars */]) = 0 uname({sys="Linux", node="xxxxx", ...}) = 0
brk(0) = 0x8052000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7fb3000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=79173, ...}) = 0 mmap2(NULL, 79173, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7f9f000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/usr/lib/libbluetooth.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360=\0"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=70360, ...}) = 0 mmap2(NULL, 69280, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) = 0xb7f8e000
mmap2(0xb7f9e000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x10) = 0xb7f9e000
close(3) = 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
open("/lib/tls/libc.so.6", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240O\1"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=1245488, ...}) = 0 mmap2(NULL, 1251484, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0xb7e5c000
mmap2(0xb7f84000, 28672, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x128) = 0xb7f84000 mmap2(0xb7f8b000, 10396, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xb7f8b000
close(3) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7e5b000
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xb7e5a000
mprotect(0xb7f84000, 20480, PROT_READ) = 0 set_thread_area({entry_number:-1 -> 6, base_addr:0xb7e5a6c0, limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, seg_not_present:0, useable:1}) = 0

munmap(0xb7f9f000, 79173)               = 0
socket(PF_BLUETOOTH, SOCK_RAW, 1)       = 3
brk(0)                                  = 0x8052000
brk(0x8073000)                          = 0x8073000
ioctl(3, 0x800448d2, 0x8052008)         = 0
close(3)                                = 0
dup(2)                                  = 3
fcntl64(3, F_GETFL)                     = 0x8001 (flags 

O_WRONLY|O_LARGEFILE)
close(3) = 0
write(2, "Device is not available: No such"..., 40Device is not
available: No such device
) = 40
exit_group(1) = ?
Process 2626 detached ------------------end----------------

With the bluetooth dongle plugged in, I see this in the output of dmesg:

Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP ver 2.9
Bluetooth: L2CAP socket layer initialized
Bluetooth: RFCOMM socket layer initialized
Bluetooth: RFCOMM TTY layer initialized
Bluetooth: RFCOMM ver 1.8
Bluetooth: BNEP (Ethernet Emulation) ver 1.2
Bluetooth: BNEP filters: protocol multicast ------------------end----------------

And here is the output of lsusb:

Bus 005 Device 001: ID 0000:0000
Bus 004 Device 009: ID 0a5c:4503 Broadcom Corp.
Bus 004 Device 008: ID 0a5c:4502 Broadcom Corp.
Bus 004 Device 007: ID 0a5c:2111 Broadcom Corp.
Bus 004 Device 006: ID 0a5c:4500 Broadcom Corp.
Bus 004 Device 001: ID 0000:0000
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000

Also, "hciconfig dev" returns "Can't get device info: No such device"

I know I'm close; please help me get bluetooth working on my system. I'll be so grateful.

This is my system:

Debian 4.0 (Etch)
Linux kernel 2.6.24.6 (i686)
bluez-firmware 1.2-1
bluez-gnome 0.6-1
bluez-hcidump 1.32-1
bluez-utils 3.7-1

I've disabled udev on my system; however, enabling it doesn't seem to make any difference. I don't know what, if anything, I should do with bluez-firmware.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Mumia,

check with hciconfig -a and make sure that either the hci_usb or btusb driver is loaded.

Regards

Marcel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Thanks Marcel; "hciconfig -a" returns nothing:

$ hciconfig -a
$

After I manually load hci_usb, "hciconfig -a" returns this:

$ hciconfig -a
hci0:   Type: 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:0 acl:0 sco:0 commands:0 errors:0

However, I don't have the btusb module, and I can't see any way to build it from "make menuconfig." When I configured my kernel before, I enabled /everything/ related to bluetooth. :-?

Hmm, "hcitool" still doesn't see my bluetooth dongle:

$ hcitool scan
Device is not available: No such device

:-?

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Hi Mumia,

hciconfig hci0 up :)

Regards

Marcel

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Thanks very much Marcel. That gets me much closer, but when I start dund like so:

hcid
sdpd
dund --nodetach --listen --persist --msdun call palm

and when I tell my Palm E2 to search for a bluetooth network connection, nothing appears on my computer screen, and the Palm doesn't find anything to connect to.

"Hcitool scan" can find my Palm, but my Palm cannot find my computer's bluetooth adapter.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Thanks Marcel, but the network connection still doesn't work.

I do this:
hcid
sdpd
dund --nodetach --listen --persist --msdun call palm

And then I tell my Palm E2's bluetooth system to search for a network connection, but the E2 never finds anything, and "dund" never displays anything other than "dund[3984]: Bluetooth DUN daemon version 3.7."

How do I get dund communicating with my PDA?

Here is a listing of my /etc/bluetooth directory:
total 12
-rw-r--r-- 1 root root 1272 2008-05-17 07:18 hcid.conf
-rw-r--r-- 1 root root 5 2008-05-17 20:44 pin
-rw-r--r-- 1 root root 396 2008-05-17 07:49 rfcomm.conf

I've attached my hcid.conf, pin, and rfcomm.conf. Please help me get my adapter working.

P.S.
I've been looking at this document: http://howto.pilot-link.org/bluesync/ga.html . I follow the procedures, but I never get any messages from dund like those in the document.

#
# HCI daemon configuration file.
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
# security user;
security auto;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# Default PIN code for incoming connections passkey "1234";
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
# name "%h-%d";
name "mybluetooth";

# Local device class
class 0x3e0100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}

1234

#
# RFCOMM configuration file.
#

#rfcomm0 {
# # Automatically bind the device at startup
# bind no;
#
# # Bluetooth address of the device
# device 11:22:33:44:55:66;
#
# # RFCOMM channel for the connection
# channel 1;
#
# # Description of the connection
# comment "Example Bluetooth device";
#}

rfcomm0 {
	bind yes;
	device **:**:**:**:**:**;
	channel 1;
	comment "My Bluetooth device";
}

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Thanks Marcel, but the network connection still doesn't work.

I do this:
hcid
sdpd
dund --nodetach --listen --persist --msdun call palm

And then I tell my Palm E2's bluetooth system to search for a network connection, but the E2 never finds anything, and "dund" never displays anything other than "dund[3984]: Bluetooth DUN daemon version 3.7."

How do I get dund communicating with my PDA?

Here is a listing of my /etc/bluetooth directory:
total 12
-rw-r--r-- 1 root root 1272 2008-05-17 07:18 hcid.conf
-rw-r--r-- 1 root root 5 2008-05-17 20:44 pin
-rw-r--r-- 1 root root 396 2008-05-17 07:49 rfcomm.conf

I've included below my hcid.conf, pin, and rfcomm.conf. Please help me get my adapter working.

P.S.
I've been looking at this document:
http://howto.pilot-link.org/bluesync/ga.html . I follow the procedures, but I never get any messages from dund like those in the document.

Below are the files in my /etc/bluetooth directory:

----------hcid.conf------------
#
# HCI daemon configuration file.
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
# security user;
security auto;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# Default PIN code for incoming connections passkey "1234";
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
# name "%h-%d";
name "mybluetooth";

# Local device class
class 0x3e0100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}

-------------pin------------
1234

------------rfccomm.conf-----------
#
# RFCOMM configuration file.
#

#rfcomm0 {
# # Automatically bind the device at startup
# bind no;
#
# # Bluetooth address of the device
# device 11:22:33:44:55:66;
#
# # RFCOMM channel for the connection
# channel 1;
#
# # Description of the connection
# comment "Example Bluetooth device";
#}

rfcomm0 {
	bind yes;
	device **:**:**:**:**:**;
	channel 1;
	comment "My Bluetooth device";
}

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users