From: Francesco Bochicchio <bockman@virgilio.it>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Microsoft Bluethooth "Elite" Keyboard & Mouse
Date: Sun, 16 Jan 2005 18:46:16 +0100 [thread overview]
Message-ID: <20050116174616.GA2201@virgilio.it> (raw)
Hi all,
I have a Microsft Bluetooth "Elite" keyboard and optical mouse,
and I'm trying to make it work with Linux.
I have googled and read stuff, but currently I'm stucked.
When I plug the USB Dongle in an USB port I get the following kernel
messages (among others):
Jan 15 13:48:22 superlap kernel: usb 1-2.2: new full speed USB device using address 8
Jan 15 13:48:23 superlap kernel: input: USB HID v1.11 Keyboard [045e:00bf] on usb-0000:00:10.0-2.2
Jan 15 13:48:24 superlap kernel: usb 1-2.3: new full speed USB device using address 9
Jan 15 13:48:25 superlap kernel: input: USB HID v1.11 Mouse [045e:00be] on usb-0000:00:10.0-2.3
Also, hotplug loads a bunch of modules, including :
usbmouse
joydev
usbkbd
usbhid
hci_usb
rfcomm
l2cap
bluetooth
Finally, I get the message:
Jan 15 13:48:31 superlap hcid[2744]: Can't init device hci0. Connection timed out(110)
The device hci0 is created but not opeerative:
superlap:/home/fb# hciconfig
hci0: Type: USB
BD Address: 00:00:00:00:00:00 ACL MTU: 0:0 SCO MTU: 0:0
DOWN
RX bytes:0 acl:0 sco:0 events:0 errors:0
TX bytes:3 acl:0 sco:0 commands:1 errors:0
and if I try to bring it up:
superlap:/home/fb# hciconfig hci0 up
Can't init device hci0. Connection timed out(110)
I also tried hcidump, but it hangs after this output:
superlap:/home/fb# hcidump -x
HCIDump - HCI packet analyzer ver 1.12
device: hci0 snap_len: 1028 filter: 0xffffffff
I tried all this with and without batteries inserted (no change).
I also tried pressing the litte button on the back while doing
"hciconfig hci0 up" and pressing keys while doing "hcidump -x".
The keyboard and mouse works with Windows XP SP2, so the problem
is not the hardware.
My questions:
1. Does this device works with Linux+blueZ ? (I know that someone had
success with other models of MS BT keyboards).
2. Do I have to patch the kernel? (actually I have a Kernel 2.6.9
pre-compiled (Debian Unstable distro) for AMD k7).
3. What else can I try?
Thanks for any hint.
Ciao
----
FB
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-01-16 17:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-16 17:46 Francesco Bochicchio [this message]
2005-01-16 17:51 ` [Bluez-users] Microsoft Bluethooth "Elite" Keyboard & Mouse Michal Semler
2005-01-16 18:01 ` Marcel Holtmann
2005-01-16 18:12 ` Michal Semler
2005-01-16 19:37 ` Francesco Bochicchio
2005-01-16 19:48 ` Michal Semler
2005-01-18 1:19 ` Marcel Holtmann
2005-01-20 19:12 ` [Bluez-users] Microsoft Bluethooth "Elite" Keyboard & Mouse - UPDATE: works with stock 2.6.10 Francesco Bochicchio
2005-01-20 19:18 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050116174616.GA2201@virgilio.it \
--to=bockman@virgilio.it \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox