Linux bluetooth development
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] cannot connect to pm-325
Date: Wed, 23 Mar 2005 23:20:23 +0100	[thread overview]
Message-ID: <1111616423.1916.16.camel@pegasus> (raw)
In-Reply-To: <20050323184658.95418.qmail@web50709.mail.yahoo.com>

Hi John,

>  Not been prompted to enter pin, keep getting 
>  
>  Can't connect RFCOMM socket: Connection refused
>  
>  despite scan finding the device.
>  
>  put those lm and lp entries in hcid.conf, and even
>  tried(afterward)putting the following in rfcomm.conf
>  
>  rfcomm0 {
>  bind no;
>  device    08:00:37:12:C4:B1;
>  channel   1;
>  comment   "PM325 by LG";
>  }
>  
> 
>  any ideas?

run "hcidump -X -V" as root and show the output to us.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005
Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows
Embedded(r) & Windows Mobile(tm) platforms, applications & content.  Register
by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2005-03-23 22:20 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 18:46 [Bluez-users] cannot connect to pm-325 John H.
2005-03-23 22:20 ` Marcel Holtmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-24 21:51 John H.
2005-03-24 22:46 ` Marcel Holtmann
2005-03-25  2:38 John H.
2005-03-25 11:55 ` 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=1111616423.1916.16.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