From: Stefan Seyfried <seife@suse.de>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Can't connect to Freedom Input Mini Duo keyboard
Date: Mon, 23 Apr 2007 12:18:38 +0200 [thread overview]
Message-ID: <20070423101838.GF8944@suse.de> (raw)
In-Reply-To: <c38065090704221456s3194f809vaf65418873f6f9ff@mail.gmail.com>
On Sun, Apr 22, 2007 at 04:56:35PM -0500, Philip S. Trasatti Jr. wrote:
> Thanks for the response. Still doesn't work.
>
> hidd is running with the --server and --master options
>
> When I run hidd the second time I get...
>
> # hidd --connect 00:0B:0D:6F:7F:88
> Can't create HID control channel: Connection reset by peer
did you press the "connect" button on the keyboard? I always connect
keyboards / mice by (with hidd --server already running):
- hidd --search (as root)
- then press the connect button on the keyboard / mouse and pressing
some keys / moving the mouse, to see once it is connected.
and this has worked fine for me all the time.
--
Stefan Seyfried
"Any ideas, John?"
"Well, surrounding them's out."
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2007-04-23 10:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-22 17:38 [Bluez-users] Can't connect to Freedom Input Mini Duo keyboard Philip S. Trasatti Jr.
2007-04-22 19:39 ` CIJOML
2007-04-22 21:56 ` Philip S. Trasatti Jr.
2007-04-23 10:18 ` Stefan Seyfried [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=20070423101838.GF8944@suse.de \
--to=seife@suse.de \
--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;
as well as URLs for NNTP newsgroup(s).