All of lore.kernel.org
 help / color / mirror / Atom feed
From: hector@ikatu.com
To: iwd@lists.01.org
Subject: Re: Interface not detected sometimes
Date: Tue, 04 Feb 2020 19:08:47 +0000	[thread overview]
Message-ID: <20200204190847.2820.5022@ml01.vlan13.01.org> (raw)
In-Reply-To: <2e72e05e-7a2a-6058-739e-f88c087b1b72@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 704 bytes --]

Hi Denis,

thanks for your reply.

Yes, I'm using brcmfmac.

I had the EBUSY errors the first time I tried iwd. I got rid of those errors setting "--interfaces wlan0" in iwd.service (I have wlan0 and uap0 interfaces, I think I just need iwd to manage the wlan0, uap0 will be managed by hostapd). After that I didn't get the EBUSY errors anymore, but now I've this "No default interface for wiphy 0" problem.

Applying the 55f9639ee37c commit didn't change the behavior. I mean, I still need to set the "--interfaces wlan0" parameter to avoid the EBUSY errors, and if I set the parameter I still need to sleep some seconds to avoid the "No default interface for wiphy 0" error.

Regards,
Hector

  reply	other threads:[~2020-02-04 19:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-04 14:54 Interface not detected sometimes hector
2020-02-04 14:58 ` hector
2020-02-04 17:06   ` Denis Kenzior
2020-02-04 19:08     ` hector [this message]
2020-02-04 20:45       ` hector
2020-02-04 22:14         ` Denis Kenzior
2020-02-05 12:58           ` hector
2020-02-05 15:00             ` Denis Kenzior
2020-02-05 13:35           ` hector
2020-02-05 15:19             ` Denis Kenzior
2020-02-05 19:28               ` hector
2020-02-06 16:27                 ` Denis Kenzior

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=20200204190847.2820.5022@ml01.vlan13.01.org \
    --to=hector@ikatu.com \
    --cc=iwd@lists.01.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.