Linux bluetooth development
 help / color / mirror / Atom feed
From: Ciro Scognamiglio <moray@libero.it>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] problems with epox dg02
Date: Thu, 11 Sep 2003 15:00:58 +0200	[thread overview]
Message-ID: <20030911130058.GD4654@libero.it> (raw)
In-Reply-To: <1063204541.14708.17.camel@z439-033-17.raab-heim.uni-linz.ac.at>

On Wed 10 Sep 03 16:35 +0200, Martin MAURER wrote:

> Connecting to my mobile phone works well,
> but when I try to use pan networking (notebook to desktop computer, both
> debian linux) I get an 
> 
> hci_acl_tx_to: hci0 ACL tx timeout
> hci_acl_tx_to: hci0 killing stalled ACL connection E0:C3:80:61:04:00
> 
> error when i try to transfer a lot of data via this connection after a
> few seconds.

This seems like my problem with the DBT-120 usb dongle I have, but:
hcidump doesn't give a clue of what is happening
and I use the serial profile to estabilish a ppp connection with the SE p800

> 
> sometimes with zero packets, and sometimes without.
> sometimes with SCO voice support, and sometimes without.

At the moment I am using the 2.4.22-mh1 and tryed enabling both
zero packets and SCO vocie. If disabled it seems to work better,
i.e. I don't have to unplug the dongle to get the connection
work again, but just kill pppd and relaunch it.

BTW, I would also like to see if it hppens also with the obex push
profile, but how? I mean, what is the best app to use to transfer
a file using BT?

ussp-push doesn't work for me...also, do I have to bind or connect an
rfcomm port to the obex push profile before trasfering files?

last ~10 rows of hcidump output before the connection dies.

If someone could help (Marcel?) I could send the whole dump as soon as I get
the connection up (it doesn't last a lot, some times just a few seconds)

> ACL data: handle 0x002a flags 0x02 dlen 34
< ACL data: handle 0x002a flags 0x02 dlen 192
< ACL data: handle 0x002a flags 0x01 dlen 67
    L2CAP(d): cid 0x42 len 255 [psm 0]
< ACL data: handle 0x002a flags 0x02 dlen 192
< ACL data: handle 0x002a flags 0x01 dlen 67
    L2CAP(d): cid 0x42 len 255 [psm 0]
< ACL data: handle 0x002a flags 0x02 dlen 192
< ACL data: handle 0x002a flags 0x01 dlen 67
    L2CAP(d): cid 0x42 len 255 [psm 0]
< ACL data: handle 0x002a flags 0x02 dlen 21
    L2CAP(d): cid 0x42 len 17 [psm 0]
> ACL data: handle 0x002a flags 0x01 dlen 40
> HCI Event: Number of Completed Packets(0x13) plen 5
> HCI Event: Number of Completed Packets(0x13) plen 5
> HCI Event: Number of Completed Packets(0x13) plen 5

Ciro.


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2003-09-11 13:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-10 14:35 [Bluez-users] problems with epox dg02 Martin MAURER
2003-09-11 13:00 ` Ciro Scognamiglio [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=20030911130058.GD4654@libero.it \
    --to=moray@libero.it \
    --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