From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Two "identical" laptops, same phone, one works, one doesn't
Date: Tue, 10 Jan 2006 17:08:28 +0100 [thread overview]
Message-ID: <1136909308.7200.8.camel@localhost.localdomain> (raw)
In-Reply-To: <37f261b0601090736w6d7157d6x6ea876ecafb3572e@mail.gmail.com>
Hi Hugo,
> This is driving me nuts. I have two Compaq nx6110 laptops here, I've
> got one working fine, the other isn't working. I try:
>
> rfcomm connect 0 00:12:47:1E:90:AE 3
>
> For the one it works great, the other I get
>
> Can't connect RFCOMM socket: Connection refused
>
> How can I debug this problem? Will a hcidump help? (Should I attach
> the two "hcidump -V" outputs to an email?)
>
> Confused and frustrated after a day of struggling,
send in the output of "hcidump -X -V" for that problem.
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-01-10 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-09 15:36 [Bluez-users] Two "identical" laptops, same phone, one works, one doesn't Hugo van der Merwe
2006-01-10 16:08 ` Marcel Holtmann [this message]
2006-01-12 11:20 ` [Bluez-users] " Hugo van der Merwe
2006-01-12 16:21 ` Hugo van der Merwe
2006-01-12 16:52 ` rangzen
2006-01-29 7:44 ` Hugo van der Merwe
2006-01-29 14:33 ` Martin Stolle
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=1136909308.7200.8.camel@localhost.localdomain \
--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