public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Chris Searle <usenet@chrissearle.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Re: hcid config
Date: Sun, 25 Jul 2004 14:23:22 +0200	[thread overview]
Message-ID: <1090758202.4791.83.camel@pegasus> (raw)
In-Reply-To: <87acxo48c4.fsf@alice.chrissearle.org>

Hi Chris,

> Still not getting any further. autoinit is already yes in the config
> file (see other post).
> 
> Some more info: on hcitool inq that both devices are reporting class
> 0x000000.
> 
> Manually restarting hcid makes no difference (same result as using the
> /etc/init.d script). Stopping all other bluez things (sdp, dund etc)
> then just starting hcid - no change.
> 
> Not sure how to follow this further.

what version of bluez-utils are you using? Try a newer or an older one
and see if the problem still exists.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-07-25 12:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23  7:01 [Bluez-users] hcid config Chris Searle
2004-07-23  8:41 ` Marcel Holtmann
2004-07-23  8:44   ` [Bluez-users] " Chris Searle
2004-07-23  8:51     ` Marcel Holtmann
2004-07-23  8:59       ` Chris Searle
2004-07-23  9:09         ` Marcel Holtmann
2004-07-23  9:14           ` Chris Searle
2004-07-25 11:47           ` Chris Searle
2004-07-25 12:23             ` 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=1090758202.4791.83.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=usenet@chrissearle.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