Given the output you have, it's not a hciattach or hciusb problem. Those
pieces are the connection from linux to the Bluetooth hardware on your
computer -- which seems to be working ok because you can do basic
operations (like hcitool scan). There is something really strange going
on because basic connectivity with the other device seems to work (as
indicated by hcitool scan, which fetches the name from the remote
device), but hcitool info and l2ping don't seem to be working properly,
which is strange. =20
Unfortunately, I don't know more than that to be able to help you. But,
I think it indicates the problem might be on the remote (phone) side,
not the laptop. Ideally, you could find a different BT device to try it
with.
Trevor
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Gary
Martin
Sent: Saturday, March 27, 2004 3:25 AM
To: [email protected]
Subject: [Bluez-users] Desperate newbie
Hi all
I'm a Linux user trying to sync my mobile phone with
my computer in desperate need of help. I'm running
Debian testing/unstable on a Apple PowerBook G3. I
have researched as much as I can, but I can't get
bluetooth to work with Linux.
My phone (Sonyericsson T628) can pair with the
PowerBook, but it says that the only service available
is "object push" and I can send files to the
PowerBook.
Multisync cannot find the phone.
Everything works perfectly in Mac OS X without any
configuration
I'm beginning to suspect it is a hci_usb -- hciattach
problem. But I don't understand hciattach.
Below are some diagnostics/output. Hopefully someone
can help
Debian:~# modinfo bfusb
filename: =20
/lib/modules/2.4.25-powerpc/kernel/drivers/bluetooth/bfusb.o
description: "BlueFRITZ! USB driver ver 1.1"
author: "Marcel Holtmann <[email protected]>"
license: "GPL"
debian:~# lsmod
Module Size Used by Not tainted
rfcomm 35640 1 (autoclean)
l2cap 18900 2 (autoclean) [rfcomm]
af_packet 15112 1 (autoclean)
hid 23108 0 (unused)
sco 10308 0 (unused)
hfs 81196 0 (unused)
dmasound_pmac 65424 1
dmasound_core 12848 1 [dmasound_pmac]
soundcore 4200 3 [dmasound_core]
i2c-core 14532 0 [dmasound_pmac]
hci_usb 9152 1
bluez 36332 3 [rfcomm l2cap sco
hci_usb]
debian:~# hcitool scan
Scanning ...
00:0E:07:54:32:0B T628
debian:~# hcitool info 00:0E:07:54:32:0B
Requesting information ...
Can't create connection: Input/output error
debian:~# hcitool inq
Inquiring ...
00:0E:07:54:32:0B clock offset: 0x747b =20
class: 0x520204
debian:~# hciconfig -a
hci0: Type: USB
BD Address: 00:0D:88:AC:D1:EE ACL MTU: 192:8=20
SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:388 acl:0 sco:0 events:18 errors:0
TX bytes:333 acl:0 sco:0 commands:15 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00
0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2
HV3
Link policy: HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'debian-0'
Class: 0x000100
Service Classes: Unspecified
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1
(0x1) LMP Subver: 0x1bb
Manufacturer: Cambridge Silicon Radio (10)
debian:~# l2ping 00:0E:07:54:32:0B
Ping: 00:0E:07:54:32:0B from 00:0D:88:AC:D1:EE (data
size 20) ...
0 bytes from 00:0E:07:54:32:0B id 200 time 56.94ms
0 bytes from 00:0E:07:54:32:0B id 201 time 32.72ms
0 bytes from 00:0E:07:54:32:0B id 202 time 44.73ms
0 bytes from 00:0E:07:54:32:0B id 203 time 38.74ms
0 bytes from 00:0E:07:54:32:0B id 204 time 38.74ms
0 bytes from 00:0E:07:54:32:0B id 205 time 48.77ms
0 bytes from 00:0E:07:54:32:0B id 206 time 41.79ms
0 bytes from 00:0E:07:54:32:0B id 207 time 42.79ms
0 bytes from 00:0E:07:54:32:0B id 208 time 39.81ms
0 bytes from 00:0E:07:54:32:0B id 209 time 44.83ms
0 bytes from 00:0E:07:54:32:0B id 210 time 42.83ms
0 bytes from 00:0E:07:54:32:0B id 211 time 41.84ms
0 bytes from 00:0E:07:54:32:0B id 212 time 39.85ms
13 sent, 13 received, 0% loss
debian:~# lsusb
Bus 002 Device 001: ID 0000:0000
Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon
Radio, Ltd Bluetooth Dongle
Bus 001 Device 001: ID 0000:0000
Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Thank you Andreas for replying to my problem. Unfortunately,
changing the class settings has not helped. I don't know how to
find the numerical equivalents of "Computer" or "Mobile phone"
If anything, my phone (T628-630) is closer to the T610 than the
T68i. Maybe too new for Bluez?
Still trying ...!
Gary
--- Andreas Deresch <[email protected]> wrote: > On Sun, 28 Mar
2004, [iso-8859-1] Gary Martin wrote:
>
> > Thanks for the suggestion Michal. I changed the class from
> 0x100; to 0x10c; in the file
> > hcid.conf, but nothing has changed. I'm glad it is not only me
> that is mystified.
> Try 0x120104 ("Laptop"). This has worked with my T28 and T68i.
> (Other possible settings are "Computer" and "Mobile Phone", the
> numerical
> values of which I don't have at hand.)
>
> ad
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and
> CEO of
> GenToo technologies. Learn everything from fundamentals to
> system
>
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
On Sun, 28 Mar 2004, [iso-8859-1] Gary Martin wrote:
> Thanks for the suggestion Michal. I changed the class from 0x100; to 0x10c; in the file
> hcid.conf, but nothing has changed. I'm glad it is not only me that is mystified.
Try 0x120104 ("Laptop"). This has worked with my T28 and T68i.
(Other possible settings are "Computer" and "Mobile Phone", the numerical
values of which I don't have at hand.)
ad
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Thanks for the suggestion Michal. I changed the class from 0x100; to 0x10c; in the file
hcid.conf, but nothing has changed. I'm glad it is not only me that is mystified.
Gary
--- "Michal Semler (volny.cz)" <[email protected]> wrote: > Hi,
>
> try change your service class to:
>
> class 0x10c;
>
> Michal
>
Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,=20
try change your service class to:
class 0x10c;
Michal
Dne ne 28. b=F8ezna 2004 01:46 Gary Martin napsal(a):
> Thanks Trevor for your assistance. I have been looking at the phone side =
of
> the problem. Now, after pairing, the phone says that there are no services
> available (before I had "object push" and I could send files to Linux).
> Below is the output from: 1) pairing the phone and 2) refreshing the
> supported services list on the phone.
>
> Does this make sense to anyone?
>
> The phone and connection works perfectly under Mac OS X??
>
> > HCI Event: Connect Request(0x04) plen 10
>
> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7
>
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: PIN Code Request(0x16) plen 6
>
> < HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23
>
> > HCI Event: Command Complete(0x0e) plen 10
> > HCI Event: Link Key Notification(0x18) plen 23
> > HCI Event: Connect Complete(0x03) plen 11
>
> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
>
> > HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
> > HCI Event: Command Complete(0x0e) plen 6
>
> < HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
>
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Connection Packet Type Changed(0x1d) plen 5
> > HCI Event: Disconn Complete(0x05) plen 4
> > HCI Event: Connect Request(0x04) plen 10
>
> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7
>
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Connect Complete(0x03) plen 11
> > HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
>
> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
>
> > HCI Event: Command Complete(0x0e) plen 6
>
> < HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
>
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Connection Packet Type Changed(0x1d) plen 5
> > ACL data: handle 0x002a flags 0x02 dlen 12
>
> L2CAP(s): Connect req: psm 1 scid 0x0040
> < ACL data: handle 0x002a flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x002a flags 0x02 dlen 16
>
> L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
> MTU 251
> < ACL data: handle 0x002a flags 0x02 dlen 14
> L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> < ACL data: handle 0x002a flags 0x02 dlen 12
> L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x002a flags 0x02 dlen 14
>
> L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
>
> > ACL data: handle 0x002a flags 0x02 dlen 12
>
> L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
> < ACL data: handle 0x002a flags 0x02 dlen 12
> L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > HCI Event: Disconn Complete(0x05) plen 4
> > HCI Event: Connect Request(0x04) plen 10
>
> < HCI Command: Accept Connection Request(0x01|0x0009) plen 7
>
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Connect Complete(0x03) plen 11
> > HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
>
> < HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
>
> > HCI Event: Command Complete(0x0e) plen 6
>
> < HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
>
> > HCI Event: Command Status(0x0f) plen 4
> > HCI Event: Connection Packet Type Changed(0x1d) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 12
>
> L2CAP(s): Connect req: psm 1 scid 0x0041
> < ACL data: handle 0x0029 flags 0x02 dlen 16
> L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0041 result 0 status 0
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 16
>
> L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
> MTU 251
> < ACL data: handle 0x0029 flags 0x02 dlen 14
> L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0
> < ACL data: handle 0x0029 flags 0x02 dlen 12
> L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 0
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 14
>
> L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
>
> > ACL data: handle 0x0029 flags 0x02 dlen 17
> > ACL data: handle 0x0029 flags 0x01 dlen 17
>
> L2CAP(d): cid 0x40 len 30 [psm 1]
> SDP SSA Req: tid 0x0 len 0x19
> pat uuid-16 0x1108 (Headset)
> max 0xffff
> aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
> (BTProfileDescList) 0x0100 (SrvName) 0x0302 ((null))
> cont 00
> < ACL data: handle 0x0029 flags 0x02 dlen 14
> L2CAP(d): cid 0x41 len 10 [psm 1]
> SDP SSA Rsp: tid 0x0 len 0x5
> cnt 0x2
> len 0x2 frm->len 0x1 n 0x0
> cont 00
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 17
> > ACL data: handle 0x0029 flags 0x01 dlen 17
>
> L2CAP(d): cid 0x40 len 30 [psm 1]
> SDP SSA Req: tid 0x0 len 0x19
> pat uuid-16 0x111e
> max 0xffff
> aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
> (BTProfileDescList) 0x0100 (SrvName) 0x0311 ((null))
> cont 00
> < ACL data: handle 0x0029 flags 0x02 dlen 14
> L2CAP(d): cid 0x41 len 10 [psm 1]
> SDP SSA Rsp: tid 0x0 len 0x5
> cnt 0x2
> len 0x2 frm->len 0x1 n 0x0
> cont 00
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 17
> > ACL data: handle 0x0029 flags 0x01 dlen 14
>
> L2CAP(d): cid 0x40 len 27 [psm 1]
> SDP SSA Req: tid 0x0 len 0x16
> pat uuid-16 0x1107 (IRMCSyncCmd)
> max 0xffff
> aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
> (BTProfileDescList) 0x0100 (SrvName)
> cont 00
> < ACL data: handle 0x0029 flags 0x02 dlen 14
> L2CAP(d): cid 0x41 len 10 [psm 1]
> SDP SSA Rsp: tid 0x0 len 0x5
> cnt 0x2
> len 0x2 frm->len 0x1 n 0x0
> cont 00
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 17
> > ACL data: handle 0x0029 flags 0x01 dlen 17
>
> L2CAP(d): cid 0x40 len 30 [psm 1]
> SDP SSA Req: tid 0x0 len 0x19
> pat uuid-16 0x1105 (OBEXObjPush)
> max 0xffff
> aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
> (BTProfileDescList) 0x0100 (SrvName) 0x0303 ((null))
> cont 00
> < ACL data: handle 0x0029 flags 0x02 dlen 14
> L2CAP(d): cid 0x41 len 10 [psm 1]
> SDP SSA Rsp: tid 0x0 len 0x5
> cnt 0x2
> len 0x2 frm->len 0x1 n 0x0
> cont 00
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 17
> > ACL data: handle 0x0029 flags 0x01 dlen 14
>
> L2CAP(d): cid 0x40 len 27 [psm 1]
> SDP SSA Req: tid 0x0 len 0x16
> pat uuid-16 0x1106 (OBEXObjTrnsf)
> max 0xffff
> aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
> (BTProfileDescList) 0x0100 (SrvName)
> cont 00
> < ACL data: handle 0x0029 flags 0x02 dlen 14
> L2CAP(d): cid 0x41 len 10 [psm 1]
> SDP SSA Rsp: tid 0x0 len 0x5
> cnt 0x2
> len 0x2 frm->len 0x1 n 0x0
> cont 00
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > ACL data: handle 0x0029 flags 0x02 dlen 12
>
> L2CAP(s): Disconn req: dcid 0x0040 scid 0x0041
> < ACL data: handle 0x0029 flags 0x02 dlen 12
> L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0041
>
> > HCI Event: Number of Completed Packets(0x13) plen 5
> > HCI Event: Disconn Complete(0x05) plen 4
>
> --- "Pering, Trevor" <[email protected]> wrote: > Given the output
> you have, it's not a hciattach or hciusb problem. Those
>
> > pieces are the connection from linux to the Bluetooth hardware on your
> > computer -- which seems to be working ok because you can do basic
> > operations (like hcitool scan). There is something really strange going
> > on because basic connectivity with the other device seems to work (as
> > indicated by hcitool scan, which fetches the name from the remote
> > device), but hcitool info and l2ping don't seem to be working properly,
> > which is strange.
> >
> > Unfortunately, I don't know more than that to be able to help you. But,
> > I think it indicates the problem might be on the remote (phone) side,
> > not the laptop. Ideally, you could find a different BT device to try it
> > with.
> >
> > Trevor
> >
> >
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Gary
> > Martin
> > Sent: Saturday, March 27, 2004 3:25 AM
> > To: [email protected]
> > Subject: [Bluez-users] Desperate newbie
> >
> > Hi all
> >
> > I'm a Linux user trying to sync my mobile phone with
> > my computer in desperate need of help. I'm running
> > Debian testing/unstable on a Apple PowerBook G3. I
> > have researched as much as I can, but I can't get
> > bluetooth to work with Linux.
> >
> > My phone (Sonyericsson T628) can pair with the
> > PowerBook, but it says that the only service available
> > is "object push" and I can send files to the
> > PowerBook.
> >
> > Multisync cannot find the phone.
> >
> > Everything works perfectly in Mac OS X without any
> > configuration
> >
> > I'm beginning to suspect it is a hci_usb -- hciattach
> > problem. But I don't understand hciattach.
> >
> > Below are some diagnostics/output. Hopefully someone
> > can help
> >
> >
> > Debian:~# modinfo bfusb
> > filename:
> > /lib/modules/2.4.25-powerpc/kernel/drivers/bluetooth/bfusb.o
> > description: "BlueFRITZ! USB driver ver 1.1"
> > author: "Marcel Holtmann <[email protected]>"
> > license: "GPL"
> >
> > debian:~# lsmod
> > Module Size Used by Not tainted
> > rfcomm 35640 1 (autoclean)
> > l2cap 18900 2 (autoclean) [rfcomm]
> > af_packet 15112 1 (autoclean)
> > hid 23108 0 (unused)
> > sco 10308 0 (unused)
> > hfs 81196 0 (unused)
> > dmasound_pmac 65424 1
> > dmasound_core 12848 1 [dmasound_pmac]
> > soundcore 4200 3 [dmasound_core]
> > i2c-core 14532 0 [dmasound_pmac]
> > hci_usb 9152 1
> > bluez 36332 3 [rfcomm l2cap sco
> > hci_usb]
> >
> > debian:~# hcitool scan
> > Scanning ...
> > 00:0E:07:54:32:0B T628
> >
> > debian:~# hcitool info 00:0E:07:54:32:0B
> > Requesting information ...
> > Can't create connection: Input/output error
> >
> > debian:~# hcitool inq
> > Inquiring ...
> > 00:0E:07:54:32:0B clock offset: 0x747b
> > class: 0x520204
> >
> > debian:~# hciconfig -a
> > hci0: Type: USB
> > BD Address: 00:0D:88:AC:D1:EE ACL MTU: 192:8
> > SCO MTU: 64:8
> > UP RUNNING PSCAN ISCAN
> > RX bytes:388 acl:0 sco:0 events:18 errors:0
> > TX bytes:333 acl:0 sco:0 commands:15 errors:0
> > Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00
> > 0x00
> > Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2
> > HV3
> > Link policy: HOLD SNIFF PARK
> > Link mode: SLAVE ACCEPT
> > Name: 'debian-0'
> > Class: 0x000100
> > Service Classes: Unspecified
> > Device Class: Computer, Uncategorized
> > HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1
> > (0x1) LMP Subver: 0x1bb
> > Manufacturer: Cambridge Silicon Radio (10)
> >
> > debian:~# l2ping 00:0E:07:54:32:0B
> > Ping: 00:0E:07:54:32:0B from 00:0D:88:AC:D1:EE (data
> > size 20) ...
> > 0 bytes from 00:0E:07:54:32:0B id 200 time 56.94ms
> > 0 bytes from 00:0E:07:54:32:0B id 201 time 32.72ms
> > 0 bytes from 00:0E:07:54:32:0B id 202 time 44.73ms
> > 0 bytes from 00:0E:07:54:32:0B id 203 time 38.74ms
> > 0 bytes from 00:0E:07:54:32:0B id 204 time 38.74ms
> > 0 bytes from 00:0E:07:54:32:0B id 205 time 48.77ms
> > 0 bytes from 00:0E:07:54:32:0B id 206 time 41.79ms
> > 0 bytes from 00:0E:07:54:32:0B id 207 time 42.79ms
> > 0 bytes from 00:0E:07:54:32:0B id 208 time 39.81ms
> > 0 bytes from 00:0E:07:54:32:0B id 209 time 44.83ms
> > 0 bytes from 00:0E:07:54:32:0B id 210 time 42.83ms
> > 0 bytes from 00:0E:07:54:32:0B id 211 time 41.84ms
> > 0 bytes from 00:0E:07:54:32:0B id 212 time 39.85ms
> > 13 sent, 13 received, 0% loss
> >
> > debian:~# lsusb
> > Bus 002 Device 001: ID 0000:0000
> > Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon
> > Radio, Ltd Bluetooth Dongle
> > Bus 001 Device 001: ID 0000:0000
>
> Find local movie times and trailers on Yahoo! Movies.
> http://au.movies.yahoo.com
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=3D1470&alloc_id=3D3638&op=3Dcli=
ck
> _______________________________________________
> Bluez-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Thanks Trevor for your assistance. I have been looking at the phone side of the
problem. Now, after pairing, the phone says that there are no services available
(before I had "object push" and I could send files to Linux). Below is the output
from: 1) pairing the phone and 2) refreshing the supported services list on the phone.
Does this make sense to anyone?
The phone and connection works perfectly under Mac OS X??
> HCI Event: Connect Request(0x04) plen 10
< HCI Command: Accept Connection Request(0x01|0x0009) plen 7
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: PIN Code Request(0x16) plen 6
< HCI Command: PIN Code Request Reply(0x01|0x000d) plen 23
> HCI Event: Command Complete(0x0e) plen 10
> HCI Event: Link Key Notification(0x18) plen 23
> HCI Event: Connect Complete(0x03) plen 11
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
> HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
> HCI Event: Command Complete(0x0e) plen 6
< HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: Connection Packet Type Changed(0x1d) plen 5
> HCI Event: Disconn Complete(0x05) plen 4
> HCI Event: Connect Request(0x04) plen 10
< HCI Command: Accept Connection Request(0x01|0x0009) plen 7
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: Connect Complete(0x03) plen 11
> HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
> HCI Event: Command Complete(0x0e) plen 6
< HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: Connection Packet Type Changed(0x1d) plen 5
> ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0040
< ACL data: handle 0x002a flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0040 result 0 status 0
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x002a flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 251
< ACL data: handle 0x002a flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
< ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 0
> HCI Event: Number of Completed Packets(0x13) plen 5
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x002a flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0040
< ACL data: handle 0x002a flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0040
> HCI Event: Number of Completed Packets(0x13) plen 5
> HCI Event: Disconn Complete(0x05) plen 4
> HCI Event: Connect Request(0x04) plen 10
< HCI Command: Accept Connection Request(0x01|0x0009) plen 7
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: Connect Complete(0x03) plen 11
> HCI Event: Page Scan Repetition Mode Change(0x20) plen 7
< HCI Command: Write Link Policy Settings(0x02|0x000d) plen 4
> HCI Event: Command Complete(0x0e) plen 6
< HCI Command: Change Connection Packet Type(0x01|0x000f) plen 4
> HCI Event: Command Status(0x0f) plen 4
> HCI Event: Connection Packet Type Changed(0x1d) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Connect req: psm 1 scid 0x0041
< ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Connect rsp: dcid 0x0040 scid 0x0041 result 0 status 0
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 16
L2CAP(s): Config req: dcid 0x0040 flags 0x0000 clen 4
MTU 251
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0041 flags 0x0000 result 0 clen 0
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Config req: dcid 0x0041 flags 0x0000 clen 0
> HCI Event: Number of Completed Packets(0x13) plen 5
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(s): Config rsp: scid 0x0040 flags 0x0000 result 0 clen 0
> ACL data: handle 0x0029 flags 0x02 dlen 17
> ACL data: handle 0x0029 flags 0x01 dlen 17
L2CAP(d): cid 0x40 len 30 [psm 1]
SDP SSA Req: tid 0x0 len 0x19
pat uuid-16 0x1108 (Headset)
max 0xffff
aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
(BTProfileDescList) 0x0100 (SrvName) 0x0302 ((null))
cont 00
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x41 len 10 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x5
cnt 0x2
len 0x2 frm->len 0x1 n 0x0
cont 00
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 17
> ACL data: handle 0x0029 flags 0x01 dlen 17
L2CAP(d): cid 0x40 len 30 [psm 1]
SDP SSA Req: tid 0x0 len 0x19
pat uuid-16 0x111e
max 0xffff
aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
(BTProfileDescList) 0x0100 (SrvName) 0x0311 ((null))
cont 00
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x41 len 10 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x5
cnt 0x2
len 0x2 frm->len 0x1 n 0x0
cont 00
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 17
> ACL data: handle 0x0029 flags 0x01 dlen 14
L2CAP(d): cid 0x40 len 27 [psm 1]
SDP SSA Req: tid 0x0 len 0x16
pat uuid-16 0x1107 (IRMCSyncCmd)
max 0xffff
aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
(BTProfileDescList) 0x0100 (SrvName)
cont 00
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x41 len 10 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x5
cnt 0x2
len 0x2 frm->len 0x1 n 0x0
cont 00
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 17
> ACL data: handle 0x0029 flags 0x01 dlen 17
L2CAP(d): cid 0x40 len 30 [psm 1]
SDP SSA Req: tid 0x0 len 0x19
pat uuid-16 0x1105 (OBEXObjPush)
max 0xffff
aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
(BTProfileDescList) 0x0100 (SrvName) 0x0303 ((null))
cont 00
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x41 len 10 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x5
cnt 0x2
len 0x2 frm->len 0x1 n 0x0
cont 00
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 17
> ACL data: handle 0x0029 flags 0x01 dlen 14
L2CAP(d): cid 0x40 len 27 [psm 1]
SDP SSA Req: tid 0x0 len 0x16
pat uuid-16 0x1106 (OBEXObjTrnsf)
max 0xffff
aid(s) 0x0001 (SrvClassIDList) 0x0004 (ProtocolDescList) 0x0009
(BTProfileDescList) 0x0100 (SrvName)
cont 00
< ACL data: handle 0x0029 flags 0x02 dlen 14
L2CAP(d): cid 0x41 len 10 [psm 1]
SDP SSA Rsp: tid 0x0 len 0x5
cnt 0x2
len 0x2 frm->len 0x1 n 0x0
cont 00
> HCI Event: Number of Completed Packets(0x13) plen 5
> ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn req: dcid 0x0040 scid 0x0041
< ACL data: handle 0x0029 flags 0x02 dlen 12
L2CAP(s): Disconn rsp: dcid 0x0040 scid 0x0041
> HCI Event: Number of Completed Packets(0x13) plen 5
> HCI Event: Disconn Complete(0x05) plen 4
--- "Pering, Trevor" <[email protected]> wrote: > Given the output you have, it's
not a hciattach or hciusb problem. Those
> pieces are the connection from linux to the Bluetooth hardware on your
> computer -- which seems to be working ok because you can do basic
> operations (like hcitool scan). There is something really strange going
> on because basic connectivity with the other device seems to work (as
> indicated by hcitool scan, which fetches the name from the remote
> device), but hcitool info and l2ping don't seem to be working properly,
> which is strange.
>
> Unfortunately, I don't know more than that to be able to help you. But,
> I think it indicates the problem might be on the remote (phone) side,
> not the laptop. Ideally, you could find a different BT device to try it
> with.
>
> Trevor
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Gary
> Martin
> Sent: Saturday, March 27, 2004 3:25 AM
> To: [email protected]
> Subject: [Bluez-users] Desperate newbie
>
> Hi all
>
> I'm a Linux user trying to sync my mobile phone with
> my computer in desperate need of help. I'm running
> Debian testing/unstable on a Apple PowerBook G3. I
> have researched as much as I can, but I can't get
> bluetooth to work with Linux.
>
> My phone (Sonyericsson T628) can pair with the
> PowerBook, but it says that the only service available
> is "object push" and I can send files to the
> PowerBook.
>
> Multisync cannot find the phone.
>
> Everything works perfectly in Mac OS X without any
> configuration
>
> I'm beginning to suspect it is a hci_usb -- hciattach
> problem. But I don't understand hciattach.
>
> Below are some diagnostics/output. Hopefully someone
> can help
>
>
> Debian:~# modinfo bfusb
> filename:
> /lib/modules/2.4.25-powerpc/kernel/drivers/bluetooth/bfusb.o
> description: "BlueFRITZ! USB driver ver 1.1"
> author: "Marcel Holtmann <[email protected]>"
> license: "GPL"
>
> debian:~# lsmod
> Module Size Used by Not tainted
> rfcomm 35640 1 (autoclean)
> l2cap 18900 2 (autoclean) [rfcomm]
> af_packet 15112 1 (autoclean)
> hid 23108 0 (unused)
> sco 10308 0 (unused)
> hfs 81196 0 (unused)
> dmasound_pmac 65424 1
> dmasound_core 12848 1 [dmasound_pmac]
> soundcore 4200 3 [dmasound_core]
> i2c-core 14532 0 [dmasound_pmac]
> hci_usb 9152 1
> bluez 36332 3 [rfcomm l2cap sco
> hci_usb]
>
> debian:~# hcitool scan
> Scanning ...
> 00:0E:07:54:32:0B T628
>
> debian:~# hcitool info 00:0E:07:54:32:0B
> Requesting information ...
> Can't create connection: Input/output error
>
> debian:~# hcitool inq
> Inquiring ...
> 00:0E:07:54:32:0B clock offset: 0x747b
> class: 0x520204
>
> debian:~# hciconfig -a
> hci0: Type: USB
> BD Address: 00:0D:88:AC:D1:EE ACL MTU: 192:8
> SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:388 acl:0 sco:0 events:18 errors:0
> TX bytes:333 acl:0 sco:0 commands:15 errors:0
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00
> 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2
> HV3
> Link policy: HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'debian-0'
> Class: 0x000100
> Service Classes: Unspecified
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x1bb LMP Ver: 1.1
> (0x1) LMP Subver: 0x1bb
> Manufacturer: Cambridge Silicon Radio (10)
>
> debian:~# l2ping 00:0E:07:54:32:0B
> Ping: 00:0E:07:54:32:0B from 00:0D:88:AC:D1:EE (data
> size 20) ...
> 0 bytes from 00:0E:07:54:32:0B id 200 time 56.94ms
> 0 bytes from 00:0E:07:54:32:0B id 201 time 32.72ms
> 0 bytes from 00:0E:07:54:32:0B id 202 time 44.73ms
> 0 bytes from 00:0E:07:54:32:0B id 203 time 38.74ms
> 0 bytes from 00:0E:07:54:32:0B id 204 time 38.74ms
> 0 bytes from 00:0E:07:54:32:0B id 205 time 48.77ms
> 0 bytes from 00:0E:07:54:32:0B id 206 time 41.79ms
> 0 bytes from 00:0E:07:54:32:0B id 207 time 42.79ms
> 0 bytes from 00:0E:07:54:32:0B id 208 time 39.81ms
> 0 bytes from 00:0E:07:54:32:0B id 209 time 44.83ms
> 0 bytes from 00:0E:07:54:32:0B id 210 time 42.83ms
> 0 bytes from 00:0E:07:54:32:0B id 211 time 41.84ms
> 0 bytes from 00:0E:07:54:32:0B id 212 time 39.85ms
> 13 sent, 13 received, 0% loss
>
> debian:~# lsusb
> Bus 002 Device 001: ID 0000:0000
> Bus 002 Device 002: ID 0a12:0001 Cambridge Silicon
> Radio, Ltd Bluetooth Dongle
> Bus 001 Device 001: ID 0000:0000
>
>
Find local movie times and trailers on Yahoo! Movies.
http://au.movies.yahoo.com
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users