From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Can't connect to a keyboard
Date: Sun, 17 Apr 2005 21:11:04 +0200 [thread overview]
Message-ID: <1113765064.16233.80.camel@pegasus> (raw)
In-Reply-To: <20050417205450.653f7567.jesuscanonavarro@yahoo.es>
Hi Jesus,
> First of all, thank you very much for reading the message and spending a little of your time helping me. I'm new in this "blue field", hope i can help people with this some day.
>
> Ok. I had an Apple Wireless Keyboard for xmas, since then, i haven't been able to use it on my GNU/Linux, a minimalistic Debian testing (in Compaq Deskpro EN series old workstation, P2 350Mhz, 256MB, 8GB; it runs so fine ;).
>
> I read Marcel's pages about bluez and bluetooth in GNU/Linux (great job man!) to get a right dongle (a 3com USB Bluetooth adapter) and get the first contact to bluetooth in GNU/Linux. I couldn't understand that pages very well since i don't know much more about the bluetooth hw, protocol, stack... Perhaps, the answer is right in front of my nose but i cann't see it. Actually, someone seemed to have the same problem in the list archives time ago, but i can't imagine what do i have to do.
>
> So, i installed "bluez-utils" pakage. And i've been trying things; the info i know i can give you by now, is:
>
> -I need to restart /etc/init.d/bluez-utils, after booting to make it work.
> -I have no problem to detect the dongle on boot or with hotplug.
> -I have tried some steps to connect with the keyboard i found in the documentation i difficultly read:
run "hcidump -X -V" as root in another terminal and then call
hidd --connect <bdaddr>
You will see that nothing happens, because your keyboard is in security
mode 3. Now push a number combination on the number pad of your keyboard
and hit return. After that a dialog should open, where you have to enter
these number combination again. Now you are paired and the keyboard is
ready for daily use.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-04-17 19:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-17 18:54 [Bluez-users] Can't connect to a keyboard Jesús Cano Navarro
2005-04-17 19:11 ` Marcel Holtmann [this message]
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=1113765064.16233.80.camel@pegasus \
--to=marcel@holtmann.org \
--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