From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] Zire72 ppp connection problem
Date: Mon, 23 May 2005 12:13:18 +0200 [thread overview]
Message-ID: <1116843198.30044.43.camel@pegasus> (raw)
In-Reply-To: <42908012.5010103@tiscali.it>
Hi Luca,
> i'm tryng to connect my zire72 to a Logitech hub, the one that comes=20
> with the Dinovo Desktop Kit Wireless...
> I'm using Suse9.2, and i have installed all the Bluez pakages that i=20
> find with Yast.
> I think that now my hub works fine, my mouse and my Keyboard works fine=
...
> My PDA find my desktop, but when i try to connect my pda say "cable=20
> problems", and Kde Bemused Server log says a lot of messages like:
> }"=E2=80=A1:... Unknown Command (}"=E2=80=A1:)... done
> or
> ~=C2=BF3=08... Unknown Command (~=C2=BF3=08)... done
> or
> }"3,... Unknown Command (}"3,)... done
>=20
> Is there a difference between the protocols used by the PDA and the des=
ktop?
> I can't understand where is the problem, i hope someone can help me...
the KDE Bemused Server is not our business. Talk to the KDE Bluetooth
guys, but you may first update to SuSE 9.3.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2005-05-23 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-22 12:50 [Bluez-users] Zire72 ppp connection problem tibe
2005-05-22 12:59 ` tibe
2005-05-23 10:13 ` 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=1116843198.30044.43.camel@pegasus \
--to=marcel@holtmann.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.