Hello,
I'm trying to connect my EPOX Buetooth Keyboard BT-KB01B but without success so far. The error message is:
hcitool conf
Connections:
> ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
< ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
Can't create HID control channel: Connection timed out
here the info from the Keyboard:
hcitool info 00:04:61:82:03:4A
Requesting information ...
BD Address: 00:04:61:82:03:4A
Device Name: Bluetooth-Keyboard 82034A
LMP Version: 1.1 (0x1) LMP Subversion: 0x356
Manufacturer: Cambridge Silicon Radio (10)
Features: 0xff 0xff 0x0b 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>
<transparent SCO>
and here the info from the bluetooth usb dongle:
hciconfig -a
hci0: Type: USB
BD Address: 00:04:61:81:5A:A8 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:967334 acl:38241 sco:0 events:47990 errors:0
TX bytes:244813 acl:260 sco:0 commands:47588 errors:0
Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy:
Link mode: SLAVE ACCEPT
Name: 'BlueZ linux (0)'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
Manufacturer: Cambridge Silicon Radio (10)
The EPOX Mous BT-MS02B works perfectly.
I'm using a Kanotix Linux with Kernel 2.6.17.7.
Can somebody help meor give me some hint what i did wrong?
Thanks in advance.
Wolfram
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi,
On Mon, Jul 31, 2006 at 08:17:05PM +0200, Marcel Holtmann wrote:
> Hi Nils,
> =
> > Probably make it as default for hcidump and let "-X" and "-V" turn it o=
ff?
> =
> it is too late for that :(
> =
> Maybe at some point when I rewrite hcidump, but I don't see that happen
> in the near future.
maybe something like that helps a bit:
Index: src/hcidump.c
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
RCS file: /cvsroot/bluez/hcidump/src/hcidump.c,v
retrieving revision 1.69
diff -u -p -r1.69 hcidump.c
--- src/hcidump.c 17 Jan 2006 18:45:06 -0000 1.69
+++ src/hcidump.c 31 Jul 2006 17:10:19 -0000
@@ -827,6 +827,12 @@ int main(int argc, char *argv[])
}
}
=
+ if (!(flags & DUMP_VERBOSE && flags & DUMP_EXT)) {
+ fprintf (stderr, "Warning: if you want to use this tool to report "
+ "a problem, you should at least\n"
+ "run \"hcidump -X -V\".\n");
+ }
+
argc -=3D optind;
argv +=3D optind;
optind =3D 0;
:-)
(not even compile-tested)
-- =
Stefan Seyfried
QA / R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out." =
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Nils,
> >> I'm trying to connect my EPOX Buetooth Keyboard BT-KB01B but without success so far. The error message is:
> >> hcitool conf
> >> Connections:
> >> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
> >> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
> >> root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
> >> Can't create HID control channel: Connection timed out
> >
> > how many times do I have to mention this. Include "hcidump -X -V" output
> > or nobody will ever will be able to help you.
>
> Probably make it as default for hcidump and let "-X" and "-V" turn it off?
it is too late for that :(
Maybe at some point when I rewrite hcidump, but I don't see that happen
in the near future.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Marcel Holtmann schrieb:
> Hi Wolfram,
Hi!
>> I'm trying to connect my EPOX Buetooth Keyboard BT-KB01B but without success so far. The error message is:
>> hcitool conf
>> Connections:
>> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
>> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
>> root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
>> Can't create HID control channel: Connection timed out
>
> how many times do I have to mention this. Include "hcidump -X -V" output
> or nobody will ever will be able to help you.
Probably make it as default for hcidump and let "-X" and "-V" turn it off?
> Regards
> Marcel
Cheers
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Well, i'm still trying to get my keyboard working.
However, i am making progress on the headset.
When i turn the headset on and hold down the powerbutton i get the flashing
red/blue light as the manual says.
As i stated below i changed the passkey in /etc/bluetooth/hcid.conf to "0000".
The manual for the headset says "The PIN/passkey is: 0000"
When i do a hidd --connect 00:0D:44:4F:37:72 or a hcitool cc 00:0D:44:4F:37:72
i see the following in hcidump now:
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: PIN Code Request (0x16) plen 6
< HCI Command: PIN Code Request Negative Reply (0x01|0x000e) plen 6
> HCI Event: Command Complete (0x0e) plen 10
> HCI Event: Connect Complete (0x03) plen 11
At the console the message "Can't get device information: Permission denied"
and kdebluetoth reports "Pairing not allowed"
That's progress, i think. I STILL am never asked for a passcode. I can
run /usr/lib/kdebluetooth/kdebluetooth manually, so i know the dialog is
operational, it just never comes up. I made a script that contains
echo "PIN:0000"
and i have tried supplying that as my pass_helper, but that is never utilized
either.
I've tried commenting out the line: #passkey "0000";
but that does not force a pin_helper to appear or be run. I have tried
entering 0000 on the keyboard but that doesn't do anything either. Do i need
to adjust something in my rfcomm.conf file? (seen here
http://www.feline-soul.com/files/bluetooth/rfcomm.conf )?
My hcid.conf file can be viewed here:
http://www.feline-soul.com/files/bluetooth/hcid.conf
Ideas?
Bearcat
On Saturday 29 July 2006 00:35 in an email titled "Re: [Bluez-users] can't
connect EPOX Keyboard BT-KB01B" Bearcat M. Sandor wrote:
>An update I just recieved my logitech headset and i'm making some headway.
>It's actually giving my some clues about the keyboard
>
>I did the following:
>
>1. in the hcid.conf file i changed the passkey to "0000"
>2. Reloaded bluez.
>3. hiconfig up and down
>4. hold power button on headset
>5. hcitool scan
>I see 00:0D:44:4F:37:72 Logitech HS03 V04
>then a hidd --connect 00:0D:44:4F:37:72 or a hcitool cc 00:0D:44:4F:37:72
>starts the connection.
>
>In hcidump i see:
>
>< HCI Command: Create Connection (0x01|0x0005) plen 13
>
>> HCI Event: Command Status (0x0f) plen 4
>> HCI Event: PIN Code Request (0x16) plen 6
>> HCI Event: Connect Complete (0x03) plen 11
>
>I am never prompted for a pin code. I even made a script which contains:
> echo "PIN:0000"
>but no pin is ever entered.
>
>Thus kdebluetooth sees the headset but it is never connected.
>
>The keyboard on the other hand is never seen at all. A hcitool scan does not
>show it, nor does it ever appear in kdebluetooth. However, the mouse is
>never seen in a scan either, yet it works perfectly and is seen in
>kdebluetooth.
>
>I'm very confused.
>
>Bearcat
>
>
>On Friday 28 July 2006 12:38 in an email titled "Re: [Bluez-users] can't
>
>connect EPOX Keyboard BT-KB01B" Bearcat M. Sandor wrote:
>>Sorry about that. I meant to say files/bluetooth on all those.
>>
>>They are here: http://www.feline-soul.com/files/bluetooth/
>>
>>Here the are inline:
>>http://www.feline-soul.net/files/bluetooth/hcid.conf:
>>#
>># HCI daemon configuration file.
>>#
>>
>># HCId options
>>options {
>> # Automatically initialize new devices
>> autoinit yes;
>>
>> # Security Manager mode
>> # none - Security manager disabled
>> # auto - Use local PIN for incoming connections
>> # user - Always ask user for a PIN
>> #
>> security user;
>>
>> # Pairing mode
>> # none - Pairing disabled
>> # multi - Allow pairing with already paired devices
>> # once - Pair once and deny successive attempts
>> pairing multi;
>>
>> # Default PIN code for incoming connections
>> passkey "BlueZ";
>>
>> # PIN helper
>> #pin_helper /usr/bin/bluepin;
>> #pin_helper /etc/bluetooth/cbpinscript;
>> pin_helper /usr/lib/kdebluetooth/kbluepin;
>>}
>>
>># Default settings for HCI devices
>>device {
>> # Local device name
>> # %d - device id
>> # %h - host name
>> name "BlueZ (%d)";
>>
>> # Local device class
>> class 0x100000;
>>
>> # Default packet type
>> #pkt_type DH1,DM1,HV1;
>>
>> # Inquiry and Page scan
>> iscan enable; pscan enable;
>>
>> # Default link mode
>> # none - no specific policy
>> # accept - always accept incoming connections
>> # master - become master on incoming connections,
>> # deny role switch on outgoing connections
>> lm accept;
>>
>> # Default link policy
>> # none - no specific policy
>> # rswitch - allow role switch
>> # hold - allow hold mode
>> # sniff - allow sniff mode
>> # park - allow park mode
>> lp rswitch,hold,sniff,park;
>>}
>>-------------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidev_-a_output:
>>hci0: Type: USB
>> BD Address: 00:07:61:1C:9F:D3 ACL MTU: 192:8 SCO MTU: 64:8
>> UP RUNNING PSCAN ISCAN
>> RX bytes:8886937 acl:584808 sco:0 events:79865 errors:0
>> TX bytes:392377 acl:192 sco:0 commands:77281 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: 'BlueZ (0)'
>> Class: 0x000000
>> Service Classes: Unspecified
>> Device Class: Miscellaneous,
>> HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP Subver: 0x34e
>>Manufacturer: Cambridge Silicon Radio (10)
>>--------------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidump:
>>HCI sniffer - Bluetooth packet analyzer ver 1.31
>>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x00 interval 0
>> Mode: Active
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x02 interval 126
>> Mode: Sniff
>>-----------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidump_hcitool_connect HCI
>>sniffer - Bluetooth packet analyzer ver 1.31
>>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
>>Packet type: DM1 DM3 DM5 DH1 DH3 DH5
>>
>>> HCI Event: Command Status (0x0f) plen 4
>>
>> Create Connection (0x01|0x0005) status 0x0c ncmd 1
>> Error: Command Disallowed
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>< HCI Command: Read RSSI (0x05|0x0005) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Read RSSI (0x05|0x0005) ncmd 1
>> status 0x00 handle 41 rssi 0
>>< HCI Command: Role Discovery (0x02|0x0009) plen 2
>> handle 41
>>
>>> HCI Event: Command Complete (0x0e) plen 7
>>
>> Role Discovery (0x02|0x0009) ncmd 1
>> 0000: 00 29 00 00 .)..
>>
>>> HCI Event: Connect Complete (0x03) plen 11
>>
>> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>>Error: Page Timeout
>>--------------------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/hcidump_hidd_connect
>>HCI sniffer - Bluetooth packet analyzer ver 1.31
>>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x00 interval 0
>> Mode: Active
>>
>>> HCI Event: Mode Change (0x14) plen 6
>>
>> status 0x00 handle 41 mode 0x02 interval 126
>> Mode: Sniff
>>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
>>Packet type: DM1 DM3 DM5 DH1 DH3 DH5
>>
>>> HCI Event: Command Status (0x0f) plen 4
>>
>> Create Connection (0x01|0x0005) status 0x00 ncmd 1
>>
>>> HCI Event: Connect Complete (0x03) plen 11
>>
>> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>>Error: Page Timeout
>>< HCI Command: Create Connection (0x01|0x0005) plen 13
>> bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
>>Packet type: DM1 DM3 DM5 DH1 DH3 DH5
>>
>>> HCI Event: Command Status (0x0f) plen 4
>>
>> Create Connection (0x01|0x0005) status 0x00 ncmd 1
>>
>>> HCI Event: Connect Complete (0x03) plen 11
>>
>> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>>Error: Page Timeout
>>-----------------------------------------------------------
>>http://www.feline-soul.net/files/bluetooth/rfcomm.conf
>>#
>># RFCOMM configuration file.
>>#
>>
>>rfcomm0 {
>> # Automatically bind the device at startup
>> bind no;
>>
>> # Bluetooth address of the device
>> device 11:22:33:44:55:66;
>>
>> # RFCOMM channel for the connection
>> channel 1;
>>
>> # Description of the connection
>> comment "Example Bluetooth device";
>>---------------------------------------------
>>
>>That's it. The commands i used to get these sets of output are in the
>>previous email.
>>
>>Thanks all,
>>
>>Bearcat
>>
>>> Hi Bearcat,
>>>
>>> On 7/28/06, Bearcat M. Sandor <[email protected]> wrote:
>>>> Thank you again for the help so far. I have placed a bunch of output
>>
>>files on
>>
>>>> my server for your viewing pleasure, instead of giving you large
>>
>>outputs
>>
>>>> in
>>>> an email body.
>>>
>>> Sorry, but I couldn't see any of those files (all links end up with "404
>>
>>Not found" error). Can you send those files inline so we can see what's
>>happening, please?
>>
>>> Regards,
>>>
>>> -- Ulisses
--
Bearcat M. Sandor
[email protected]
ICQ: 6628727
MSN: [email protected]
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: [email protected]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Wolfram,
> I'm trying to connect my EPOX Buetooth Keyboard BT-KB01B but without success so far. The error message is:
>
> hcitool conf
> Connections:
> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
> root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
> Can't create HID control channel: Connection timed out
how many times do I have to mention this. Include "hcidump -X -V" output
or nobody will ever will be able to help you.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
An update I just recieved my logitech headset and i'm making some headway.
It's actually giving my some clues about the keyboard
I did the following:
1. in the hcid.conf file i changed the passkey to "0000"
2. Reloaded bluez.
3. hiconfig up and down
4. hold power button on headset
5. hcitool scan
I see 00:0D:44:4F:37:72 Logitech HS03 V04
then a hidd --connect 00:0D:44:4F:37:72 or a hcitool cc 00:0D:44:4F:37:72
starts the connection.
In hcidump i see:
< HCI Command: Create Connection (0x01|0x0005) plen 13
> HCI Event: Command Status (0x0f) plen 4
> HCI Event: PIN Code Request (0x16) plen 6
> HCI Event: Connect Complete (0x03) plen 11
I am never prompted for a pin code. I even made a script which contains:
echo "PIN:0000"
but no pin is ever entered.
Thus kdebluetooth sees the headset but it is never connected.
The keyboard on the other hand is never seen at all. A hcitool scan does not
show it, nor does it ever appear in kdebluetooth. However, the mouse is
never seen in a scan either, yet it works perfectly and is seen in
kdebluetooth.
I'm very confused.
Bearcat
On Friday 28 July 2006 12:38 in an email titled "Re: [Bluez-users] can't
connect EPOX Keyboard BT-KB01B" Bearcat M. Sandor wrote:
>Sorry about that. I meant to say files/bluetooth on all those.
>
>They are here: http://www.feline-soul.com/files/bluetooth/
>
>Here the are inline:
>http://www.feline-soul.net/files/bluetooth/hcid.conf:
>#
># HCI daemon configuration file.
>#
>
># HCId options
>options {
> # Automatically initialize new devices
> autoinit yes;
>
> # Security Manager mode
> # none - Security manager disabled
> # auto - Use local PIN for incoming connections
> # user - Always ask user for a PIN
> #
> security user;
>
> # Pairing mode
> # none - Pairing disabled
> # multi - Allow pairing with already paired devices
> # once - Pair once and deny successive attempts
> pairing multi;
>
> # Default PIN code for incoming connections
> passkey "BlueZ";
>
> # PIN helper
> #pin_helper /usr/bin/bluepin;
> #pin_helper /etc/bluetooth/cbpinscript;
> pin_helper /usr/lib/kdebluetooth/kbluepin;
>}
>
># Default settings for HCI devices
>device {
> # Local device name
> # %d - device id
> # %h - host name
> name "BlueZ (%d)";
>
> # Local device class
> class 0x100000;
>
> # Default packet type
> #pkt_type DH1,DM1,HV1;
>
> # Inquiry and Page scan
> iscan enable; pscan enable;
>
> # Default link mode
> # none - no specific policy
> # accept - always accept incoming connections
> # master - become master on incoming connections,
> # deny role switch on outgoing connections
> lm accept;
>
> # Default link policy
> # none - no specific policy
> # rswitch - allow role switch
> # hold - allow hold mode
> # sniff - allow sniff mode
> # park - allow park mode
> lp rswitch,hold,sniff,park;
>}
>-------------------------------------------------------------------
>http://www.feline-soul.net/files/bluetooth/hcidev_-a_output:
>hci0: Type: USB
> BD Address: 00:07:61:1C:9F:D3 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:8886937 acl:584808 sco:0 events:79865 errors:0
> TX bytes:392377 acl:192 sco:0 commands:77281 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: 'BlueZ (0)'
> Class: 0x000000
> Service Classes: Unspecified
> Device Class: Miscellaneous,
> HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP Subver: 0x34e
>Manufacturer: Cambridge Silicon Radio (10)
>--------------------------------------------------------------------
>http://www.feline-soul.net/files/bluetooth/hcidump:
>HCI sniffer - Bluetooth packet analyzer ver 1.31
>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>
>> HCI Event: Mode Change (0x14) plen 6
>
> status 0x00 handle 41 mode 0x00 interval 0
> Mode: Active
>
>> HCI Event: Mode Change (0x14) plen 6
>
> status 0x00 handle 41 mode 0x02 interval 126
> Mode: Sniff
>-----------------------------------------------------------------
>http://www.feline-soul.net/files/bluetooth/hcidump_hcitool_connect HCI
>sniffer - Bluetooth packet analyzer ver 1.31
>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
>Packet type: DM1 DM3 DM5 DH1 DH3 DH5
>
>> HCI Event: Command Status (0x0f) plen 4
>
> Create Connection (0x01|0x0005) status 0x0c ncmd 1
> Error: Command Disallowed
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>< HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
>< HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
>> HCI Event: Command Complete (0x0e) plen 7
>
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
>
>> HCI Event: Connect Complete (0x03) plen 11
>
> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>Error: Page Timeout
>--------------------------------------------------------------------
>http://www.feline-soul.net/files/bluetooth/hcidump_hidd_connect
>HCI sniffer - Bluetooth packet analyzer ver 1.31
>device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
>
>> HCI Event: Mode Change (0x14) plen 6
>
> status 0x00 handle 41 mode 0x00 interval 0
> Mode: Active
>
>> HCI Event: Mode Change (0x14) plen 6
>
> status 0x00 handle 41 mode 0x02 interval 126
> Mode: Sniff
>< HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
>Packet type: DM1 DM3 DM5 DH1 DH3 DH5
>
>> HCI Event: Command Status (0x0f) plen 4
>
> Create Connection (0x01|0x0005) status 0x00 ncmd 1
>
>> HCI Event: Connect Complete (0x03) plen 11
>
> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>Error: Page Timeout
>< HCI Command: Create Connection (0x01|0x0005) plen 13
> bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
>Packet type: DM1 DM3 DM5 DH1 DH3 DH5
>
>> HCI Event: Command Status (0x0f) plen 4
>
> Create Connection (0x01|0x0005) status 0x00 ncmd 1
>
>> HCI Event: Connect Complete (0x03) plen 11
>
> status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
>Error: Page Timeout
>-----------------------------------------------------------
>http://www.feline-soul.net/files/bluetooth/rfcomm.conf
>#
># RFCOMM configuration file.
>#
>
>rfcomm0 {
> # Automatically bind the device at startup
> bind no;
>
> # Bluetooth address of the device
> device 11:22:33:44:55:66;
>
> # RFCOMM channel for the connection
> channel 1;
>
> # Description of the connection
> comment "Example Bluetooth device";
>---------------------------------------------
>
>That's it. The commands i used to get these sets of output are in the
>previous email.
>
>Thanks all,
>
>Bearcat
>
>> Hi Bearcat,
>>
>> On 7/28/06, Bearcat M. Sandor <[email protected]> wrote:
>>> Thank you again for the help so far. I have placed a bunch of output
>
>files on
>
>>> my server for your viewing pleasure, instead of giving you large
>
>outputs
>
>>> in
>>> an email body.
>>
>> Sorry, but I couldn't see any of those files (all links end up with "404
>
>Not found" error). Can you send those files inline so we can see what's
>happening, please?
>
>> Regards,
>>
>> -- Ulisses
--
Bearcat M. Sandor
[email protected]
ICQ: 6628727
MSN: [email protected]
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: [email protected]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Nils,
> > No such luck for me yet. Strangly the hcitool does not allow the auth
> > option for me. I had to do a hciconfig /dev/usb/hci0 auth to turn the auth
> > on the hub. Auth is now on but the keyboard still doesn't connect. As
> > usuall nothing is reported in the syslogs.
> >
> > Do i need to turn on the auth for the keyboard too (is that even an option)?
>
> No, the keyboard will require that automatically.
actually only the Apple keyboards require this and this is wrong
according to the HID specification. The host must make the decision to
authenticate and switch on encryption.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Sorry about that. I meant to say files/bluetooth on all those.
They are here: http://www.feline-soul.com/files/bluetooth/
Here the are inline:
http://www.feline-soul.net/files/bluetooth/hcid.conf:
#
# HCI daemon configuration file.
#
# HCId options
options {
# Automatically initialize new devices
autoinit yes;
# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;
# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;
# Default PIN code for incoming connections
passkey "BlueZ";
# PIN helper
#pin_helper /usr/bin/bluepin;
#pin_helper /etc/bluetooth/cbpinscript;
pin_helper /usr/lib/kdebluetooth/kbluepin;
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "BlueZ (%d)";
# Local device class
class 0x100000;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept;
# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}
-------------------------------------------------------------------
http://www.feline-soul.net/files/bluetooth/hcidev_-a_output:
hci0: Type: USB
BD Address: 00:07:61:1C:9F:D3 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:8886937 acl:584808 sco:0 events:79865 errors:0
TX bytes:392377 acl:192 sco:0 commands:77281 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: 'BlueZ (0)'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP Subver: 0x34e
Manufacturer: Cambridge Silicon Radio (10)
--------------------------------------------------------------------
http://www.feline-soul.net/files/bluetooth/hcidump:
HCI sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 41 mode 0x00 interval 0
Mode: Active
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 41 mode 0x02 interval 126
Mode: Sniff
-----------------------------------------------------------------
http://www.feline-soul.net/files/bluetooth/hcidump_hcitool_connect HCI
sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x0c ncmd 1
Error: Command Disallowed
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
> HCI Event: Connect Complete (0x03) plen 11
status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
Error: Page Timeout
--------------------------------------------------------------------
http://www.feline-soul.net/files/bluetooth/hcidump_hidd_connect
HCI sniffer - Bluetooth packet analyzer ver 1.31
device: hci0 snap_len: 1028 filter: 0xffffffffffffffff
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 41 mode 0x00 interval 0
Mode: Active
> HCI Event: Mode Change (0x14) plen 6
status 0x00 handle 41 mode 0x02 interval 126
Mode: Sniff
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
Error: Page Timeout
< HCI Command: Create Connection (0x01|0x0005) plen 13
bdaddr 00:07:61:1B:50:9B ptype 0xcc18 rswitch 0x01 clkoffset 0x0000
Packet type: DM1 DM3 DM5 DH1 DH3 DH5
> HCI Event: Command Status (0x0f) plen 4
Create Connection (0x01|0x0005) status 0x00 ncmd 1
> HCI Event: Connect Complete (0x03) plen 11
status 0x04 handle 0 bdaddr 00:07:61:1B:50:9B type ACL encrypt 0x00
Error: Page Timeout
-----------------------------------------------------------
http://www.feline-soul.net/files/bluetooth/rfcomm.conf
#
# RFCOMM configuration file.
#
rfcomm0 {
# Automatically bind the device at startup
bind no;
# Bluetooth address of the device
device 11:22:33:44:55:66;
# RFCOMM channel for the connection
channel 1;
# Description of the connection
comment "Example Bluetooth device";
---------------------------------------------
That's it. The commands i used to get these sets of output are in the
previous email.
Thanks all,
Bearcat
> Hi Bearcat,
>
> On 7/28/06, Bearcat M. Sandor <[email protected]> wrote:
>> Thank you again for the help so far. I have placed a bunch of output
files on
>> my server for your viewing pleasure, instead of giving you large
outputs
>> in
>> an email body.
>
> Sorry, but I couldn't see any of those files (all links end up with "404
Not found" error). Can you send those files inline so we can see what's
happening, please?
>
> Regards,
>
> -- Ulisses
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Bearcat,
On 7/28/06, Bearcat M. Sandor <[email protected]> wrote:
> Thank you again for the help so far. I have placed a bunch of output files on
> my server for your viewing pleasure, instead of giving you large outputs in
> an email body.
Sorry, but I couldn't see any of those files (all links end up with
"404 Not found" error). Can you send those files inline so we can see
what's happening, please?
Regards,
-- Ulisses
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Folks,
Thank you again for the help so far. I have placed a bunch of output files on
my server for your viewing pleasure, instead of giving you large outputs in
an email body.
This is the output from hcidump -X -V while just pressing keys on the keyboard
after pressing the connect button:
http://www.feline-soul.com/files/hcidump
This is the output from hcidump -X -V when a "hcitool cc 00:07:61:1B:50:9B" is
run:
http://www.feline-soul.com/files/hcidump_hcitool_connect
This is the output from hcidump -X -V when a "hidd --connect
00:07:61:1B:50:9B" is run:
http://www.feline-soul.com/files/hcidump_hidd_connect
My hcid configuration file:
http://www.feline-soul.com/files/hcid.conf
My rfcomm configuration file (I have never altered it)
http://www.feline-soul.com/files/rfcomm.conf
The daemon hidd is indeed running:
root 4750 0.0 0.0 5040 484 ? Ss Jul26
0:00 /usr/bin/hidd --server
Pertainent modules are as follows:
hidp 17152 3
l2cap 22408 14 rfcomm,hidp
usbhid 37024 0
bluetooth 47268 12 rfcomm,hidp,l2cap,hci_usb
hci_usb 15892 6
I have taken the batteries out of the keyboard, pressed the gray button,
pressed the button on my hub, unplugged and plugged the hub back in, and
sacrificed AOL Cd's on an alter in the name of Tux.
I am never prompted for a pin (and i don't know what it would be if i was). I
have taken the kde pin handler line out of the config and still i am never
asked for a pin. Truthfully, i don' t even know if i should be or not.
What else can i provide?
Thank you again,
Bearcat M. Sandor
On Friday 28 July 2006 03:46 in an email titled "Re: [Bluez-users] can't
connect EPOX Keyboard BT-KB01B" Marcel Holtmann wrote:
>Hi Nils,
>
>> > No such luck for me yet. Strangly the hcitool does not allow the auth
>> > option for me. I had to do a hciconfig /dev/usb/hci0 auth to turn the
>> > auth on the hub. Auth is now on but the keyboard still doesn't connect.
>> > As usuall nothing is reported in the syslogs.
>> >
>> > Do i need to turn on the auth for the keyboard too (is that even an
>> > option)?
>>
>> No, the keyboard will require that automatically.
>
>actually only the Apple keyboards require this and this is wrong
>according to the HID specification. The host must make the decision to
>authenticate and switch on encryption.
>
>Regards
>
>Marcel
--
Bearcat M. Sandor
[email protected]
ICQ: 6628727
MSN: [email protected]
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: [email protected]
Bearcat M. Sandor schrieb:
> Wolfram, Nils,
Hi!
> No such luck for me yet. Strangly the hcitool does not allow the auth
> option for me. I had to do a hciconfig /dev/usb/hci0 auth to turn the auth
> on the hub. Auth is now on but the keyboard still doesn't connect. As
> usuall nothing is reported in the syslogs.
>
> Do i need to turn on the auth for the keyboard too (is that even an option)?
No, the keyboard will require that automatically.
> I am never prompted for a pin and even if i was, i don't know what it
> would be. Is the pin connected to the keyboard, the hub (should i find out
> from logitech what their default is) or is it a pin kept by bluez?
The problem is that the keyboards I have seen so far require that you
input the PIN on the keyboard first and then you will be prompted to
second this on the desktop PC.
So what might happen at your side now is that the keyboard is waiting
for the PIN to be input.
Maybe try again and try to connect to the keyboard using hidd then type
in a PIN code on the keyboard and press ENTER. If you are lucky the
dialog the pops up.
> Also, i don't have a program called hcidump. Is that part of the bluez
> package?
In Debian it is a seperate package but it belongs to the BlueZ project.
> Thanks all,
> Bearcat
Cheers
nils faerber
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Bearcat,
> I installed the hcidump program (and made/distributed a package for my
> distro).
>
> When i press buttons on my keyboards hcidump reports nothing. There is nothing
> about a pin or security when i turn auth on and try to reestablish
> connections with the mouse. After auth is off the mouse works fine.
>
> When trying to connect the keyboard i get a lot of:
> < HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
> > HCI Event: Command Complete (0x0e) plen 7
> Role Discovery (0x02|0x0009) ncmd 1
> 0000: 00 29 00 00 .)..
> < HCI Command: Read RSSI (0x05|0x0005) plen 2
> handle 41
> > HCI Event: Command Complete (0x0e) plen 7
> Read RSSI (0x05|0x0005) ncmd 1
> status 0x00 handle 41 rssi 0
> < HCI Command: Role Discovery (0x02|0x0009) plen 2
> handle 41
>
> Does that mean anything?
this is totally out of context. Make sure that we at least see the
create connection command.
And don't use "hciconfig hci0 auth" unless you know what you are doing.
This is security mode 3 and its config option has been removed for a
very good reason.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
I installed the hcidump program (and made/distributed a package for my
distro).
When i press buttons on my keyboards hcidump reports nothing. There is nothing
about a pin or security when i turn auth on and try to reestablish
connections with the mouse. After auth is off the mouse works fine.
When trying to connect the keyboard i get a lot of:
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Role Discovery (0x02|0x0009) ncmd 1
0000: 00 29 00 00 .)..
< HCI Command: Read RSSI (0x05|0x0005) plen 2
handle 41
> HCI Event: Command Complete (0x0e) plen 7
Read RSSI (0x05|0x0005) ncmd 1
status 0x00 handle 41 rssi 0
< HCI Command: Role Discovery (0x02|0x0009) plen 2
handle 41
Does that mean anything?
Bearcat
On Thursday 27 July 2006 19:22 in an email titled "Re: [Bluez-users] can't
connect EPOX Keyboard BT-KB01B" Marcel Holtmann wrote:
>Hi Bearcat,
>
>> No such luck for me yet. Strangly the hcitool does not allow the auth
>> option for me. I had to do a hciconfig /dev/usb/hci0 auth to turn the auth
>> on the hub. Auth is now on but the keyboard still doesn't connect. As
>> usuall nothing is reported in the syslogs.
>>
>> Do i need to turn on the auth for the keyboard too (is that even an
>> option)?
>>
>> I am never prompted for a pin and even if i was, i don't know what it
>> would be. Is the pin connected to the keyboard, the hub (should i find out
>> from logitech what their default is) or is it a pin kept by bluez?
>>
>> Also, i don't have a program called hcidump. Is that part of the bluez
>> package?
>
>it is in bluez-hcidump and you should start using it. Otherwise you are
>starting to speculate and this doesn't help.
>
>Regards
>
>Marcel
--
Bearcat M. Sandor
[email protected]
ICQ: 6628727
MSN: [email protected]
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: [email protected]
Hi Wolfram,
> I'm trying to connect my Buetooth Keyboard BT-KB01B but without success so far. The error message is:
>
> hcitool conf
> Connections:
> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
> root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
> Can't create HID control channel: Connection timed out
run "hcidump -X -V" so see what is really going on.
> and here the info from the bluetooth usb dongle:
>
>
> hciconfig -a
> hci0: Type: USB
> BD Address: 00:04:61:81:5A:A8 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:967334 acl:38241 sco:0 events:47990 errors:0
> TX bytes:244813 acl:260 sco:0 commands:47588 errors:0
> Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy:
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ linux (0)'
> Class: 0x000000
> Service Classes: Unspecified
> Device Class: Miscellaneous,
> HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver: 0x20d
> Manufacturer: Cambridge Silicon Radio (10)
Make sure that hcid is running. From this output it doesn't look like it
is running.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi Bearcat,
> No such luck for me yet. Strangly the hcitool does not allow the auth
> option for me. I had to do a hciconfig /dev/usb/hci0 auth to turn the auth
> on the hub. Auth is now on but the keyboard still doesn't connect. As
> usuall nothing is reported in the syslogs.
>
> Do i need to turn on the auth for the keyboard too (is that even an option)?
>
> I am never prompted for a pin and even if i was, i don't know what it
> would be. Is the pin connected to the keyboard, the hub (should i find out
> from logitech what their default is) or is it a pin kept by bluez?
>
> Also, i don't have a program called hcidump. Is that part of the bluez
> package?
it is in bluez-hcidump and you should start using it. Otherwise you are
starting to speculate and this doesn't help.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Linux: 2.6.17
bluez (utils and libs) 3.1
kdebluetooth 1.0_beta
Nothing seems to work when trying to connect this keyboard. The mouse works
just fine.
I entered pin_helper /usr/lib/kdebluetooth/kbluepin; into
my /etc/bluetooth/hid.conf file.
If i do a "hciconfig /dev/usb/hiddev0 auth" and then jiggle the mouse i can
see kdebluetooth trying to reconnect. It fails with a "LMP Responce Timeout".
I never get asked for a pin. I have run kbluepin just do see what it would
do. It does indeed run and return what i type in it.
Turning off auth via hciconfig and jiggling the mouse brings it back just
fine.
Following Nils' instructions in the responce to Wolfram, i tried getting the
keyboard to work that way. If i give the command "hcitool cc
00:07:61:1B:50:9B" (the keyboards id) i get "Can't create connection:
Input/output error"
A "hcitool scan", "hidd --search", "hcitool inq", "hcitool scan" find nothing,
but a "hidd --show" shows me the mouse.
When the mouse is disconnected and i move it around i see the kbluetooth
emblem blinking and it comes up. When i press the connect button on the
keyboard or hit keys the kdebluetooth emblem doesn't so much as blink.
I know the keyboard works, and both keyboard and mouse work in pure hid (no
hci) mode.
Any ideas at all? Where do i start? I'm just chasing my tail here.
The hub info:
hci0: Type: USB
BD Address: 00:07:61:1C:9F:D3 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:6053157 acl:423452 sco:0 events:15327 errors:0
TX bytes:72942 acl:166 sco:0 commands:13618 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: 'BlueZ (0)'
Class: 0x000000
Service Classes: Unspecified
Device Class: Miscellaneous,
HCI Ver: 1.1 (0x1) HCI Rev: 0x34e LMP Ver: 1.1 (0x1) LMP Subver: 0x34e
Manufacturer: Cambridge Silicon Radio (10)
Thank you in advance for the help,
Bearcat
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Wolfram, Nils,
No such luck for me yet. Strangly the hcitool does not allow the auth
option for me. I had to do a hciconfig /dev/usb/hci0 auth to turn the auth
on the hub. Auth is now on but the keyboard still doesn't connect. As
usuall nothing is reported in the syslogs.
Do i need to turn on the auth for the keyboard too (is that even an option)?
I am never prompted for a pin and even if i was, i don't know what it
would be. Is the pin connected to the keyboard, the hub (should i find out
from logitech what their default is) or is it a pin kept by bluez?
Also, i don't have a program called hcidump. Is that part of the bluez
package?
Thanks all,
Bearcat
Wolfram wrote:
> Hi nils,
> Now it's working Yeah!!!!!!!!!!!!
>
> I followed your recommendation and switched auth on via hcitool and
> looked to the hcidump but everything moved very fast and i didn't see any
> popup where i can put in the pin string?
>
> But after doing
>
> hidd --connect 00:04:61:82:03:4A i can write suddenly on my keyboar which
> i'm using now to write the email !!!
<snip>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Hi nils,
Now it's working Yeah!!!!!!!!!!!!
I followed your recommendation and switched auth on via hcitool and looked=
to the hcidump but everything moved very fast and i didn't see any popup w=
here i can put in the pin string?
But after doing =
hidd --connect 00:04:61:82:03:4A i can write suddenly on my keyboar which =
i'm using now to write the email !!!
here is the evidence:
hidd --connect show
root@woraBox:/home/rw024419# hidd --show
00:04:61:82:03:4A Bluetooth HID Boot Protocol Device [0000:0000] connected =
[boot-protocol]
00:04:61:81:F7:C8 Bluetooth HID Boot Protocol Device [0000:0000] connected =
[boot-protocol]
So now i'm hapy that everything works but i'm a little afraid to disconnect=
and try again to understand really what happend. Nothing to see in the sys=
log!
But it looks like auth is required. But the pin input via hcidump is really=
weard isn't ist?
Next Step would be to make this permanent that after boot the keyboard and=
mouse is connected automatically! Any hint on that?
Nils, many thanks for your great idea and help.
Best Regards
Wolfram
----- Urspr=FCngliche Mail ----
Von: Nils Faerber <[email protected]>
An: [email protected]; BlueZ users <[email protected]>
CC: Wolfram Reda <[email protected]>
Gesendet: Donnerstag, den 27. Juli 2006, 19:43:11 Uhr
Betreff: Re: [Bluez-users] can't connect EPOX Keyboard BT-KB01B
Bearcat M. Sandor schrieb:
> Wolfram,
Hi!
> I'm having the same problem with my logitech Cordless Elite. The mouse wo=
rks =
> great, but the keyboard just won't connect. Perhaps there is something w=
rong =
> with keyboards in general or our keyboards are based on the same topology.
> =
> If i figure it out, i'll let you know. In the mean time, we ought to comp=
are =
> notes.
Hmm.. usually those keyboards want to be paired first.
So must have auth enabled.
But even then it might be that you have to enter the PIN on the keyboard
first before the requester on the Linux side pops-up.
So IIRC the process could be (as root):
put keyboard in pairing mode (press some button somewhere so it also
becomes visible)
start hcidump as root on some console and watch the output ;)
try to connect the hidd to the keyboard (hidd --connect <bdaddr>)
now you may get a auth request from the keyboard in the hcidump
now enter a PIN on the keyboard and press the ENTER key, the PIN
usually can only consist of numbers (like 1234) typed on the regular
number key, not the numeric keypad!
now again watch the hcidump output
if your host is setup correctly the PIN request dialog should come up
and you have to enter the same PIN as before there
watch hcidump again - auth successful? Then it should work now!
Not successful?
Darn!
OK, take two.
Make the keyboard visible again.
Now create a L2CAP connection manually by doing
hcitool cc <bdaddr>
And now trigger the auth process manually
hcitool auth <bdaddr>
And then follow the above steps right _after_ the connect hidd step.
After PIN exchange you should be paired and should be able to connect
using hidd to your keyboard.
Good luck!
> Bearcat
Cheers
nils
> On Thursday 27 July 2006 01:46 in an email titled "[Bluez-users] can't co=
nnect =
> EPOX Keyboard BT-KB01B" Wolfram Reda wrote:
>> Hello,
>> I'm trying to connect my Buetooth Keyboard EPOX BT-KB01B but without suc=
cess
>> so far. The error message is:
>>
>> hcitool conf
>>
>> Connections:
>> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
>>
>> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
>> root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
>> Can't create HID control channel: Connection timed out
>>
>> here the info from the Keyboard:
>>
>>
>> hcitool info 00:04:61:82:03:4A
>> Requesting information ...
>> BD Address: 00:04:61:82:03:4A
>> Device Name: Bluetooth-Keyboard 82034A
>> LMP Version: 1.1 (0x1) LMP Subversion: 0x356
>> Manufacturer: Cambridge Silicon Radio (10)
>> Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
>> <3-slot packets> <5-slot packets> <encryption> <slot offs=
et>
>> <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>
>> <transparent SCO>
>>
>> and here the info from the bluetooth usb dongle:
>>
>>
>> hciconfig -a
>> hci0: Type: USB
>> BD Address: 00:04:61:81:5A:A8 ACL MTU: 192:8 SCO MTU: 64:8
>> UP RUNNING PSCAN ISCAN
>> RX bytes:967334 acl:38241 sco:0 events:47990 errors:0
>> TX bytes:244813 acl:260 sco:0 commands:47588 errors:0
>> Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>> Link policy:
>> Link mode: SLAVE ACCEPT
>> Name: 'BlueZ linux (0)'
>> Class: 0x000000
>> Service Classes: Unspecified
>> Device Class: Miscellaneous,
>> HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
>> 0x20d Manufacturer: Cambridge Silicon Radio (10)
>>
>> The EPOX Mous BT-MS02B works perfectly.
>>
>> I'm using a Kanotix Linux with Kernel 2.6.17.7.
>>
>> Can somebody help meor give me some hint what i did wrong?
>>
>> Thanks in advance.
>>
>> Wolfram
>>
-- =
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=3Djoin.php&p=3Dsourceforge&CID=3DDE=
VDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Bearcat M. Sandor schrieb:
> Wolfram,
Hi!
> I'm having the same problem with my logitech Cordless Elite. The mouse works
> great, but the keyboard just won't connect. Perhaps there is something wrong
> with keyboards in general or our keyboards are based on the same topology.
>
> If i figure it out, i'll let you know. In the mean time, we ought to compare
> notes.
Hmm.. usually those keyboards want to be paired first.
So must have auth enabled.
But even then it might be that you have to enter the PIN on the keyboard
first before the requester on the Linux side pops-up.
So IIRC the process could be (as root):
put keyboard in pairing mode (press some button somewhere so it also
becomes visible)
start hcidump as root on some console and watch the output ;)
try to connect the hidd to the keyboard (hidd --connect <bdaddr>)
now you may get a auth request from the keyboard in the hcidump
now enter a PIN on the keyboard and press the ENTER key, the PIN
usually can only consist of numbers (like 1234) typed on the regular
number key, not the numeric keypad!
now again watch the hcidump output
if your host is setup correctly the PIN request dialog should come up
and you have to enter the same PIN as before there
watch hcidump again - auth successful? Then it should work now!
Not successful?
Darn!
OK, take two.
Make the keyboard visible again.
Now create a L2CAP connection manually by doing
hcitool cc <bdaddr>
And now trigger the auth process manually
hcitool auth <bdaddr>
And then follow the above steps right _after_ the connect hidd step.
After PIN exchange you should be paired and should be able to connect
using hidd to your keyboard.
Good luck!
> Bearcat
Cheers
nils
> On Thursday 27 July 2006 01:46 in an email titled "[Bluez-users] can't connect
> EPOX Keyboard BT-KB01B" Wolfram Reda wrote:
>> Hello,
>> I'm trying to connect my Buetooth Keyboard EPOX BT-KB01B but without success
>> so far. The error message is:
>>
>> hcitool conf
>>
>> Connections:
>> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
>>
>> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
>> root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
>> Can't create HID control channel: Connection timed out
>>
>> here the info from the Keyboard:
>>
>>
>> hcitool info 00:04:61:82:03:4A
>> Requesting information ...
>> BD Address: 00:04:61:82:03:4A
>> Device Name: Bluetooth-Keyboard 82034A
>> LMP Version: 1.1 (0x1) LMP Subversion: 0x356
>> Manufacturer: Cambridge Silicon Radio (10)
>> Features: 0xff 0xff 0x0b 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>
>> <transparent SCO>
>>
>> and here the info from the bluetooth usb dongle:
>>
>>
>> hciconfig -a
>> hci0: Type: USB
>> BD Address: 00:04:61:81:5A:A8 ACL MTU: 192:8 SCO MTU: 64:8
>> UP RUNNING PSCAN ISCAN
>> RX bytes:967334 acl:38241 sco:0 events:47990 errors:0
>> TX bytes:244813 acl:260 sco:0 commands:47588 errors:0
>> Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
>> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
>> Link policy:
>> Link mode: SLAVE ACCEPT
>> Name: 'BlueZ linux (0)'
>> Class: 0x000000
>> Service Classes: Unspecified
>> Device Class: Miscellaneous,
>> HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
>> 0x20d Manufacturer: Cambridge Silicon Radio (10)
>>
>> The EPOX Mous BT-MS02B works perfectly.
>>
>> I'm using a Kanotix Linux with Kernel 2.6.17.7.
>>
>> Can somebody help meor give me some hint what i did wrong?
>>
>> Thanks in advance.
>>
>> Wolfram
>>
--
kernel concepts Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users
Wolfram,
I'm having the same problem with my logitech Cordless Elite. The mouse works
great, but the keyboard just won't connect. Perhaps there is something wrong
with keyboards in general or our keyboards are based on the same topology.
If i figure it out, i'll let you know. In the mean time, we ought to compare
notes.
Bearcat
On Thursday 27 July 2006 01:46 in an email titled "[Bluez-users] can't connect
EPOX Keyboard BT-KB01B" Wolfram Reda wrote:
>Hello,
>I'm trying to connect my Buetooth Keyboard EPOX BT-KB01B but without success
> so far. The error message is:
>
> hcitool conf
>
>Connections:
> > ACL 00:04:61:81:F7:C8 handle 44 state 1 lm SLAVE
>
> < ACL 00:04:61:82:03:4A handle 41 state 1 lm MASTER
>root@woraBox:/home/rw024419# hidd --connect 00:04:61:82:03:4A
>Can't create HID control channel: Connection timed out
>
>here the info from the Keyboard:
>
>
>hcitool info 00:04:61:82:03:4A
>Requesting information ...
> BD Address: 00:04:61:82:03:4A
> Device Name: Bluetooth-Keyboard 82034A
> LMP Version: 1.1 (0x1) LMP Subversion: 0x356
> Manufacturer: Cambridge Silicon Radio (10)
> Features: 0xff 0xff 0x0b 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>
> <transparent SCO>
>
>and here the info from the bluetooth usb dongle:
>
>
>hciconfig -a
>hci0: Type: USB
> BD Address: 00:04:61:81:5A:A8 ACL MTU: 192:8 SCO MTU: 64:8
> UP RUNNING PSCAN ISCAN
> RX bytes:967334 acl:38241 sco:0 events:47990 errors:0
> TX bytes:244813 acl:260 sco:0 commands:47588 errors:0
> Features: 0xff 0xff 0x0b 0x00 0x00 0x00 0x00 0x00
> Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
> Link policy:
> Link mode: SLAVE ACCEPT
> Name: 'BlueZ linux (0)'
> Class: 0x000000
> Service Classes: Unspecified
> Device Class: Miscellaneous,
> HCI Ver: 1.1 (0x1) HCI Rev: 0x20d LMP Ver: 1.1 (0x1) LMP Subver:
> 0x20d Manufacturer: Cambridge Silicon Radio (10)
>
>The EPOX Mous BT-MS02B works perfectly.
>
>I'm using a Kanotix Linux with Kernel 2.6.17.7.
>
>Can somebody help meor give me some hint what i did wrong?
>
>Thanks in advance.
>
>Wolfram
>
>
>
>-------------------------------------------------------------------------
>Take Surveys. Earn Cash. Influence the Future of IT
>Join SourceForge.net's Techsay panel and you'll get the chance to share your
>opinions on IT & business topics through brief surveys -- and earn cash
>http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>_______________________________________________
>Bluez-users mailing list
>[email protected]
>https://lists.sourceforge.net/lists/listinfo/bluez-users
--
Bearcat M. Sandor
[email protected]
ICQ: 6628727
MSN: [email protected]
Yahoo: bearcatsandor
AIM: bearcatmsandor
Jabber: [email protected]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-users