[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bluetooth Device Failing to Initialize
Max,
I have included the requested output below,
On Wed, 2006-01-11 at 16:39 -0800, Maksim Yevmenkin wrote:
> Hello,
>
> > I am have a problem with a linksys usbbt100 bluetooth
> > dongle.
>
> lets see...
>
> > I am running
> >
> > 6.0-RELEASE FreeBSD 6.0-RELEASE #0: Sat Jan 7 08:48:40 CST
> > 2006
>
> ok
>
> >>From dmesg I get this
> >
> > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
> > ubt0: vendor 0x0a12 product 0x0001, rev 1.10/5.25, addr 2
> > ubt0: Interface 0 endpoints: interrupt=0x81, bulk-in=0x82,
> > bulk-out=0x2
> > ubt0: Interface 1 (alt.config 5) endpoints: isoc-in=0x83,
> > isoc-out=0x3;
> > wMaxPacketSize=49; nframes=6, buffer size=294
>
> looks fine to me
>
> > I have setup the /etc/rc.bluetooth file as described in the
> > handbook, and am using the ng_ubt module that is said to be
> > the correct one.
> >
> > When i run
> >
> > /etc/rc.bluetooth start ubt0
> >
> > I get
> >
> > bash-2.05b# /etc/rc.bluetooth start ubt0
> > BD_ADDR: 00:0c:41:e2:01:84
> > Features: 0xff 0xff 0xf 00 00 00 00 00
> > <3-Slot> <5-Slot> <Encryption> <Slot offset>
> > <Timing accuracy> <Switch> <Hold mode> <Sniff mode>
> > <Park mode> <RSSI> <Channel quality> <SCO link>
> > <HV2 packets> <HV3 packets> <u-law log> <A-law log>
> > <CVSD>
> > <Paging scheme> <Power control> <Transparent SCO data>
> > Max. ACL packet size: 192 bytes
> > Number of ACL packets: 8
> > Max. SCO packet size: 64 bytes
> > Number of SCO packets: 8
>
> everything above looks fine
>
> > Could not execute command "initialize". Device not
> > configured
>
> this is *very* strange.
>
> 1) did you check your /var/log/messages to see if device has detached?
This is in the messages after I run /etc/rc.bluetooth after a fresh
reboot;
Jan 12 17:54:28 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x3, OCF=0x3. Timeout
Jan 12 17:54:28 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=4
Jan 12 17:54:28 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:28 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
Jan 12 17:54:33 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x4, OCF=0x9. Timeout
Jan 12 17:54:33 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=10
Jan 12 17:54:33 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:33 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
Jan 12 17:54:38 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x4, OCF=0x3. Timeout
Jan 12 17:54:38 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=12
Jan 12 17:54:38 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:38 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
Jan 12 17:54:43 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x4, OCF=0x5. Timeout
Jan 12 17:54:43 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=11
Jan 12 17:54:43 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:43 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
Jan 12 17:54:48 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x3, OCF=0x1a. Timeout
Jan 12 17:54:48 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=4
Jan 12 17:54:48 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:48 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
Jan 12 17:54:53 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x3, OCF=0x24. Timeout
Jan 12 17:54:53 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=4
Jan 12 17:54:53 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:53 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
Jan 12 17:54:58 bigboy kernel: ng_hci_process_command_timeout: ubt0hci -
unable to complete HCI command OGF=0x3, OCF=0x13. Timeout
Jan 12 17:54:58 bigboy kernel: ng_hci_process_event: ubt0hci - got HCI
event=0xe, length=4
Jan 12 17:54:58 bigboy kernel: complete_command: ubt0hci - no pending
command, state=0x1
Jan 12 17:54:58 bigboy kernel: ubt_request_complete2: ubt0 - Control
request failed. TIMEOUT (15)
>
> 2) can you please run as root the following commands
>
> # ngctl types
bash-2.05b# ngctl types
There are 7 total types:
Type name Number of living nodes
--------- ----------------------
socket 1
btsock_l2c 1
btsock_l2c_raw 1
btsock_hci_raw 1
l2cap 1
hci 1
ubt 1
>
> # ngctl li
bash-2.05b# ngctl li
There are 7 total nodes:
Name: ngctl704 Type: socket ID: 00000013 Num hooks: 0
Name: ubt0l2cap Type: l2cap ID: 0000000c Num hooks: 3
Name: ubt0hci Type: hci ID: 00000008 Num hooks: 3
Name: btsock_l2c Type: btsock_l2c ID: 00000004 Num hooks: 1
Name: btsock_l2c_raw Type: btsock_l2c_raw ID: 00000003 Num hooks: 1
Name: btsock_hci_raw Type: btsock_hci_raw ID: 00000002 Num hooks: 1
Name: ubt0 Type: ubt ID: 00000001 Num hooks: 1
>
> # ngctl status ubt0:
bash-2.05b# ngctl status ubt0:
Status for "ubt0:":
Hook: hook
Flags: 0x30
Debug: 3
CMD queue: [have:0,max:12]
ACL queue: [have:0,max:12]
SCO queue: [have:0,max:12]
>
> # ngctl status ubt0hci:
bash-2.05b# ngctl status ubt0hci:
Status for "ubt0hci:":
bdaddr 0:0:0:0:0:0
Hooks drv acl raw
State 0x1
Queue cmd:0
Buffer cmd:1,acl:1,1,17,sco:1,1,10
>
> after you have executed "rc.bluetooth start ubt0" and got the error.
>
> > if i run
> >
> > hccontrol -n ubt0hci initialize
> >
> > i get
> >
> > bash-2.05b# hccontrol -n ubt0hci initialize
> > Could not execute command "initialize". Device not
> > configured
>
> please run the commands above and send me the output.
>
> > I am running hcidump at the same time, which doesnt seem to
> > see the initialize command;
>
> that is fine. "initialize" is an internal (to bluetooth stack) command.
> it only flips a bit inside hci node and tells it that initialization
> sequence was performed. you wont see "initialize" command in the hci dumps.
>
> [...]
>
> > The device looks like it is ok, but something freaky is not
> > allowing it to initialize properly and subsequent inquiry
> > commands just time out. I should also point out that I have
> > had the dongle working in Windows Land.
>
> i suspect that device is gone (detached).
>
> > Would this failure to initialize be preventing me from
> > successfuly inquiring another device?
>
> yes, because if i'm right and device is indeed gone then you cant do
> anything.
>
> thanks,
> max
regards
Chriso
