Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Cannot create L2CAP socket
Date: Mon, 18 Apr 2005 16:42:40 +0200	[thread overview]
Message-ID: <1113835360.16233.95.camel@pegasus> (raw)
In-Reply-To: <20050418141520.70316.qmail@web15501.mail.cnb.yahoo.com>

Hi,

> when I tried to connect to the GN by typing the
> command "pand --connect BTADDR",It failed .The
> /var/log/message shows the following :
> 
> kernel: application bug: pand(5128) has SIGCHLD set to
> SIG_IGN but calls wait().
> kernel: (see the NOTES section of 'man 2 wait').
> Workaround activated.
> modprobe: modprobe: Can't locate module bt-proto-0
> pand[5128]: Cannot create L2CAP socket. No such file
> or directory(2)
> 
> I'm a beginner of bluez,I don't know why this happened
> .What can I do to solve this problem ?

call "modprobe l2cap".

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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2005-04-18 14:42 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-18 14:15 [Bluez-users] Cannot create L2CAP socket Zhixiang Deng
2005-04-18 14:42 ` 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=1113835360.16233.95.camel@pegasus \
    --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