Early failures with Treo 650

Bluez-users David Britton 4 participants 13 messages May 21, 2005 – Jul 30, 2005 Bluetooth drivers

Share & tools

David Britton

author

2005-05-21 07:14 UTC #0 lore raw

Hi,

Having problems even getting past the early stages with connecting my treo 650 to my Kensington. I did a search through the archives, and I can't seem to find anyone who has been stuck this early.

Symptoms:

- I can see the PC from my plam (it shows up as a "Device").
- I have put the treo into "discoverable" mode.
- I can see the BT USB Dongle using hciconfig
- I cannot get "hcitool scan" to return any devices

Output:

red:/home/dpb# hciconfig
hci0:   Type: USB
       BD Address: 00:0C:55:F8:5A:2B ACL MTU: 377:10 SCO MTU: 16:0
       UP RUNNING PSCAN ISCAN INQUIRY
       RX bytes:461 acl:0 sco:0 events:73 errors:0
       TX bytes:3271 acl:0 sco:0 commands:73 errors:0
red:/home/dpb# hcidump  -x -V &
HCI sniffer - Bluetooth packet analyzer ver 1.17
device: hci0 snap_len: 1028 filter: 0xffffffff
[1] 24217
red:/home/dpb# hcitool scan
Scanning ...
Inquiry failed: Connection timed out
red:/home/dpb#

Please let me know if I have not specified enough information here -- I just don't even know where to start. All FAQ/HOW-TO's that I read sort of assume that this part will work.

TIA.

Signature · 12 lines

David Britton


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-23 10:06 UTC #1 lore raw

Hi David,

Quoted 31 lines

Having problems even getting past the early stages with connecting my treo 650 to my Kensington. I did a search through the archives, and I can't seem to find anyone who has been stuck this early.
Symptoms:
- I can see the PC from my plam (it shows up as a "Device").
- I have put the treo into "discoverable" mode.
- I can see the BT USB Dongle using hciconfig
- I cannot get "hcitool scan" to return any devices
Output:
red:/home/dpb# hciconfig
hci0:   Type: USB
        BD Address: 00:0C:55:F8:5A:2B ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN INQUIRY
        RX bytes:461 acl:0 sco:0 events:73 errors:0
        TX bytes:3271 acl:0 sco:0 commands:73 errors:0
red:/home/dpb# hcidump  -x -V &
HCI sniffer - Bluetooth packet analyzer ver 1.17
device: hci0 snap_len: 1028 filter: 0xffffffff
[1] 24217
red:/home/dpb# hcitool scan
Scanning ...
Inquiry failed: Connection timed out
red:/home/dpb#

Quoted 3 lines

Please let me know if I have not specified enough information here -- I just don't even know where to start. All FAQ/HOW-TO's that I read sort of assume that this part will work.

show us "hciconfig -a" and run "hcidump -X -V" as root while you are scanning. Also a "hcitool info" on the Treo would be nice.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-users mailing list [email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

David Britton

author

2005-05-24 02:38 UTC #2 lore raw

Quoted 4 lines · Marcel Holtmann

show us "hciconfig -a" and run "hcidump -X -V" as root while you are scanning.

Thanks for the reply Marcel,

I have confirmed that this device does work on windows (a friends machine)... for a while I was wondering.

Now on to the infomation requested:

hcitool/hciconfig output:
-------------------------

red:/home/dpb# hcitool scan
Scanning ...
Inquiry failed: Connection timed out
red:/home/dpb#
hciconfig -a:
red:/home/dpb# hciconfig -a
hci0:   Type: USB
        BD Address: 00:0C:55:F8:5A:2B ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN INQUIRY AUTH
        RX bytes:101 acl:0 sco:0 events:13 errors:0
        TX bytes:304 acl:0 sco:0 commands:13 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: HOLD SNIFF PARK
        Link mode: ACCEPT MASTER
        Name: 'red (0)'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver:
0x6965
        Manufacturer: Broadcom Corporation (15)

red:/home/dpb#

hcidump -X -V output:
---------------------

red:/home/dpb# hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.17
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Inquiry (0x01|0x0001) plen 5
  0000: 33 8b 9e 08 64                                    3...d

Quoted 1 line

HCI Event: Command Status (0x0f) plen 4

    Inquiry (0x01|0x0001) status 0x00 ncmd 1

< HCI Command: Read Local Name (0x03|0x0014) plen 0

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 252

    Read Local Name (0x03|0x0014) ncmd 1
    status 0x00
    0000: 72 65 64 20 28 30 29 00  00 00 00 00 00 00 00 00  red (0).........
    0010: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0020: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0030: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0040: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0050: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0060: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0070: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0080: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    0090: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    00a0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    00b0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    00c0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    00d0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    00e0: 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  ................
    00f0: 00 00 00 00 00 00 00 00                           ........

< HCI Command: Read Class of Device (0x03|0x0023) plen 0

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 7

    Read Class of Device (0x03|0x0023) ncmd 1
    status 0x00
    0000: 00 01 00                                          ...

< HCI Command: Read Local Version Information (0x04|0x0001) plen 0

Quoted 1 line

HCI Event: Command Complete (0x0e) plen 12

    Read Local Version Information (0x04|0x0001) ncmd 1
    status 0x00
    0000: 02 00 00 02 0f 00 65 69                           ......ei

I ran the hcitool scan first, then the hciconfig -a, and both output through the dumper. If I try to run more hcitool scan commands, I don't get any output from those commands back in the dumper (probably still stuck on the first one?) until I unplug the device and plug it back in, etc.

Quoted 3 lines

Also a "hcitool info" on the Treo would be nice.

I think I get similar results when running the hcitool info. However, when I run the hcitool info (got the device number off the windows install), the treo screen comes on (lights up) and it plays the "bluetooth connection sound". Nothing else, but at least that happens. :)

hcitool info output:
--------------------

red:/home/dpb# hcitool info 00:07:e0:05:0a:11
Requesting information ...
Can't create connection: Connection timed out
red:/home/dpb#

hcidump from info request:
--------------------------

red:/home/dpb# hcidump -X -V
HCI sniffer - Bluetooth packet analyzer ver 1.17
device: hci0 snap_len: 1028 filter: 0xffffffff
< HCI Command: Create Connection (0x01|0x0005) plen 13
  0000: 11 0a 05 e0 07 00 18 cc  02 00 00 00 01           .............

< HCI Command: Create Connection (0x01|0x0005) plen 13
0000: 11 0a 05 e0 07 00 18 cc 02 00 00 00 01 .............

Not sure if it is helpful, but I also attached the syslog output during all these things.

I appreciate your help.

Signature · 1 line

David Britton <[email protected]>

May 23 21:29:04 localhost kernel: usb 3-2: new full speed USB device using address 30
May 23 21:29:04 localhost kernel: hub 3-2:1.0: USB hub found
May 23 21:29:04 localhost kernel: hub 3-2:1.0: 3 ports detected
May 23 21:29:05 localhost usb.agent[15650]:      usbcore: already loaded
May 23 21:29:05 localhost kernel: usb 3-2.1: new full speed USB device using address 31
May 23 21:29:05 localhost hcid[15344]: HCI dev 0 registered
May 23 21:29:05 localhost hcid[15344]: HCI dev 0 up
May 23 21:29:05 localhost hcid[15344]: Starting security manager 0
May 23 21:29:06 localhost usb.agent[15805]:      hci_usb: already loaded
May 23 21:29:06 localhost usb.agent[15823]:      hci_usb: already loaded
May 23 21:29:06 localhost usb.agent[15799]:      hci_usb: already loaded
May 23 21:29:07 localhost usb.agent[15782]:      hci_usb: already loaded
May 23 21:29:07 localhost kernel: usb 3-2.2: new full speed USB device using address 32
May 23 21:29:07 localhost hal.hotplug[15966]: DEVPATH is not set
May 23 21:29:07 localhost kernel: input: USB HID v1.11 Keyboard [0a5c:3502] on usb-0000:00:10.2-2.2
May 23 21:29:07 localhost udev[15963]: configured rule in '/etc/udev/rules.d/udev.rules[113]' applied, 'event4' becomes 'input/%k'
May 23 21:29:07 localhost udev[15963]: creating device node '/dev/input/event4'
May 23 21:29:07 localhost input.agent[15950]:      evdev: already loaded
May 23 21:29:07 localhost input.agent[15967]:      evdev: already loaded
May 23 21:29:07 localhost input.agent[15967]:      joydev: already loaded
May 23 21:29:07 localhost usb.agent[16031]:      usbhid: already loaded
May 23 21:29:07 localhost kernel: usb 3-2.3: new full speed USB device using address 33
May 23 21:29:08 localhost hal.hotplug[16120]: DEVPATH is not set
May 23 21:29:08 localhost kernel: input: USB HID v1.11 Mouse [0a5c:3503] on usb-0000:00:10.2-2.3
May 23 21:29:08 localhost udev[16109]: configured rule in '/etc/udev/rules.d/udev.rules[113]' applied, 'event5' becomes 'input/%k'
May 23 21:29:08 localhost udev[16109]: creating device node '/dev/input/event5'
May 23 21:29:08 localhost udev[16113]: configured rule in '/etc/udev/rules.d/udev.rules[111]' applied, 'mouse2' becomes 'input/%k'
May 23 21:29:08 localhost udev[16113]: creating device node '/dev/input/mouse2'
May 23 21:29:08 localhost udev[16117]: configured rule in '/etc/udev/rules.d/udev.rules[115]' applied, 'ts2' becomes 'input/%k'
May 23 21:29:08 localhost udev[16117]: creating device node '/dev/input/ts2'
May 23 21:29:08 localhost input.agent[16121]:      evdev: already loaded
May 23 21:29:08 localhost input.agent[16121]:      joydev: already loaded
May 23 21:29:08 localhost input.agent[16121]:      mousedev: already loaded
May 23 21:29:08 localhost input.agent[16121]:      tsdev: already loaded
May 23 21:29:08 localhost input.agent[16196]:      evdev: already loaded
May 23 21:29:08 localhost input.agent[16224]:      evdev: already loaded
May 23 21:29:08 localhost input.agent[16253]:      evdev: already loaded
May 23 21:29:08 localhost usb.agent[16283]:      usbhid: already loaded
May 23 21:29:12 localhost dund[15351]: Accept failed. Interrupted system call(4)
May 23 21:29:12 localhost pand[15353]: Accept failed. Interrupted system call(4)
May 23 21:29:12 localhost hcid[15344]: Exit.
May 23 21:29:12 localhost sdpd[15347]: terminating...   
May 23 21:29:12 localhost pand[15353]: Service record unregistration failed.
May 23 21:29:13 localhost hcid[16333]: Bluetooth HCI daemon
May 23 21:29:13 localhost hcid[16333]: Starting security manager 0
May 23 21:29:13 localhost sdpd[16337]: Bluetooth SDP daemon 
May 23 21:29:13 localhost dund[16339]: Bluetooth DUN daemon version 2.15
May 23 21:29:13 localhost pand[16341]: Bluetooth PAN daemon version 2.15
May 23 21:31:15 localhost kernel: hci_cmd_task: hci0 command tx timeout

Marcel Holtmann

maintainer

2005-05-24 08:48 UTC #3 lore raw

Hi David,

Quoted 35 lines

Quoted 2 lines

show us "hciconfig -a" and run "hcidump -X -V" as root while you are scanning.

I have confirmed that this device does work on windows (a friends machine)... for a while I was wondering.

Now on to the infomation requested:

hcitool/hciconfig output:
-------------------------

red:/home/dpb# hcitool scan
Scanning ...
Inquiry failed: Connection timed out
red:/home/dpb#
hciconfig -a:
red:/home/dpb# hciconfig -a
hci0:   Type: USB
        BD Address: 00:0C:55:F8:5A:2B ACL MTU: 377:10 SCO MTU: 16:0
        UP RUNNING PSCAN ISCAN INQUIRY AUTH
        RX bytes:101 acl:0 sco:0 events:13 errors:0
        TX bytes:304 acl:0 sco:0 commands:13 errors:0
        Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: HOLD SNIFF PARK
        Link mode: ACCEPT MASTER
        Name: 'red (0)'
        Class: 0x000100
        Service Classes: Unspecified
        Device Class: Computer, Uncategorized
        HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver:
0x6965
        Manufacturer: Broadcom Corporation (15)

Quoted 1 line

red:/home/dpb#

what kind of USB dongle is this? What version of kernel and what versions of bluez-* packages are installed?

Why do you set "auth" in hcid.conf? Why is "rswitch" not activated in hcid.conf?

Show us the content of /proc/bus/usb/devices.

Regards

Marcel

David Britton

author

2005-05-26 04:43 UTC #4 lore raw

Quoted 3 lines · Marcel Holtmann

what kind of USB dongle is this?

The USB dongle is a "Kensington Bluetooth USB Adapter".

Quoted 2 lines

What version of kernel and what
versions of bluez-* packages are installed?

I sent all output on kernel version 2.6.8-1-386 (debian stock). I just copiled my own kernel 2.6.11 with bluetooth support, and I got very similar results. I could see the computer in a "scan" from the PDA, but could not see the PDA when running "hditool scan".

Quoted 3 lines

Why do you set "auth" in hcid.conf? Why is "rswitch" not activated in hcid.conf?

I was probably just mucking with options. I have set rswitch on and auth off, same results.

Quoted 2 lines

Show us the content of /proc/bus/usb/devices.

red:~# cat /proc/bus/usb/devices

T:  Bus=05 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=480 MxCh= 8
B:  Alloc=  0/800 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=01 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.11 ehci_hcd
S:  Product=VIA Technologies, Inc. USB 2.0
S:  SerialNumber=0000:00:10.4
C:* #Ifs= 1 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=256ms

T:  Bus=04 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.11 uhci_hcd
S:  Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#4)
S:  SerialNumber=0000:00:10.3
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

T:  Bus=04 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=058f ProdID=9360 Rev= 1.00
S:  Manufacturer=
S:  Product=USB Reader
S:  SerialNumber=9205291
C:* #Ifs= 1 Cfg#= 1 Atr=80 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
E:  Ad=01(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms

T:  Bus=03 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc= 68/900 us ( 8%), #Int=  4, #Iso=  2
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.11 uhci_hcd
S:  Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#3)
S:  SerialNumber=0000:00:10.2
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

T:  Bus=03 Lev=01 Prnt=01 Port=01 Cnt=01 Dev#=  6 Spd=12  MxCh= 3
D:  Ver= 2.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=3535 Rev= 1.00
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=255ms

T:  Bus=03 Lev=02 Prnt=06 Port=00 Cnt=01 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=047d ProdID=105d Rev= 0.06
S:  Manufacturer=Broadcom
S:  Product=BCM92035DG
S:  SerialNumber=000C55F85A2B
C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)

T:  Bus=03 Lev=02 Prnt=06 Port=01 Cnt=02 Dev#=  8 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=3502 Rev= 1.00
S:  SerialNumber=000C55F85A2B
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

T:  Bus=03 Lev=02 Prnt=06 Port=02 Cnt=03 Dev#=  9 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0a5c ProdID=3503 Rev= 1.00
S:  SerialNumber=000C55F85A2B
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   4 Ivl=10ms

T:  Bus=02 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=365/900 us (41%), #Int=  4, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.11 uhci_hcd
S:  Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (#2)
S:  SerialNumber=0000:00:10.1
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

T:  Bus=02 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#=  3 Spd=12  MxCh= 4
D:  Ver= 1.00 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0452 ProdID=0050 Rev= 3.03
S:  Product=Mitsubishi USB Hub
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   1 Ivl=32ms

T:  Bus=02 Lev=02 Prnt=03 Port=01 Cnt=01 Dev#=  4 Spd=1.5 MxCh= 0
D:  Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c309 Rev=15.00
S:  Manufacturer=Logitech
S:  Product=Logitech USB Keyboard
C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=01 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms
I:  If#= 1 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=82(I) Atr=03(Int.) MxPS=   8 Ivl=32ms

T:  Bus=02 Lev=02 Prnt=03 Port=02 Cnt=02 Dev#=  5 Spd=1.5 MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=046d ProdID=c002 Rev= 1.20
S:  Manufacturer=Logitech
S:  Product=USB-PS/2 Mouse M-BA47
C:* #Ifs= 1 Cfg#= 1 Atr=a0 MxPwr= 50mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=01 Prot=02 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=10ms

T:  Bus=02 Lev=02 Prnt=03 Port=03 Cnt=03 Dev#=  6 Spd=12  MxCh= 0
D:  Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0452 ProdID=0051 Rev= 3.03
S:  Product=Mitsubishi USB Monitor
C:* #Ifs= 1 Cfg#= 1 Atr=40 MxPwr=100mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=03(HID  ) Sub=00 Prot=00 Driver=usbhid
E:  Ad=81(I) Atr=03(Int.) MxPS=   8 Ivl=32ms

T:  Bus=01 Lev=00 Prnt=00 Port=00 Cnt=00 Dev#=  1 Spd=12  MxCh= 2
B:  Alloc=  0/900 us ( 0%), #Int=  0, #Iso=  0
D:  Ver= 1.10 Cls=09(hub  ) Sub=00 Prot=00 MxPS= 8 #Cfgs=  1
P:  Vendor=0000 ProdID=0000 Rev= 2.06
S:  Manufacturer=Linux 2.6.11 uhci_hcd
S:  Product=VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller
S:  SerialNumber=0000:00:10.0
C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 1 Cls=09(hub  ) Sub=00 Prot=00 Driver=hub
E:  Ad=81(I) Atr=03(Int.) MxPS=   2 Ivl=255ms

red:~#

Signature · 12 lines

David Britton <[email protected]>


-------------------------------------------------------
SF.Net email is sponsored by: GoToMeeting - the easiest way to collaborate
online with coworkers and clients while avoiding the high cost of travel and
communications. There is no equipment to buy and you can meet as often as
you want. Try it free.http://ads.osdn.com/?ad_id=7402&alloc_id=16135&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-26 08:16 UTC #5 lore raw

Hi David,

Quoted 3 lines

Quoted 1 line
what kind of USB dongle is this?
The USB dongle is a "Kensington Bluetooth USB Adapter".

be a little bit more specific.

Quoted 29 lines

Quoted 1 line

Show us the content of /proc/bus/usb/devices.

red:~# cat /proc/bus/usb/devices

T:  Bus=03 Lev=02 Prnt=06 Port=00 Cnt=01 Dev#=  7 Spd=12  MxCh= 0
D:  Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs=  1
P:  Vendor=047d ProdID=105d Rev= 0.06
S:  Manufacturer=Broadcom
S:  Product=BCM92035DG
S:  SerialNumber=000C55F85A2B
C:* #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=  0mA
I:  If#= 0 Alt= 0 #EPs= 3 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=81(I) Atr=03(Int.) MxPS=  16 Ivl=1ms
E:  Ad=82(I) Atr=02(Bulk) MxPS=  64 Ivl=0ms
E:  Ad=02(O) Atr=02(Bulk) MxPS=  64 Ivl=0ms
I:  If#= 1 Alt= 0 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   0 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   0 Ivl=1ms
I:  If#= 1 Alt= 1 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=   9 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=   9 Ivl=1ms
I:  If#= 1 Alt= 2 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  17 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  17 Ivl=1ms
I:  If#= 1 Alt= 3 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  32 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  32 Ivl=1ms
I:  If#= 1 Alt= 4 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms

Quoted 8 lines

E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 1 Alt= 5 #EPs= 2 Cls=e0(unk. ) Sub=01 Prot=01 Driver=hci_usb
E:  Ad=83(I) Atr=01(Isoc) MxPS=  64 Ivl=1ms
E:  Ad=03(O) Atr=01(Isoc) MxPS=  64 Ivl=1ms
I:  If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
E:  Ad=84(I) Atr=02(Bulk) MxPS=  32 Ivl=0ms
E:  Ad=04(O) Atr=02(Bulk) MxPS=  32 Ivl=0ms
I:  If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=00 Driver=(none)

So here we go. You can first try to load the hci_usb module with the reset=1 parameter, but I doubt that it helps for this dongle. What you need will be the attached patch to switch it from HID into HCI mode.

Regards

Marcel

drivers/bluetooth/hci_usb.c (mode:100644) +3 -0

Index: drivers/bluetooth/hci_usb.c
===================================================================
@@ -107,6 +107,9 @@
 	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
 	{ USB_DEVICE(0x0a5c, 0x2009), .driver_info = HCI_BCM92035 },
 
+	/* Kensington Bluetooth USB adapter */
+	{ USB_DEVICE(0x047d, 0x105d), .driver_info = HCI_BCM92035 },
+
 	/* Microsoft Wireless Transceiver for Bluetooth 2.0 */
 	{ USB_DEVICE(0x045e, 0x009c), .driver_info = HCI_RESET },

David Britton

author

2005-05-27 02:15 UTC #6 lore raw

Quoted 9 lines · Marcel Holtmann

Hi David,
Quoted 3 lines
Quoted 1 line
what kind of USB dongle is this?
The USB dongle is a "Kensington Bluetooth USB Adapter".
be a little bit more specific.

I would have been more specific, the only other distinguishing thing on it is the model number:

Kensington Bluetooth USB Adapter
Model #33085

Here is the product info page:
http://www.kensington.com/html/6397.html

Quoted 4 lines

So here we go. You can first try to load the hci_usb module with the reset=1 parameter, but I doubt that it helps for this dongle. What you need will be the attached patch to switch it from HID into HCI mode.

Excellent! The patch did it (after also loading with the reset=1). I'm
now on my way trying to set up a PPP connection. Thanks a lot for the
curteous help Marcel.

Signature · 12 lines

David Britton <[email protected]>


-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo!
Search APIs Find out how you can build Yahoo! directly into your own
Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

Marcel Holtmann

maintainer

2005-05-27 07:05 UTC #7 lore raw

Hi David,

Quoted 6 lines

Quoted 5 lines
Quoted 3 lines
Quoted 1 line
what kind of USB dongle is this?
The USB dongle is a "Kensington Bluetooth USB Adapter".
be a little bit more specific.

Quoted 8 lines

I would have been more specific, the only other distinguishing thing on it is the model number:
Kensington Bluetooth USB Adapter
Model #33085
Here is the product info page:
http://www.kensington.com/html/6397.html

I hate companies that are not able to clearly name their product. Once they build another Bluetooth adapter you can't differentiate between them :(

It seems that this dongle is not available in Germany. Does anyone have a spare one for me?

Quoted 6 lines

Quoted 3 lines
So here we go. You can first try to load the hci_usb module with the reset=1 parameter, but I doubt that it helps for this dongle. What you need will be the attached patch to switch it from HID into HCI mode.
Excellent! The patch did it (after also loading with the reset=1). I'm now on my way trying to set up a PPP connection.

So loading with "modprobe hci_usb reset=1" and without the patch doesn't make it work? Don't using "reset=1" and applying the patch does also not work? Only when you do both things the dongle is working. This is odd, because one of my previous Broadcom based dongles like this only needed the BCM92035 quirk to switch from HID into HCI mode. Please test all possibilities so I can add the correct quirk to the kernel.

If you add HCI_RESET to the line for your device it will have the same effect as if you provide "reset=1" on module loading.

Quoted 2 lines

Thanks a lot for the
curteous help Marcel.

You are welcome.

Regards

Marcel

-------------------------------------------------------
This SF.Net email is sponsored by Yahoo.
Introducing Yahoo! Search Developer Network - Create apps using Yahoo! Search APIs Find out how you can build Yahoo! directly into your own Applications - visit http://developer.yahoo.net/?fr=offad-ysdn-ostg-q22005
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

David Britton

author

2005-05-28 05:46 UTC #8 lore raw

Quoted 8 lines · Marcel Holtmann

So loading with "modprobe hci_usb reset=1" and without the patch doesn't make it work? Don't using "reset=1" and applying the patch does also not work? Only when you do both things the dongle is working. This is odd, because one of my previous Broadcom based dongles like this only needed the BCM92035 quirk to switch from HID into HCI mode. Please test all possibilities so I can add the correct quirk to the kernel.

OK -- here are the results:

1) Stock 2.6.11 hci_usb module:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a) modprobe hci_usb
=> FAIL timeout on the scan (original behavior)
b) modprobe hci_usb reset=1
=> PASS This works, can scan, and info my device

2) hci_usb module with given patch applied:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a) modprobe hci_usb
=> FAIL timeout on the scan (seems to be the same as 1a)
b) modprobe hci_usb reset=1
=> PASS This works, can scan, and info my device. Also, there is a
significant increase in response when I do more "hcitool scan" commands after the first one, I have no idea why this is or if it is important?

3) hci_usb module with attached patch applied:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a) modprobe hci_usb
=> PASS since we do the bitwise or of HCI_RESET added to BCM92035 quirk
in the module, no need to specify reset at the command line of modprobe, so this works just as 2b worked (just as you said it would). Speed increase on multiple "hcitool scan" commands is also present as in 2b.

If you need anything else tested, let me know.

Signature · 1 line

David Britton <[email protected]>

hci_usb.c.patch renamed from hci_usb.c +3 -0

@@ -107,6 +107,9 @@
 	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
 	{ USB_DEVICE(0x0a5c, 0x2009), .driver_info = HCI_BCM92035 },
 
+	/* Kensington Bluetooth USB adapter */
+	{ USB_DEVICE(0x047d, 0x105d), .driver_info = HCI_RESET | HCI_BCM92035 },
+
 	/* Microsoft Wireless Transceiver for Bluetooth 2.0 */
 	{ USB_DEVICE(0x045e, 0x009c), .driver_info = HCI_RESET },

Marcel Holtmann

maintainer

2005-05-28 13:41 UTC #9 lore raw

Hi David,

Quoted 27 lines

Quoted 6 lines
So loading with "modprobe hci_usb reset=1" and without the patch doesn't make it work? Don't using "reset=1" and applying the patch does also not work? Only when you do both things the dongle is working. This is odd, because one of my previous Broadcom based dongles like this only needed the BCM92035 quirk to switch from HID into HCI mode. Please test all possibilities so I can add the correct quirk to the kernel.
OK -- here are the results:
1) Stock 2.6.11 hci_usb module:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a) modprobe hci_usb
=> FAIL timeout on the scan (original behavior)
b) modprobe hci_usb reset=1
=> PASS This works, can scan, and info my device
2) hci_usb module with given patch applied:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a) modprobe hci_usb
=> FAIL timeout on the scan (seems to be the same as 1a)
b) modprobe hci_usb reset=1
=> PASS This works, can scan, and info my device. Also, there is a
significant increase in response when I do more "hcitool scan" commands after the first one, I have no idea why this is or if it is important?

Quoted 7 lines

3) hci_usb module with attached patch applied:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
a) modprobe hci_usb
=> PASS since we do the bitwise or of HCI_RESET added to BCM92035 quirk
in the module, no need to specify reset at the command line of modprobe, so this works just as 2b worked (just as you said it would). Speed increase on multiple "hcitool scan" commands is also present as in 2b.

explain the speed increase to me. I don't understand it. The RESET quirk should be enough, because the BCM92035 quirk is only for a very specific dongle from Broadcom.

Check the dmesg output for added and removed USB while you are attaching the dongle. You should see a mouse and a keyboard that will disappear minutes later.

Regards

Marcel

David Britton

author

2005-06-02 04:46 UTC #10 lore raw

Quoted 8 lines · Marcel Holtmann

explain the speed increase to me. I don't understand it. The RESET quirk should be enough, because the BCM92035 quirk is only for a very specific dongle from Broadcom.
Check the dmesg output for added and removed USB while you are attaching the dongle. You should see a mouse and a keyboard that will disappear minutes later.

Well Marcel, as usual, you are correct on this one as well. The speed drop is corallated to the mouse/keyboard add somehow. Once the mouse and keyboard are removed:

Jun  1 23:37:02 localhost kernel: usb 3-2.2: USB disconnect, address 44
Jun  1 23:37:02 localhost udev[16373]: removing device node
'/dev/input/event3'
Jun  1 23:37:02 localhost hal.hotplug[16386]: DEVPATH is not set
Jun  1 23:37:02 localhost kernel: usb 3-2.3: USB disconnect, address 45
Jun  1 23:37:02 localhost udev[16421]: removing device node
'/dev/input/mouse2'
Jun  1 23:37:02 localhost udev[16423]: removing device node

'/dev/input/event4'

The speed for the hcitool scan returns to normal. It is not related to the BCM92035 quirk at all. FYI, the symptom is that before these removal messages, "hcitool scan" takes on average 3 seconds longer to perform a scan. I did not test any other hci tools. This must be related to some contention in the usb code somewhere?

Attached is the patch with just the reset quirk for the Kensington adapter. I believe that you are correct in that this is all that is needed for this adapter to function.

Signature · 1 line

David Britton <[email protected]>

hci_usb.c.patch renamed from hci_usb.c +3 -0

@@ -107,6 +107,9 @@
 	{ USB_DEVICE(0x0a5c, 0x200a), .driver_info = HCI_RESET | HCI_BROKEN_ISOC },
 	{ USB_DEVICE(0x0a5c, 0x2009), .driver_info = HCI_BCM92035 },
 
+	/* Kensington Bluetooth USB adapter */
+	{ USB_DEVICE(0x047d, 0x105d), .driver_info = HCI_RESET },
+
 	/* Microsoft Wireless Transceiver for Bluetooth 2.0 */
 	{ USB_DEVICE(0x045e, 0x009c), .driver_info = HCI_RESET },

Ken M

2005-07-28 18:02 UTC #11 lore raw

Quoted 31 lines · David Britton <davidpbritton <at> gmail.com> writes:

Quoted 8 lines · Marcel Holtmann
explain the speed increase to me. I don't understand it. The RESET quirk should be enough, because the BCM92035 quirk is only for a very specific dongle from Broadcom.
Check the dmesg output for added and removed USB while you are attaching the dongle. You should see a mouse and a keyboard that will disappear minutes later.
Well Marcel, as usual, you are correct on this one as well. The speed drop is corallated to the mouse/keyboard add somehow. Once the mouse and keyboard are removed:
Jun  1 23:37:02 localhost kernel: usb 3-2.2: USB disconnect, address 44
Jun  1 23:37:02 localhost udev[16373]: removing device node
'/dev/input/event3'
Jun  1 23:37:02 localhost hal.hotplug[16386]: DEVPATH is not set
Jun  1 23:37:02 localhost kernel: usb 3-2.3: USB disconnect, address 45
Jun  1 23:37:02 localhost udev[16421]: removing device node
'/dev/input/mouse2'
Jun  1 23:37:02 localhost udev[16423]: removing device node
'/dev/input/event4'
The speed for the hcitool scan returns to normal. It is not related to the BCM92035 quirk at all. FYI, the symptom is that before these removal messages, "hcitool scan" takes on average 3 seconds longer to perform a scan. I did not test any other hci tools. This must be related to some contention in the usb code somewhere?

Quoted 4 lines

Attached is the patch with just the reset quirk for the Kensington adapter. I believe that you are correct in that this is all that is needed for this adapter to function.

Hey guys, thanks for the great info!

I've got the same adapter, and am seeing the exact same problem. I've tried both adding a "reset=1" to the modprobe, as well as adding HCI_RESET to the hci_usb, neither seem to work for me.

As a matter of fact, the driver refuses the "reset" setting:

Jul 28 14:16:05 FatboySlim kernel: hci_usb: Unknown parameter `reset'

I'm running FC3 (2.6.10-770) and the first patch Marcel sent didn't work as "HCI_BCM92035" wasn't defined in my kernel tree.

The second patch that David wrote, setting the driver to "HCI_RESET" still gives me a "Connection Timed Out" error when attempting any "hcitool scan|inq", yet my Treo 650 sees it in discovery.

"hcitool dev" gives me:
Devices:

        hci0    00:01:52:F3:A4:55

"hciconfig -a" gives me:
[root@FatboySlim bluetooth]# hciconfig -a
hci0: Type: USB
BD Address: 00:0C:55:F6:A0:53 ACL MTU: 377:10 SCO MTU: 16:0 UP RUNNING PSCAN ISCAN INQUIRY AUTH ENCRYPT
RX bytes:101 acl:0 sco:0 events:13 errors:0
TX bytes:304 acl:0 sco:0 commands:13 errors:0
Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'FatboySlim-0'
Class: 0x120104
Service Classes: Networking, Object Transfer
Device Class: Computer, Desktop workstation
HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x6965
Manufacturer: Broadcom Corporation (15)

What more can I do to help debug this? I am pretty savvy with this stuff, but I'm stumped..

Ken

-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users

bc90021

2005-07-30 00:10 UTC #12 lore raw

[Bluez-users] Treo 650 Oddities

Hi All,

I have three devices:

Dell Desktop, with USB Dongle
Dell Laptop, with USB Dongle
Treo 650 (Verizon)

Quoted 3 lines

Quoted 3 lines
From the desktop, I can see the phone and the laptop. From the laptop, I can see the desktop and the phone. From the phone, I can see the desktop, but not the laptop.

No matter what I do, the phone will not discover the laptop. It sees the desktop with no problem.

I've tried switching the dongles, to no effect. I've tried updating my BlueZ software, to no effect. I've tried updating the kernel, to no effect.

I can't use hcidump to find out what's going on, because it doesn't register the connection attempt from the phone. (I tried that with the desktop, too, with the same effect.) However, the desktop can successfully connect to the phone nonetheless, as the laptop should. (I've backed up the Treo with pilot-xfer, so I know it works.)

The dongle (either one), when in the laptop, will turn to a more solid blue (as opposed to intermittently flashing), making it look like it is getting a signal. I'm never more than three feet from the laptop with the phone, so range is not an issue.

The kernel versions are the same on the desktop and the laptop. The BlueZ software versions are identical (I'm using Gentoo on both). The configuration files are the same (literally, I scp'ed them) on the laptop as they are on the desktop.

Can anyone suggest what to try next? I'm at a loss here... I want to be able to use the Treo as a modem for the laptop while I'm on vacation, but since I can't pair them, I can't do that right now.

Thanks in advance for any and all help.

-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users