public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Odysseus Flappington" <deriziotis@gmail.com>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Bluetooth dongle not reconnecting
Date: Thu, 24 Jan 2008 11:22:48 +0000	[thread overview]
Message-ID: <5eee8c670801240322y265a6838we5de45ca22ba0501@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 3543 bytes --]

I posted this last week sometime, but here it is again in the hopes my
desperation will yield results.

I can pair my bluetooth mouse and keyboard perfectly fine, but after
rebooting, hidd doesn't re-establish the connections. I've tried
re-connecting manually, but the only way to get them working again, is by
re-pairing. I've tested other dongles which re-connect perfectly fine.

My dmesg displays the following messages whenever I move the mouse:

[  169.162683] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.173697] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.185666] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.196648] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.207684] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.218657] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.230635] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.231635] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.241628] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.252655] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.263642] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.275601] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42
[  169.286629] hci_acldata_packet: hci0 ACL packet for unknown connection
handle 42

And my hcidump -X -V displays the following:

> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 03 fd 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 03 fd 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 01 00 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 02 fe 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 01 ff 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 02 ff 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 01 00 00                                 ......
> ACL data: handle 42 flags 0x02 dlen 10
    L2CAP(d): cid 0x0041 len 6 [psm 0]
      0000: a1 02 00 01 00 00                                 ......
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 42 mode 0x00 interval 0
    Mode: Active
> HCI Event: Mode Change (0x14) plen 6
    status 0x00 handle 42 mode 0x02 interval 112
    Mode: Sniff

If I do a sudo hidd --connect [MAC] I get the following:

Can't get device information: Operation already in progress

I'm using an Edimax EB-DGC2 USB 2.0 bluetooth dongle running on Ubuntu
7.10with bluez-utils
3.19-0ubuntu3.

This is a shame, since the Edimax manufacturer's website actually advertises
linux compatibility (
http://www.edimax.co.uk/en/produce_detail.php?pd_id=127&pl1_id=13&pl2_id=43),
but state they don't develop or maintain the drivers. Perhaps they can be
contacted to help provide specs to solve the problem?

Many thanks,
Alex

[-- Attachment #1.2: Type: text/html, Size: 5715 bytes --]

[-- Attachment #2: Type: text/plain, Size: 228 bytes --]

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

             reply	other threads:[~2008-01-24 11:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 11:22 Odysseus Flappington [this message]
2008-01-28 12:07 ` [Bluez-users] Bluetooth dongle not reconnecting Odysseus Flappington
  -- strict thread matches above, loose matches on Subject: below --
2008-01-19 19:36 Odysseus Flappington

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=5eee8c670801240322y265a6838we5de45ca22ba0501@mail.gmail.com \
    --to=deriziotis@gmail.com \
    --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