public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] rctest[3790]: Can't set L2CAP link mode
Date: Wed, 29 Dec 2004 20:34:03 +0100	[thread overview]
Message-ID: <1104348843.6325.1.camel@notepaq> (raw)
In-Reply-To: <cqunik$ule$1@sea.gmane.org>

Hi,

> This is part of my lsmod output:
> 
> [soraberri@castejon temp]$ lsmod
> Module                  Size  Used by
> hci_usb                15041  3
> rfcomm                 36701  2
> l2cap                  25285  7 rfcomm
> bluetooth              46917  11 hci_usb,rfcomm,l2cap
> 
> sdpd and hcid are running
> 
> I think all the important stuff is there, and then why am I getting the 
> following error?
> 
> [soraberri@castejon temp]$rctest -r
> rctest[3790]: Can't set L2CAP link mode. Protocol not available(92)

this error is wrong and I actually fixed it in the CVS now.

> Well it seems that the error is born within the call to
> setsockopt(s, SOL_RFCOMM, RFCOMM_LM, &opt, sizeof(opt))
> in rctest.c

You need a kernel with RFCOMM service level security support. This is
not mainline yet.

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://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-12-29 19:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-29 16:55 [Bluez-users] rctest[3790]: Can't set L2CAP link mode soraberri
2004-12-29 19:34 ` 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=1104348843.6325.1.camel@notepaq \
    --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