From: "Dave Young" <hidave.darkstar@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] hciconfig hci0 reset bug
Date: Mon, 3 Mar 2008 09:24:25 +0800 [thread overview]
Message-ID: <a8e1da0803021724h654f65ceif24b2035dc94a5ec@mail.gmail.com> (raw)
In-Reply-To: <a8e1da0803021721m3145bc7fpd896760d4bed7d97@mail.gmail.com>
On Mon, Mar 3, 2008 at 9:21 AM, Dave Young <hidave.darkstar@gmail.com> wrote:
> On Fri, Feb 29, 2008 at 6:51 AM, Odysseus Flappington
> <deriziotis@gmail.com> wrote:
>
>
> > So, it turns out that in order for any external usb bluetooth adapters
> > to re-connect to paired input devices on reboot, you need to issue an
> > 'hciconfig hci0 reset' command after rebooting in order to reconnect.
> >
> > More info can be found in bug #133690 on Launchpad
> > (https://bugs.launchpad.net/ubuntu/+source/bluez-utils/+bug/133690).
> >
> > This bug isn't Ubuntu-specific since I have reproduced in Fedora 8, so
> > I'm posting here.
> >
> > Simply adding 'hciconfig hci0 reset' in /etc/default/bluetooth in
> > source would solve this bug. Is this a reasonable solution?
> >
> > What is required in order to get a fix implemented?
Sorry for previous blank reply.
For your problem, if you don't want to patch kernel you can also try
load the bluetooth module with parameter "reset=1"
Could you send the lsusb output?
Regards
dave
-------------------------------------------------------------------------
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/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-03-03 1:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 22:51 [Bluez-users] hciconfig hci0 reset bug Odysseus Flappington
2008-03-03 1:21 ` Dave Young
2008-03-03 1:24 ` Dave Young [this message]
2008-03-03 11:35 ` Odysseus Flappington
2008-03-03 22:19 ` Odysseus Flappington
2008-03-17 12:28 ` Odysseus Flappington
2008-03-18 7:14 ` Dave Young
2008-03-20 17:19 ` Odysseus Flappington
2008-03-22 0:29 ` Dave Young
2008-03-26 16:22 ` Marcel Holtmann
2008-04-04 8:58 ` Odysseus Flappington
2008-07-21 20:53 ` Odysseus Flappington
2008-07-22 5:02 ` Dave Young
2008-03-26 12:50 ` Peter Stephenson
2008-03-26 16:24 ` 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=a8e1da0803021724h654f65ceif24b2035dc94a5ec@mail.gmail.com \
--to=hidave.darkstar@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