All of lore.kernel.org
 help / color / mirror / Atom feed
From: Denis Kenzior <denkenz@gmail.com>
To: Bruno Dantas <dantas@airpost.net>,
	James Prestwood <prestwoj@gmail.com>,
	iwd@lists.linux.dev
Subject: Re: iwd release 1.30 onwards cannot find available networks
Date: Mon, 12 Dec 2022 16:00:21 -0600	[thread overview]
Message-ID: <0bd53fcf-7367-46de-0567-e4e0fa8cca09@gmail.com> (raw)
In-Reply-To: <5056edba-fa23-b133-73ac-f8daa483cf23@airpost.net>

Hi Bruno,

On 12/12/22 13:27, Bruno Dantas wrote:
> Hi, Denis.
> 
>> And can you elaborate what 'hangs' mean?  If there are no networks, then you should see a "No networks available" print or something similar.
> 
> By "hangs" I mean that when I run "station wlan0 scan", the command never returns. I work in a hospital office where there are _many_ wifi networks within range, including ones with strong signal.

Gotcha.  Having a hang in 'station wlan0 scan' makes sense since it is an async 
method.  The get-networks method is synchronous so it shouldn't ever 'hang'.

Please try

[PATCH] scan: remove early supported check for 6ghz in wiphy watch

that James just sent and see if it fixes your issue.

Regards,
-Denis

  parent reply	other threads:[~2022-12-12 22:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12 16:54 iwd release 1.30 onwards cannot find available networks Bruno Dantas
2022-12-12 17:22 ` James Prestwood
2022-12-12 17:52   ` Bruno Dantas
2022-12-12 18:39     ` Paul Menzel
2022-12-12 18:58       ` Bruno Dantas
2022-12-12 19:01     ` Denis Kenzior
2022-12-12 19:27       ` Bruno Dantas
2022-12-12 19:38         ` Alvin Šipraga
2022-12-12 20:07           ` Bruno Dantas
2022-12-13 14:42           ` Bruno Dantas
2022-12-13 17:23             ` James Prestwood
2022-12-13 20:15               ` Bruno Dantas
2022-12-13 20:33                 ` James Prestwood
2022-12-13 21:02                   ` Bruno Dantas
2022-12-12 22:00         ` Denis Kenzior [this message]
2022-12-12 23:31           ` Bruno Dantas

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=0bd53fcf-7367-46de-0567-e4e0fa8cca09@gmail.com \
    --to=denkenz@gmail.com \
    --cc=dantas@airpost.net \
    --cc=iwd@lists.linux.dev \
    --cc=prestwoj@gmail.com \
    /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.