From: Marcel Holtmann <marcel@holtmann.org>
To: rcox27@triad.rr.com
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Connection dropped or cannot connect (Solved!!!!!!)
Date: Sun, 11 Apr 2004 18:37:42 +0200 [thread overview]
Message-ID: <1081701462.5398.54.camel@pegasus> (raw)
In-Reply-To: <200404111146.47402.conardcox@earthlink.net>
Hi Richard,
> Seems I spoke too soon 8^( As soon as I sent this, it disconnected again. I
> should have waited a bit longer to post I suppose. Nevertheless, for some
> reason, it went much longer without this error this time....I'll keep trying.
I really think that this an USB problem. You should test the 2.4.26-rc2
or switch to the latest 2.6.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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:[~2004-04-11 16:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-10 1:10 [Bluez-users] Connection dropped or cannot connect Jean-Pierre Lord
2004-04-10 10:28 ` Marcel Holtmann
2004-04-16 1:17 ` Jean-Pierre Lord
2004-04-10 20:42 ` Richard Cox
2004-04-10 21:09 ` Marcel Holtmann
2004-04-10 21:15 ` Richard Cox
2004-04-10 21:25 ` Marcel Holtmann
2004-04-10 21:31 ` Richard Cox
2004-04-11 15:38 ` [Bluez-users] Connection dropped or cannot connect (Solved!!!!!!) Richard Cox
2004-04-11 15:46 ` Richard Cox
2004-04-11 16:37 ` Marcel Holtmann [this message]
2004-04-11 19:54 ` Richard Cox
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=1081701462.5398.54.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=rcox27@triad.rr.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