From: Paul Gardiner <osronline@glidos.net>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hcid.conf seemingly ignored
Date: Thu, 21 Dec 2006 23:13:29 +0000 [thread overview]
Message-ID: <458B1519.6020800@glidos.net> (raw)
In-Reply-To: <4589BBF5.5090604@glidos.net>
Paul Gardiner wrote:
> Stefan Seyfried wrote:
>>>> If the procedure explained in /usr/share/doc/packages/bluez-utils/README.dund
>>>> does not work, please file a bugreport at bugzilla.novell.com so i can update
>>>> the documentation.
>>> 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:
>
> Dec 20 22:15:22 plonty dund[13620]: Accept failed. Interrupted system
> call(4)
> Dec 20 22:15:22 plonty pand[13617]: Accept failed. Interrupted system
> call(4)
> Dec 20 22:16:58 plonty dund[13730]: Accept failed. Interrupted system
> call(4)
> Dec 20 22:16:58 plonty pand[13727]: Accept failed. Interrupted system
> call(4)
>
>
> Could that be anything to do with it.
I've since realised that these warnings are just part of bluez shutting
down, so nothing to do with my problem.
> I added the option "debug" to /etc/ppp/peers/dun, but I didn't
> see any new output from that.
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.
-------------------------------------------------------------------------
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
next prev parent reply other threads:[~2006-12-21 23:13 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 [this message]
2006-12-22 11:06 ` Stefan Seyfried
2006-12-22 11:18 ` Paul Gardiner
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=458B1519.6020800@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