From: Marcel Holtmann <marcel@holtmann.org>
To: pat <pat@xvalheru.org>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] newbe: rfcomm_recv_frame: bad checksum in packet
Date: Sun, 12 Sep 2004 16:00:03 +0200 [thread overview]
Message-ID: <1094997603.5695.9.camel@pegasus> (raw)
In-Reply-To: <20040910155027.M37511@xvalheru.org>
Hi Pat,
> I have installed the BlueZ to my laptop because I want to use GPRT through the
> Bluetooth. I have scripts and the rest configured and I'm able to connect and
> upload some data, but within 30 seconds the connection go down. The system log
> contains only this line "rfcomm_recv_frame: bad checksum in packet". Could
> someone help me ???
actually this should never happen, because the underlaying L2CAP layer
is reliable. Try to use the latest 2.6 kernel and run "hcidump -X" as
root and show the output to us.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2004-09-12 14:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-10 15:57 [Bluez-users] newbe: rfcomm_recv_frame: bad checksum in packet pat
2004-09-12 14:00 ` Marcel Holtmann [this message]
2004-09-13 15:20 ` pat
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=1094997603.5695.9.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
--cc=pat@xvalheru.org \
/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