public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] headset$
Date: Thu, 1 Jul 2004 11:45:18 +0200	[thread overview]
Message-ID: <20040701094518.GB4505@gmx.net> (raw)
In-Reply-To: <amsbr1-glo.ln1@ID-90813.users.dfncis.de>

On  0, Steffen Schwientek <schwientek@web.de> wrote:
> I want to use my plantronics M9000 headset. Since it?s my only bluetooth
> part, I can?t figure out, if bluetooth works. Connecting the USB dongle,
> the kernel (2.6.6) reports:

Better use 2.6.7 or apply the latest -mh patch to 2.6.6. 

> An hcitool scan detects (if I put the headset in pairing mode)
> 00:03:89:46:E2:0F       M3000 by Plantronics
> 
> So nice, so far. Unfortunately I don?t know what I need next (I tried the
> kbluetooth daemon, but this doesn?t detect the headset at all, or failed
> due to an timeout.

Did you pair Headset and Computer? Normally you have to switch the
headset in pairing mode (-> Manual) and then insert the pin on the
computer. (you can also specifiy pin in a file?) This should happen
transparently, when  a program tries to connect to a remote device and
their was no pairing before, then it tries to get the Pin from pinhelper
application or from file. 

> Next I try an hcitool cc, but nothing happens. kdebluetooth shows me an
> connection, but after a while it reports an error (0x22).
> /var/log/messages shows no error.
 
Try the syslog file, if your distribution offers one. hcitool cc is not
recommend for users, it is more a development and debugging feature.

nicholas


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-07-01  9:45 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-30 22:50 [Bluez-users] headset Steffen Schwientek
2004-07-01  9:45 ` Nicholas A. Preyss [this message]
2004-07-01 18:47   ` [Bluez-users] Re: headset$ Steffen Schwientek
2004-07-01 23:57     ` Steffen Schwientek

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=20040701094518.GB4505@gmx.net \
    --to=nalp@gmx.net \
    --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