public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gardiner <osronline@glidos.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid.conf seemingly ignored
Date: Fri, 22 Dec 2006 11:18:43 +0000	[thread overview]
Message-ID: <458BBF13.3010300@glidos.net> (raw)
In-Reply-To: <20061222110611.GA9345@suse.de>

Stefan Seyfried wrote:
> On Thu, Dec 21, 2006 at 11:13:29PM +0000, Paul Gardiner wrote:
>> Paul Gardiner wrote:
>>> Stefan Seyfried wrote:
>>>>> Ok thanks. I'm not sure I have read that before. That may help a lot.
>>>> If it does not work, let me know so that i can fix the documentation.
>>> No, I still can't tease any response out of dund, whatever I do. I'm
>>> seeing this in the logs:
> 
> Bad.
> 
>> So, is there any other way I can debug this problem?  I can get a
>> trace from hcidump. Is there a way to get that to display the meaning
>> of what is transmitted?
>>
>> I really don't want to just give up, seeing as I had this working
>> perfectly on whatever version of bluez ran under suse 10.1.  I
>> can't believe the changes that went through bluez since then
>> have made connecting a Qtek S100 to a linux box impossible.
>> That would be a real backward step.
> 
> I also don't think we broke it on purpose :-)

Sorry. I know I'm being a bit of a misery.  :-)

> I will try it out, and check if it works for me, but probably not before
> the first week of next year.

That would be brilliant, thanks.

BTW, lots of other things seem to be working or at least trying to.
If I try ActiveSync via bluetooth from my S100, I get some sort of
connection, and if running vnc at the time, I see a chat window
appear on the server. The two devices are to some extent talking.

Also, provided I issue the command "sdptool add DUN", the S100
will consider the server as being a modem, its just that the
attempt to connect always fails.

Cheers,
     Paul.


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2006-12-22 11:18 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 10:12 [Bluez-users] hcid.conf seemingly ignored Paul Gardiner
2006-12-19 10:20 ` Marcel Holtmann
2006-12-19 12:28   ` Paul Gardiner
2006-12-19 15:36     ` Stefan Seyfried
2006-12-19 15:49       ` Paul Gardiner
2006-12-19 16:31         ` Stefan Seyfried
2006-12-19 17:23           ` Paul Gardiner
2006-12-19 17:37             ` Ulisses Furquim
2006-12-19 17:42             ` Stefan Seyfried
2006-12-19 17:51               ` Marcel Holtmann
2006-12-19 20:23       ` Paul Gardiner
2006-12-20  8:54         ` Stefan Seyfried
2006-12-20  9:38           ` Paul Gardiner
2006-12-20 11:04             ` Stefan Seyfried
2006-12-20 22:40               ` Paul Gardiner
2006-12-21 23:13                 ` Paul Gardiner
2006-12-22 11:06                   ` Stefan Seyfried
2006-12-22 11:18                     ` Paul Gardiner [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=458BBF13.3010300@glidos.net \
    --to=osronline@glidos.net \
    --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