From: Pacho Ramos <pachoramos@gmail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: About needing to run "udevadm trigger" to get bluetooth adapter detected at boot
Date: Wed, 04 Jan 2012 23:11:46 +0100 [thread overview]
Message-ID: <1325715106.3277.1.camel@belkin4> (raw)
In-Reply-To: <1325714356.10711.2.camel@belkin4>
El mié, 04-01-2012 a las 22:59 +0100, Pacho Ramos escribió:
> Hello
>
> I would like to know why do we need to run things like:
> udevadm trigger --subsystem-match=bluetooth --action=add
>
> or even simpler:
> udevadm trigger
>
> Manually or using a "bluetooth" init.d script to simply run that or,
> otherwise, bluetooth adapter is not detected. Reading OpenSuSE Changelog
> in their bluez package seems that this is caused because dbus needs to
> be running to get it detected. In that case, I would like to know why
> only bluez looks to be affected by this problem and, also, know if there
> is another way to workaround (or fix) this issue than needing to add a
> bluez init.d script to simply run this
>
> Thanks a lot
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Looks like, on Gentoo, we have an init.d script that runs:
udevadm trigger --type=failed -v
after dbus is running, but looks like running udevadm trigger with
"--type=failed" option won't start bluetoothd... will investigate it a
bit more, sorry for the noise :S
prev parent reply other threads:[~2012-01-04 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 21:59 About needing to run "udevadm trigger" to get bluetooth adapter detected at boot Pacho Ramos
2012-01-04 22:11 ` Pacho Ramos [this message]
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=1325715106.3277.1.camel@belkin4 \
--to=pachoramos@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