Return-Path: Message-ID: <4A652C88.3040000@gmail.com> Date: Mon, 20 Jul 2009 19:48:40 -0700 From: "Justin P. Mattock" MIME-Version: 1.0 To: Mario Limonciello CC: linux-bluetooth@vger.kernel.org Subject: Re: bluetooth works with udev-145 but had some weired issues with it References: <4A648DDF.7060303@dell.com> In-Reply-To: <4A648DDF.7060303@dell.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Sender: linux-bluetooth-owner@vger.kernel.org List-ID: Mario Limonciello wrote: > 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. > Don't mean to be latent on the response. Anyways I tried adding udevadm trigger --subsystem-match=bluetooth to init.d/udev but the system fails hard(livecd to recover), but adding the same entry to another init script after udev has done its job results in a successful activation. So I think it's safe to safe this is the same issue ubuntu was having. Justin P. Mattock