From: Colin Beckingham <colbec@start.ca>
To: Johan Hedberg <johan.hedberg@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Permission denied (13) on Samsung WEP475 headset?
Date: Thu, 04 Aug 2011 09:22:19 -0400 [thread overview]
Message-ID: <4E3A9D0B.7080706@start.ca> (raw)
In-Reply-To: <20110804121703.GA23534@dell>
On 08/04/2011 08:17 AM, Johan Hedberg wrote:
> Hi Colin,
>
> On Thu, Aug 04, 2011, Colin Beckingham wrote:
>> I'd like to provide some feedback regarding a Samsung WEP475 headset
>> which fails to connect to linux specifically.
>>
>> The USB bluetooth adapter is a Model: Belkin BLUETOOTH USB +EDR
>> ADAPTER v2.1 UHE which successfully interconnects with 2 Jabra and 1
>> Plantronics headsets, plus a Nokia E71 phone. Samsung WEP475
>> successfully connects to a Windows XP machine and to the Nokia E71.
>>
>> Using Opensuse 11.4 with custom kernel 3.0 currently, (also fails
>> with 2.6.38), bluez 4.96 and bluedevil manager.
>>
>> Symptoms are that bluedevil sees the headset in pairing mode and
>> correctly retrieves the name WEP475, connected button flashes green
>> and then returns to grey (not connected). WEP475 led changes to
>> connected status but bluedevil shows headset not connected and
>> headset does not work.
>>
>> With bluetoothd in debug mode, I get the following transactions in
>> /var/log/messages:
>
> There seems to be something strange going on with the secure simple
> pairing logic. For some reason the initial link key isn't good enough
> (auth request + link key negative reply after the initial key has been
> generated) and then there's a user confirm negative reply for the second
> attempt. It'd be good to get to the bottom of this and fix it properly,
> but meanwhile you can probably work around this by disabling SSP on your
> side (hciconfig hci0 sspmode 0) and retrying pairing.
>
> Johan
>
Johan, sspmode 0 did have a positive effect. I have now been able to
pair the headset and use it in a pipe arecord to aplay context with good
results at least two times from scratch. Thanks very much.
What further feedback would be useful to developers to track down the
fundamental issue?
--
---
Colin Beckingham
next prev parent reply other threads:[~2011-08-04 13:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 11:10 Permission denied (13) on Samsung WEP475 headset? Colin Beckingham
2011-08-04 11:30 ` Colin Beckingham
2011-08-04 12:17 ` Johan Hedberg
2011-08-04 13:22 ` Colin Beckingham [this message]
2011-08-04 14:54 ` Peter Hurley
2011-08-06 14:36 ` Peter Hurley
2011-08-06 15:33 ` Colin Beckingham
2011-08-06 16:50 ` Peter Hurley
2011-08-06 17:22 ` Colin Beckingham
2011-08-08 12:38 ` Peter Hurley
2011-08-08 13:31 ` Colin Beckingham
2011-08-08 13:53 ` Peter Hurley
2011-08-08 14:01 ` Colin Beckingham
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=4E3A9D0B.7080706@start.ca \
--to=colbec@start.ca \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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).