From: "Phil Endecott" <spam_from_bluez_users@chezphil.org>
To: <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Apple wireless keyboard
Date: Wed, 23 Apr 2008 20:04:03 +0100 [thread overview]
Message-ID: <1208977443694@dmwebmail.dmwebmail.chezphil.org> (raw)
In-Reply-To: <5eee8c670804220813m351b6d10l57ad21bd34c812f0@mail.gmail.com>
Odysseus Flappington wrote:
> You're probably suffering from the following bug:
>
> https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/79394
>
> Try a 'hciconfig hci0 reset' after restarting and then your keyboard should
> reconnect again.
Thanks for the suggestion. That bug reporter was seeing "UP RUNNING"
but not scanning in the hciconfig output; I am getting "UP RUNNING
PSCAN ISCAN", so I don't think it's the same thing.
On more investigation, it seems that the failure happens after the
keyboard has gone to sleep and I wake it up; I then see this in syslog:
Apr 23 18:09:37 egypt hidd[2856]: New HID device 00:1E:52:F9:60:2C
(Apple Inc. Keyboard)
Apr 23 18:09:37 egypt kernel: input: Apple Inc. Keyboard as /class/input/input13
Apr 23 18:09:37 egypt kernel: usb 3-2: uhci_result_common: failed with
status 440000
Apr 23 18:09:37 egypt kernel: usb 3-2: uhci_result_common: failed with
status 440000
Does anyone know what "status 440000" is? It makes me think that it's
a lower level problem with the USB dongle.
After 30 mins I get this, which is presumably related:
Apr 23 18:39:37 egypt kernel: hci_acl_tx_to: hci0 ACL tx timeout
Apr 23 18:39:37 egypt kernel: hci_acl_tx_to: hci0 killing stalled ACL
connection 2C:60:F9:52:1E:00
Apr 23 18:39:37 egypt kernel: hci_acl_tx_to: hci0 ACL tx timeout
Apr 23 18:39:37 egypt kernel: hci_acl_tx_to: hci0 killing stalled ACL
connection 2C:60:F9:52:1E:00
I can make the keyboard work again by re-plugging the USB dongle and
waking up the keyboard.
Anyway, I am going to try to get a USB bluetooth dongle that has a HID
proxy mode, and hopefully this can all be avoided. If anyone can
suggest a particular brand/model that is known to work in HID proxy
mode, please let me know! Thanks.
Phil.
-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
Don't miss this year's exciting event. There's still time to save $100.
Use priority code J8TL2D2.
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-04-23 19:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 14:58 [Bluez-users] Apple wireless keyboard Phil Endecott
2008-04-22 15:13 ` Odysseus Flappington
2008-04-23 19:04 ` Phil Endecott [this message]
2008-04-23 19:50 ` Odysseus Flappington
2008-04-24 15:32 ` Phil Endecott
2008-04-23 17:25 ` Johan Hedberg
2008-04-24 15:49 ` Phil Endecott
2008-04-24 17:29 ` Johan Hedberg
-- strict thread matches above, loose matches on Subject: below --
2006-07-12 4:07 [Bluez-users] Apple Wireless Keyboard William Voorhees
2006-07-12 23:27 ` Marcel Holtmann
2004-06-11 18:44 [Bluez-users] apple wireless keyboard Simone Crippa
2004-06-14 12:31 ` Collin R. Mulliner
2004-06-14 23:29 ` Marcel Holtmann
2004-06-14 16:16 ` Marcel Holtmann
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=1208977443694@dmwebmail.dmwebmail.chezphil.org \
--to=spam_from_bluez_users@chezphil.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).