From: Mario Limonciello <mario_limonciello@dell.com>
To: Justin Mattock <justinmattock@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: bluetooth works with udev-145 but had some weired issues with it
Date: Mon, 20 Jul 2009 10:31:43 -0500 [thread overview]
Message-ID: <4A648DDF.7060303@dell.com> (raw)
In-Reply-To: <dd18b0c30907192036r477c9637x450562df605294e8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 917 bytes --]
Hi Justin:
Justin Mattock wrote:
> For some reason in rules.d
> for the permission setting:
>
> #ACTION=="add", SUBSYSTEM=="bluetooth", RUN+="/usr/sbin/bluetoothd --udev"
> to
> RUN+="/usr/sbin/bluetoothd --udev"
> gets this working for me.
> prior to this, udev just would not activate
> bluetoothd
> Anyways thought it would be good to let people know.
>
>
I'm wondering if you are seeing something similar that was happening on
Ubuntu when getting bluez-4.45 added in where the daemon failed to start
upon bootup but works fine later (eg if you hotplug the device).
It turned out that dbus wasn't up and running at the time udev triggered
all devices early in the boot.
The easiest solution was to run:
udevadm trigger --subsystem-match=bluetooth
later on, during an init script or similar.
--
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]
next prev parent reply other threads:[~2009-07-20 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-20 3:36 bluetooth works with udev-145 but had some weired issues with it Justin Mattock
2009-07-20 7:14 ` Marcel Holtmann
2009-07-20 7:41 ` Justin P. Mattock
2009-07-20 16:44 ` Kay Sievers
2009-07-20 15:31 ` Mario Limonciello [this message]
2009-07-20 16:52 ` Justin P. Mattock
2009-07-21 2:48 ` Justin P. Mattock
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=4A648DDF.7060303@dell.com \
--to=mario_limonciello@dell.com \
--cc=justinmattock@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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