public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Bearcat@feline-soul.com, BlueZ users <bluez-users@lists.sourceforge.net>
Cc: Nils Faerber <nils.faerber@kernelconcepts.de>
Subject: Re: [Bluez-users] can't connect EPOX Keyboard BT-KB01B
Date: Fri, 28 Jul 2006 03:22:05 +0200	[thread overview]
Message-ID: <1154049725.7650.8.camel@localhost> (raw)
In-Reply-To: <1171.216.47.50.125.1154031396.squirrel@webmail.feline-soul.net>

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
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2006-07-28  1:22 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-27  7:46 [Bluez-users] can't connect EPOX Keyboard BT-KB01B Wolfram Reda
2006-07-27 17:30 ` Bearcat M. Sandor
2006-07-27 17:43   ` Nils Faerber
2006-07-27 18:50     ` Wolfram Reda
2006-07-27 20:16       ` Bearcat M. Sandor
2006-07-28  1:22         ` Marcel Holtmann [this message]
2006-07-28  3:26           ` Bearcat M. Sandor
2006-07-28  7:21             ` Marcel Holtmann
2006-07-28  9:39         ` Nils Faerber
2006-07-28  9:46           ` Marcel Holtmann
2006-07-28 16:48             ` Bearcat M. Sandor
2006-07-28 18:21               ` Ulisses Furquim
2006-07-28 18:38                 ` Bearcat M. Sandor
2006-07-29  6:35                   ` Bearcat M. Sandor
2006-07-29 21:20                     ` [Bluez-users] Connecting a Logitech Mobile Traveler...progress Bearcat M. Sandor
2006-07-28  0:18     ` [Bluez-users] Mouse works now, but can't connect Logitech Cordless Elite keyboard Bearcat M. Sandor
  -- strict thread matches above, loose matches on Subject: below --
2006-07-27  8:33 [Bluez-users] can't connect EPOX Keyboard BT-KB01B Wolfram Reda
2006-07-29 12:57 ` Marcel Holtmann
2006-07-31 14:21   ` Nils Faerber
2006-07-31 18:17     ` Marcel Holtmann
2006-07-31 17:13       ` Stefan Seyfried
2006-07-26 21:13 Wolfram Reda
2006-07-28  1:23 ` 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=1154049725.7650.8.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=Bearcat@feline-soul.com \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=nils.faerber@kernelconcepts.de \
    /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