From: Marcel Holtmann <marcel@holtmann.org>
To: KEYUR DESAI <keyurde@nortelnetworks.com>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Connection failed error (110)
Date: Mon, 25 Oct 2004 05:57:39 +0200 [thread overview]
Message-ID: <1098676659.6465.72.camel@pegasus> (raw)
In-Reply-To: <E337F6C8A5154F4C8E95349BA276D63008FBB4@zrtphxm0.corp.nortel.com>
Hi Keyur,
> Here is my current scenario
>=20
> =20
>=20
> Hardware: Belkin Dongle
>=20
> O.S.: Fedora Core 2 Kernel 2.6.5-1.358
>=20
> =20
>=20
> =20
>=20
> Here is the problem:
>=20
> =20
>=20
> When I do=20
>=20
> #hciconfig hci0 up The device works fine.
>=20
> =20
>=20
> However on doing a hciconfig hci0 down followed by a hciconfig hci0
> up . The dongle does not work.
>=20
> It gives an error=20
>=20
> Can=A2t init device hci0. Connection timed out (110).
what kind of dongle is this (hciconfig -a) and why don't you update to
the latest Linux kernel and BlueZ utils first?
Regards
Marcel
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-10-25 3:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-25 3:44 [Bluez-users] Connection failed error (110) KEYUR DESAI
2004-10-25 3:57 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-25 5:41 KEYUR DESAI
2004-10-25 8:49 ` Marcel Holtmann
[not found] <E337F6C8A5154F4C8E95349BA276D63008FBC4@zrtphxm0.corp.nortel.com>
2004-11-03 1:47 ` 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=1098676659.6465.72.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=keyurde@nortelnetworks.com \
/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