* [Bluez-devel] link_key pairing problem
@ 2005-05-21 13:00 Ruben Jenster
2005-05-23 10:08 ` Marcel Holtmann
0 siblings, 1 reply; 7+ messages in thread
From: Ruben Jenster @ 2005-05-21 13:00 UTC (permalink / raw)
To: bluez-devel
Hi,
I hoped to get rid of the pairing problem with my headset but it still exists.
I had to manually delete the link_key file in /etc/bluetooth. I found a ugly
and simple hack: Symlinked /dev/null to /etc/bluetooth/link_key so that
everything that gets written to link_key is automatically deleted. This way
repairing works but it's not a clean way. I think there is a problem with the
pairing mechanism in bluez. Or could that be a problem of my headset/dongle?
Actually I'm using bluez-utils /bluez-libs version 2.15. I allready tried 2.16
but that doesn't solve the problem.
Does anyone of you has the same problem?
Regards
Ruben
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] link_key pairing problem
2005-05-21 13:00 [Bluez-devel] link_key pairing problem Ruben Jenster
@ 2005-05-23 10:08 ` Marcel Holtmann
2005-05-25 12:47 ` Ruben Jenster
0 siblings, 1 reply; 7+ messages in thread
From: Marcel Holtmann @ 2005-05-23 10:08 UTC (permalink / raw)
To: bluez-devel
Hi Ruben,
> I hoped to get rid of the pairing problem with my headset but it still exists.
> I had to manually delete the link_key file in /etc/bluetooth. I found a ugly
> and simple hack: Symlinked /dev/null to /etc/bluetooth/link_key so that
> everything that gets written to link_key is automatically deleted. This way
> repairing works but it's not a clean way. I think there is a problem with the
> pairing mechanism in bluez. Or could that be a problem of my headset/dongle?
>
> Actually I'm using bluez-utils /bluez-libs version 2.15. I allready tried 2.16
> but that doesn't solve the problem.
use bluez-utils-2.17 and use a clean start. Don't modify hcid.conf and
remove the link_key file (new place and file format since 2.16). Run
"hcidump -X -V" to show what happens.
Maybe your headset is broken.
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] link_key pairing problem
2005-05-23 10:08 ` Marcel Holtmann
@ 2005-05-25 12:47 ` Ruben Jenster
2005-05-25 13:26 ` Marcel Holtmann
0 siblings, 1 reply; 7+ messages in thread
From: Ruben Jenster @ 2005-05-25 12:47 UTC (permalink / raw)
To: bluez-devel
[-- Attachment #1: Type: text/plain, Size: 976 bytes --]
>
> use bluez-utils-2.17 and use a clean start. Don't modify hcid.conf and
> remove the link_key file (new place and file format since 2.16). Run
> "hcidump -X -V" to show what happens.
>
> Maybe your headset is broken.
>
I think that the headset is not broken rather than the dongle.
I tried to pair the headset multiple times with my new thinkpad that has a
builtin bluetooth device an it works without any problems.
After that I also tried it with the bluetooth dongle on the thinkpad and it
doesn't work. As they are both using the same module 'hci_usb'
I assume that it must be the dongle that is causing problems.
Maybe this dongle does not work like other dongles and is not fully or proper
implemented in hci_usb driver.
The dongle is a "Allnet ALL1575" Poor product infos are available on
http://www.allnet.de/product_info_allnet.php?cPath=_&products_id=22844
I'v attech the output of lsusb -vvv maybe that helps to track down the
problem.
Regards
Ruben
[-- Attachment #2: lsusb_vvv --]
[-- Type: text/plain, Size: 17183 bytes --]
Bus 004 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 1 Single TT
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.11-gentoo-r9 ehci_hcd
iProduct 2 EHCI Host Controller
iSerial 1 0000:00:1d.7
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xe0
Self Powered
Remote Wakeup
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 12
Language IDs: (length=4)
0409 English(US)
Bus 003 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.11-gentoo-r9 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.2
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0409 English(US)
Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 224 Wireless
bDeviceSubClass 1 Radio Frequency
bDeviceProtocol 1 Bluetooth
bMaxPacketSize0 64
idVendor 0x0a12 Cambridge Silicon Radio, Ltd
idProduct 0x0001 Bluetooth Dongle
bcdDevice 8.28
iManufacturer 0
iProduct 0
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 193
bNumInterfaces 3
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 16
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type none
wMaxPacketSize 64
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 0
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 1
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 9
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 9
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 2
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 17
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 17
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 3
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 25
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 25
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 4
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 33
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 33
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 5
bNumEndpoints 2
bInterfaceClass 224 Wireless
bInterfaceSubClass 1 Radio Frequency
bInterfaceProtocol 1 Bluetooth
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x03 EP 3 OUT
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 49
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 1
Transfer Type Isochronous
Synch Type none
wMaxPacketSize 49
bInterval 1
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 0
bInterfaceClass 254 Application Specific Interface
bInterfaceSubClass 1 Device Firmware Update
bInterfaceProtocol 0
iInterface 0
unknown descriptor type: 07 21 07 88 13 ff 03
Language IDs: (length=4)
0409 English(US)
Bus 002 Device 003: ID 046d:c016 Logitech, Inc. Optical Mouse
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x046d Logitech, Inc.
idProduct 0xc016 Optical Mouse
bcdDevice 3.40
iManufacturer 1 Logitech
iProduct 2 Optical USB Mouse
iSerial 0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 34
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xa0
Remote Wakeup
MaxPower 100mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 3 Human Interface Devices
bInterfaceSubClass 1 Boot Interface Subclass
bInterfaceProtocol 2 Mouse
iInterface 0
HID Device Descriptor:
bLength 9
bDescriptorType 33
bcdHID 1.10
bCountryCode 0
bNumDescriptors 1
bDescriptorType 34 Report
wDescriptorLength 52
cannot get report descriptor
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 4
bInterval 10
Language IDs: (length=4)
0409 English(US)
Bus 002 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.11-gentoo-r9 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.1
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0409 English(US)
Bus 001 Device 001: ID 0000:0000
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 9 Hub
bDeviceSubClass 0 Unused
bDeviceProtocol 0
bMaxPacketSize0 8
idVendor 0x0000
idProduct 0x0000
bcdDevice 2.06
iManufacturer 3 Linux 2.6.11-gentoo-r9 uhci_hcd
iProduct 2 UHCI Host Controller
iSerial 1 0000:00:1d.0
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 25
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 0mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 9 Hub
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type none
wMaxPacketSize 2
bInterval 255
Language IDs: (length=4)
0409 English(US)
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Bluez-devel] link_key pairing problem
2005-05-25 12:47 ` Ruben Jenster
@ 2005-05-25 13:26 ` Marcel Holtmann
2005-05-25 15:24 ` Ruben Jenster
0 siblings, 1 reply; 7+ messages in thread
From: Marcel Holtmann @ 2005-05-25 13:26 UTC (permalink / raw)
To: bluez-devel
Hi Ruben,
> > use bluez-utils-2.17 and use a clean start. Don't modify hcid.conf and
> > remove the link_key file (new place and file format since 2.16). Run
> > "hcidump -X -V" to show what happens.
> >
> > Maybe your headset is broken.
>
> I think that the headset is not broken rather than the dongle.
> I tried to pair the headset multiple times with my new thinkpad that has a
> builtin bluetooth device an it works without any problems.
> After that I also tried it with the bluetooth dongle on the thinkpad and it
> doesn't work. As they are both using the same module 'hci_usb'
> I assume that it must be the dongle that is causing problems.
>
> Maybe this dongle does not work like other dongles and is not fully or proper
> implemented in hci_usb driver.
> The dongle is a "Allnet ALL1575" Poor product infos are available on
> http://www.allnet.de/product_info_allnet.php?cPath=_&products_id=22844
> I'v attech the output of lsusb -vvv maybe that helps to track down the
> problem.
what does "hciconfig -a" and "hcitool info" say?
Regards
Marcel
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] link_key pairing problem
2005-05-25 13:26 ` Marcel Holtmann
@ 2005-05-25 15:24 ` Ruben Jenster
2005-05-25 15:51 ` Marcel Holtmann
0 siblings, 1 reply; 7+ messages in thread
From: Ruben Jenster @ 2005-05-25 15:24 UTC (permalink / raw)
To: bluez-devel
>
> what does "hciconfig -a" and "hcitool info" say?
root@thinkpad [/etc] hciconfig -a
hci0: Type: USB
BD Address: 00:0C:55:FD:8E:6B ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:306 acl:0 sco:0 events:41 errors:0
TX bytes:900 acl:0 sco:0 commands:39 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Thinkpad (0)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
Manufacturer: Cambridge Silicon Radio (10)
root@thinkpad [/etc] hcitool info 00:0D:B5:80:21:04
Requesting information ...
1 BD Address: 00:0D:B5:80:21:04
Device Name: BT808 Headset
LMP Version: 1.1 (0x1) LMP Subversion: 0x434
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
<3-slot packets> <5-slot packets> <encryption> <slot offset>
<timing accuracy> <role switch> <hold mode> <sniff mode>
<park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
<HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
<power control> <transparent SCO>
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread* Re: [Bluez-devel] link_key pairing problem
2005-05-25 15:24 ` Ruben Jenster
@ 2005-05-25 15:51 ` Marcel Holtmann
2005-05-25 20:34 ` Ruben Jenster
0 siblings, 1 reply; 7+ messages in thread
From: Marcel Holtmann @ 2005-05-25 15:51 UTC (permalink / raw)
To: bluez-devel
Hi Ruben,
> > what does "hciconfig -a" and "hcitool info" say?
>
> root@thinkpad [/etc] hciconfig -a
> hci0: Type: USB
> BD Address: 00:0C:55:FD:8E:6B ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:306 acl:0 sco:0 events:41 errors:0
> TX bytes:900 acl:0 sco:0 commands:39 errors:0
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy: RSWITCH HOLD SNIFF PARK
> Link mode: SLAVE ACCEPT
> Name: 'Thinkpad (0)'
> Class: 0x3e0100
> Service Classes: Networking, Rendering, Capturing
> Device Class: Computer, Uncategorized
> HCI Ver: 1.1 (0x1) HCI Rev: 0x33c LMP Ver: 1.1 (0x1) LMP Subver: 0x33c
> Manufacturer: Cambridge Silicon Radio (10)
>
> root@thinkpad [/etc] hcitool info 00:0D:B5:80:21:04
> Requesting information ...
> 1 BD Address: 00:0D:B5:80:21:04
> Device Name: BT808 Headset
> LMP Version: 1.1 (0x1) LMP Subversion: 0x434
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
> <3-slot packets> <5-slot packets> <encryption> <slot offset>
> <timing accuracy> <role switch> <hold mode> <sniff mode>
> <park state> <RSSI> <channel quality> <SCO link> <HV2 packets>
> <HV3 packets> <u-law log> <A-law log> <CVSD> <paging scheme>
> <power control> <transparent SCO>
>
both are CSR based and they should work without any problems. If you
find a note about "full reset" of your headset in its manual, then you
maybe should try that.
Regards
Marcel
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [Bluez-devel] link_key pairing problem
2005-05-25 15:51 ` Marcel Holtmann
@ 2005-05-25 20:34 ` Ruben Jenster
0 siblings, 0 replies; 7+ messages in thread
From: Ruben Jenster @ 2005-05-25 20:34 UTC (permalink / raw)
To: bluez-devel
Hi Marcel,
>
> both are CSR based and they should work without any problems. If you
> find a note about "full reset" of your headset in its manual, then you
> maybe should try that.
>
No, the headset does not have a full reset funktion.
But really think it's not the headset as it does work perfecly with the
builtin bluetooth module of the thinkpad which is also CSR based.
hci0: Type: USB
BD Address: 00:20:E0:7D:21:C7 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:143 acl:0 sco:0 events:19 errors:0
TX bytes:317 acl:0 sco:0 commands:17 errors:0
Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH HOLD SNIFF PARK
Link mode: SLAVE ACCEPT
Name: 'Thinkpad (0)'
Class: 0x3e0100
Service Classes: Networking, Rendering, Capturing
Device Class: Computer, Uncategorized
HCI Ver: 1.1 (0x1) HCI Rev: 0x222 LMP Ver: 1.1 (0x1) LMP Subver: 0x222
Manufacturer: Cambridge Silicon Radio (10)
Maybe I fool myself but I think the dongle is the basic problem. The best
would be if someone who has the same or at least a dongle with the same chip
revision could deny or confirm this behaviour
Although it's not a solution at the moment I feel comfortable with /dev/zero
symlinked to link_key.
Regards
Ruben
-------------------------------------------------------
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-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2005-05-25 20:34 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-05-21 13:00 [Bluez-devel] link_key pairing problem Ruben Jenster
2005-05-23 10:08 ` Marcel Holtmann
2005-05-25 12:47 ` Ruben Jenster
2005-05-25 13:26 ` Marcel Holtmann
2005-05-25 15:24 ` Ruben Jenster
2005-05-25 15:51 ` Marcel Holtmann
2005-05-25 20:34 ` Ruben Jenster
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.