linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: pacho@condmat1.ciencias.uniovi.es
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Users need to manually run "hid2hci --method dell -v 413c -p 8158 --mode hci" even when udev rule is installed
Date: Sat, 19 Jun 2010 16:55:36 +0100	[thread overview]
Message-ID: <1276962936.13559.143.camel@localhost.localdomain> (raw)
In-Reply-To: <1276959945.16187.0.camel@localhost.localdomain>

On Sat, 2010-06-19 at 17:05 +0200, Pacho Ramos wrote:
> El sáb, 24-04-2010 a las 20:42 +0200, Pacho Ramos escribió:
> > Hello
> > 
> > I would like to ask for help to try to find where could be the problem
> > causing this:
> > http://bugs.gentoo.org/show_bug.cgi?id=315749
> > 
> > Reporter seems to need to manually run:
> > hid2hci --method dell -v 413c -p 8158 --mode hci
> > 
> > to get bluetooth switched to hci mode.
> > 
> > I don't understand why he needs to run it since involved udev rule file
> > seems to be properly installed.
> > 
> > Could anybody help us on this please?
> > 
> > Thanks a lot
> 
> This is still affecting to some users, can anybody help us? At least,
> how could we check if udev is, at least, trying to execute hid2hci from
> 97-bluetooth-hid2hci.rules file?

2 things.

This is already fixed in udev upstream, and hid2hci doesn't live in
bluez, but in udev now.

This was also fixed recently in Fedora 14.

Cheers


  reply	other threads:[~2010-06-19 15:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 18:42 Users need to manually run "hid2hci --method dell -v 413c -p 8158 --mode hci" even when udev rule is installed Pacho Ramos
2010-06-19 15:05 ` Pacho Ramos
2010-06-19 15:55   ` Bastien Nocera [this message]
2010-06-19 18:59     ` Pacho Ramos
2010-06-24 14:34       ` Bastien Nocera
2010-06-24 15:01         ` Pacho Ramos

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=1276962936.13559.143.camel@localhost.localdomain \
    --to=hadess@hadess.net \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=pacho@condmat1.ciencias.uniovi.es \
    /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).