Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Cavallari <nicolas.cavallari@green-communications.fr>
To: buildroot@busybox.net
Subject: [Buildroot] wpa_supplicant not starting correctly
Date: Fri, 27 Mar 2015 17:21:36 +0100	[thread overview]
Message-ID: <55158390.2020102@green-communications.fr> (raw)
In-Reply-To: <55131639.9040408@gmail.com>

On 25/03/2015 21:10, Alexey Mednyy wrote:
> Hello there,
> 
> I've got configuration with eudev,dbus and  busybox init.
> Previously everything worked fine, but now wpa_supplicant not starting.
> and I see this in /var/log/messages :
> 
> Mar 25 22:56:25 hostname daemon.notice dbus[120]: [system] Activating
> service name='fi.w1.wpa_supplicant1' (using servicehelper)
> Mar 25 22:56:26 hostname daemon.info init: starting pideudev 146, tty
> '/dev/ttyS0': '/sbin/getty -L  ttyS0 0 vt100 '
> Mar 25 22:56:26 hostname daemon.notice dbus[120]: [system] Activated
> service 'fi.w1.wpa_supplicant1' failed: Failed to execute program
> fi.w1.wpa_supplicant1: Success
> 
> I'm not an expert in dbus, so asking for help what causes such problem?
> I think before some recent commit wpa_supplicant started by init script
> not by dbus is it true?

If you use network-manager or something managing wpa_supplicant, then
they have always relied on D-Bus activation to start wpa_supplicant.

You seem to not run systemd, so the standard D-Bus activation should
work.  Check that you can run wpa_supplicant normally (i.e. by running
it with the same parameters as specified in
/usr/share/dbus-1/system-services/fi.w1.wpa_supplicant1.service ).  If
it does, there is another problem.

My current supposition is that your wpa_supplicant was built without
D-Bus support.

      reply	other threads:[~2015-03-27 16:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-25 20:10 [Buildroot] wpa_supplicant not starting correctly Alexey Mednyy
2015-03-27 16:21 ` Nicolas Cavallari [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=55158390.2020102@green-communications.fr \
    --to=nicolas.cavallari@green-communications.fr \
    --cc=buildroot@busybox.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